Chapter 05
Closeout and handover from day one
Why owner-side handover should be designed into the contract from mobilisation, how the captured record reduces the cost of warranty and latent-defect recovery, and what to specify so the asset arrives in a state the owner can operate.
01
Orient: handover starts at mobilisation
Most handover packs arrive late and incomplete because the project treated handover as a closeout activity rather than a continuous one. The captured base allows the opposite. From mobilisation, the project is producing the evidence the handover will need: progress records, design verification, quality non-conformances and dispositions, training and competence records, commissioning evidence, gate and delivery records that anchor the as-built to a calendar. The owner who specifies handover from day one tends to receive a coherent pack on time. The owner who specifies it three months before practical completion is too late: the practices that produce a clean pack have already been set on the ground, the records have been kept in formats that suit the contractor rather than the asset manager, and the chase is on. The cost of late specification is paid in two places. The first is the closeout itself, which becomes a scramble to assemble a pack that the asset manager will accept. The second is the warranty period, where the asset manager is operating against a record that was not built for them and answering tenant questions by reaching back into the project rather than using the archive that should have been left behind. Specifying at signing is the same conversation, held cheaply. The conversation later, after the records have already been kept in the wrong shape, is held against accumulated practice and against the contractor´s reasonable position that they cannot now change what they did not know they were being asked to do.
02
Owner-frame: what the asset manager actually needs
Asset managers do not need every clip and every drawing. They need a record that lets them defend warranty calls, plan major maintenance, and respond to latent-defect emergencies without rebuilding the project from scratch from the contractor´s archive. That means an indexed closeout archive: as-built record tied to the design baseline, NCR dispositions linked to the affected systems, commissioning evidence preserved with chain of custody, training and competence records for the trades that worked on serviceable systems, and a retention term that runs through the latent-defect period rather than ending at practical completion. The archive should be indexed in a way that mirrors the asset register the operations team will use, so a tenant warranty call about a leaking riser maps directly to the system, the package, the contractor, the dispositions, and the captured-base reference. The asset manager should be able to answer a tenant warranty query without ringing the project director who has long since moved to another job and who, increasingly, is no longer with the contractor at all. The owner who specifies the archive at signing is making a gift to their own asset management team three years in advance. The team usually only realises the value of the gift the first time they avoid a remediation argument that would have eaten a quarter of their year.
03
Workflow: specify at signing
An owner should specify, at contract stage, the captured base to be retained, the format and indexing standard of the closeout archive, the access rights for the warranty and latent-defect periods, and the named custodian and their successor in the event of contractor exit, acquisition, or insolvency. Specification at signing costs nothing beyond the time of the conversation, because the contractor has not yet built the practices that would have to change. Specification at the start of mobilisation costs a discussion, because the practices are being formed and the contractor can still adjust. Specification three months before practical completion costs a renegotiation, and the renegotiation usually loses, because the leverage on both sides is gone: the contractor cannot rebuild a year of records, and the owner cannot withhold practical completion over an archive that was not in the agreement. The discipline is administrative, not technical, and it is the move that distinguishes owners who keep their record from owners who do not. The legal team can mark up the spec, the contractor´s commercial team can challenge specifics, and the conversation is over in a fortnight. The pack that arrives at handover is then a deliverable rather than a hope. The owner who runs the discipline once usually carries the same template into every subsequent agreement and pushes their internal legal precedent to match, which is how a single contract change becomes a portfolio-level standard within a year or two.
04
Governance: ESG, regulatory, and the long tail
The closeout archive serves a longer tail than warranty alone. ESG reporting against embodied-carbon claims is more credible when the as-built record can be cross-referenced against the materials specified and delivered, with gate records and delivery verification that tie what was actually installed to the supplier and the lot. Regulatory inspections through the asset´s life are answered faster when the archive is indexed to the inspection regime, particularly for life-safety systems and any installations that fall under building-safety legislation. Insurance renewal in the latent-defect period is cheaper when the underwriter can be shown a coherent record of how the asset was built rather than being asked to underwrite an unknown. Refinancing events are smoother when the diligence pack draws on the same archive. None of these uses is exotic; they are the ordinary uses an asset has over its first decade. The owner who has the archive answers them as routine; the owner who does not answers them as a project, with the cost in time, professional fees, and stress that any project carries. Across a portfolio over a decade, the difference compounds into a real number. None of these uses appears in the original case for the discipline at signing, which is why the case at signing is rarely the case that ends up justifying the move; the move justifies itself in the years afterward, in the small interactions that did not turn into projects of their own.
05
What good looks like
Good is when a warranty issue eighteen months after handover is resolved in a fortnight, not a quarter. The asset manager pulls the as-built and the disposition record, identifies the responsible package, and calls the contractor with the evidence already in hand. The contractor either accepts and acts, or contests with their own evidence, and the resolution is on the merits rather than on who can sustain the argument longest. A latent-defect emergency at year four is answered from the archive in days, not weeks, with the captured base showing the relevant area at the relevant time, the disposition history, and the chain of trades through that part of the asset. The retention cost is small, particularly relative to the value of the asset under warranty. The dispute cost it prevents, across a portfolio over a decade, is large enough that owners who run the discipline tend to make it the standard for every subsequent agreement and to push their legal teams to update the template accordingly. The change shows up in the operating numbers within two or three years, not in any single dramatic moment, which is the honest pattern of how good administrative discipline pays back. By the time it is obvious in the numbers, the owners who installed it earliest tend to be the ones whose portfolios are the cheapest to operate and the easiest to refinance, which is the kind of compounding the asset-management side of the business actually rewards.
Practice
01. Draft the handover-pack specification you would attach to your next development agreement. Cover scope, format, indexing, retention term, custody, access rights, and successor arrangements.
Look for: A workable specification names the captured-base components retained (360 walks, drone, fixed-camera, gate records, delivery records), the indexing standard tied to the WBS or asset register, a retention term running through the latent-defect period, a named custodian, a successor in the event of contractor exit, and read access for the owner on a named portal in a court-admissible export format. The legal team should be able to mark it up rather than draft it from scratch, and the contractor´s commercial team should find that most of the spec is administrative rather than commercial.
02. Pick a warranty issue that arose on a recent completed project. Describe how it would have resolved with a properly indexed closeout archive in place, and estimate the time and cost difference against how it actually resolved.
Look for: The exercise lands when the reader can name the artefact that would have closed the issue (an as-built tied to the responsible package, a disposition record showing the prior NCR, a commissioning record showing the system signed off in a particular state) and estimate the saving honestly: usually weeks of internal time, sometimes external counsel avoided, occasionally a five- or six-figure remediation argued down to a fair share. The reader who runs this exercise across three or four past warranty issues tends to make a stronger internal case for the discipline than any vendor pitch could.
Checkpoint
On your next contract, can you specify the captured-base retention, custody, indexing standard, and warranty-period access rights at signing, in language that survives review by your legal team and the contractor´s?
Recommended reading