Construction is finished but the asset will not hand over. Why

A familiar situation: construction is complete, physical progress is close to 100%, and the asset is neither handed over nor operating. A month passes, then a second, then a third. Each time a new cause appears: missing test reports, the vendor has not attended testing, the punch list is open, documentation does not meet acceptance requirements.

Structurally the cause is always the same: the handover phase was never planned as a phase, with its own activities, resources, durations and predecessors.

Three things that get confused

• Mechanical completion — equipment is installed and connected. That is not function.
• Start-up works — the technical activities that bring systems to design parameters.
• Commissioning — the management process above them: system boundaries, readiness criteria, test sequence, participant coordination and documentation of the result.

A project that planned only construction reaches completion and discovers that handover needs several more months of work that is not in the schedule and for which no resources are contracted.

Why commissioning is planned during design

System boundaries, testing requirements and the required documentation set all influence design decisions and vendor contract terms. Three concrete examples:

1. Splitting the asset into systems for staged handover determines power and control topologies. After installation that cannot be changed.
2. Vendor attendance at installation supervision and testing must be in the supply contract. Without it, getting a specialist to site becomes a separate negotiation with its own price and lead time.
3. The composition and format of test records is set in advance: a record not prepared to acceptance requirements has to be redone, and some tests repeated.

Punch list: managed or unmanaged

A list of defects before acceptance exists on every project. The difference is whether it is run as a managed register or as a set of lists held by different parties.

A managed punch list has three mandatory properties: a single register (one table per project), categorisation by impact on handover (items blocking handover separated from cosmetic ones), and closure status with an owner and a date. Without categorisation a team spends equal time closing the critical and the trivial.

Documentation completeness: the main source of delay

The most frequent cause of handover delay is site record documentation. The core problem is that some evidence is physically unrecoverable: if covered works were closed without inspection, the certificate cannot be issued properly — the work is no longer visible.

Site records cannot be assembled before acceptance. They can only be maintained alongside the works — or you discover that part of the evidence is permanently lost.

What to do if the asset is already there

1. Take an inventory: what is actually complete, which systems are tested, which records exist, which documents are missing.
2. Build one punch list, categorised by whether items block handover.
3. Build the handover programme as a project in itself: activities, resources, vendor attendance, durations, critical path.
4. Identify which evidence is unrecoverable and agree compensating measures — testing, openings, supplementary expert opinions.
5. Appoint an owner for handover as a distinct phase. While the person accountable for handover is also accountable for construction, handover stays a secondary task.