Five Percent Is a Guess, Not a Plan
Ask a developer how they arrived at their construction contingency budget and the honest answer is often a shrug. Five percent is the industry default because it is easy to write into a pro forma, not because it reflects the actual risk profile of the project. A ground-up hotel in a market with soil issues, a complex mechanical scope, or a compressed procurement window does not carry the same risk as a straightforward renovation with known conditions. Applying the same flat percentage to both is not conservative underwriting. It is a placeholder that happens to look precise.
For an investor evaluating IRR before capital is committed, a round-number contingency is a red flag. It suggests the risk has not been quantified, only assumed. Contingency should be a calculated number, derived from the specific unknowns in the deal, not a habit carried over from the last project.
What Contingency Really Covers
Contingency is not a slush fund for scope creep or a buffer for poor estimating. It exists to absorb defined categories of risk that cannot be fully priced at the time of budget lock. Those categories generally fall into a few buckets:
- Design development risk, the gap between a schematic budget and a fully detailed construction document set
- Market volatility in material pricing and subcontractor labor availability
- Unforeseen conditions, particularly on renovation or adaptive reuse projects where existing structure is unknown until it is opened up
- Permitting and jurisdictional risk that can shift scope after entitlement
Each of these has a different probability and a different cost impact. A capital stack that treats them identically is either overfunding contingency it does not need or underfunding the risk that actually threatens the schedule. The truth is that most overruns are not contingency failures at all. They are traced back to decisions made long before mobilization, which is why budget overruns start in design, not on the job site.
How Capital Partners Size It
Sophisticated capital does not accept a flat percentage without scrutiny. Lenders and equity partners who have underwritten dozens of hotel deals size contingency against the specific risk register of the project, weighted by design completion, market conditions, and the track record of the delivery team. A project entering construction with a fully coordinated set and early trade buy-in warrants a tighter contingency than one moving forward on a partially resolved design.
This is where early GC involvement changes the math. When a contractor is engaged during design rather than after it, pricing risk gets identified and resolved before it becomes a change order. That shift alone can justify a lower contingency line, because the uncertainty it is meant to cover has already been reduced. Capital partners who understand this dynamic look for it specifically, because early GC involvement protects the capital stack in ways a bid-day relationship cannot.
Sizing contingency correctly also means being skeptical of the bid that comes in conveniently low. A number that undercuts every other bidder is rarely a sign of efficiency. It is more often a sign that scope has been narrowed, risk has been shifted, or the contractor is planning to recover margin through change orders once the project is underway. The lowest bid is a risk signal, and an undersized contingency paired with an aggressively low bid compounds exposure rather than reducing it.
Contingency Discipline
A well-sized contingency is only useful if it is managed with discipline once construction starts. That means tracking draws against contingency by category, not treating it as a single pool that gets depleted on a first-come basis. It means distinguishing between a true unforeseen condition and a preventable coordination failure, because the second should trigger a conversation about accountability, not a quiet draw against the buffer.
Discipline also means understanding the connection between contingency and schedule. A depleted contingency line often shows up first as a delay, not a budget line item, because teams slow down to renegotiate scope rather than proceed on an assumption. That delay has a direct and quantifiable cost. A 90 day delay’s effect on projected IRR is rarely trivial, and schedule drift’s cost to IRR compounds the longer it goes unaddressed. Contingency that is sized correctly and drawn with discipline protects both the budget and the calendar, which is the same thing as protecting return.
The developers who consistently hit their return targets are not the ones who guessed right on a percentage. They are the ones who treated contingency as a risk-adjusted number from the start, revisited it as design matured, and held their delivery team accountable for how it was spent. That level of rigor is not standard practice across the industry, which is part of why it shows up directly in performance. To see how this fits into a broader delivery approach, review what Pro Commercial does for capital-aligned development partners.
If your current budget still treats contingency as a round number rather than a calculated risk line, it is worth a closer look before capital is committed. A pro forma and feasibility review can identify where the real exposure sits and whether your contingency actually covers it.