What documentation is handed over at completion?

The building is the obvious deliverable. The documentation is the one the client uses every day for the next thirty years.

What the package contains

**Operation and maintenance manuals** for every installed system, with the manufacturer's data, the maintenance schedules and the servicing requirements.

**As-built drawings** showing what was actually built, including the service positions and any changes made during construction. Not the tender drawings.

**Certificates and compliance documents.** Electrical certificates of compliant work, fire safety certification, structural certifications, waterproofing certificates, and the occupation certificate where one applies.

**Warranties.** The manufacturer warranties on installed products and equipment, with their start dates and their conditions, alongside the contractor's own defects obligation.

**Test and commissioning results.** Compaction testing, pressure testing, electrical testing, system commissioning, whatever the works generated.

**Asset information.** What was installed, where it is, what it is, so it can be added to the client's asset register.

**Spares and keys.** Attic stock of finishes, spare keys, access codes, and the security handover.

Why it is assembled during the project

A documentation package compiled at the end is a documentation package with gaps.

Certificates are collected as each trade completes. Test results are filed when the test is done. As-built information is marked up as changes are made rather than reconstructed from memory afterwards.

Everything is held in the Integrated Management System through the project, so the handover package is a compilation rather than an investigation.

The alternative is chasing a subcontractor for a certificate three months after they left the site, which is exactly how handovers get delayed.

What the client actually needs it for

**Statutory obligations.** A building owner needs its fire safety certification to issue the annual fire safety statement. Without it, the building is non-compliant regardless of how well it was built.

**Maintenance.** A facilities team cannot maintain equipment it has no manual for, and cannot service it at the right interval without the schedule.

**Warranty claims.** A warranty is only usable if the documentation establishing it can be found.

**The next project.** The as-built information is what stops the next contractor guessing where the services are, which is where service location problems come from in the first place.

Format follows the client

Government and institutional clients frequently specify the format, the structure and the delivery method for the handover package.

The NSW Department of Education, councils and the other authorities each have their own requirements, and meeting them is part of the contract rather than a preference.

Delivering the right information in the wrong format still delays the handover.

It is not the end of the obligation

Handover starts the defects liability period, it does not close the project.

The documentation is what the client relies on during that period and long after it, and it is the part of the project that stays useful once everybody involved in building it has moved on.

Discuss what a handover package would include.