Every estimate carries two lines that do not behave like the rest of the work: the allowance and the contingency. They look alike on the sheet — both add money you do not have a firm price for yet — and that is exactly why they get confused. They are not the same line, and treating them as interchangeable is how a bid that looked healthy on bid day runs dry at closeout.
The short version
An allowance covers a known item with an unknown price. Interior caulk, hardware, a storefront vision glass — the scope is defined, the cost is not, so you fix a dollar amount in the contract and true it up when the actual price lands.
A contingency covers a cost that may or may not occur. Bad soil, a design gap that shows up at plan review, an owner change pressed late — the event is uncertain, so you hold a reserve against it.
The two behave differently for a reason you can test with one question: can you name the thing you are pricing? If yes, it is an allowance. If you cannot, it is a contingency. Run every line through that question once and most of the confusion dissolves.
Where an allowance comes from
Allowances are written into the contract, and the contract tells you what they cover. The governing definition in the most common set of general conditions — AIA Document A201, Section 3.8 — says an allowance covers the cost of materials and equipment delivered to the site, including taxes, net of trade discounts. Installation and your overhead and profit are carried elsewhere in the sum.
The word that matters is placeholder. An allowance holds a position for a specific line item until the item is selected and bought, and then the actual cost replaces it through the change-order process. So an allowance is not a windfall and not a shortfall — it is a ticket. You either spend it on the item it names, or you true the difference up or down.
Where a contingency comes from
A contingency is a reserve for events that may never happen, and that is precisely why the percentage is negotiable and why nobody agrees on it. The AIA’s guidance on managing the contingency allowance treats it as a predetermined amount held for unpredictable changes in the work, and industry practice hangs the number on how much you do not know yet:
| Phase | Conventional range |
|---|---|
| Schematic design | 10–15% |
| Design development | 7–10% |
| Construction documents | 5–10% |
| During construction | 3–5% |
Those are ranges, not rules. The logic underneath them is the point: the less defined the design and the less settled the site conditions, the more you hold back. A flat 10% on every job is a guess, not a strategy — the number should track the level of uncertainty you actually face at the moment you sign.
The trap that costs money
The expensive mistake is meeting the owner halfway. Bidding the allowance low so the number wins and hoping the contingency absorbs the difference is one line doing two jobs, and the line loses.
An allowance is priced at the expected cost of a named item. A contingency is priced at the probability-weighted cost of unnamed events. When you under-price the allowance and over-rely on the contingency, you are drawing the reserve down on things everyone could see coming — which means it stops being a reserve and starts being a negotiated discount, and the reserve stops covering what it was actually for.
The fix is to keep them separate on the sheet and in your head:
- Price the allowance at what the item will really cost today, not at the number that wins the bid.
- Hold the contingency for the events you cannot name, and track draws against it like any project line.
- When an allowance runs over, treat it as a change order, not as a silent draw on the reserve.
Why this belongs in your estimating process
An allowance and a contingency are decisions you make while the estimate is still a stack of takeoff sheets, not lines you bolt on at the end. If your estimate is built by work item with clean values, the allowance slots in where a specific product is undefined and the contingency sits on top as a single, watched reserve. If your estimate is a single lump sum, you are inventing both numbers under a deadline — and that is where they become interchangeable guesses instead of deliberate lines.
The same discipline that keeps allowances honest applies to the rest of the package. When you level five subcontractor bids back to a common baseline, you will find allowances treated differently in every quote — some rolled in, some listed, some left out — and the comparison only works if you price the deltas rather than noting them. And when the number is set, the way it flows into your schedule of values decides whether the cash lands when you need it: an allowance tied to a late-purchased item belongs on a late line, not front-loaded. That is the kind of decision a structured estimating workflow makes once and reuses — not the arithmetic you reconstruct from scratch under a deadline.
A contingency that sits unused is a project that did not need it, and the owner can see the burn-down. An allowance that ends in a credit is a line you priced honestly. Keep the arithmetic straight and both lines do their job: the allowance names the thing, the contingency covers what you cannot name, and neither one quietly becomes the other.
Want the allowance and contingency lines in your takeoff built the same way every time? Get in touch — that is the kind of repeatable estimating work we structure on top of the EC System.