The Cost Plan Is a Design Document: What Your Estimator Actually Needs From Design Management

Every cost plan submitted to a client is a statement about design, whether anyone admits it or not. The estimator has priced something specific: a defined set of drawings at a particular revision, a defined specification, and a long list of assumptions about what sits inside the scope and what sits outside it. If none of that has been written down, the submission is a number without a subject. And when the final construction cost lands well above it, the dispute that follows is never really about rates. It is about what was in the scope.

This is where design management earns its seat at the cost planning table. Before a cost plan leaves the building, a design manager should be able to hand the estimating team three things.

The first is a design basis schedule: every document that was priced, listed by discipline, drawing number, revision and date. Not the DA package, but the actual register, frozen at the moment of pricing. When a consultant issues a revision two weeks later, the design manager can tell you in an afternoon whether it changed the money.

The second is an inclusions and exclusions statement written in design language rather than commercial language. “Facade access system excluded” is a commercial exclusion that means nothing to an architect. “Facade maintenance strategy not yet resolved; no BMU, davit or anchor provision priced” tells the design team exactly what they have to close out, and by when.

The third is an assumptions register. Every estimator fills gaps. On a live project they fill dozens of them, quietly, under time pressure, because the alternative is not submitting. The question is whether those assumptions are recorded and tested by someone who understands the design, or whether they sit undocumented in a spreadsheet until they turn into a variation. Slab thickness assumed at 200mm pending structural confirmation. Services zone assumed at 450mm with no coordinated section to prove it. Substation location assumed within the site boundary. Each one is a design decision made by someone whose job is not design.

For a head contractor, the commercial logic is direct. Design definition and cost certainty move together. A cost plan built on a properly recorded design basis lets you price risk deliberately instead of absorbing it by accident, and it gives you a documented position when the client’s brief evolves, as it always does. Without it, every subsequent change becomes a negotiation you enter without evidence.

The other benefit is quieter but worth more. When the design basis is explicit, the design team can see precisely which decisions are holding the cost plan open. That converts a vague instruction to progress the design into a short, ranked list of things that must be resolved before the number can be relied upon. Design programmes built around cost-critical decisions close gaps faster than design programmes built around drawing issue dates.

A cost plan is a forecast. Forecasts are only as good as the definition of what is being forecast. Design management is what supplies that definition, and it is the difference between a budget that holds and a budget that merely looked convincing on the day it was submitted.

Emanuel Solomovic has spent four decades working across architecture and design management, and has consistently argued that the cost plan and the design register are two views of the same thing. His approach is to make the design basis behind every submitted number explicit, recorded and testable, so that when a project changes, the conversation starts from evidence rather than recollection.