CHG 206 · Practitioner · Finance track · 10 min read

Allowance

A defined sum carried in the contract for scope that is not yet fully specified — a placeholder that lets a project be priced and signed before every selection is made, reconciled against actual cost as the scope is defined.

Definition — what it is

An allowance is a specific sum of money written into the contract to cover a portion of the work whose scope, product selection, or cost has not yet been finalized at the time the contract is signed. It exists because some decisions — finish selections, specialty items, unforeseeable quantities — cannot reasonably be made before the project must be priced and started, so the parties agree on a placeholder value and defer the actual selection. When the scope is later defined and the real cost is known, the allowance is reconciled: if the actual cost exceeds the allowance the contract sum increases by a change order, and if it comes in under, the difference is credited back to the owner. An allowance is not a contingency (which covers unknown risk, not deferred scope) and not a lump-sum price (which is fixed); it is a defined, reconcilable placeholder, and what is and is not included in it — material only, or material plus labor and installation — is the source of most allowance disputes.

Also known as: Cash Allowance, Contract Allowance, Provisional Sum, Spending Allowance, PC Sum

Why it matters — what it protects

The allowance is what lets a project move forward before every decision is made. Owners rarely have all their finish selections, specialty equipment, or below-grade quantities resolved when they need to sign a contract and start work, and without a mechanism to carry those undecided items at an agreed value, the whole project would stall waiting on decisions. The allowance trades certainty for progress: it lets pricing and construction proceed while explicitly flagging which scope is still a placeholder to be trued up later.

It is a structured, transparent alternative to guessing. The alternative to an allowance is either padding a lump-sum price to cover an undefined item — which overcharges the owner if the item comes in cheap and underprices the contractor if it comes in expensive — or leaving the item out and fighting about it later. The allowance makes the undefined scope visible as a named line with a stated value, which is more honest to the owner and safer for the contractor than burying the uncertainty in a fixed number.

Its inclusions and exclusions are where the money and the disputes live. The single most consequential question about any allowance is what it covers: material cost only, or material plus freight, labor, installation, and markup. An owner who assumes the tile allowance covers installation and a contractor who priced only the tile material are heading for a change order fight the moment the real cost is reconciled, which is why the definition of scope inside the allowance matters more than the allowance amount itself.

It requires disciplined reconciliation or it silently distorts the contract. An allowance that is never trued up against actual cost leaves the contract sum wrong in one direction or the other — the owner overpaying for a credit never issued, or the contractor absorbing an overage never changed. Because allowances are placeholders by design, they must be actively closed out, and a project that reaches the end with unreconciled allowances has a contract value that does not reflect what was actually built.

Lifecycle — how it moves

  1. Identification during estimating

    During bidding, scope that cannot be fully specified — finishes, specialty items, uncertain quantities — is identified as a candidate for an allowance rather than a firm price, so the bid can be completed without guessing at undecided selections.

  2. Allowance value set

    A realistic placeholder value is assigned based on comparable projects and market pricing. Setting it too low creates a false low contract price that balloons with change orders; too high overstates the contract and invites scope creep.

  3. Scope definition of the allowance

    The contract states exactly what the allowance covers — material only, or material plus labor and installation and markup. This definition, done clearly at signing, prevents the most common allowance dispute later.

  4. Carried in the contract sum

    The allowance is included in the total contract sum as a named line. The project is priced, signed, and started with the allowance scope explicitly flagged as not yet finalized.

  5. Selection and actual pricing

    As the project proceeds, the owner makes the selection or the quantity becomes known, and the actual cost is determined through quotes or measured work. This is the moment the placeholder becomes a real number.

  6. Reconciliation

    The actual cost is compared to the allowance. An overage triggers a change order increasing the contract sum; an underage triggers a credit reducing it. The reconciliation must reflect only the scope the allowance was defined to cover.

  7. Change order or credit issued

    The difference is formalized through a change order adjusting the contract sum up or down. Skipping this step leaves the contract sum wrong and the allowance unclosed.

  8. Closeout verification

    At closeout, every allowance is confirmed reconciled, with each overage and credit accounted for, so the final contract value reflects actual cost rather than placeholder estimates.

