Handover closes a project with evidence, not a checkbox. You move through the closeout stages, clear the snags that matter, capture the client walkthrough, record a real sign-off, and hand the client a branded completion certificate that renders as a PDF.
How handover works in Panzo
Handover walks a project through its closeout stages with genuine gates, so a project cannot be marked delivered before the work backing it is actually done. Every stage move and walkthrough save is written to the audit log with the person who did it, so the closeout is traceable long after the site team has moved on.
- Snag gate. Critical snags surface first, so the urgent defects lead the closeout push.
- Evidence-backed sign-off. Ticking Client Has Signed Off requires a real sign-off document on the project, not just a tick.
- Closed is final. Once a handover reaches closed, Panzo refuses further changes, so a delivered project cannot quietly regress.
- Full audit trail. Each stage change and walkthrough is logged with the actor.
Closing out a project
Open Handover
Go to the project and open its Handover workspace.Clear the snags
Work down the snag list, closing critical defects first. Snags are raised and closed on the project's snag list.Record the walkthrough
Capture the client walkthrough and notes as you step through the finished site together.Record the sign-off
Attach the client sign-off document to the project, then mark the client as signed off. The sign-off cannot be ticked without that document on file.Complete the handover
Advance the project to completed once the checks are met, which sets the completion date and locks the record.
Tip
Snags close first
The completion certificate
The Completion Certificate is a branded, printable document that renders as a PDF. You can preview or download it from the top of the Handover screen. It states the completion date, the client and project, the handover checks that were met, and a per-item warranty table that doubles as a record of what was installed and its cover.
The completion facts are read from the project, not asserted. If the project has not reached completed, the certificate renders with a Draft watermark rather than certifying early. A few fields are left as blanks for you to fill in by hand, because Panzo does not store them: signatory names and designations, the defect-liability period, and a dedicated certificate number (the reference reuses the project code).
Note
Sending the certificate
Handover checks reference
| Check | What it requires |
|---|---|
| Critical snags | Read from the snag list. Clear the critical defects before sign-off. |
| Client sign-off | A sign-off document on the project before the flag can be set. |
| Completion | Advancing to completed, which sets the handover date and locks the record. |
| Warranty summary | A per-item table of installed assets and their cover on the certificate. |
| Audit trail | Every stage move and walkthrough logged with the actor. |
Warranty activation itself is a genuine next step in Aftercare after handover, where installed assets are activated and AMC entitlements begin.
Key takeaways
- Handover closes a project through gated stages, not a single checkbox.
- Sign-off needs a real sign-off document, and a closed handover is final.
- The completion certificate renders as a PDF with the completion date, checks and a warranty table.
- Some certificate fields (signatories, defect-liability period, certificate number) are yours to fill in.
- Every stage move and walkthrough is written to the audit log with the actor.