1. What the dossier is actually for
A handover dossier serves three audiences with different needs, and confusing them is why so many dossiers are simultaneously enormous and unusable.
- Contractual — proof that the scope was executed and accepted, supporting payment, warranty and liability positions.
- Regulatory — evidence for the authority having jurisdiction that statutory testing, certification and inspection were carried out.
- Operational — the working reference operations and maintenance use for years: what the tag is, how it was set, what it was tested to, who supplied it.
The operational audience is the one that gets designed for last and complains longest. A dossier that satisfies the contract but cannot be searched by tag is a dossier that gets rebuilt by the operator within two years.
2. Structure it by subsystem, index it by tag
The dossier structure should mirror the subsystem breakdown that everything else in completions used, because that is the unit of certification and the unit of custody transfer.
| Level | Contents |
|---|---|
| Project | Scope description, register of subsystems, certificate index, punch summary, deviation register. |
| System | System description, P&IDs and single line diagrams, system-level test records, operating philosophy. |
| Subsystem | Certificate set (MCC, RFC, RFSU), walkdown records, punch list with status, boundary marked drawings. |
| Tag | ITRs, calibration certificates, material certificates, vendor documentation, as-built data attributes. |
Structure alone is not enough. Every document must carry the tag and subsystem as metadata, not just in the filename, so the dossier can be queried rather than browsed. This is the single largest difference between a digital dossier and a scanned one.
Put a number on it
What is this costing your project right now?
Estimate the hours and cost lost to transcription, register consolidation and dossier assembly — with editable assumptions and the maths shown.
3. The data quality rules operators check
Operator acceptance checks are more predictable than they look. Build against them from day one and closeout shortens dramatically.
- Every tag in the dossier exists in the master tag register, spelled identically. Tag naming drift is the most common rejection reason.
- Every record references a tag that is in scope for the subsystem it is filed under.
- No document is orphaned — anything without a tag or subsystem reference will not be found again.
- Signatures are attributable — a name, a role, a date, and evidence the signatory held the authority.
- As-built reflects reality — where the plant deviates from drawing, the deviation is recorded and the drawing revised, not annotated verbally.
- Open punch is listed with owners and dates, and reconciles exactly with the punch register.
4. Digital dossier vs a folder of PDFs
| Capability | Scanned PDFs | Structured digital dossier |
|---|---|---|
| Find every record for a tag | Manual search across folders. | One query, complete result. |
| Prove a certificate's evidence set | Cross-reference by hand. | Certificate links to its underlying records. |
| Detect a missing record | Discovered at audit. | Detected continuously as a gap. |
| Reuse data in the CMMS | Re-keyed from documents. | Exported as structured attributes. |
| Show change history | Not available. | Full revision and signature trail. |
The commercial argument is simple: re-keying tag attributes into the maintenance system is a large, error-prone, entirely avoidable cost. If the completions system holds tags, attributes and records against a controlled register, the CMMS load becomes an export rather than a project.
5. Build it continuously, not at the end
A dossier assembled at the end is an archaeology exercise. A dossier that accumulates as records are signed is a by-product. The difference comes down to four habits:
- One master register from the start. Tags, systems and subsystems defined before the first ITR is raised, so nothing needs re-mapping later — see master data.
- Capture at source. Records signed in the field carry their tag, subsystem, signatory and timestamp automatically; paper collected later never does.
- Continuous gap reporting. The dossier completeness view should be live throughout the project, not produced at closeout.
- Agree the format early. Confirm the operator's required structure, metadata and naming convention during engineering. Reformatting 40,000 documents at the end is a real and recurring project cost.
6. Getting it accepted
- Issue a sample dossier early — one complete subsystem, months before handover, and get it formally reviewed. Every comment on that sample is a comment you avoid on all the others.
- Agree the acceptance criteria in writing, including how missing vendor documentation is handled and what constitutes an acceptable deviation.
- Reconcile the punch register and the dossier punch list before issue; a mismatch here undermines confidence in everything else.
- Hand over by subsystem as each is certified, so acceptance is incremental rather than a single cliff at the end of the project.
See handover and RFSU for how dossier acceptance interacts with custody transfer and final acceptance.
Check your own process
Score your handover readiness in eight questions
A structured self-assessment of register control, evidence capture, sign-off and gate logic — with a specific recommendation for every gap.
