Skip to main content
BuilderGrid

Article · 7 min read

Contingency budgeting: when to use it and when to refuse to spend it

The discipline of holding the line on contingency. Typical rates, the budget-line vs. bank-account distinction, and the rule on usage that protects the year-end P&L.

By BuilderGrid editorialPublished 2026-05-01Updated 2026-05-01

Contingency is the line on a construction budget that is meant to absorb the cost of conditions nobody could have known about in advance. It is not a safety net for poor estimating, a slush fund for scope creep, or a reservoir the buyer can draw from to upgrade finishes. Builders who treat contingency with that discipline finish projects with money left in the line and call it profit. Builders who let contingency be the answer to every problem finish projects with the line empty and the margin gone.

Typical contingency rates

The right contingency rate depends on the type of project, the level of unknown in the scope, and the buyer’s contract. Residential new construction on a developed lot carries the lowest rate because the scope is well understood and the conditions are mostly predictable. Heavy renovation carries the highest rate because hidden conditions are routine.

Project typeTypical contingencyDriver
Spec build, developed lot3–5% of hard costKnown conditions, repeatable plan
Semi-custom, raw lot4–7% of hard costSite unknowns, plan revisions
Custom build, complex site5–8% of hard costTopography, soils, owner involvement
Light remodel5–10% of hard costSurface unknowns under finishes
Heavy renovation, structural10–20% of hard costHidden conditions, code triggers
Historic rehab15–25% of hard costMaterial matching, regulatory review

On 926 Stratford, a 1,784 SF semi-custom new build on a developed lot in Sweetwater, a contingency of 5 percent is appropriate. On a $370,000 hard cost, that is $18,500. The contract carries the contingency as a line item; the buyer sees the dollar figure; and the line is owned by the builder, drawable only with cause.

Budget line vs. bank account

Two conventions are in common use. The cleaner convention is the separate-line approach. Contingency lives as a distinct budget line, with its own cost code, and any draw against it is recorded explicitly. The budget shows the original contingency, the amount used, and the amount remaining. The buyer and the lender can see at a glance how much of the reserve has been touched.

The other convention bakes contingency into the trade lines. The framing line is budgeted at $44,000 with a $2,000 cushion that the buyer never sees as separate. Cumulatively, the cushions add up to the contingency rate. The advantage is that the buyer sees lower trade margins. The disadvantage is that overruns on one trade quietly absorb cushion from others, and at the end of the project nobody knows whether the contingency was used efficiently or wasted.

For builds where the buyer or the lender will see the budget, the separate-line approach is the standard. It produces a clear audit trail, a clean draw mechanism, and a year-end variance report that actually means something.

The rule on usage

Contingency is for genuinely unforeseen conditions. The bar is high, and the test is whether the cost could have been known with reasonable diligence at the time of the bid. A few categories pass the test cleanly.

  • Rock encountered in the foundation excavation that the soils report did not predict.
  • Water table elevation higher than the geotech specified, requiring drainage work that was not in the scope.
  • Structural conditions revealed in a remodel after demolition opens up the assembly: undersized headers, rotted sill plates, knob-and-tube wiring that triggers a code update.
  • Material price spikes between bid and order date that exceed the bid’s validity period through no fault of the builder.
  • Code interpretation changes mid-project that require rework of completed assemblies.

The categories that fail the test are equally important to name. Scope creep is not a contingency event. Estimating errors are not a contingency event. The framer bidding 8 percent low because he was hungry is not a contingency event. The buyer’s late decision to upgrade the cabinets is not a contingency event. Each of those is a different budget mechanism, and conflating them with contingency is how the line runs dry by month six.

Draw mechanics

Most construction loans require lender approval before contingency is drawn. The mechanics are straightforward. The builder identifies a cost that meets the contingency criteria, prepares a written explanation, and submits a contingency draw request to the lender along with supporting documentation. The lender reviews, approves or denies, and either funds or sends the request back.

The documentation that supports a contingency draw is the discipline that keeps the line honest. A contingency draw request typically includes a narrative description of the unforeseen condition, photographs or inspection reports demonstrating the condition, vendor invoices or change orders quantifying the cost, and a budget update showing the contingency line before and after the draw. Lenders who see a request without that documentation deny it and ask for it.

The discipline that makes contingency draws routine is treating the request like a small audit. A 10-minute investment in documentation at the time of the event saves an hour of back-and-forth with the lender two weeks later, and produces a paper trail that supports the year-end review.

Who owns the contingency line

On a fixed-price contract, the contingency belongs to the builder. The builder priced the project to include the contingency as part of the cost basis, and any unused contingency at closeout flows to the builder’s margin. On a cost-plus contract, the contingency usually belongs to the buyer. The buyer is paying actual costs plus a fee, and any unused contingency at closeout reduces the buyer’s final invoice rather than flowing to the builder.