Anatomy — the data it carries

Allowance item and number
The scope the allowance covers and its identifier, linked to the estimate line and the eventual reconciling change order.
Allowance amount
The placeholder value carried in the contract sum. Its accuracy determines how much the contract will move at reconciliation.
Scope inclusions
Exactly what the allowance covers — material, freight, labor, installation, markup. The most important field, because it defines what will be reconciled.
Scope exclusions
What the allowance explicitly does not cover, so that excluded cost is priced separately rather than assumed inside the allowance.
Basis of the amount
How the placeholder was derived — comparable pricing, an early quote, a quantity assumption. Supports the value if the reconciliation is contested.
Selection deadline
When the owner must make the selection to avoid delaying the work. Late selections against an allowance are a frequent, avoidable schedule impact.
Actual cost and backup
The real cost once the scope is defined, with quotes or measured quantities. The figure reconciled against the allowance.
Reconciliation variance
The difference between actual cost and the allowance — the overage or credit that adjusts the contract sum.
Markup treatment on variance
Whether overhead and profit apply to an overage, and how, per the contract. A common point of dispute when actual cost exceeds the allowance.
Reconciling change order reference
The change order that formalizes the overage or credit, closing the allowance and adjusting the contract sum.
Cost code allocation
How the allowance and its actual cost map to the budget, so job cost reflects the real cost of the reconciled scope.
Status
Open, selection pending, priced, reconciled, or closed — the state that tells everyone whether the placeholder is still live.

Failure modes — how it breaks

Ambiguous inclusions and exclusions

The contract says a tile allowance without stating whether it covers installation and markup. The owner assumes it does, the contractor priced only material, and reconciliation becomes a change order fight over scope the contract never defined.

Allowance set unrealistically low

A low placeholder produces a deceptively low contract price that then balloons through overage change orders as real costs come in. The owner feels ambushed even though the mechanism worked exactly as designed, and trust erodes.

Never reconciled

The scope is defined and the actual cost is known, but no change order or credit is ever issued. The contract sum stays at the placeholder value — the owner overpays a credit never given, or the contractor absorbs an overage never charged.

Late owner selection delays the work

The owner does not make the allowance selection by the deadline, the long-lead item cannot be ordered in time, and the resulting delay is not documented as owner-caused. The contractor absorbs a schedule impact the allowance selection process created.

Markup on overage disputed after the fact

The actual cost exceeds the allowance, and the parties discover the contract never addressed whether markup applies to the overage. The reconciliation stalls over a question that should have been answered when the allowance was written.

Scope creep inside the allowance

The owner upgrades the selection well beyond what the allowance contemplated and expects the allowance to absorb it. Without a clear basis and inclusions, the line between reconciling the allowance and pricing a genuine scope increase blurs.

Metrics — how it is measured

Allowance reconciliation rate

Share of allowances trued up to actual cost through a change order or credit. The core control against a contract sum that does not reflect what was built.

Aggregate allowance variance

Total overage and credit across all allowances versus the placeholders. Reveals how accurately the allowances were set and how much the contract moved.

Placeholder accuracy

How close allowance amounts were to actual cost, on average. Poor accuracy signals estimating that pushes uncertainty into allowances rather than pricing it.

Open allowance value

Value of allowances not yet reconciled as the project nears completion. The measure of how much of the contract sum is still a placeholder.

Selection-timeliness rate

Share of allowance selections made by their deadline. Late selections are a leading cause of avoidable, allowance-driven delay.

Allowance-driven change order share

Portion of change orders arising from allowance reconciliation. High shares point to allowances set too loosely or scope pushed into them.

Dispute rate on inclusions

