Construction Contingency Management: How GCC Contractors Budget, Track, and Release Contingency Without Losing Control

The Contingency Problem Nobody Talks About

Every GCC construction budget has a contingency line. Most contractors set it at 3–5% of contract value, drop it into the budget as a comfort buffer, and then watch it disappear before the halfway mark. By the time the project director asks why contingency is 70% consumed at month 4, nobody can give a coherent answer.

Contingency is not the problem. The absence of a management system around it is. On a SAR 250M project, a 4% contingency is SAR 10M. That is not a rounding error — it is a cost centre with its own risk profile, and it deserves the same discipline as any other budget line.

Contingency vs Provisional Sum vs Management Reserve

Three concepts get bundled together on most GCC cost reports under a single contingency label. Separating them is the first step to managing them.

Contingency Reserve

Allocated to cover identified risks that may or may not materialise. Foundation conditions, design development gaps, productivity uncertainty on complex MEP scope, subcontractor performance variance. You know these are possible; you do not know whether they will happen. Contingency reserve is sized from the risk register — not from a percentage rule.

Provisional Sums

Budget placeholders for defined scope items where cost is genuinely uncertain at contract award: client-nominated subcontractors, specialist equipment, undefined fit-out elements. Unlike contingency, provisional sums are almost always spent — they just get spent on the thing they were provisioned for, which makes them fundamentally different from risk-based contingency.

Management Reserve

Held at portfolio or company level for unknowns that cannot be tied to a specific risk. The true catch-all. Typically 1–2% on a large GCC project, controlled by the CFO or Commercial Director rather than the project team.

Treating these three as one undifferentiated pool is how GCC contractors end up running out of contingency on projects that have not yet hit their identified risks. The provisional sums were spent correctly, the management reserve was drawn informally, and the actual risk contingency was never properly ring-fenced.

How GCC Contractors Get Contingency Sizing Wrong

The standard approach — 3% for a clean civil scope, 5% for complex MEP, 7–10% for design-and-build in early design — produces numbers that feel right but have no traceable basis. When a client or auditor asks what SAR 12M in contingency covers, the answer is it is 4% of contract value rather than it is the expected value of these seven quantified risks plus a 1.3 correlation loading.

A more defensible approach builds contingency from the risk register. Quantify each identified risk — probability multiplied by estimated cost impact — and aggregate the expected values. Apply a correlation factor (risks on large GCC projects rarely materialise independently). Add a residual allowance for risks identified but not yet fully characterised. The result is a contingency that can be explained line by line and adjusted as risks resolve or escalate.

For a SAR 300M civil package, the difference between a flat 3% allowance (SAR 9M) and a risk-register-based calculation might be SAR 6M to SAR 15M, depending on design stage and site complexity. The number matters less than knowing exactly what it covers.

Three Failure Patterns That Drain Contingency Before Risk Events Arrive

1. The Free Money Effect

When contingency appears as a visible balance in every project report, site teams treat it as available slack. We have SAR 8M in contingency translates informally into we have SAR 8M to work with. Requests for specification upgrades, goodwill variations to difficult subcontractors, and informal scope extensions start being approved against the contingency balance rather than processed as variation claims. By month 6, the SAR 8M is SAR 2M — and the actual risk events have not started.

2. Contingency Without a Governance Chain

On many GCC construction projects, there is no defined approval process for contingency draws. The QS adds a line to the cost report, the PM approves by email, and the CFO finds out three months later at a board review. On a SAR 200M project running across 8 active packages, this produces a SAR 15M contingency that is consumed and unaccountable — no draw register, no risk register reference, no audit trail.

3. No Link to the Risk Register

Contingency gets drawn against reasons that have nothing to do with the risks it was sized to cover. Productivity shortfalls — which should have been in the risk register — trigger a draw. Meanwhile, the foundation condition risk that was explicitly priced at SAR 3M is still open, still probable, and no longer funded. The contingency balance looks green. The actual risk exposure is much worse.

What a Functioning Contingency System Looks Like

Four Legitimate Draw Triggers

