A handover dossier is the structured set of records that proves a system, area or facility was built, inspected, tested and commissioned as designed, and gives the operator what it needs to run and maintain it. A complete dossier normally holds the completion certificates, signed inspection and test records (ITRs), the punch list status, vendor and manufacturer data, as-built drawings, operating and maintenance manuals, spares information and any regulatory certificates. On industrial projects it is usually assembled per system, not per building or per discipline, so each package can be handed over as soon as that system is ready.
Different clients call it different things: turnover package, handover package, completion dossier, system handover package, MC dossier. The name matters less than agreeing its contents and structure early, because a dossier that is only defined at the end of the project is a dossier that will be late.
Why the handover dossier matters
The dossier is the evidence behind every signature on a completion certificate. When the owner signs to accept care, custody and control of a system, they are relying on the dossier to show that nothing has been skipped. If a pressure test record is missing or a relief valve certificate is out of date, the operator inherits that gap, and so does their insurer and regulator.
It also has a long working life. Maintenance teams will go back to the vendor data and as-builts for decades. A dossier that is a heap of scanned PDFs with no index is technically "handed over" but practically useless.
Handover dossier contents, section by section
The exact structure is usually set by the client's handover specification or completions procedure, so check that first. The table below is a typical system handover package for an industrial or energy project.
| Section | Typical contents | Who normally provides it |
|---|---|---|
| 1. Index and system definition | Dossier index, system and subsystem description, marked-up systemisation drawings (P&IDs, single-line diagrams), tag list | Completions team |
| 2. Certificates | Mechanical completion certificate, ready for commissioning certificate, any interim certificates, handover or transfer of care certificate | Completions / commissioning |
| 3. Construction ITRs ("A" records) | Signed inspection records per tag: installation, alignment, cable terminations, instrument installation, and so on | Construction contractors, QA/QC |
| 4. Pre-commissioning and commissioning records ("B" records) | Loop checks, insulation resistance, flushing and cleaning, function tests, signed commissioning test procedures | Commissioning team |
| 5. Test packs | Hydrotest or pneumatic test packs, reinstatement records, weld and NDE summaries where required | Piping contractor, QA/QC |
| 6. Punch list status | Open and closed punch items with category, owner and target date, plus any agreed carry-over list | Completions team |
| 7. Vendor and manufacturer data | Data sheets, material certificates, factory acceptance test reports, calibration certificates, certificates of conformity | Procurement / vendors |
| 8. As-built documentation | As-built drawings, redlines incorporated, final revision of design documents | Engineering / document control |
| 9. Operating and maintenance information | O&M manuals, recommended maintenance, lubrication schedules, special tools | Vendors, engineering |
| 10. Spares | Commissioning spares used, capital and operating spares lists, recommended spares | Procurement / vendors |
| 11. Regulatory and safety certificates | Pressure system documentation, lifting equipment certificates, hazardous area (Ex) records, electrical certificates | Specialists, QA/QC |
| 12. Preservation records | Preservation history from delivery to handover | Construction / completions |
Buildings projects use a similar list with a different emphasis: building services commissioning records, the building log book, fire strategy and alarm certificates, and health and safety file content. Wherever you work, the principle is the same: every document in the dossier should trace back to a tag, a system or an area.
Certificates and inspection records
These are the core of the dossier. The certificates summarise; the ITRs prove. A mechanical completion certificate that says a system is complete should be backed by a signed "A" record for every tag in it, and the ready for commissioning certificate by the relevant "B" records. If you need a refresher on how those certificates chain together, see commissioning certificates explained and mechanical completion explained.
Punch list status
A system is rarely handed over with zero punch items. What matters is that the open items are the ones the receiving party agreed to accept, usually lower-category items that don't affect safety or operation. The dossier should include the punch list at the moment of handover, with each item's category and owner, so there is no argument later about what was known. The rules for which categories can remain open are covered in punch list categories A, B and C.
Vendor data
Vendor data is the section that most often holds up a dossier. It depends on third parties, it arrives in inconsistent formats, and it is often chased only when handover is imminent. Tie vendor document requirements into purchase orders and track their receipt from the start of procurement, not the start of commissioning.
As-built documentation
As-built drawings reflect what was actually installed, including field changes. The weak point is the gap between site redlines and the formally revised drawing. Agree who incorporates redlines, when, and what revision status is acceptable at handover. Some owners accept "as-built redline" at mechanical completion and require fully drafted as-builts at final handover; others want the lot before they sign.
How to assemble a dossier per system
Building dossiers by system follows the same logic as commissioning by system. Once your systemisation is fixed, every document can be allocated to a system or subsystem, and each system's dossier can be built up progressively.
A practical process:
- Agree the dossier specification early. Get the client's handover requirements into the completions procedure before construction starts: sections, document types, format, naming, signatures, and whether electronic signatures are accepted.
- Build a required-document matrix per system. For each system, list the documents that must exist: which ITRs per tag type, which test packs, which vendor documents for each equipment item. This is the checklist the dossier is measured against.
- Link documents to tags and systems as they are created. An ITR signed today should land in the right dossier today, not be sorted into it during a filing week before handover.
- Track gaps continuously. Report missing documents per system alongside ITR progress and punch status. A system that is mechanically complete but has half its vendor data missing is not ready for handover.
- Review before the walkdown. Have the dossier reviewed internally before the client's handover walkdown, so the client's time is spent on the plant, not on finding missing signatures.
- Compile, sign and lock. At handover, compile the dossier, obtain the handover signatures and freeze it. Later changes should go through a controlled revision, not an edit to the original.
- Transmit and record acceptance. Issue the dossier by formal transmittal and record who received it and when.
Common reasons dossiers are late
- The dossier structure was agreed at the end, so records were filed to the wrong structure and had to be reworked.
- ITRs were signed on paper and scanned in batches, with pages missing or illegible.
- Vendor data was not chased until commissioning.
- The punch list was maintained in a separate spreadsheet that nobody reconciled with the dossier.
- As-built redlines lived in site cabins and were never returned to document control.
- Nobody owned the dossier. Completions assumed document control would do it, and document control assumed completions would.
Handover dossier checklist
Use this as a final check before issuing a system handover package:
- Index complete and matching the actual contents
- System boundaries and tag list match the current systemisation
- Every tag has the required "A" ITRs signed by the right parties
- Every required "B" record and commissioning procedure is signed
- Test packs are closed and reinstatement is recorded
- All required certificates issued, in the right order, with dates that make sense
- Punch list attached, with only agreed categories left open
- Vendor data received for every equipment item, at the required revision
- As-built drawings at the agreed status
- O&M manuals and spares lists included
- Regulatory and statutory certificates included and in date
- Preservation records complete up to handover
- Signatures present and legible; no unsigned or undated pages
- Dossier locked and transmitted with a record of receipt
Digital vs paper handover dossiers
Paper dossiers still exist, especially where clients insist on wet signatures or where the handover specification was written years ago. They are slow to assemble, hard to check and easy to lose. A single missing page can mean reopening a lever-arch file and re-issuing it.
A digital dossier generated from a completions system is a different thing from a paper dossier scanned to PDF. In the digital case, the dossier is a view over data that already exists: tags, ITRs, certificates and punch items are linked, so gaps show up as soon as they occur rather than at compilation. The final output can still be a set of PDFs with an index, if that is what the client wants, but the checking happens in the system.
| Paper or scanned dossier | Dossier compiled from a completions system | |
|---|---|---|
| Gap detection | Manual review at the end | Continuous, against a required-document matrix |
| Traceability | Depends on indexing discipline | Documents linked to tags, systems and certificates |
| Revisions | Re-print and re-issue | Controlled revision with history |
| Effort at handover | High: collating, scanning, checking | Lower: compile and review |
| Data reuse by operator | Limited to reading documents | Structured data can feed maintenance systems |
If the owner also wants structured asset data rather than documents alone, that is increasingly specified through standards such as CFIHOS. Either way, the earlier you decide what the dossier is, the less rework you do.
Managing handover dossiers in Accord
Accord manages handover dossiers as part of the completions process rather than as a separate filing exercise. Each system has a required-document matrix, and Accord raises missing-document alerts so gaps are visible long before handover. ITRs, punch items and certificates are all linked to the system and subsystem hierarchy, and certificates cannot be issued without their prerequisites. When a system is ready, the dossier is auto-compiled and locked as an archive. Revision-controlled documents, OCR intake of scanned records and an immutable audit trail mean you can show exactly what was handed over and when.
Frequently asked questions
What is the difference between a handover dossier and a turnover package?
In most cases they are the same thing under different names. "Turnover package" is more common on North American and international EPC projects, while "handover dossier" is widely used in the UK and Europe. Check the client's specification, because some companies use "turnover package" for a system-level package and "dossier" for the complete project record.
Who is responsible for compiling the handover dossier?
Normally the contractor delivering the work compiles it, led by the completions or document control team, and the owner reviews and accepts it. Responsibility should be written into the completions procedure with a named owner for each system dossier. When ownership is vague, the dossier is usually late.
When should handover documentation be started?
At the start of construction, not at the end. The dossier structure, required-document matrix and naming rules should be agreed before the first ITR is signed, so each record is filed correctly as it is created. Vendor data requirements should be set at purchase order stage.
What is included in as-built documentation?
As-built documentation records what was actually installed, including field changes and deviations from design. It typically covers as-built drawings such as P&IDs, layouts, isometrics, single-line diagrams and cable schedules, and the final revision of key design documents. The status required at handover, redline or fully drafted, varies by contract.
Can a system be handed over with open punch items?
Usually yes, provided the remaining items are in categories the receiving party has agreed to accept and are listed in the dossier. Items that affect safety, integrity or the ability to commission or operate the system are normally required to be closed first. The exact rules depend on the project's punch category definitions.