Contingency

Definition — what it is

A contingency is a sum of money held in reserve within a project's budget or contract to cover the cost of risks that are expected to occur in aggregate but cannot be identified or priced individually at the outset. It exists because no estimate is perfect and no project runs exactly as planned: quantities differ from takeoff, conditions surprise, minor scope gaps emerge, and coordination costs arise, and the contingency is the deliberate acknowledgment of that uncertainty expressed as a funded reserve rather than a hope. A contingency is not an allowance (which covers specific deferred scope) and not padding or profit (which is not meant to be spent); it is a risk reserve, drawn down only as identified risks materialize, and its defining discipline is the governance of who may authorize its use and for what. There are typically distinct contingencies with different owners — an owner's contingency, a design contingency, and a contractor's or general conditions contingency — and confusing whose contingency covers what is a persistent source of dispute.

Also known as: Contingency Reserve, Management Reserve, Risk Reserve, Buffer, Owner Contingency, GC Contingency

Why it matters — what it protects

The contingency is the difference between a budget that survives contact with reality and one that fails at the first surprise. Every project encounters costs that were not specifically estimated — a differing condition, a quantity overrun, a small unforeseen scope gap — and without a reserve to absorb them, each one becomes a crisis, a change order fight, or an overrun. The contingency is the honest recognition, funded up front, that some unknown cost is certain even though its specifics are not, and a project priced with no contingency is a project that has hidden its risk rather than managed it.

Its governance is what makes it a control rather than a slush fund. A contingency with no rules about who can draw it, for what, and with what documentation is quickly consumed on ordinary cost overruns and scope creep, leaving nothing when a real risk hits. The discipline that matters is not the size of the reserve but the authorization and tracking of every draw — because a contingency spent early and casually offers no protection later, when it is most needed.

Whose contingency covers a given cost is a recurring and consequential dispute. An owner's contingency typically covers owner-driven scope additions and risks the owner retains; a design contingency covers the cost of design development and errors within the designer's responsibility; a contractor's contingency covers the contractor's own estimating and coordination risk. When a cost arises and the parties disagree about which contingency should absorb it — or whether it should be a change order against the owner instead — the money and the responsibility are both at stake, which is why the definition and ownership of each contingency must be explicit.

The draw-down pattern of the contingency is one of the truest early signals of project health. A contingency being consumed faster than the project is progressing is a leading indicator that the estimate was optimistic, the design was incomplete, or execution is struggling — often visible in the contingency burn long before it shows in the final cost report. Executives and sureties watch contingency depletion because it reveals trouble while there is still time to react, whereas a final overrun reveals it only when it is too late.

Lifecycle — how it moves

1. Sizing during estimating

   The contingency is set as a percentage of cost or through a risk-based analysis, informed by the design's completeness, the project's complexity, and historical performance. Setting it too low hides risk; too high inflates the price and invites the reserve to be spent because it is there.

2. Definition and ownership

   The contract or budget defines which contingencies exist — owner, design, contractor — what each covers, and who may authorize a draw. Ambiguity here is the root of most later disputes about who absorbs a given cost.

3. Carried in budget or contract

   The contingency is held as a distinct line, visible and separate from the estimated cost of work. Burying it inside line items destroys the ability to track its draw-down and defeats its purpose as a governed reserve.

4. Risk materializes

   A specific unforeseen cost arises — a differing condition, a quantity overrun, a coordination gap. The event is identified and priced, and the question becomes whether it is a legitimate contingency draw or a change order against another party.

5. Authorization of the draw

   The draw is approved by whoever holds authority over that contingency, with documentation of the risk it covers. This governance step is what separates a controlled reserve from a fund quietly consumed by ordinary overruns.

6. Draw-down and tracking

   The approved amount is drawn, the remaining balance is updated, and the draw is tracked against the risk it covered. The running balance and burn rate are monitored as a health indicator.

7. Periodic reforecast

   As the project progresses and risks resolve, the adequacy of the remaining contingency is reassessed against the risks still open. A depleting reserve against unresolved risk triggers management action while there is still time.

