The turnover package is a deliverable, and it is priced last

Every construction contract requires a turnover package: as-built drawings, operating and maintenance manuals, test and commissioning records, an asset register, warranty documentation, spare parts, and training.

It is also, on most projects, the last thing anybody thinks about. The requirement is stated in general terms, no date attaches to it, no payment depends on it, and it is due at the moment the contractor's site organization is demobilizing. The result is predictable and nearly universal: a package that is late, partial, and of limited use to the people who need it.

Why it matters more than it appears to

The turnover package is the asset's operating manual and its evidentiary record. Three consequences follow from its absence.

Maintenance cannot be planned. A maintenance regime requires a complete asset list with locations, models, serial numbers, and service intervals. Where the register is incomplete, the operating team builds one by walking the facility, which takes months and misses what is concealed.

Faults take longer to find. An as-built record that does not reflect what was installed sends a technician to the wrong valve, the wrong circuit, or the wrong isolation point. The cost is paid on every intervention for the life of the asset.

Warranty and defect claims weaken. A defect claim rests on the installation record, the test result, and the commissioning data. Where those are missing, the claim becomes an argument about what happened, and the party with the records wins it.

There is a fourth, less obvious consequence. Where a facility's documentation is poor, any later modification begins with a survey. Every future capital project on the asset pays a premium for the documentation this one did not produce.

Why it arrives late

The mechanism is the same as with any obligation nothing depends on.

The package is due at completion, and completion is when the contractor is under maximum pressure to finish physical work. Documentation competes with construction for the same management attention and loses, correctly, because the physical work is what certification depends on.

The people who hold the information also leave in the wrong order. Commissioning records live with commissioning technicians, as-built information with the trades who installed the work, and vendor documentation with suppliers whose contracts closed months earlier. By the time the package is assembled, its sources have dispersed.

And the specification is usually too vague to enforce. A requirement for as-built drawings and manuals, without a format, a structure, a level of detail, or a submission schedule, cannot be rejected for non-compliance because compliance was never defined.

A deliverable with no date, no format, and no payment attached is not a deliverable. It is an expectation, and it will be met to the standard that costs the least.

Specifying it so it arrives

Four provisions change the outcome, and none is onerous.

Define the format and structure before construction starts. Naming convention, file structure, drawing standards, asset register fields, and the system the data has to load into. Documentation delivered in the wrong structure has to be re-worked by the owner, which is the most common hidden cost of a poorly specified package.

Require progressive submission by system. Each system's records — test results, as-builts, manuals, asset data — are submitted as that system completes, not at the end. This aligns documentation with the commissioning sequence and captures the information while the people who produced it are still present.

Attach payment. A defined portion of the contract sum, payable against acceptance of the documentation for each system. This is more effective than any withholding applied at the end, because it acts while the contractor still has an organization on site.

Make it a condition of completion. Where substantial completion is defined to require the turnover package for the systems being handed over, the package is produced. Where it is an obligation that survives completion, it is produced under protest, if at all.

Reviewing what arrives

The package should be reviewed by the people who will use it, against the facility, before acceptance. That means an operating representative checking a sample of the asset register against installed plant, a maintenance representative confirming that isolation points and access routes on the as-builts match reality, and someone confirming that the vendor documentation is for the models actually installed rather than for the ones specified.

That review takes days and finds most of what is wrong. Conducted before acceptance, it is a punch list. Conducted after, it is a discovery, and the party who could have fixed it has gone.