From Cost Plan to Final Account: How Design Management Holds the Number Through Delivery

Getting the cost plan right at submission is only half the exercise. The number then has to survive eighteen months of design development, authority conditions, client changes, subcontractor buyability and coordination reality. Most budget overruns are not estimating errors. They are the accumulated cost of design movement that nobody measured against the original basis.

Holding a cost plan through delivery is a design management function, and it rests on one mechanism: every design issue is reconciled back to the design basis that was priced.

In practice that means a gate at each design issue where the design manager compares what has just been issued against the register that sat behind the cost plan, and classifies each difference into one of three categories. Development, where the design has become more detailed within the priced intent and there is no cost effect. Change, where the design has moved beyond the priced intent and the cost effect must be quantified. Correction, where the design was wrong or incomplete at pricing, and the cost effect is absorbed or claimed depending on who owned the gap. Three categories, applied consistently, and the drift becomes visible while it is still small enough to do something about.

The second mechanism is a design decisions register with a commercial column. Most projects keep some record of decisions. Few of them record whether the decision cost anything, and almost none record it at the moment the decision is made. Yet that is precisely when the information is cheapest to capture and most useful. A decision to change ceiling type in the level three lobbies is a two-minute cost check on the day it is taken. Discovered eight months later during procurement, it is a variation with a program impact and an argument attached.

The third is the discipline of pricing the design program, not just the construction one. Every design deliverable has a date by which it must be resolved for the procurement it feeds. When a consultant slips a package by six weeks, the real question is not whether the design program has float. It is whether the subcontract can still be let against a properly defined scope, or whether it now has to be let with qualifications, which is the moment the cost plan quietly stops being reliable. A design manager tracking deliverables against procurement dates sees that four months before a quantity surveyor sees it in a cost report.

What ties all three together is that they are early warning systems rather than reporting systems. A monthly cost report tells you what has already happened. A design manager reconciling issues, decisions and deliverables tells you what is about to happen, at a point where the options are still cheap: revise the design, absorb the change, or go back to the client with a documented case. All three are viable. Discovering the same movement at procurement usually leaves only the expensive option.

For a head contractor carrying design risk on a design and construct contract, this is the whole ball game. The contract transfers the consequences of design movement onto the builder. The only real defence is a system that measures the movement continuously and forces a decision while a decision still helps. That system is design management, and it should not switch off the day the cost plan is accepted. That is the day it starts to matter most.

Emanuel Solomovic has spent more than twenty years as a design manager on projects where the gap between the cost plan and the final account was decided long before anyone opened a final account. His work centres on integrated systems that keep design decisions, deliverables and commercial exposure visible in one place, so that drift is caught early rather than explained late.