8. Release or reconciliation

   Unused contingency at completion is released — returned to the owner, or recognized in the contractor's margin depending on the contract type. How the unused reserve is treated is defined by whether the contract is cost-plus with a guaranteed maximum, lump sum, or another form.

Anatomy — the data it carries

Contingency type and owner

Owner, design, or contractor contingency, and who controls it. Determines what it covers and who authorizes draws — the field that prevents whose-contingency disputes.

Contingency amount

The reserve carried, as a value and often a percentage of cost. Its size reflects the assessed risk and the completeness of the design.

Basis for sizing

How the amount was derived — a percentage convention or a risk-based analysis. Supports the reserve if its adequacy is later questioned.

Scope of coverage

What risks the contingency is meant to absorb and, importantly, what it is not — so it is not consumed on costs that belong in a change order or another party's contingency.

Authorization rules

Who may approve a draw, at what thresholds, and with what documentation. The governance that keeps the reserve a control rather than a slush fund.

Draw log

Each draw with its date, amount, the specific risk it covered, and the authorizer. The record that makes the reserve auditable and its depletion explainable.

Remaining balance

The current unspent reserve. The number watched against remaining risk to judge whether the project is still protected.

Burn rate

The pace of draw-down relative to project progress. A burn faster than progress is an early warning of an optimistic estimate or troubled execution.

Open-risk register linkage

The identified risks still outstanding that the remaining contingency must cover. Reconciling balance against open risk is how adequacy is judged.

Reforecast adjustment

Periodic reassessment of whether the remaining reserve is adequate, feeding the cost-to-complete and the projected final cost.

Release treatment

How unused contingency is handled at completion — returned to the owner or recognized as margin — per the contract type.

Status

Funded, partially drawn, depleted, or released — the state of the reserve relative to the project's remaining risk.

Failure modes — how it breaks

Spent as a slush fund

With no authorization rules, the contingency is drawn on for ordinary overruns and minor scope creep as they arise. It is exhausted at 60 percent completion, and when a genuine unforeseen condition hits later, there is no reserve left to absorb it.

Wrong contingency charged

A cost that should have been a change order against the owner, or drawn from the owner's contingency, is quietly absorbed by the contractor's contingency instead. The contractor depletes its own reserve for a cost the owner should have borne, and the mischarge is discovered too late to recover.

Buried and untrackable

The contingency is spread across line items rather than held as a distinct reserve. Its balance and burn rate cannot be tracked, so the earliest warning signal of trouble — accelerating draw-down — is invisible until the money is simply gone.

Sized to hit a target price, not the risk

The contingency is trimmed to make the bid competitive rather than to match the actual risk of the project. The underfunded reserve runs out early, and the shortfall surfaces as an overrun the project was never funded to absorb.

Never reforecast against open risk

The remaining balance is tracked but never compared to the risks still open. A reserve that looks healthy in dollars may be dangerously thin against the unresolved risks ahead, and nobody notices until a risk lands with no coverage.

Unused reserve treated wrongly at closeout

On a guaranteed-maximum-price contract, unused contingency that belongs to the owner is absorbed as margin, or vice versa. The release treatment was never clarified against the contract type, and the closeout produces a dispute over who owns the leftover reserve.

Metrics — how it is measured

Contingency burn rate

Rate of draw-down relative to project progress. A burn outpacing progress is the earliest quantitative warning of an optimistic estimate or troubled execution.

Remaining balance versus open risk

The unspent reserve compared to the priced exposure of risks still open. The truest read on whether the project is still protected.

Draw authorization compliance

Share of draws made through the defined authorization process with documentation. Measures whether the reserve is governed or leaking.

Mischarge rate

Share of draws that should have been change orders or another party's contingency. Reveals whether the contractor is absorbing costs it should recover.

Contingency adequacy at milestones

Whether the reserve remaining at key completion milestones is sufficient for the risk profile ahead. A forward-looking control, not a rearview one.

