Warranty in Panzo is a promise you can keep honestly: versioned policies you assign and activate on each installed asset, a status that is always right because it is derived from dates, advisory claim checks, and a first year of preventive service visits kept on schedule. This guide covers all four.
Versioned warranty policies
A warranty policy sets the cover for a category of work: the term, and the pro-rated replacement bands that decide how much of a replacement the customer bears as cover ages. Policies are versioned, so improving next quarter's terms never rewrites the promise made to a customer who was covered under an earlier version. You manage policies in Control Panel alongside the rest of the After Care settings.
- Each policy version records its term and pro-ration bands.
- Assigning a policy to an asset is a deliberate step, there is no default policy-per-category mapping.
- Activation, done separately, is what actually starts the cover clock.
Assign, then activate on the asset
Cover lives on the installed asset, not on the customer in the abstract. When a project reaches handover completed, Panzo builds the installed-asset register from the deal BOQ automatically. The process is idempotent, and it leaves brand, model and serial blank for an operator to fill rather than guessing them.
Assets arrive from BOQ at handover
On handover completion, the register is generated from the BOQ, and warranty activation is attempted best-effort so an After Care hiccup can never block the handover itself.Assign a policy
Pick the warranty policy version that applies to the asset. This is manual and deliberate.Activate cover
Activation sets the start date. From there the status and expiry are derived from dates, so cover is correct without any nightly job.Fill asset details
Enter the brand, model and serial that were left blank, so the register reads true rather than guessed.
Note
Status is derived, not scheduled
Assessing a claim
When a claim comes in, Panzo is advisory: it surfaces eligibility and raises flags for an authorised person to weigh, and it never auto-rejects a customer. On a service visit, the cover position is pre-filled from the claim and the linked asset so the engineer starts from the right default.
| Flag | What it signals |
|---|---|
| Expired | The cover period has ended on the derived dates. |
| Payment due | There is an outstanding balance on the account. |
| Reported late | The issue was reported well after it is said to have occurred. |
| Possible latent defect | The symptom may point to a hidden defect worth a closer look. |
| Third-party tampering | Signs that someone outside the firm altered the installed work. |
The flags inform a decision; they do not make it. An authorised user decides whether the visit is covered or chargeable.
AMC preventive service
An AMC (annual maintenance) entitlement gives a customer scheduled preventive visits, not just reactive repairs. In year one, that is four quarterly windows, on a cadence an admin sets in Control Panel. Each window is consumed once, when a preventive visit for that quarter is completed, so the entitlement is spent against real work and cannot be double-counted.
| Aspect | How it works |
|---|---|
| Year-one entitlement | Four preventive visits, one per quarter. |
| Cadence | Set by an admin in Control Panel. |
| Consumption | A quarter's window is spent when its preventive visit is completed. |
Key takeaways
- Warranty policies are versioned, so a customer keeps the terms in force when their cover was activated.
- Cover is assigned and then activated on the installed asset; status and pro-ration are derived from dates, with no cron.
- Claim assessment is advisory: Panzo surfaces eligibility and flags, an authorised user decides.
- AMC gives four quarterly preventive windows in year one, each consumed once when its visit is completed.