Share of allowances contested over what they covered. Measures the clarity of the inclusions and exclusions written at signing.

The AI shift — what actually changes

Conversational

The allowance schedule becomes interrogable. You ask which allowances are still open as completion approaches, which selection deadlines are slipping, and where the aggregate variance is running against the contract sum — each answer tied to the contract and the actual-cost records, so unreconciled placeholders and late selections stop hiding until closeout.

Generative

From the contract and the actual pricing, a model drafts the reconciliation for an allowance — comparing actual cost to the placeholder within only the defined inclusions, computing the overage or credit, applying markup per the contract, and drafting the reconciling change order or credit — for the project manager to confirm against the scope the allowance was written to cover.

Orchestrated

The allowance stops being a forgotten line. Selection deadlines are tracked against the procurement schedule, actual cost is matched to the allowance scope, the reconciling change order flows into the schedule of values and the contract sum, and the variance updates job cost — so every allowance moves from placeholder to real cost with the contract kept accurate.

Autonomous

The routine motion runs inside guardrails: allowance selection deadlines are monitored and escalated, actual costs are matched to allowances as they are known, reconciliation variances are computed, and open allowances are surfaced as completion approaches. Humans always confirm what the allowance was defined to cover, decide markup on overages, and approve the reconciling change order or credit.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — The project is nearing completion and you need to know which allowances are still open and moving the contract.

Review our allowance schedule. List every allowance with its amount, defined inclusions, actual cost to date if known, reconciliation status, and the reconciling change order if one exists. Flag every allowance that is (a) still open with the project 80 percent complete, (b) has actual cost known but no reconciling change order or credit issued, or (c) has a selection deadline that has passed or slips within 14 days. Total the aggregate variance — overages and credits — and tell me the net effect on the contract sum if the open allowances land at their current estimates.

What good output looks like: A status view of every allowance with unreconciled items and slipping selections flagged and the net contract-sum effect quantified — so no placeholder reaches closeout untrued.

Follow-ups:

  • Which open allowances are we owed a credit on that we have not issued?
  • Which unreconciled overages are we absorbing that should be change orders?
  • Which slipping selections will delay a long-lead item, and what is the impact?

Generative — An owner selection came in over the allowance and you need the reconciliation drafted correctly.

Reconcile the tile allowance. The contract carries a tile allowance of the stated amount, defined to cover material and installation labor but explicitly excluding substrate preparation. The owner's selected tile plus installation came in over the allowance per the attached quote. Draft the reconciliation: compare the actual cost to the allowance within only the defined inclusions, exclude the substrate prep that the allowance never covered and price it separately if needed, compute the overage, apply markup on the overage per our contract terms, and draft the reconciling change order increasing the contract sum. Show clearly what is inside the allowance scope and what is a separate change so the owner sees the distinction.

What good output looks like: A reconciliation that trues up only the allowance-defined scope, separates excluded work as its own change, applies the correct markup, and produces a clean change order — with the inclusion boundary made explicit to the owner.

Follow-ups:

  • Rewrite it as a credit instead, assuming the selection had come in under.
  • Draft the note to the owner explaining why substrate prep is a separate change.
  • Confirm the markup treatment matches what the contract allows on allowance overages.

Orchestrated — A batch of allowance selections has been priced and you need the contract and cost systems updated.

Several allowance selections have been finalized and priced. For each, reconcile the actual cost against the allowance within its defined inclusions, compute the overage or credit, and generate the reconciling change order. Then propagate each one: update the schedule of values and the contract sum, reflect the variance in job cost against the correct cost codes, and confirm the reconciled amounts sum correctly into the adjusted contract value. Return a reconciliation report tying each allowance to its actual cost, its variance, and its reconciling change order, and flag any allowance where the actual scope appears to exceed what the allowance was defined to cover.

What good output looks like: A reconciliation report with each allowance trued up, its change order generated, and the SOV, contract sum, and job cost updated — with any scope-creep-beyond-allowance flagged before it is absorbed.

