Contingency Is Not a Guess: How U.S. Engineering Projects Are Losing Money Before Work Even Begins
There is a particular kind of financial pain that comes not from poor execution, but from poor preparation. In U.S. engineering and construction projects, that pain has a name most project owners know well: the contingency shortfall. It arrives quietly — buried in change orders, schedule extensions, and scope adjustments — and by the time it surfaces, the damage is already done.
The frustrating reality is that this pattern is not random. It is structural. And it begins with a fundamental misunderstanding of what risk contingency is supposed to do.
The Flat-Percentage Problem
Ask a project manager how contingency was calculated on their last major engagement, and a common answer surfaces: a fixed percentage — often somewhere between five and fifteen percent — applied to the base estimate. Sometimes that figure is negotiated down during budget approval. Sometimes it is simply inherited from a previous project of similar scope.
This approach is not entirely without logic. It is fast, it is defensible in a budget presentation, and it provides the appearance of fiscal prudence. What it does not provide is accuracy.
Flat-percentage contingency ignores the actual risk profile of a given project. A ten percent buffer applied to a $20 million mechanical systems upgrade in a regulated facility is a fundamentally different calculation than the same percentage applied to a greenfield civil infrastructure project in a region with complex permitting requirements. The number looks the same on paper. The exposure it covers is entirely different.
When contingency is undersized relative to actual risk, the consequences are not merely financial. Schedules compress. Scope gets cut. Relationships with clients and subcontractors deteriorate. And the project team spends the back half of execution managing a funding crisis rather than delivering outcomes.
Why the Underestimation Persists
Several forces sustain this problem, and understanding them is necessary before addressing them.
First, there is competitive pressure. In a procurement environment where project awards are often driven by initial cost estimates, there is an implicit incentive to keep contingency lean. A project owner comparing two proposals may favor the one with a tighter budget — even if that budget reflects optimism rather than rigor. The firm that builds a well-justified, larger contingency fund can appear less competitive, even when it is actually being more responsible.
Second, there is organizational inertia. Many firms rely on historical averages rather than project-specific analysis. If a class of projects has historically run five percent over budget, five percent becomes the default contingency — regardless of whether current market conditions, supply chain pressures, or regulatory complexity have shifted the risk landscape.
Third, and perhaps most consequentially, there is a weak feedback loop between project outcomes and future estimating. When cost overruns occur, they are often absorbed, explained away, or attributed to circumstances deemed exceptional. The underlying estimation methodology is rarely interrogated. The next project uses the same approach, with the same predictable results.
What Data-Driven Risk Modeling Actually Looks Like
Leading engineering firms and sophisticated project owners are moving away from percentage-based contingency toward probabilistic risk modeling — an approach that treats contingency sizing as an analytical exercise rather than a convention.
The core methodology involves identifying discrete risk categories — design uncertainty, procurement volatility, regulatory delay, labor availability, site conditions — and assigning both a probability of occurrence and a potential cost impact to each. Monte Carlo simulation or similar probabilistic tools then generate a range of possible project outcomes, allowing teams to select a contingency level that corresponds to a specific confidence threshold.
In practical terms, this means a project team might determine that a contingency fund sized at a given dollar amount provides an eighty percent probability of covering cost growth, while a larger fund raises that confidence to ninety-five percent. The choice between those figures becomes a deliberate risk tolerance decision — not a guess.
This approach also produces a more useful artifact than a single contingency line item. It generates a risk register: a living document that assigns ownership to individual risk categories, tracks mitigation efforts, and allows contingency to be actively managed throughout the project lifecycle rather than simply held in reserve.
The Role of Project Owners in Fixing This
It would be convenient to frame this as purely a contractor or engineering firm problem. It is not. Project owners bear significant responsibility for the conditions that produce underestimated contingency.
Owners who pressure design and construction teams to submit lean estimates — implicitly or explicitly — are creating the environment in which contingency gets trimmed. Owners who do not require transparent risk documentation during procurement have no mechanism to evaluate whether the contingency a firm is proposing is defensible. And owners who fail to conduct post-project reviews that connect contingency adequacy to actual cost performance will never accumulate the institutional knowledge needed to improve their own standards.
The practical steps available to project owners are not complicated, but they require discipline. Requiring bidders to submit a documented risk register alongside their cost estimates is a straightforward starting point. Establishing internal benchmarks for contingency adequacy — informed by actual project history rather than industry averages — is another. Engaging an independent third party to review risk assumptions on major projects before budget approval is a measure that consistently pays for itself.
Contingency as a Strategic Instrument
There is a broader reframing worth considering here. In most project budgets, contingency is treated as a cost — money set aside that ideally will not be spent. That framing, while understandable, obscures a more useful way of thinking about it.
Well-calibrated contingency is a strategic instrument. It is what allows a project team to respond to genuine uncertainty without destabilizing the broader engagement. It is what preserves client relationships when conditions change. It is what separates firms that deliver on their commitments from those that consistently explain why they could not.
For engineering project owners operating in today's environment — where supply chain unpredictability, labor market tightness, and regulatory complexity are not temporary conditions but structural features of the landscape — the cost of underestimating risk is not a one-time event. It is a recurring tax on every major engagement.
The firms that treat contingency sizing as a rigorous discipline rather than a budgetary afterthought are not being conservative. They are being precise. And in a business where margins are thin and credibility is everything, precision is the competitive advantage that compounds over time.
Presto Engineering Group works with project owners and engineering teams across the United States to develop robust project planning frameworks, including risk-informed contingency strategies that protect budgets and sustain delivery performance. Contact us to learn how structured risk modeling can be integrated into your next major engagement.
