Every project has a budget before it has a shovel in the ground, and somebody has to own that number all the way through. On a lot of jobs that falls to the contractor by default, whether it is written into the contract or not, because you are the one who sees the real cost of every decision as it happens.
Cost planning through each project stage is what keeps that ownership from turning into a liability. The number gets checked and updated as the job moves, instead of being set once and defended forever.
Cost planning is not a one-off exercise
A budget set at tender stage and never revisited is not a budget, it is a wish. As the job moves from early stages through detailed information to construction, the cost picture needs revisiting at each stage, not just at the start and the end. Build cost checks into your own programme the same way you build in delivery dates.
Whether the job follows RIBA Plan of Work stages or your own set of gateways, the principle is the same. Each time the information gets more detailed, the cost plan should get more detailed with it.
What cost planning through each project stage looks like
Here's how the budget typically needs to develop as a job moves forward:
- Brief and feasibility. A range, not a figure. Based on what's known about size, use and site, with the unknowns written down alongside it.
- Concept or scheme drawings. The main elements can now be measured roughly. The budget becomes an elemental cost plan with allowances for everything not yet designed.
- Detailed design. Most elements are drawn. Measure them properly and replace allowances with measured quantities wherever you can.
- Tender and contract. The measured, priced estimate becomes the baseline. Provisional sums are named and limited to what genuinely can't be priced yet.
- Construction. The baseline is tracked against valuations, variations and instructions every month until final account.
At every step, the new figure should be reconciled with the last one. If the budget moved, somebody should be able to say which elements moved it and why.
NRM2 gives you a shared language
Whatever internal method you use to build the numbers, structuring cost information along NRM2 lines means everyone reading the budget, client included, is looking at the same categories in the same order. That alone stops a lot of arguments before they start, because nobody is comparing two different ways of slicing the same job.
It also makes stage-to-stage comparison possible. If the substructure figure has grown between the scheme cost plan and the tender estimate, a consistent structure shows you that at a glance. Two differently organised documents would just show you two different totals.
Nobody minds a rising cost as much as they mind being surprised by one.
Where budgets actually fall apart
It is rarely one dramatic overspend. It is late instructions that get built without a proper price first, provisional sums that get treated as spent money rather than placeholders, and small variations that never get logged until final account. Track every change against the budget as it happens, not in a batch at the end of the job.
Say a client adds an extra rooflight during construction. On its own, it's a small change. But if it isn't logged, measured and priced when it's instructed, it joins a pile of other small changes that arrive at final account together, by which point nobody remembers who asked for what. Logged at the time, it's one line in a running record. Left, it's part of an argument.
Keep the client in the loop, properly
A client who only hears about cost movement at the final meeting has every reason to distrust the number. Regular, plain updates on where the budget stands, and why, keep the relationship workable even when the news is not good.
A short monthly cost report is usually enough: the original budget, approved changes, pending changes, and the current forecast. Four numbers and a sentence or two of explanation each. It doesn't need to be elaborate. It needs to be regular.
The timing matters as much as the format. Tell the client about a likely cost increase when the decision that causes it is still being made, not once it's built. A client choosing between two finishes can weigh the cost difference. A client told about it afterwards can only argue about it. Early information turns cost movement into a choice the client made, rather than a bill they received.
Holding a budget properly through a job is not glamorous work. It is checking, logging and explaining, stage after stage, so that the final account matches what everyone expected rather than fighting over what happened along the way.
The job is far easier when each stage's budget sits on measured quantities rather than rough rates. We measure drawings to NRM2 at whatever stage they're at and price them on current UK rates, local to the job, for a fixed fee agreed before we start. See a sample estimate to get an idea of how we structure a budget from day one, or read our explainer on what cost planning actually means for a contractor.
One check at every stage gate
Each time the drawings move up a stage, ask: can I explain the difference between this budget and the last one, element by element? If you can, your cost planning through each project stage is doing its job. If the total has moved and you can't say where, stop and find out before anything else gets committed, whether that's an order, a subcontract or a price to the client. That gap won't close on its own, and it only gets more expensive the longer it's left.