Delivery is the stage nobody writes about, which is odd, because it is where a project either becomes the thing it was meant to be or quietly fails to. The reason for the silence is that it is unglamorous and that by the time it arrives everyone involved is tired.

That fatigue is the central problem. Attention falls away exactly when the remaining work is least forgiving. The decisions left are small, numerous and interdependent, and each one is individually too minor to escalate. A building is not usually spoiled by one bad decision at the end. It is spoiled by two hundred small ones taken by people who were ready to be finished.

The second difficulty is that delivery is when every assumption made years earlier gets tested simultaneously. Things that were compatible on paper meet each other physically for the first time. Most of them fit. The ones that do not are discovered in an order determined by the build rather than by importance, and they have to be resolved against a completion that is no longer movable.

The third is that the developer's leverage is at its lowest precisely when the need for it is high. Earlier in a project almost everything is still adjustable. At delivery, most parties have discharged most of their obligations and the remaining work sits with whoever is still there. What the role has at that point is relationships and credibility accumulated earlier, which is a real argument for how you conduct yourself in the stages before.

The fourth is an obligation that outlives the handover entirely. Whoever operates the building afterward sat in none of the meetings and inherits every decision taken in them. Some of those decisions are elegant on site and punishing to live with, and the developer will never meet the person who discovers that. Thinking forward to somebody you will never meet is unrewarded and invisible in the finished work, and I think it is a fair test of whether the job was done properly.

My arguable position is that delivery deserves the same seniority as acquisition, and almost nowhere gets it. The people who decide what a project is are rarely the people present when it becomes it, and the handover between them is where quality is lost. The standard objection is that senior attention is scarce and better spent where the leverage is largest, which is early. I think that argument confuses leverage with consequence.

The honest limit is that I have not solved this on every project. Staying properly engaged through a stage that is long, granular and unrewarding is genuinely difficult, and I have been better at it on some buildings than others. It is the part of this work I would most like to be more disciplined about.

None of it is done alone. The construction manager, the superintendent and the commissioning agents carry the substance of this stage, and the developer's job is to remain present, keep the standard where it was set, and be reachable for the decisions that only they can take.