Close-out, handover, defects and warrantiesBuildPath management templateSometimes requiredHandover and close-outProject-controlledReviewed 11 August 2026

Lessons learned template

Use the Lessons learned template to prove that completion, authority, defect, as-built, warranty, operation and archive obligations are closed before handover or settlement. It is a control aid, not a substitute for the current official, contractual or professionally prepared document where one governs.

Who initiates it

Project manager, contract administrator or handover lead

Who fills it out

Client/developer, project manager or delegated document owner

Who reviews it

The project manager and the person with technical, contractual or commercial authority for the subject

Who approves it

Client/developer and the person authorised for the relevant completion/consent/contract decision

Applicability

Use from pre-practical-completion through the defects/warranty period and tailor it to the signed contract, consent and client/buyer requirements.

Who needs it

The project owner and the person controlling handover and close-out, including each reviewer, approver or recipient named by the live project process.

Who signs it

Only the person with the authority or professional competence required by the source document, contract, insurer, lender or authority process.

When it is needed

Prepare before the related handover and close-out decision or activity. Update it when scope, revision, cost, programme, responsibility, evidence or approval status changes.

Information needed

Completion/defect status and objective acceptance evidence
CCC, producer/trade certificates and as-builts
Warranties, manuals, keys, training, final account and archive

Where to find the information

Contract completion requirements and inspection records
Council/consultant/trade close-out records
Supplier warranties, manuals, as-builts and client acceptance

Step-by-step

How to prepare, review and file it

01Confirm whether this record applies to the project and who has authority to prepare, review, sign, submit and approve it.
02Download or open the current official form or source requirements when an authority, insurer, lender or contract controls the format.
03Gather the latest controlled source documents and confirm their revisions before entering information.
04Complete every field using project-specific facts; mark not applicable with a reason and clearly label unverified assumptions.
05Cross-check names, addresses, legal description, consent numbers, dates, values, drawing references, policy details and attachments.
06Have the appropriate project owner and qualified adviser review technical, legal, financial, insurance, safety and compliance content.
07Submit or issue it through the required channel, save proof of issue and record any response or RFI.
08Track actions to close-out, then save the final signed/accepted record and attachments in the controlled project file.

Where to submit or store it

Keep as a controlled internal project record and issue by the contract or project communication method when another party must review, approve or act on it.

Submission channels

Controlled project document system
Contract communication or document transmittal
Email only where the project communication plan permits it

Documents to attach

Current drawings, specifications, reports or approval documents referenced in the record
Marked-up plans, photographs, quotes, correspondence, inspection results or certificates that support the entries
Required signatures, declarations, schedules, evidence or authority-generated receipt/acknowledgement

What happens after issue or submission

Verify completeness rather than file presence alone, issue the indexed pack, obtain acknowledgement and retain an immutable project archive plus residual-action tracker.

Controlled storage

Save the final record and supporting evidence in the controlled project document system, with the revision, issue status and related workspace record.

Source applicability

Confirm the project stage, contract, consent, consultant scope and actual site circumstances before use.

Common mistakes

Using an old template, superseded drawing, expired certificate or outdated authority process.
Copying generic wording without checking the specific property, consent, contract, policy or work package.
Leaving ownership, dates, revision, status, attachments or close-out evidence unclear.
Treating an internal checklist as an official authority, insurance, lender, legal or professional form.

Red flags and stop points

Required information conflicts between title, consented plans, consultant reports, contracts or site conditions.
A person is being asked to sign, certify or approve outside their authority or competence.
Work, purchase, payment, submission or occupation is proposed before a required approval or insurance confirmation is recorded.
Insufficient data to verify — confirm against the current consented drawings, specifications, Auckland Council requirements, Auckland Unitary Plan, NZ Building Code, relevant NZ Standard, consultant advice, manufacturer instructions, insurance broker, insurer, lender, lawyer, accountant or project contract.

Connected project controls

Related quote package: Relevant consultant, authority, supplier or trade package
Related checklist items: Handover and close-out; Prepare and review Lessons learned template; File evidence and close outstanding actions
Related software tool: Handover Pack Builder / Defects Tracker
Example completed version: Example: Lessons learned template for 12 Example Road, Auckland; prepared by the named project owner; current source documents listed by number and revision; assumptions marked; two actions assigned with dates; reviewed by the appropriate adviser; final version and evidence filed in the controlled project record.

Connected Workspace record

Handover Pack Builder / Defects Tracker

Open Workspace area

Blank editable template

Complete a project-specific record

Free · saved in this browser

1. Lessons learned template: identity and statusEnter the controlled reference, revision, status, prepared/reviewed dates and exact project/work area.Where this information comes from: Project document register, project details and the current source process2. Deliverable and requirementList each completion item, source requirement and responsible provider.Where this information comes from: Contract, consent and handover index3. Status and dependencyRecord missing/received/reviewed/accepted, due date and affected handover/settlement dependency.Where this information comes from: Close-out tracker and programme4. Evidence and acceptanceLink the exact certificate, photo, as-built, warranty or signed acceptance.Where this information comes from: Controlled document/evidence system5. Residual obligationRecord defects-period/warranty owner, expiry, access and unresolved actions.Where this information comes from: Defect and warranty registers6. Actions, owner and deadlineAssign every missing, failed, conditional or conflicting item to one named owner and decision deadline.Where this information comes from: Issue, decision, responsibility and programme records7. Review, approval and close-outRecord reviewer/approver authority, outcome, conditions, linked evidence and final controlled location.Where this information comes from: Authority register, signed/portal response and close-out evidence

BuildPath NZ is an educational guide and project-management resource only. It does not replace advice from Auckland Council, a planner, architect, engineer, surveyor, quantity surveyor, lawyer, accountant, lender, insurer, insurance broker, WorkSafe, Watercare, utility provider, building consent authority or other qualified professional.

Open connected workspace module

Verification

Source / where to check

Use current official information and the controlled documents for the actual project.

Project-controlled documents

Use the current project brief, approval authorities, issued drawings, specifications, contracts, consultant reports, programme, correspondence and controlled registers.

Relevant professional advice

Planner, surveyor, architect, engineer, quantity surveyor, lawyer, accountant, lender, valuer, real estate agent, and other project specialists must confirm site-specific decisions.

Project-specific consented documents and professional advice override generic guidance.

Educational resource and verification warning

Insufficient data to verify — confirm against the current consented drawings, specifications, Auckland Council requirements, Auckland Unitary Plan, NZ Building Code, relevant NZ Standard, consultant advice, manufacturer instructions, insurance broker, insurer, lender, lawyer, accountant or project contract.