Contingencydrawdown
Contingency is a budget, not a slush fund.
Contingency is money set aside for the risks you know are coming but cannot yet price. Managed well, it burns down in step with the work as those risks retire. Managed badly, it becomes a slush fund, or it runs dry with the riskiest work still ahead. The drawdown curve is where you see which is happening.
Two pots, not one
Contingency is money held inside the cost baseline for known-unknowns: the risks you can name but not yet price, like unforeseen conditions, rework, or price movement. The project team draws it down as those risks occur or retire. Management reserve is different money for a different problem.
Management reserve covers unknown-unknowns, scope no one has defined yet. It sits above the baseline and is usually the owner's to release, through a deliberate transfer, not the team's to spend. Blur the two and you lose the one thing they were built to make clear: who is on the hook when a change lands.
Contingency vs management reserve
They look alike on a budget summary and behave nothing alike. The difference is what each covers, where it sits, and above all who is allowed to spend it.
| Contingency | Management reserve | |
|---|---|---|
| What it covers | Known-unknowns inside the current scope | Unknown-unknowns, scope not yet defined |
| Where it sits | Inside the project cost baseline | Above the baseline, in the total budget |
| Who controls it | The project team, drawn down as risks retire | The owner or sponsor, released deliberately |
| How it moves | A drawdown against an identified risk | A formal transfer into the baseline when released |
How much should you carry?
There is no single right number. Contingency is sized to the risk, not set by habit. It commonly runs a single-digit percentage of construction cost, higher early when design and estimate uncertainty are greatest, and lower as the project matures and the big risks retire.
The figure matters less than the discipline behind it. A flat percentage carried unchanged from award to closeout is a warning sign on its own, because the risk it is meant to reflect never stops moving. A contingency that is reassessed as risks open and close is doing its job; one that just sits there is not.
A worked example
A $50M job carries a $3.0M contingency, about 6 percent. At 55 percent complete, $2.1M of it has already been drawn, leaving $0.9M. That is 70 percent of the contingency spent against 55 percent of the work: it is burning about a quarter faster than the job is progressing. Hold that rate and the balance reaches zero at roughly 79 percent complete, which leaves the last fifth of the job, and whatever risk it still carries, with no cover left to draw on. The single contingency line on the budget summary looks fine. The drawdown curve does not.
The drawdown curve
The dashed line is the planned drawdown, contingency falling in step with the work. The amber area is the actual balance, draining faster. Where it hits the floor, at about 79 percent complete, the contingency is gone, and the red tail is the stretch of work left carrying its risk with nothing behind it.
Drawdown should track retired risk
The healthy pattern is simple to state and hard to fake: the contingency balance should fall roughly in step with how much of the risky work is behind you. Draw it down as each identified risk occurs or passes, and the curve tells the truth about where the job stands.
The two failure modes are opposite and equally telling. A balance that outruns progress, like the example above, will run dry before the finish. A balance that barely moves late in the job is rarely luck; more often the real overruns are being absorbed quietly on other lines while the untouched contingency masks them. Either way, the drawdown curve surfaces what a single budget line hides.
The same $3.0M contingency, tracked month by month as it is drawn down, with the projection carried forward to the point it runs out. Reading the burn against the calendar and against progress is what turns a static budget line into an early warning.
Contingency Burndown
PODContingency burndown
Contingency used
Balance
Four ways it goes wrong
Spending it on convenience or quiet scope creep, rather than the risks it was set aside for, leaves nothing when a real risk lands. Contingency is earmarked money, not spare budget.
A contingency still near full late in a job is rarely great luck. More often the real overruns are being absorbed on other lines, and the untouched contingency is masking them.
Drawing contingency down faster than the job progresses means it runs out before the work does. The remaining scope then carries its risk with no cover left to draw on.
Spending management reserve as if it were contingency, or the reverse, breaks the line between team-controlled risk money and owner-controlled reserve, and hides who is actually absorbing a change.
A line in a spreadsheet vs a live curve
Contingency is only useful as a warning while there is still work left to protect. The difference between a number you reconcile at closeout and a curve you can steer by is entirely about when the drawdown gets read against progress.
- ·Contingency is a single line in the budget spreadsheet
- ·Drawdown is reconciled at closeout, not tracked against progress
- ·Contingency and management reserve are rolled into one number
- ·The uncovered tail only shows once it is already there
- ·POD reads the budget and cost data your job already produces
- ·The contingency line stays current against actual cost and progress
- ·A drawdown running ahead of the work shows every period
- ·The risk of running dry before the finish is visible while there is time
POD reads the budget and cost data your job produces and keeps the contingency line current against progress, so a drawdown running ahead of the work is visible every period. It pairs with budget vs committed, change order management, and the estimate at completion. Contingency touches all three.
The project controls library
The pillar guide: where contingency and reserve discipline sits among cost, schedule, and earned value.
The buy-out buffer that protects contingency before you ever have to draw on it.
An absorbed change with no change order is one of the quietest ways contingency drains.
A contingency projected to run dry before the finish is a forecast overrun in the making.
How budgets blow, and why a masked or exhausted contingency is often the first sign.
The progress measure a disciplined drawdown is judged against, period by period.
Contingency questions
What is contingency in construction?▾
Contingency is money set aside within the project budget to cover known-unknowns: risks that are anticipated in the current scope but whose cost is not yet certain, such as unforeseen conditions, rework, or price movement. It sits inside the cost baseline and is drawn down as those risks either occur or retire. It is earmarked risk money, not spare budget to reallocate at will.
How much contingency should a construction project have?▾
There is no single right figure; contingency is sized to the risk, not set by habit. It is commonly a single-digit percentage of construction cost, higher early when design and estimate uncertainty are greatest and lower as the project matures and risks retire. A fixed flat percentage carried unchanged through the job is a warning sign, because the risk it should reflect is always changing.
What is the difference between contingency and management reserve?▾
Contingency covers known-unknowns inside the current scope and sits within the cost baseline, drawn down by the project team as risks retire. Management reserve covers unknown-unknowns, scope not yet defined, and is held above the baseline, usually released by the owner or sponsor through a deliberate transfer. Spending one as if it were the other breaks the line between team-controlled and owner-controlled money.
What is contingency drawdown?▾
Drawdown is the planned reduction of the contingency balance as the job progresses and risks either occur or pass. A healthy drawdown tracks retired risk: the balance falls roughly in step with how much of the risky work is behind you. When drawdown runs ahead of progress the contingency will exhaust early; when it lags far behind, real overruns may be hiding on other budget lines.
Who controls contingency and management reserve?▾
Contingency is normally controlled by the project team and drawn down against identified risks as part of managing the work. Management reserve is normally controlled by the owner or program sponsor and released into the baseline only by a deliberate decision. Keeping the two authorities distinct is what makes it clear, later, who actually absorbed a given change.
How does POD help track contingency drawdown?▾
POD reads the budget and cost data your job already produces and keeps the contingency line current against actual cost and progress, so a drawdown running ahead of the work is visible every period rather than at closeout. Because the same platform holds the budget, the earned value, and the estimate at completion, the risk of running dry before the finish shows while there is still time to act on it.
POD reads the contingency against progress
Begin with the free budget tracker, then let POD read the budget and cost data already moving through your jobs, so a contingency burning faster than the work shows every period.