A contingency percentage only becomes meaningful when it is read against buyout, design completeness, allowances, exclusions, changes, schedule, and the scope still exposed to pricing.
Start by naming the contingency
A development budget may include owner contingency, contractor contingency, design contingency, lender reserves, escalation, or allowances that appear to serve a similar purpose. They are not automatically interchangeable. The governing contracts, budget, and loan requirements should establish who controls the money, when it may be used, and whether it remains available to complete the project.
A single combined percentage can hide those distinctions. Before assessing adequacy, the review should identify each contingency or reserve, its current amount, its intended use, and any restrictions or shared claims on the same funds.
Measure the uncertainty still in the project
Contingency should be read against the work that remains exposed. Design completion, contractor and subcontractor buyout, allowances, alternates, exclusions, owner-furnished items, utilities, permitting, hazardous materials, existing conditions, market escalation, and schedule can each create a different kind of cost pressure.
The same percentage can mean very different things on two projects. A substantially bought-out project with coordinated documents and limited unresolved scope may present one profile; an early guaranteed maximum price with broad allowances, exclusions, incomplete design, and long-lead exposure may present another.
Separate known costs from residual risk
Known or reasonably identified costs should not remain buried in contingency simply because a final change order has not been executed. Pending changes, unresolved scope, expected permit or utility costs, design-development items, and identified budget gaps should be shown separately enough for the lender to understand what has already claimed part of the cushion.
The review should also distinguish gross contingency from the amount reasonably available after known and potential uses. That does not turn every early estimate into a committed cost; it prevents the same dollars from appearing available while also being relied upon to cover identified exposure.
Reconcile the budget before judging the ratio
A contingency ratio is only as reliable as its denominator and source data. The consultant should understand whether the percentage is measured against hard cost, remaining cost, unbought work, total development cost, or another base, and whether budget transfers have changed the apparent result.
A useful plan and cost review connects the development budget, construction contract, schedule of values, allowances, alternates, owner costs, soft costs, financing costs where included, and other identified sources and uses. Gaps or duplication in that reconciliation can matter more than a nominal contingency benchmark.
Use closing as the monitoring baseline
The closing report should preserve the assumptions behind the contingency conclusion: design status, buyout, key allowances and exclusions, known changes, unresolved information, schedule conditions, and funds controlled outside the construction contract. Those assumptions become comparison points during later draw reviews.
During monitoring, contingency use should be read with approved and pending changes, transfers, newly identified exposure, buyout progress, remaining work, and cost to complete. The lender’s documents and credit decision govern what is required; the consultant’s role is to make the technical and budget relationships visible within the agreed scope.