The contract structure changes how the contingency conversation goes with the buyer. On fixed-price the builder defends the line because protecting it protects margin. On cost-plus the builder still defends the line, but the language is different: protecting the line protects the buyer from cost overruns the builder did not cause. Both conversations end the same place, with the line drawable only for legitimate unforeseen events, but the framing matters when the buyer is asking why a request was denied.

The change-order pressure on custom builds

On custom and semi-custom builds, the recurring pressure on contingency comes from the buyer. The pattern is consistent. The buyer asks for a change. The builder prices it, and the buyer pushes back on the price with some version of “but you have contingency, right?”

The answer is no, the buyer does not have access to the contingency, and the change is not a contingency event. The cleaner way to deliver the answer is procedurally. Every change request goes through a written change order. The change order specifies the scope, the cost, the schedule impact, and the price the buyer is paying. The buyer signs the change order before the work begins. The cost flows to a change order line on the budget, not to contingency.

On 926 Stratford a buyer asked mid-project to upgrade the kitchen backsplash from $1,800 to $4,200. The change order documents the new scope and the $2,400 incremental cost, the buyer signs, and the $2,400 appears as a billable change to the contract. The contingency line remains untouched. If the buyer had refused to pay, the change does not happen. Contingency does not become the answer to a buyer who wants upgrades for free.

How to refuse cleanly

Refusing a contingency draw is a procedural act, not a confrontation. The builder explains the difference between unforeseen conditions and change requests, points to the contract section that defines contingency, offers a written change order as the alternative, and lets the buyer decide. Buyers who understand the structure accept it. Buyers who do not understand it learn quickly when the alternative is paying out of pocket for the change they wanted.

The contract language matters. A clause that defines contingency as “reserve for unforeseen conditions, drawable on builder’s approval and lender consent, not available for buyer-initiated changes or scope additions” sets the terms before the project starts. Builders without that language in their contract have a harder time holding the line and end up either eating costs or arguing with the buyer.

Year-end view: contingency as a profitability indicator

Closed-out contingency rate is one of the cleanest indicators of project management quality. The rate is computed as contingency used divided by contingency budgeted. A project that budgeted 5 percent contingency on $370,000 hard cost ($18,500) and spent $4,200 of it shows a 23 percent usage rate, with $14,300 remaining as project margin.

Closed contingency usageReading
0–25%Healthy. Estimating and scope control both working.
25–60%Normal. A few legitimate events absorbed.
60–100%Stressed. Investigate whether the events were truly contingency-eligible or whether scope creep crept in.
Over 100%Failed. Either the bid was light, the scope was loose, or the discipline lapsed. Worth a project post-mortem.

Across a year of projects, a builder who consistently runs in the 0–25 percent band is recovering meaningful margin from contingency. On ten projects at $430k each with 5 percent contingency, the line carries $185,000 in aggregate. Holding usage to 20 percent means $148,000 returns to the bottom line as project profit. That figure is the difference between a tight year and an excellent one.

Tracking contingency draws through the build

The mechanical record-keeping for contingency is straightforward. Each contingency draw has a date, a triggering event, a documented cost, an approval (lender, builder, and where applicable the buyer), and a running balance. The simplest format is a contingency log appended to the project budget, updated within a week of each event, and reconciled at month-end alongside the main budget.

On 926 Stratford a typical log might show two events across a ten-month build. A March entry records $1,800 against rock encountered in the north footing run, with photographs from the excavator, the change-order documentation from the foundation sub, and the lender approval email. A July entry records $2,400 against an HVAC supply line that needed rerouting around a structural beam that the engineering plan placed differently than the framer installed. Both events pass the unforeseen test, both are documented, and the contingency line shows $14,300 remaining at closeout.

The log compounds in value across multiple projects. A builder who keeps clean contingency records on every job builds a reference library of unforeseen events on residential construction in their market. After eight to ten projects the patterns become visible: rock shows up on lots in certain neighborhoods, a particular jurisdiction is aggressive on code interpretation during framing inspections, the third-party inspector at one lender flags water-management items that the field never sees coming. Those patterns translate into smarter bidding and tighter contingency rates on future projects.

The discipline summarized

Contingency works when it is rare, documented, and reserved for the events that justify it. Carrying it as a separate line, requiring lender approval to draw, refusing to spend it on scope creep, and running every change as a written change order is the operating posture that protects the line. The builders who finish the year with money in contingency are the same builders who finish the year with margin intact. The discipline is the same in both cases.

Ready to see the product?

A 30-minute walkthrough with the team building it. Bring your toughest budget or draw scenario.