Working is one of three conditions.

Systems cut across areas

Construction is organised by place. A floor, a block, a grid reference, a chainage — and week 21 packaged the work that way because a crew can be handed a place.

Commissioning is organised by function. A chilled water system, a fire detection loop, a drainage network. None of those is anywhere in particular: each threads through most of the areas the project was built in.

So two disciplines describe the same works under two incompatible breakdowns, and neither can be derived from the other without somebody doing the mapping by hand. That is week 12's missing key, arriving at the point in the project where there is least time to construct one.

And it has a reporting consequence. Progress by area and progress by system give different pictures of the same works, and a project reporting only the first has no visibility of the second until the second becomes the constraint.

Which happens abruptly. Area progress can read ninety per cent while no system is complete, because a system needs all of its areas and ninety per cent of the areas leaves every system one short.

The sequence inverts

The second collision is about order.

Construction runs from the ground up and outward: substructure, frame, envelope, fit-out. Commissioning runs from the supply inward: a system can't be tested until whatever feeds it is live, so power, water and control systems have to work before anything they serve can be proven.

Which means the areas built last can contain the systems needed first, and the plant room that was low priority for the frame becomes the item everything waits on.

Nothing about that is a surprise to a commissioning engineer. It is a surprise to a construction programme that was sequenced on constructability, and the two sequences were produced by different people at different times against different logic.

Which means the two disciplines disagree about what finished means at exactly the point where they have to hand over to each other. Construction reports an area as complete when the work in it is done; commissioning needs every system passing through that area, most of which run into other areas that aren't.

The documents are a gate

The as-built records and the manuals have the look of paperwork to be finished afterwards. The contract puts them before the tests.

As-built records are to be submitted before the Tests on Completion commence. Provisional operation and maintenance manuals, likewise, before the tests begin — and if the tests reveal an error in those manuals, the correction is at the contractor's risk and cost.

Then the final manuals are required before any Taking-Over Certificate is issued. And the standard fixes the level of detail by naming what the employer must be able to do with them: not just run the plant day to day, but take it apart, put it back together, tune it and mend it — with the spares needed to do so listed. That is a far higher bar than an operating guide, and it is the bar a certificate waits behind.

Read that list of verbs. Dismantle and reassemble isn't a description of a handover document. It is a description of a manual written by somebody who understood the machine.

Training can withhold a certificate

The third condition is the one that surprises people, and it is stated plainly.

Where the requirements call for training ahead of handover, the works stay incomplete — for handover purposes — until the training has actually happened. Not been scheduled, not been offered. Happened.

So a course sits on the critical path of a certificate. It needs a trainer, a syllabus, a room, and — the part that gets missed — the employer's own staff, who have to be recruited, released from other duties and present on the days offered.

And the wording is about delivery rather than about offering. Training that was scheduled and unattended hasn't been carried out, whoever's fault the empty room was.

That last dependency is outside your control and inside your obligation, which is the combination week 11 described. The remedy is the same: ask early, in writing, with dates.

All of it was generated years ago

Here is what makes this phase expensive, and it is a lifecycle observation rather than a commissioning one.

The as-built record is the accumulation of every change since the first drawing was issued — every one of the events week 23 followed through its three ages. The spare parts inventory comes from the vendor documents of week 16. The training content comes from the manuals, which come from the same vendor documents.

All of that information existed at the moment it was created and none of it was collected as it was made. So the finishing phase opens with a reconstruction: assembling, from files and memory, a record of what was built by people who have left.

Which is the same failure this track has followed since week 1, met for the last time, at the point where it is most expensive to repair and impossible to prevent.

And the people who could confirm it have gone. An as-built discrepancy found during commissioning is resolved by whoever is still on site, from drawings, rather than by the person who installed the thing and knew why it moved.

System design

Row five carries a distinction the clause makes and projects miss: the requirement is that training has been carried out, not that it was offered. An attendance record naming people is the evidence; an email offering dates isn't.

Record	Produced by	Required quality	Verified against	Feeds
System list with boundaries	Commissioning, early	States where each system starts and stops, so nothing sits between two	The services drawings	What gets tested as a unit
System-to-area matrix	You, in month one	Every system against every area it passes through	The drawings, not memory	What a system waits on
As-built records	The contractor, before the tests	Submitted before the Tests on Completion commence, then kept updated	What was actually built	Manuals · the certificate · operation
O&M manuals	The contractor, twice	Enough to dismantle and rebuild, not merely to run	The plant they describe	Whether a certificate can issue
Training delivered	The contractor, to named people	Attendance recorded, because the requirement is delivery not offer	Who was released to attend	Whether the works count as complete

Row one is the entry that has to exist before any of the others make sense. A system without a stated boundary produces items that belong to nothing, and those are the ones discovered during the tests rather than before them.

Practical insight

Build your system-to-area matrix in month one of construction, not in the month commissioning starts.

Your rows are systems, your columns are the construction areas, and a mark means that system passes through that area. It costs you an afternoon with a set of services drawings, and you can do it before a single system is energised.

Two things fall out of it immediately. Read across a row and you have every area that must be finished before that system can be tested — the constraint list nobody else holds. Read down a column and you have the systems that area is holding up, which turns your argument about area priority into an argument with evidence in it.

Then put three dates against every system: as-built submitted, provisional manual submitted, training delivered. They are contractual preconditions, they are invisible on a construction programme, and you will be the only person tracking them until the month they stop the certificate.

Which is worth doing even if nobody asks you to. The three dates cost you a column each and they are the difference between discovering a gate in the week it closes and knowing about it a year out.

Key takeaways

• Taking over requires the works to run, the as-built records and manuals to exist, and specified training to have been delivered.
• A plant that performs perfectly can fail to be complete because a manual is unfinished or a course hasn't been run.
• Construction is organised by place and commissioning by function, and neither breakdown can be derived from the other without a manual mapping.
• Progress by area and progress by system give different pictures, and a project reporting only the first is blind to the second.
• Commissioning runs from the supply inward, so a system can't be tested until whatever feeds it is live.
• The areas built last can contain the systems needed first, because the two sequences were produced against different logic.
• As-built records and provisional manuals are due before the Tests on Completion commence, not afterwards.
• An error found in the provisional manuals during the tests is corrected at the contractor’s risk and cost.
• Final manuals are required before any Taking-Over Certificate, and detailed enough to take the plant apart and rebuild it rather than merely run it.
• Training before taking over is a condition of completion, and it depends on the employer’s own staff being available.
• The as-builts, the spare parts inventory and the training content all derive from information created years earlier and never collected as it was made.

Records born here. The system list, with a boundary for each · the system-to-area matrix · as-built records, submitted before the tests · provisional and final O&M manuals, with their dates · the spare parts inventory · the training syllabus, the attendance record, and who was released to attend · the commissioning sequence, and what each system waits on.

What is coming next

With the systems running and the documents in, the works have to be demonstrated against a standard somebody wrote down years earlier.

That demonstration has a procedure, a set of consequences for failing it, and a second attempt with its own rules. It is also the point at which the difference between a test proving the works were built correctly and a test proving they perform as promised stops being a distinction and starts being two separate obligations with separate consequences.