Risk Contingency in Construction Estimates: How Much Should You Add?

Contingency is one of the most misunderstood line items in construction estimating. Applied correctly, it's a disciplined, risk-based buffer against genuine project unknowns. Applied out of habit, a flat percentage tacked onto every estimate regardless of what the project actually needs, it either under-protects a genuinely risky project or over-prices a straightforward one, losing bids it should have won.

What Contingency Is (and Isn't)

Contingency is money set aside in an estimate to cover costs from risks that are known to exist in general but can't be precisely predicted or priced at the time of estimating: an unforeseen site condition, a design detail that isn't fully resolved yet, a material price movement beyond what's already built into base pricing. It is not a substitute for an inaccurate or incomplete takeoff. Contingency covers genuine uncertainty; it shouldn't be used to compensate for scope that wasn't properly measured or priced in the first place.

Why a Flat Percentage Doesn't Work

A common shortcut is applying a flat 5% or 10% contingency to every estimate, regardless of the project's actual risk profile. The problem is that project risk isn't uniform. A renovation of a 1960s building with unknown existing conditions carries fundamentally different risk than a straightforward new-construction project with a complete, well-coordinated design. Applying the same flat percentage to both means the renovation is very likely under-protected while the new build may be needlessly padded, a padding that can lose a competitive bid it otherwise would have won.

A Risk-Based Framework for Setting Contingency

Rather than a single flat number, contingency should scale with the specific risk factors a project actually carries:

Design completeness. A project bid off a fully developed construction document set carries meaningfully less risk than one bid off a conceptual or schematic design still in flux. Early-stage estimates commonly warrant contingency in the 15% to 20%+ range, while a fully detailed, coordinated design set might reasonably carry 5% to 10%.

Site and existing conditions uncertainty. New construction on a well-surveyed site carries less risk than renovation work in an existing building, or ground-up construction on a site with limited geotechnical investigation. Projects with real unknowns below grade or behind existing walls warrant a higher contingency allocation than projects with well-documented conditions.

Schedule aggressiveness. A compressed schedule increases the likelihood of overtime, trade stacking, and coordination issues that a more generous timeline would avoid, all of which carry cost implications worth reflecting in contingency.

Market volatility exposure. Given current material price volatility in categories like steel, aluminum, and copper, along with labor cost pressure driven by industry-wide labor shortages, projects with extended timelines or heavy exposure to volatile material categories warrant additional contingency specifically tied to that exposure, separate from general project risk.

Complexity and coordination requirements. Projects involving many trades, tight site logistics, or unusual technical requirements carry more coordination risk than a straightforward, well-understood scope, and that coordination risk translates into real potential cost if it isn't managed well.

Typical Contingency Ranges by Project Stage

| Estimate Stage | Typical Contingency Range | |---|---| | Concept / feasibility stage | 15%–25% | | Schematic design stage | 10%–20% | | Design development stage | 7%–15% | | Construction documents / final bid | 3%–10% |

These ranges reflect a general pattern: contingency should shrink as design certainty increases and more of the project's actual scope and conditions become known. A contingency that doesn't decrease as a project moves through design stages suggests either the design isn't actually resolving open questions, or the contingency figure isn't being genuinely reassessed at each stage.

Contingency Isn't Just for Contractors

Owners and developers benefit from the same risk-based contingency discipline, and arguably need it more, since an owner absorbs cost overruns directly rather than passing them through a contract. A contingency in the range of 15% to 20% above the base construction estimate is a commonly recommended buffer for owners at the development stage, particularly given current material and labor cost volatility.

Contingency vs. Escalation: A Distinction Worth Making

Contingency and escalation are related but distinct concepts, and conflating them leads to under-protecting against one or the other. Contingency covers scope and condition uncertainty, the risk that something wasn't fully known or resolved at the time of estimating. Escalation specifically covers the risk that known costs will rise between the time of the estimate and the time of actual purchase or labor deployment, a distinct risk driven by market conditions rather than scope uncertainty. A project estimate genuinely benefits from accounting for both separately, particularly in the current environment of active material and labor cost movement, rather than lumping them into a single generic buffer.

What Happens When Contingency Isn't Used

A detail worth understanding on the owner side: contingency spent versus unspent isn't necessarily an indicator of good or bad estimating on its own. A project that uses very little of its contingency may reflect a well-executed, low-risk project, or it may reflect a contingency that was set too high to begin with, effectively overcharging the client for risk that didn't materialize. Conversely, a project that exhausts its contingency early isn't automatically evidence of poor management. It may reflect genuine unforeseen conditions that a reasonable, risk-based contingency correctly anticipated as a possibility, even if the specific outcome wasn't guaranteed. What matters most is whether the original contingency figure was set based on an honest assessment of actual project risk, not a flat habit or an arbitrary round number.

Communicating Contingency Clearly

Contingency should be visible and explained in an estimate, not buried invisibly inside line-item pricing. A client or owner who understands what the contingency is for, and what specific risks it's meant to cover, is far better positioned to understand why it exists and how it might be used, rather than viewing it as an unexplained padding on top of the "real" price.

The Bottom Line

Contingency done well is a disciplined, risk-based calculation tied to a project's actual, identified uncertainties, not a habitual percentage applied the same way to every estimate regardless of what the project actually needs. Getting it right protects margin on genuinely risky projects while keeping straightforward, well-defined projects competitively priced, a balance that a flat, one-size-fits-all contingency simply can't achieve.

Contingency is only as good as the risk assessment behind it. A detailed estimate that accounts for your project's specific design completeness, site conditions, and market exposure sets a contingency figure that actually protects the budget it's meant to protect.