A well-governed contingency has four — and only four — valid reasons for a draw:

• An identified risk materialises — draw against the risk register entry, close the risk or reduce its probability score, document actual versus estimated cost
• A scope uncertainty resolves higher — a provisional sum finalises above budget; the difference is drawn from contingency with a reference to the provisional sum line
• Design development produces a cost above the allowance — relevant on design-and-build and early-contractor-involvement contracts where design was incomplete at award
• Force majeure or genuinely unforeseeable circumstances — events outside risk register assumptions, with contemporaneous documentation

Site team inefficiency, poor subcontractor productivity, specification upgrades, and commercial goodwill are not contingency events. They belong in the cost management system as variations if client-caused, or operational underperformance if contractor-caused.

Governance Thresholds

Define approval authority in writing before mobilisation and make it part of the project controls procedure:

• Up to SAR 100K — Project Manager approval
• SAR 100K to SAR 500K — Commercial Director approval
• SAR 500K and above — Board or steering committee approval
• Any draw against a risk with less than 50% probability — mandatory risk register review before approval

The Draw Register

Every contingency draw should produce a register entry: date, amount, risk register reference, approver name, and remaining balance after draw. The register is a project document, not a cost report footnote. On open-book contracts with Aramco, NEOM, or ROSHN clients, it will be requested — and its absence reads as a controls failure.

Separate Reporting Lines

Contingency should never appear in the same cost code as operational budget. Report it separately — with sub-ledger detail showing each draw — in every monthly cost report. The balance should be explainable in one paragraph at any point in the project.

Contingency and FIDIC Contracts

FIDIC contracts do not reference the contractor's internal contingency directly — that is an internal construct. But two provisions interact directly with how contingency should be managed.

Provisional Sums (FIDIC Clause 13.5): The Engineer's authority to instruct expenditure against provisional sums means these must be tracked separately from risk contingency, with actual expenditure recorded against each provisional sum line. Bundling provisional sums into a contingency pool creates disputes at final account and misrepresents the contract cost structure.

Unforeseeable Physical Conditions (FIDIC Clause 4.12): When a genuinely unforeseeable site condition arises, the contractor's ability to recover hinges on a Clause 20.2.1 notice, contemporaneous records, and a quantified cost impact. Contractors who draw contingency against a Clause 4.12 event without issuing a formal notice simultaneously lose their contingency and their contractual entitlement. Both disciplines — contingency management and FIDIC notice management — must run in parallel.

Connecting Contingency to the Rest of the Cost System

Contingency management without live cost data is guesswork. A system that functions requires four things:

• Live committed costs — POs, work confirmations, and timesheets feeding the cost report in real time so the remaining contingency reflects actual expenditure, not estimated
• A live change order register — separating approved, instructed, and submitted variations so variation risk is not double-counted against the contingency balance
• An updated risk register — probability scores adjusting as risks resolve or intensify, so the contingency balance reflects current exposure rather than opening-day assumptions
• WBS-level EAC (Estimate at Completion) — so the contingency balance is compared against a credible forecast gap, not a historical budget line that no longer reflects reality

When these are in place, the contingency balance is a meaningful number. Without them, contingency trends toward zero and surprises everyone when it gets there.

Five Starting Steps

1. Separate contingency from provisional sums immediately — create distinct budget lines and track them independently from the first cost report. They must never share a cost code.
2. Size contingency from the risk register, not a percentage rule — build the register before mobilisation, quantify the expected value of each identified risk, and document the basis. It protects you at final account and in client audits.
3. Define approval thresholds in writing before any draw occurs — three tiers minimum covering PM, Commercial Director, and Board levels. Make them part of the project controls procedure, not a PM's informal discretion.
4. Require a risk register reference on every draw request — if a draw cannot be tied to an identified risk or a genuine design uncertainty, it is not a contingency event. Return it to the cost management process as a variation claim or operational underperformance.
5. Report contingency draws separately in every monthly cost report — with draw amount, purpose, risk reference, approver, and remaining balance. Clients on open-book contracts will demand it; it protects internal governance on every contract type.