Unused-at-completion percentage

Share of the original contingency unspent at completion. Very low suggests underfunding or slush-fund use; very high suggests overpricing of risk.

Draw documentation completeness

Share of draws with the covered risk and authorizer recorded. The determinant of whether the reserve's depletion can be explained and audited.

The AI shift — what actually changes

Conversational

The contingency becomes something you interrogate rather than a number you hope is enough. You ask what the burn rate is relative to progress, whether the remaining balance covers the open risks still on the register, and whether any recent draws should have been change orders instead — each answer tied to the draw log and the risk register, so depletion and mischarges surface early rather than at the overrun.

Generative

From the risk register and the draw history, a model drafts the contingency reforecast — comparing the remaining balance to the priced open risks, projecting whether the reserve is adequate to completion, and drafting the narrative that explains the burn to executives — a structured analysis the project manager validates rather than assembles by hand under pressure.

Orchestrated

The contingency stops being an isolated line. Each draw is checked against its authorization rules and the coverage scope, mischarges that should be change orders are flagged, the balance and burn rate update against the risk register, and the remaining reserve flows into the cost-to-complete and the projected final cost — so contingency governance and cost forecasting move together.

Autonomous

The routine motion runs inside guardrails: the balance and burn rate are tracked against progress and the open-risk register, draws are checked for authorization and coverage, and depletion outpacing progress is escalated. Humans always authorize the actual use of the reserve, decide whether a cost is a legitimate draw or a change order, and set the release treatment at closeout.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — You want an honest read on whether the contingency will hold to the end of the job.

Assess our contingency position. Give me the original amount, total drawn, remaining balance, and burn rate relative to percent complete. Compare the remaining balance to the priced exposure of the risks still open on our risk register and tell me candidly whether the reserve is adequate to completion or trending short. Then review the draw log and flag any draw that (a) lacks the required authorization or documentation, or (b) looks like it should have been a change order against the owner or drawn from a different contingency. Rank the concerns by dollars at risk.

What good output looks like: A candid adequacy assessment comparing remaining balance to open risk, with the burn rate contextualized against progress and any mischarged or undocumented draws flagged — an early warning, not a post-mortem.

Follow-ups:

• Which draws did we absorb that should have been change orders, and can we still recover them?
• If the open risks land at their current estimates, when do we run out?
• What draw-down rate keeps us covered through completion?

Generative — You need to reforecast the contingency and explain the burn to executives.

Draft our contingency reforecast for the monthly project review. Using the draw log and the open-risk register, summarize how much of the reserve has been drawn and for what categories of risk, compute the remaining balance and the burn rate against percent complete, and project whether the remaining contingency is adequate against the priced open risks through completion. Where the reserve is trending short, quantify the projected shortfall and identify the risks driving the burn. Write a clear narrative an executive can read in two minutes, distinguishing draws that covered genuine unforeseen risk from draws that suggest estimating or execution problems.

What good output looks like: A reforecast narrative that ties the burn to specific risk categories, projects adequacy to completion, and separates legitimate risk draws from warning signs — decision-ready, not a raw balance.

Follow-ups:

• Add a recommendation on whether we need to request additional contingency and why.
• Break the burn down by whether the driver was design, condition, or coordination.
• Draft the one-line status for the executive dashboard.

Orchestrated — A cost just arose and you need to determine and process the right source correctly.

An unforeseen below-grade obstruction added cost to the foundation work. Determine how this cost should be sourced: is it a legitimate draw against our contingency, a draw against the owner's contingency, or a change order against the owner under the differing-site-conditions clause. Check the contract's definitions of each contingency and the differing-conditions provision, and recommend the correct source with the reasoning. If it is a contingency draw, process it against the correct contingency with the authorization documentation, update the balance and burn rate, and reflect the remaining reserve in the cost-to-complete. If it should be a change order, flag it for a change event instead of a draw. Return your recommendation with each conclusion tied to the contract language.

