The Inherited Project: Ten Tests for a Handover Pack That Earns Its Signature
Photo: UK facilities manager reviewing building handover documents and asset register in plant room, via facts.net
Completion is not the finish line
Practical completion is often treated as the finish line. The certificate is signed, the ceremony is held and the project team moves on. For the people who inherit the building, the transition has only just begun. If the facilities manager cannot find the isolation valve, if the warranty register is incomplete or if the training amounted to a single walkthrough, value is already leaking out of the project.
The handover pack should be written for its inheritors, not for the project file. In UK commercial projects, JCT and NEC4 provide mechanisms for completion, defects and final certificates, but they do not guarantee operational readiness. The Building Safety Act 2022 and the golden thread have raised the stakes for information quality. The practical test remains simple: can the receiving team operate, maintain and repair the asset without calling the project team every week?
Why the gap persists
Project teams are measured on delivery. Operations teams are often brought in late. Documentation is assembled at the end, when the people with the best knowledge are already looking at the next job. Training becomes generic. Defects are logged as promises rather than owned actions. The result is a handover pack that exists in form but not in function.
Ten tests for a handover pack
-
The asset register matches physical reality. Every significant item should have a unique identifier, location, serial number, warranty position, maintenance regime and critical spares note. A desk-based register is not enough. Someone should walk the building and verify it.
-
Warranties and guarantees can be enforced. Dates, scope, exclusions, assignability and contact routes should be recorded in one place. A bundle of manufacturer certificates is not a warranty register.
-
O&M manuals are written for operators. They should explain isolation points, fault-finding, reset procedures and maintenance intervals in plain language. Manufacturer brochures alone rarely help at 2am.
-
Training is role-based and evidenced. Attendance records, competence checks, recordings and refresher arrangements should be in the pack. A single site walkthrough is not training.
-
Spare parts and consumables are scheduled. The receiving team needs lead times, suppliers, storage requirements and minimum stock levels. Otherwise a minor failure becomes a long shutdown.
-
The defects register has owners and dates. Each item should have evidence, access arrangements, a target close-out date and an escalation route. A list of unresolved promises is not a defects register.
-
The statutory and safety file is complete. Fire strategy, asbestos information, electrical and gas records, water hygiene and the CDM health and safety file should be present and usable. Where the golden thread applies, the information should be structured and retrievable, not buried in a folder.
-
Commissioning and test data are available. Results, settings, witness records and seasonal or load testing should show that systems perform as designed. A commissioning sheet with blanks is a warning sign.
-
Contacts and escalation routes are clear. The pack should say who to call for warranty issues, defects, emergencies and out-of-hours support, with expected response times.
-
The handover passes an operational acceptance test. The receiving team should dry-run the pack: find the asset, isolate the system, locate the spare, raise a defect and trace the warranty. If they cannot, the pack is not ready.
Make the ceremony earn its place
A completion ceremony should follow operational acceptance, not replace it. The operations lead should sign off the handover pack, not only the project director. Handover should be a gate with defined deliverables, not a race to the final certificate.
The contract can help. Define the handover deliverables and acceptance criteria clearly. Require operations input during commissioning, not after it. Name a handover manager. Track open items to closure. Where appropriate, link retention release or final payment milestones to handover acceptance rather than to the ceremony itself.
The value case
A good handover reduces downtime, energy waste, maintenance cost, safety risk and disputes. A poor one transfers risk to the client and calls it completion. The ten tests above are not bureaucratic extras. They are the difference between an asset that can be run and a file that has to be reinterpreted.
The question is not whether a handover pack exists. It is whether it works for the people who inherit it. Until that test is passed, the ceremony can wait.
