Construction handover pack guide
A practical structure for making built-asset records easier to find, interpret, and hand over. The example below uses the fictional North Quay Works project; its asset names and document details are illustrative.
Organize around the asset and its status
A reader should be able to identify what a record covers, which version to use, and what remains unresolved.
Group documents by asset or system, then by topic. Give each file a descriptive title and enough identifying detail to distinguish it from related records: asset or system, document type, revision or date where available, and status.
Keep accepted reference material separate from superseded copies and open items. An open item describes a gap or unresolved handoff; it does not make the related information complete or accepted.
What belongs in each pack section
Illustrative structure for North Quay Works; use approved project and owner conventions for actual handovers.
| Pack section | Purpose | Example |
|---|---|---|
| Asset records | Identify assets and their records | Fictional example: AHU-02 asset record, model reference, and location identifier |
| Approved drawings | Make the identified approved issue easy to distinguish | Fictional pump-room drawing: file the approved issue with its revision; mark the earlier issue superseded |
| Operations resources | Group reference material used by the receiving operations team | Fictional example: equipment information and operations references filed under the relevant system |
| Training evidence | Record what training was delivered and what evidence is available | Fictional example: session record and materials; these do not, by themselves, establish competence or authorization |
| Open items | State unresolved gaps and the handoff needed | Fictional example: pump-room equipment schedule not yet included; keep it separate from approved drawing references |
Read the worked drawing example correctly
In the fictional North Quay Works pump-room set, the earlier drawing issue is labeled superseded. The identified approved issue is filed with its revision so a reader can tell which copy is intended as the current reference. The equipment schedule is listed separately as an open item because it is missing from the example pack.
This example demonstrates document organization, not project acceptance. Use the applicable document-control process and authorized project roles to determine status. Training evidence records what was delivered; it does not itself establish competence, authorization, or permission to perform work. For safety-critical, regulated, or sensitive decisions, use the applicable approved local process and trained-role handoff.