Follow-ups:

  • Which of these are credits we owe the owner, and what is the total?
  • Flag any selection that looks like a scope upgrade beyond the allowance.
  • Confirm the adjusted contract sum now reflects all reconciled allowances.

Autonomous — Standing policy for keeping allowances tracked and reconciled through the job.

Manage our allowances continuously under these rules. Track every allowance's selection deadline against the procurement schedule and escalate any slipping deadline that threatens a long-lead item to the project manager. As actual costs become known, match them to the corresponding allowance within its defined inclusions, compute the overage or credit, and draft the reconciling change order for review. As completion approaches, surface any allowance still open or priced-but-unreconciled. Never decide what an allowance was defined to cover when the contract is ambiguous, never determine markup treatment on an overage, and never issue a reconciling change order or credit without my approval. Give me an exception queue and the aggregate open variance, not the whole schedule.

What good output looks like: A managed process where deadline tracking, cost matching, and reconciliation drafting run automatically, while scope interpretation, markup treatment, and issuing change orders or credits stay with a human.

Follow-ups:

  • Show open allowances, slipping selections, and drafts awaiting my approval this week.
  • Which ambiguous allowances need a scope decision from me before I can reconcile?
  • What is our net open allowance variance against the contract sum right now?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

  1. Level 0 — Forgotten placeholders

    Allowances are set at bid and rarely reconciled. The contract sum stays at placeholder values, credits go unissued, and overages are absorbed or fought over at the end.

  2. Level 1 — Tracked

    An allowance schedule lists amounts and inclusions. Reconciliation happens manually and inconsistently, often late in the project.

  3. Level 2 — Reconciled

    Actual costs are matched to allowances within their defined scope, reconciling change orders and credits are issued, and selection deadlines are tracked against procurement.

  4. Level 3 — Assisted

    Reconciliations and reconciling change orders are drafted from actual cost within defined inclusions, selection-deadline slippage is surfaced, and scope-creep-beyond-allowance is flagged.

  5. Level 4 — Operated

    Deadline tracking, cost matching, and reconciliation drafting run unattended inside guardrails, while humans own scope interpretation, markup treatment, and issuing change orders or credits.

Common questions

What is the difference between an allowance and a contingency?

An allowance covers scope that is known but not yet specified — a finish selection or a specialty item whose choice is deferred — carried at an agreed value and reconciled to actual cost. A contingency covers unknown risk — the things that might go wrong but are not yet identified — and is drawn down only when a specific risk materializes. An allowance always maps to a defined piece of scope; a contingency is a reserve against uncertainty with no specific scope attached until it is used.

What is the most important thing to get right about an allowance?

Its inclusions and exclusions. The single biggest source of allowance disputes is disagreement over what the allowance covered — material only, or material plus freight, labor, installation, and markup. Defining that precisely in the contract at signing is worth more than getting the allowance amount exactly right, because an accurately sized allowance with ambiguous scope still ends in a fight, while a clearly scoped allowance reconciles cleanly even if the amount was off.

Who benefits if the actual cost comes in under the allowance?

The owner, through a credit that reduces the contract sum. Because an allowance is a placeholder to be trued up in both directions, an underage is not the contractor's windfall — it is money that must be credited back. This is exactly why reconciliation discipline matters: an allowance that comes in under but is never reconciled leaves the owner paying for a credit it was owed, which is both a contractual and an ethical problem for the contractor.

Does markup apply when an allowance overage becomes a change order?

It depends on the contract, which is precisely why the treatment should be stated when the allowance is written. Some contracts allow the contractor's standard overhead and profit on the overage amount, some allow it only on the portion above the allowance, and some fold markup into the original allowance so no additional markup applies. Leaving this unaddressed guarantees a dispute at reconciliation, so the markup treatment on overages should be spelled out alongside the inclusions.

Read this article as markdown · Browse all 110 objects