What good output looks like: A sourcing recommendation grounded in the contract's contingency definitions and differing-conditions clause, with the cost routed to a draw or a change event correctly and the balance and forecast updated — not a reflexive draw against the nearest reserve.

Follow-ups:

• Draft the change event and notice if this should be a change order against the owner.
• If we draw from our contingency here, how does that affect our adequacy to completion?
• Confirm we are not absorbing a cost the owner's contingency should cover.

Autonomous — Standing policy for governing the contingency without letting it leak.

Govern our contingency continuously under these rules. Track the balance and burn rate against percent complete and against the priced exposure on the open-risk register, and escalate to me whenever the burn outpaces progress or the remaining reserve falls below the open risk it must cover. For every proposed draw, check it against the authorization rules and the defined coverage scope, and flag any draw that appears to belong in a change order against the owner or in a different contingency. Maintain the draw log with the covered risk and authorizer for each draw. Never authorize the actual use of the reserve, never decide whether a cost is a legitimate draw or a change order, and never set the closeout release treatment — route all of those to me with your analysis. Give me an exception queue and the adequacy status, not the whole ledger.

What good output looks like: A governed reserve where balance, burn, adequacy, and authorization checks run automatically, while every actual use of the contingency, every draw-versus-change-order call, and the release treatment stay with a human.

Follow-ups:

• Show the draws you flagged for wrong-source and the current adequacy status.
• Which proposed draws are awaiting my authorization and why?
• Are we on track to run short before completion at the current burn?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Padding by another name

   Contingency is a vague buffer with no rules, spent on whatever overruns arise. It is gone before the real risks hit and its depletion is untrackable.

1. Level 1 — Held and drawn

   A distinct contingency line exists and draws are recorded. Authorization is loose and the balance is not systematically compared to open risk.

2. Level 2 — Governed

   Draws follow authorization rules with documentation, the balance and burn rate are tracked, and each draw is tied to the risk it covered. Contingency types and ownership are defined.

3. Level 3 — Assisted

   Reforecasts comparing balance to open risk are drafted, burn rate is monitored against progress, and draws that should be change orders or belong to another contingency are flagged.

4. Level 4 — Operated

   Balance, burn, adequacy, and authorization checks run unattended inside guardrails, while humans own every actual use of the reserve, the draw-versus-change-order call, and the closeout release treatment.

Common questions

What is the difference between contingency and allowance?

A contingency is a reserve against unknown risk — costs that are anticipated in aggregate but not identified individually — drawn down only when a specific risk materializes. An allowance covers known but unspecified scope, like a finish selection whose choice is deferred, carried at an agreed value and reconciled to actual cost. The allowance always maps to a defined piece of scope; the contingency has no specific scope attached until a risk lands and consumes part of it.

Why does it matter whose contingency covers a cost?

Because it determines who bears the cost and whether it should be a draw or a change order. An owner's contingency covers risks the owner retains; a design contingency covers design development and errors; a contractor's contingency covers the contractor's own estimating and coordination risk. A cost mischarged to the contractor's contingency that should have been a change order against the owner depletes the wrong reserve for a cost the contractor should have recovered, which is why each contingency's ownership and coverage must be defined explicitly.

What happens to unused contingency at the end of a project?

It depends entirely on the contract type. On a cost-plus contract with a guaranteed maximum price, unused contingency typically belongs to the owner or is shared under a savings clause. On a lump-sum contract, the contingency is embedded in the fixed price and any unused portion generally accrues to the contractor as margin. Because the treatment differs so sharply, it must be clarified against the contract form up front, or closeout ends in a dispute over who owns the leftover reserve.

Why do executives watch contingency burn so closely?

Because it is one of the earliest reliable signals of project trouble. A contingency being consumed faster than the project is progressing indicates an optimistic estimate, incomplete design, or struggling execution — and it shows up in the burn rate long before it surfaces in the final cost report, while there is still time to act. A final overrun tells you the project failed; an accelerating contingency burn tells you it is about to, which is far more useful.