A project budget isn't something set once and then left alone. A number gets carried through months of design and into construction, during which the project becomes far more specific and the market moves. Keeping that number meaningful is ongoing work, and it's what separates a budget that guides decisions from one that simply gets discovered to be wrong.
The project budget and the construction budget, kept in view together
As described in why a project budget should exist before design begins, the project budget covers the whole investment: construction, professional services, approvals, investigations, contingency and other project costs. The construction budget is the portion available for the physical work. As a project moves toward construction, the construction budget is the number the developing design is tested against, while the project budget keeps the larger picture honest.
An estimate is a conversation with the design
An estimate isn't a single event. It's repeated as the project develops, and each version rests on more specific information than the one before:
- Early concept
- Relies on area, an assumed level of quality and comparable work.
- Gives a broad range: enough to test whether the scope and the project budget are compatible at all.
- Developing design
- Relies on defined systems, assemblies and major selections.
- Gives a narrower range, and shows where the money is concentrated while decisions can still change.
- Resolved documents
- Relies on specific quantities, details and specifications.
- Gives a price that reflects what will actually be built, as described in buildable information.
- Procurement and buyout
- Relies on quotes from trades and suppliers for the actual work.
- Provides market-based pricing for the defined work, and exposes changes from earlier estimates.
The value of repeating the process isn't a more impressive number. It's that every update arrives while there is still room to respond.
When the estimate and the construction budget diverge
Sooner or later they usually do. What matters is the response. The weak response is across-the-board cutting, which tends to degrade the whole project to recover a figure. A stronger one treats the gap as a set of decisions: adjust area or scope, change a system or assembly, rebalance parts of the project budget, phase the work, or consider a different level of investment. Those decisions are made against the priorities the project has established, as described in What Happens When Everything in Your Project Feels Important?, while the choices are still information.
The number isn't set once. It's kept in step with the design.
Allowances and contingency, handled openly
Two tools carry uncertainty through a project, and both need to be visible. An allowance is a placeholder amount for something not yet selected or fully defined. It should be tracked and then closed out as the real selection is made, so the owner can see whether it came in over or under. Contingency is an amount held for uncertainty and risk that cannot yet be precisely resolved. It's most useful when it's spent deliberately and reported, not drifted into. Practices vary between teams, which is why it's worth asking how each is handled.
One number, shared
The most practical protection is that everyone is working from the same current number and knows what has changed since the last one: the owner, the architect and the builder. Market conditions, availability and lead times can all move a price, and a project is better served when those shifts are raised early than when they surface at the end.
Questions to ask about the estimate
- How often will the estimate be updated, and what will each update be based on?
- How are allowances tracked and closed out?
- How is contingency held and reported?
- What happens when the estimate and the construction budget don't match?