It grows by walking, shrinks by inspection.

Two different things on one list

The standard forms treat outstanding work and defects together — there is a sub-clause covering the completion of the one and the remedying of the other, as a single obligation.

For remedy purposes that coupling is sensible: both end with somebody returning to do work, and the contract cares about the return rather than the reason. On the ground they aren't the same thing at all.

Outstanding work was never done. A skirting not fitted, a valve not installed, a room not painted. It has a quantity, it can be priced, and somebody knew it was missing.

A defect was done and is wrong. It has no quantity of its own, it may require removing work already paid for, and whether it is a defect at all can be the argument rather than the fact.

A list that doesn't distinguish them can't be managed, because the two need different people, different lead times and different conversations. And separating them afterwards is harder than it sounds, since an entry reading door not right could be either, and the person who wrote it has moved on.

The remedy is also a different person in each case. Outstanding work needs a foreman and a crew; a defect needs somebody who can decide whether the specification has been met. Sending both to the same meeting means one of them waits.

The list has a price

Here is the mechanism that surprises people, and it turns the list from an administrative nuisance into a number.

Where a part of the works is taken over, any reduction in delay damages is calculated on the value of that part — excluding the value of outstanding work and of defects still to be remedied.

Read that twice. The relief you get for the employer having taken something over is reduced by whatever remains on the list against it. So every item isn't merely a task: it is a deduction from the benefit of having handed over.

Which changes what a punch list is for. It is a schedule of work, and it is also a running valuation of how much of the handover hasn't yet counted. Taking over in parts has a later week of its own; what matters here is that the list carries a price and nothing on the project produces that figure.

Care splits inside one building

The second consequence is stranger and it is easy to miss.

At the boundary, responsibility for the care of the works passes to the employer. But the contractor keeps responsibility for the care of any work that was outstanding at that date, until that work is completed.

So the building is in two custodies at once. The employer holds the structure; you hold the twenty-three things on the list, inside it. If one of them is damaged before it's finished, it was in your care — in a building whose access you no longer control, with other trades and the employer's own people moving through it.

That's a real exposure, and it's managed by closing items rather than by arguing about it. Every entry removed is a piece of care handed back, which is the one argument for closure that doesn't depend on anybody agreeing with you.

And the reporting doesn't stop

One more thing survives the boundary, and teams demobilise without noticing that it has.

The progress reporting obligation runs to the date of completion — or, where outstanding work is listed in the taking-over certificate, until that work has been completed.

Which is a small clause with an awkward shape. The obligation is triggered by the very thing that makes it hard to discharge: a list long enough to be worth listing keeps the reporting alive for however long it takes to close, and the reporting is done by the reduced team that is closing it.

So the monthly report continues after handover, produced by whoever is left, about a list rather than about a programme. Nobody plans for that report. It is produced late, by somebody who has inherited it, and it is the last formal record the project makes.

Who is allowed to close an item

The final asymmetry is about standing, and it decides the rate at which the list moves.

Adding requires only an opinion. Closing requires somebody whose acceptance binds the employer — and different individuals with that standing accept differently, so the closure rate depends on who attends rather than on what has been done.

Which produces a measurable and slightly absurd effect: the list shortens faster in the weeks when a particular person is available. That isn't a criticism of them. It's what happens when a document is closed by judgement and no entry carries a written test for what finished means.

Adding that test costs a clause and nothing in the process asks for one. An entry reading make good architrave to room 214, to match adjacent can be closed by anybody who can look at it. An entry reading architrave poor requires the person who wrote it, and their diary.

And it collides with week 19's round trip. The list is longest exactly when the site is thinnest, because demobilisation began at the boundary and the people who could close items quickly are the people who have gone.

There is a cheap mitigation and it belongs to whoever writes the entries. An item worded so that its completion is observable can be closed by anybody with standing; an item worded as a judgement can only be closed by the person who formed it. The wording is chosen at the moment of inspection, by somebody who has no reason to think about who will close it.

System design

Row three exists because the figure is already being used against you and is held by nobody on your side. A punch list priced from the rates takes an afternoon and produces the only number that connects closing items to money.

Record	Produced by	Required quality	Verified against	Feeds
The list as issued	The inspecting party, at the boundary	Dated and kept as issued, separate from every later version	The works as they stood	What was disputed at handover
Outstanding work, separated	You, on day one	Never-done items held apart from done-and-disputed ones	The entry itself, while it is fresh	Two workstreams at two speeds
Value per item	You, from the rates	Priced, because the damages calculation already uses these figures	The bill the work came from	What the list is costing in relief
Attendance required	You, one column	Names who must be present to close, so chases can be batched	Who actually closed items last month	The rate the list moves at
Care position	The contract, read once	States which open items remain in your care and where they sit	The taking-over certificate	Exposure while the list is open

Row four is the cheapest thing in the table and it changes the rate the list moves at. Sorting by who must attend converts a long list of individual chases into a short list of appointments, which is the only lever available once the site has thinned.

Practical insight

Split your list into two on the day it is issued, before anybody has argued about anything.

One for work that was never done, one for work done and disputed. Your first list is a production problem with a quantity and a crew. Your second is a technical argument needing a specification reference and somebody senior. They move at different speeds, and mixing them means your whole list moves at the speed of the slower one.

Then add two columns nobody will give you: what each item is worth, and who has to attend to close it. Your values give you the number the damages calculation is already using and nobody on your side is holding. Sort your attendance column and you will find that eleven items need the same person — which converts eleven chases into one appointment you can actually get.

Do it in your first week. A fortnight later the list has been circulated, quoted and argued over, and splitting it then looks like a party repositioning rather than a planner organising — same act, different reading, entirely because of when you did it.

Key takeaways

• Adding an item costs a walk and a sentence; closing one costs an inspection by somebody with standing.
• Those are asymmetric acts, so the list lengthens for months before it shortens, by mechanism rather than by workmanship.
• The standard forms couple outstanding work and defects under one remedy, and on the ground they are different things.
• Outstanding work was never done and has a quantity; a defect was done, is wrong, and whether it counts as a defect can itself be the argument.
• A list that doesn't separate them moves at the speed of its slower half.
• Where a part is taken over, the reduction in delay damages excludes the value of outstanding work and defects.
• So every item on the list is a deduction from the benefit of having handed over, and the list is a running valuation as well as a schedule.
• Care of the works passes at the boundary; care of work outstanding at that date stays with the contractor until it is done.
• The building is therefore in two custodies at once, and closing items is how care is handed back.
• Progress reporting continues past handover until the listed outstanding work is complete, and nobody resources that report.
• Closure rate depends on who is available to accept, and the list is longest exactly when the site is thinnest.

Records born here. The list as issued at the boundary, dated · outstanding work separated from defects · the value of each item · who must attend to close each one · the date each item was added and by whom · the care position for items still open · the post-handover reports, until the list is closed.

What is coming next

All of this assumes a building that is finished enough to be walked and judged. On a plant, something else has to happen first.

The works have to be made to run, and running is tested by a discipline that counts in systems rather than in areas, works to a sequence that inverts the one construction used, and measures completion by whether something functions rather than by whether it is built.