Why an allowance needs a register

An allowance can cover an unknown quantity, an unfinished design, a pending selection, or a known scope that cannot yet be measured. Those conditions do not share the same review path, so a single lump sum hides important differences. The register records the allowance type, the scope it covers, the basis for the amount, the owner, the expiry date, and the evidence that would replace it with a measured line.

Separate allowance from contingency

An allowance addresses a specific known uncertainty. Contingency addresses residual risk across the estimate. Combining them makes it difficult to see whether a design gap has been closed or a risk posture has changed.

Keep the terms distinct in the summary and in the review notes. If a line is moved from allowance to contingency, record the reason and the reviewer. The routine is easier to hand off through cost estimator support.

Set a trigger for review

Each allowance should have a trigger, such as a design milestone, a bid package receipt, a vendor selection, or a scheduled review date. The trigger tells the team when the allowance should be tested again. When the trigger is reached, the owner either replaces the allowance with measured scope, adjusts it with new evidence, or marks it unresolved.

The estimate should not carry an expired allowance without a decision. The evidence path is described in the bid package coverage map.

Report the uncertainty at release

The release note lists open allowances, their owners, their expiry dates, and the decisions still needed. This gives the reviewer a view of what is known, what is estimated, and what remains unresolved. A smaller number of well-described allowances is easier to review than a large allowance with no scope note.

The register should improve the question, not merely move it. For a broader review frame, use the AACE recommended practices.

Source notes

External reference: AACE International recommended practices. Background sources: GAO cost estimating guide and Census construction spending program.

Allowance register fields
FieldPurposeReview evidence
Allowance typeDistinguishes design, quantity, and selection uncertaintyScope note and source
OwnerNames the person who will resolve itAssignment and review date
TriggerDefines when the allowance is tested againMilestone or document receipt

Frequently Asked Questions

How is an allowance different from contingency?

An allowance covers a specific known uncertainty. Contingency covers residual risk across the estimate. They should remain separate in the summary.

What makes an allowance reviewable?

A scope note, a basis, an owner, an expiry or trigger date, and the evidence that would replace it with measured scope.

Should an expired allowance stay in the estimate?

Only with a recorded decision. Otherwise the owner should replace it, adjust it with new evidence, or mark it unresolved.

Construction EstimatingConstruction EstimatingCost Support