Chapter 06
Handover of the capture plan
How the capture plan transitions at handover, what survives into warranty, and how to leave the owner with a record that is usable years later rather than a folder no one can navigate.
01
What actually transitions at handover
At handover, the capture plan transitions. Most active capture stops, but the records produced under the plan should not. The closeout archive should retain the records the workflows produced, indexed against the plan, with the retention windows the plan specified. An archive that survives handover but the plan that produced it does not is hard to use — the records are present, but the structure that makes them retrievable is missing. Both should travel together. The handover deliverable is the plan, the archive, the revision minutes, and the index that maps records to workflows. The owner inherits a usable evidence base; the contractor closes the contract with a defensible position; the digital construction lead leaves a piece of work that has a half-life beyond the contract.
02
Continued capture during the defects period
Some capture continues into the warranty period, and the post-handover plan should specify it rather than leave it implicit. Limited fixed coverage during the defects period is common — a small number of cameras retained at low cadence to support warranty calls and refurbishment planning. Annual 360 walks against the as-built record give the owner a way to see how the building has changed without sending an inspection crew to every floor. Drone surveys at six- or twelve-month intervals are appropriate on projects with significant external scope, particularly infrastructure and energy assets where the surrounding environment can change. The post-handover capture plan is much smaller than the construction-phase plan, but it should still be a plan, with named workflows, named sources, and a named owner on the operations side. Without specification, the project tends to lose access to the captured base much sooner than the warranty needs, and the records become orphaned.
03
Indexing the archive against future use
A closeout archive is only useful if someone can navigate it years later. The index should be flat enough for a non-specialist to use — by date, by package, by workflow, by location — and deep enough to retrieve a specific record without scrolling. A common pattern is a top-level index by floor or by chainage, a mid-level index by package and date, and a leaf-level index by source and tag. The index lives with the archive and travels with it on any storage migration. The most expensive moment for the owner is the first time they need to retrieve a record from the archive after a personnel change on their side, and the index is what determines whether that retrieval takes minutes or weeks.
04
The owner´s long memory and the discipline at handover
A capture plan that handed over cleanly becomes the owner´s long memory of the project. A warranty issue, a refurbishment, a future tender, a regulatory inspection, a planning application for an extension — each benefits from being able to retrieve the captured record in minutes rather than rebuild it from drawings and memory. The cost of preserving the plan and the records together at handover is small relative to the value of the access years later. The discipline is to make the future access possible rather than implicit. That means a written handover protocol, a named recipient on the owner side, a tested retrieval — pick a record at random and find it together — and a documented retention schedule that survives any storage vendor change. Done well, the handover is the moment when the capture plan stops being a contractor artefact and becomes part of the asset.
05
Failure modes at handover
The most common failure is a handover where the records pass over but the plan does not, leaving the owner with files and no map. The second is a handover where the plan passes over but the index does not survive the storage migration, so the records are present but not retrievable. The third is the soft failure — the handover is technically complete, but no one on the owner side has been trained to use the archive, so the first warranty call goes unanswered and the archive falls into disuse. Each is preventable by treating the handover of the capture plan as a workflow in its own right, with a named owner, a checklist, a tested retrieval, and a follow-up six months in to confirm the owner is still using the plan.
Practice
01. Draft a handover protocol for your next project closeout. Include the deliverables, the named owner-side recipient, the tested retrieval, and the six-month follow-up. Identify which deliverables are not currently produced as a matter of course.
Look for: A workable protocol lists the capture plan, the revision minutes, the indexed archive, the retention schedule, and a short user guide as deliverables. The named recipient is usually the asset manager or facilities lead. The tested retrieval picks two records — one recent, one early in the contract — and walks them through. The six-month follow-up confirms the records are still accessible and the index still works after any storage migration. Most projects do not currently produce the revision minutes or the user guide, and these are the first additions worth making.
02. Specify the post-handover capture plan for a notional project of your scale during the two-year defects period. Name the sources, cadence, retention, and workflows, and cost it relative to the construction-phase plan.
Look for: A typical specification retains two fixed cameras at the principal elevations on quarterly recording, an annual 360 walk against the as-built, and a six-monthly drone flight if the project has external scope. The workflows are warranty support, refurbishment planning, and any residual claims. Cost runs at five to ten per cent of the construction-phase capture spend, justified by the value of warranty defence and the option value of the long-memory archive.
Checkpoint
For your last completed project, can you locate the capture plan, the revision minutes, and the archive together today, and could a non-specialist on the owner side do the same?
Recommended reading