The installed-asset register is the list of everything your firm actually put into a client's home or office. It is built automatically when a project is handed over, and it is the backbone that warranty cover, service tickets and preventive visits all hang off.
What the register is
Every project that reaches handover carries a register of its installed assets, one record per line of work. A modular kitchen, a set of wardrobes, a false ceiling, the lighting: each becomes an asset you can look up, warrant and service for years after the site closes. Without this list a handed-over project would track nothing, and the first warranty call would start from a blank page.
- It is the single place that answers "what did we install here, and is it still under cover?"
- Warranty policies, service tickets and preventive visits are all linked to an asset, not floated loose.
- It reuses the same customer and project records as the rest of the pipeline, so the account has one continuous history.
Built automatically from the deal BOQ
The moment a project's stage becomes Handover Completed, Panzo reads the deal's BOQ and creates an installed-asset record for each line, in the background. You do not run a separate "generate assets" step, and there is nothing to forget. The process is idempotent: completing or re-completing a handover never produces duplicate assets.
Panzo fills in only what it can stand behind. Brand, OEM, model and serial number are left blank, because the BOQ does not carry them, and a guess in a warranty record helps no one. You complete those fields by hand where you know them. At the same time Panzo attempts warranty activation on a best-effort basis, so an aftercare hiccup can never block or reverse the handover itself.
Note
Warranty policy assignment stays manual
Completing the register after handover
Complete the handover
Reach the Handover Completed stage as usual. The installed assets are created from the deal BOQ on the spot.Fill in the make and serial
Open the project's aftercare assets and add brand, OEM, model and serial number where you know them, so a future claim has the real detail.Assign a warranty policy
Follow the handover nudge to attach a warranty policy to the relevant assets or categories.Let activation apply the cover
Activation sets the cover live and derives status from the activation and expiry dates, so warranty state is always current without any nightly job.
What each asset holds
| Field | What it means |
|---|---|
| Source line | The deal BOQ line the asset was created from, kept as the origin of the record. |
| Brand / OEM / model / serial | Created blank; you fill these in from the actual product installed. |
| Warranty policy | The versioned policy you assign, which activation then makes live. |
| Cover status | Derived from activation and expiry dates: active, expired or not yet activated. |
| Preventive entitlements | The scheduled service windows (for example four quarterly visits in year one) tied to the asset. |
Key takeaways
- Installed assets are generated automatically from the deal BOQ when a project is handed over, with no manual generate step.
- Brand, OEM, model and serial are created blank for you to fill, because Panzo will not guess them.
- Assigning a warranty policy stays a deliberate manual step; activation then applies the cover and derives status from dates.
- The register is the anchor for warranty, service tickets and preventive visits across the life of the account.