The punch list is a contract choice.

Four lines

Set them side by side and the differences turn out to be structural rather than semantic.

The FIDIC line. A Taking-Over Certificate is issued when the works are complete and the Tests on Completion have been passed — and outstanding work is listed on the certificate itself. So the boundary explicitly carries a schedule of what isn't done, and completion and a list of incompleteness coexist by design.

The common law line. Substantial completion means the work can be used for the agreed purpose. The contract law literature holds that firmly apart from performance, which means whole fulfilment of the obligations. Two different states, and the gap between them is where the remaining work lives.

The NEC line. Completion is a defined event, tied to what the scope says was to be done. Taking over is a separate act, following within two weeks — and the client may state in advance that it won't take over before the completion date at all. So completion and possession are deliberately decoupled.

The line drawn by behaviour. Where an employer occupies the works and begins using them, the works may be deemed complete whatever any certificate says. That one isn't chosen. It happens.

The name that is in none of them

There is a fifth term that process and energy projects use constantly, and it appears in no contract.

Mechanical completion — the point at which construction hands over to commissioning — is a working concept rather than a contractual one. Across eighteen construction and contract references it doesn't appear once, in any spelling, and neither do its relatives: systems completion, mechanical acceptance, ready for commissioning.

Which matters practically. A project can run a mechanical completion process, hold walkdowns against it, issue certificates for it, and none of that touches the contractual boundary at all. Two completion regimes run in parallel, one operational and one contractual, and the dates they produce are unrelated.

The confusion this creates is worth anticipating. A commissioning manager announcing mechanical completion has said something true and precise about the plant. A commercial manager hearing it has heard something about entitlement. Neither of them is wrong and they are discussing different events.

What actually moves at the line

Whichever line applies, crossing it isn't a milestone. It is six transfers happening at once, and a project that treats it as one event will miss five of them.

Responsibility for care of the works passes. Insurance obligations change hands. Delay damages stop running. The defects period starts, so the clock on your remaining liability begins. Part of the retention becomes due. And access changes character — from a site you occupy to a site you visit.

Those six need not move together, and across the four families they don't. A form separating completion from taking over separates some of them by a fortnight; a boundary reached by occupation may move care and insurance without moving anything financial.

That last case is the one that catches people. An employer who starts using part of the works has changed your risk position and possibly your insurance obligations, and has done it by walking in rather than by issuing anything.

So the useful question at handover isn't whether the project is complete. It is which of the six have moved.

Why finished on time doesn't compare

One consequence is worth stating because it affects how the industry talks about itself.

The same physical state — the same building, the same plant, the same list of small things outstanding — is complete under one form and not complete under another. A job that hit its date under a substantial completion test might not have hit it under a regime requiring tests to be passed first.

Which means comparing projects, or contractors, on finished-on-time across contract families is comparing different events that share a name. It is the same defect this track met in week 12: one word, two meanings, no field recording which is in use.

Which makes benchmarking across contracts a trap rather than a comparison. Two projects reporting the same completion date under different forms have handed over different quantities of unfinished work, and the one that looks worse on a punch list may have transferred less.

Which line leaves the most behind

Put the four together against the quantity of unfinished work at the moment of transfer and they order themselves.

A line drawn at usability leaves a good deal behind, because usable and finished are different standards. A line requiring tests to be passed leaves less, because passing a test is a harder gate than being usable. A line reached by occupation leaves the most of all and records none of it, because nobody scheduled the event that triggered it.

None of that is a ranking of contract families. Leaving work outstanding at handover can be the sensible arrangement — an employer who needs the asset gains nothing from waiting for the last handle. What matters is knowing, before the month it happens, how much your form intends to leave and therefore how large the list is going to be.

And the answer was fixed before anybody could weigh it against the finishing team's capacity. A form that leaves a great deal behind suits an owner who wants early use and burdens a contractor who has already demobilised, and those two facts were never set against each other in the room where the form was chosen.

System design

Row three is the one that changes how handover is discussed. A project that can say which of the six have moved is having a different conversation from one arguing about whether a certificate should be issued.

Record	Produced by	Required quality	Verified against	Feeds
Completion definition	You, from the contract	Extracted and dated, months before it matters	The clause it came from	What everybody means by complete
Triggering event	The same extract	Names the event, not the date it is expected on	The contract wording	When the six transfers begin
The six transfers	You, one line each	Each with the moment it moves under this form	The clauses that move them	Care · insurance · damages · money
Forecast outstanding list	Your team, eight weeks out	A forecast rather than a survey, so there is time to act on it	What is actually outstanding on the day	Whether the list is a plan or a negotiation
Operational completion record	Commissioning, in parallel	Kept separately, because its dates are unrelated to the contract’s	The systems it covers	Start-up sequence, not entitlement

Row five exists because two completion regimes run at once and the industry uses one vocabulary for both. Keeping the operational record separate isn't bureaucracy; it prevents a walkdown certificate being read as a contractual position.

Practical insight

Find your completion definition and read it in the month before it starts to matter, rather than the month it does. You will need half an hour and the contract you already have.

You are looking for four things: what event triggers your certificate or notice, whether outstanding work may be listed at that point, what happens to each of the six transfers, and whether taking over is the same act or a separate one. Half a page of notes and you will know more about your own handover than anybody else on the job.

Then ask the one question that follows from it: on the day this is issued, what will still be outstanding? Ask your own team eight weeks out, not as a challenge but as a forecast, and write down what comes back to you.

What you have is the punch list before anybody calls it one. Produced eight weeks early it is a work plan and you have time to shorten it. Produced on the day, by somebody walking round with the other party, it is a negotiation you didn't prepare for.

Key takeaways

• Complete isn't one thing, and four families of contract draw the finishing line in four different places.
• Under FIDIC, taking over follows tests being passed, and outstanding work is listed on the certificate itself.
• At common law, substantial completion means usable for the agreed purpose and is held apart from performance, which is whole fulfilment.
• Under NEC, completion is a defined event and taking over is a separate act, which the client can decline before the completion date.
• A fourth line is drawn by behaviour: occupation and use can deem the works complete whatever a certificate says.
• Mechanical completion appears in no contract in the pool, in any spelling, so an operational completion regime and a contractual one run in parallel with unrelated dates.
• Crossing the line is six simultaneous transfers — care, insurance, delay damages, the defects period, retention, and the character of access.
• Those six need not move together, and across the four families they don't.
• So the useful question at handover is which of the six have moved, rather than whether the project is complete.
• The same physical state is complete under one form and not another, so finished-on-time doesn't compare across families.
• A line at usability leaves the most work outstanding; a line requiring tests leaves less; a line reached by occupation leaves the most and records none of it.

Records born here. The completion definition, extracted and dated · what event triggers the certificate or notice · whether outstanding work may be listed at that point · the six transfers, each with the moment it moves · whether taking over is the same act or separate · the forecast list of what will still be outstanding, made eight weeks out.

What is coming next

Whichever line applies, something is left behind when it is crossed, and it goes onto a list.

That list is the last document on the project everybody reads. It decides when money is released, it is written by whoever is walking round, and the question underneath every line of it is the one nobody has agreed in advance: what counts as finished.