Every project budget has a line that makes people nervous. It sits near the bottom, it doesn't buy any lumber or concrete, and the first time a number gets tight, someone asks whether we really need it.
That line is contingency. After more than twenty years in construction and real estate development, I've come to think it's one of the most honest numbers on the page, as long as everyone understands what it's for.
Contingency is not a cushion for bad estimating
Padding is when you quietly inflate every line item so you never have to explain a miss. It hides risk inside the numbers, which means nobody can see it, manage it, or make good decisions about it.
Contingency is the opposite. It says out loud: we have looked hard at this project, we have priced what we can see, and there are still things we cannot know yet. Here is the amount we're setting aside for those things, in one visible place.
That difference matters. A padded budget feels safe until it isn't, and then nobody knows where the slack went. A budget with a clear contingency gives the owner and the builder something to manage together.
Size it to the unknowns, not to a habit
A lot of people pick a contingency percentage because it's the number they always use. That's better than nothing, but it skips the real question: how much don't we know about this particular project?
A few honest questions get you closer:
- How complete is the design? Early-stage numbers built on concept drawings deserve more room than numbers built on finished construction documents.
- What's behind the walls or under the ground? Renovations, older buildings, and sites without good soils information carry hidden conditions that new work on a clean site may not.
- How stable are prices and lead times right now? When materials or key equipment are hard to predict, the budget should admit it.
- How many decisions are still open? Every finish, fixture, or system that hasn't been chosen is a small unknown.
The answer won't be a perfect number. It doesn't need to be. It needs to be a number you can explain.
Decide who controls it before you need it
The worst time to figure out who gets to spend contingency is in the middle of a problem.
Before the project starts, agree on a few things in plain words: which contingency belongs to the owner (for their own changes and decisions), which belongs to the builder (for risks inside the builder's scope), how a draw against it gets approved, and how quickly. Write it down. It takes an hour and prevents weeks of arguments later.
Spend it out loud
Contingency only builds trust if people can see it move. Every time some of it gets used, log what it was for, how much, and what's left. Share that running balance at regular project meetings, not just at the end.
When the owner can see that the contingency covered a real surprise, like an unexpected site condition or a price jump on a long-lead item, the conversation stays calm. When contingency disappears without a trail, even honest spending starts to look like a blank check.
Give back what you don't use
If the unknowns turn out smaller than expected, that's good news, and it should be treated as good news. Agree up front on what happens to leftover contingency, whether that's returning it to the owner, sharing it, or moving it to something the project actually needs.
A builder who returns unused contingency, or shows exactly where it went, earns more trust than one who comes in "on budget" with no explanation. People remember that on the next job.
The real point
Contingency isn't pessimism. It's the part of the plan that admits the world is uncertain and decides ahead of time how you'll handle it together. Projects rarely go sideways because something unexpected happened. Something unexpected always happens. They go sideways when nobody planned for it and everyone has to argue about money at the worst possible moment.
Put the unknowns in one visible line, agree on the rules, and spend it in the open. That's how hard projects stay calm.
