The Handover Date Is Fixed. Are Commissioning and Closeout Ready?
A fixed handover date is credible only when testing, commissioning, snagging, documentation, training, asset data and approvals are planned as integrated completion work.
The short answer
A fixed handover date is credible only if commissioning and closeout are planned as production work, not as documentation that begins after installation finishes. Testing sequences, system dependencies, snagging, statutory and client approvals, operating manuals, asset data, training, demonstrations and final records all consume time and require inputs from different teams. If they are not visible in the programme early, “construction complete” can arrive while the project is still far from practical completion or client acceptance.
The control objective is to build a completion chain that starts months before handover and shows the evidence required for each system, area and approval. Closeout should progress with the work rather than accumulate at the end.
A project example
A project has a non-negotiable handover date at the end of the month. Physical installation appears almost complete. During the final weeks, however, integrated testing cannot start because one controls interface is unresolved, several certificates are missing, the client's facilities team has not confirmed training dates, asset data is incomplete, and snags are being tracked in separate lists by each trade.
The master programme still shows handover on time because many construction activities are 95–100% complete. Yet the remaining 5% contains dependencies that cannot simply be compressed. Testing must occur in sequence, defects may require retest, documents need review, and approvals depend on evidence.
This is the closing stage of the same programme-to-site control chain. Completion is reliable only when the programme includes the work required to prove that systems, spaces and information are ready for use.
Define completion by system and area
A single project-wide percentage obscures closeout. Commissioning often follows systems while handover may follow areas, floors, phases or assets. The project should define the completion structure early enough to support both technical testing and client acceptance.
For each system or handover unit, identify the required construction completion, pre-commissioning checks, tests, integrated tests, defect closure, documents, training and approvals. Not every project needs every step, but the required evidence should be explicit.
This structure allows management to see where a physically complete area is waiting on documentation or where a complete document set is waiting on unresolved site work.
Start commissioning logic before installation finishes
Commissioning sequences have dependencies of their own. Power must be available, controls must be commissioned, water systems may need flushing, interfaces must be tested and upstream equipment must be stable. These dependencies should be mapped into the programme rather than represented by one late “commissioning” bar.
Early planning also identifies temporary requirements such as test power, access, specialist vendors, calibrated equipment, witness dates and client representatives. Some of these have long lead times even though they do not look like traditional procurement.
The planning team should work with commissioning leads to identify the few milestones that genuinely control readiness and to link them to the installation packages that feed them.
Manage snagging as flow, not a final list
Snagging becomes dangerous when the project waits for substantial completion and then creates a massive undifferentiated list. Record defects and incomplete items progressively, assign owner and location, classify whether they block testing or handover, and verify closure with suitable evidence.
A blocking snag can prevent commissioning, safety approval or client use. A minor cosmetic item may be safely closed after another milestone. Classification helps the team protect scarce closeout time.
The same logic used for workface readiness between trades applies at project closeout: completion should be assessed from the receiving party's requirements, not only from the delivering team's view.
Build documentation alongside physical work
Operating manuals, test certificates, as-built information, warranties, asset data and training materials should not begin as a last-week collection exercise. Each deliverable should have an owner, required format, source, review status and relation to the relevant system or asset.
As-built information is especially vulnerable to late reconstruction. Site changes should feed the record progressively so final drawings reflect installed reality. Asset data also depends on procurement and supplier information that may be easier to collect when orders are placed than months later.
A project-centric ERP such as Saturn can provide common project, package, procurement and cost context around closeout records. It should complement specialist commissioning, document and asset-management processes where those are required.
Plan training and client participation
Training is often shown as a single activity even though it depends on completed systems, approved manuals, available trainers, client staff and sometimes recorded attendance or competency evidence. Confirm the audience, format, prerequisites and dates early enough that training does not become a last-minute scheduling conflict.
Client witnesses and authorities can also constrain testing. Their availability may be outside the contractor's control, so required notice periods and re-test allowances should be visible in the plan.
Where demonstrations depend on live operating conditions, the project should confirm that the environment required to demonstrate performance will actually exist before the session is booked.
Make approvals evidence-based
Closeout statuses such as “ready for handover” should have defined evidence. Depending on the project, this may include completed tests, closed blocking snags, approved manuals, training completion, statutory certificates, accepted asset data and signed area handovers.
Do not rely on a single percentage that teams can interpret differently. A traffic-light view can be useful only when the conditions behind the colour are clear. If one requirement is waived or deferred, record who approved the exception and how it will be closed.
This protects both project control and client communication. Management can distinguish genuine completion risk from administrative items that have a controlled closeout route.
Connect late changes to commissioning consequence
Design revisions and site instructions near completion can have disproportionate effect. A small control change may require software updates, re-testing, manual revisions and new training. The operational effect should be assessed as soon as the change is known.
This is why closeout cannot sit apart from change and document control. The project should know which systems, tests and deliverables are affected by the latest approved revision. Otherwise a team may complete testing against information that has already changed.
For significant revisions, use the same discipline described in drawing revision control at the workface: preserve revision identity and trace the change into downstream records.
Protect time for retesting and acceptance
A commissioning plan that assumes every test passes first time is not a robust handover plan. Build realistic space for defect correction, retest, document revision and client review where those steps are foreseeable. The allowance does not need to be hidden contingency; it can be explicit logic between first test, issue resolution and final acceptance.
This makes late decisions easier to evaluate. If a change consumes the remaining retest window, management can see the consequence immediately instead of discovering at handover that the date depended on perfect first-time performance.
Five practical controls
1. Define completion by system, area and required evidence. Avoid one project-wide percentage as the only closeout signal.
2. Programme commissioning dependencies early. Include utilities, controls, specialist vendors, witnesses and retest allowance.
3. Manage blocking snags separately from minor items. Protect testing and handover priorities.
4. Collect documents and asset data progressively. Tie deliverables to packages and systems as work proceeds.
5. Plan client training and approvals as real activities. Give them owners, prerequisites and dates.
These controls turn handover from an end-of-project scramble into a managed production stream.
What management should measure
Useful indicators include:
- systems physically complete but not ready for commissioning;
- planned tests blocked by missing predecessor conditions;
- blocking snags outstanding by system or handover area;
- required documents or asset records not yet submitted or approved;
- training sessions without confirmed prerequisites or attendees;
- re-tests caused by late change or failed integrated testing;
- handover units without a complete evidence set for acceptance.
The strongest indicator is often the age and consequence of unresolved closeout exceptions, not the raw number of open items.
Frequently asked questions
When should commissioning planning begin?
Early enough to influence installation sequence, utilities, access, controls interfaces, specialist procurement and witness planning. On complex projects, waiting until physical installation is nearly complete is usually too late to resolve all dependencies efficiently.
Is snagging the same as closeout?
No. Snagging is one component. Closeout can also include testing, approvals, manuals, as-built records, training, asset data, warranties and contractual handover evidence.
Should documentation be complete before testing starts?
The required sequence depends on the project and test. Some documents are prerequisites; others are produced from the test itself. Define the evidence and review gates for each system rather than applying one blanket rule.
How can management tell if the handover date is genuinely achievable?
Look beyond construction percentage complete. Review the remaining commissioning dependencies, blocking snags, evidence deliverables, approvals, training and retest allowance by system and handover area. A fixed date is credible only when those remaining paths are visible and owned.