What it means
A project budget contains money set aside for identified risks. When a risk occurs, the team asks to use part of the reserve.
Project contingency draw approval rate measures how often eligible requests to draw that reserve receive the required authorized decision under the project's rules. Define the reserve, because contingency for identified risks and a separately controlled management reserve are not the same fund.
PMI discusses project cost reserves tied to risk and distinguishes typical control of contingency and management reserves; the article offers project-management context, not permission for any particular person to spend a customer's money. Define the draw too, since a forecasted possibility is not a spend request, and name the point when a request enters approval.
Check the risk link, because the draw should connect to a documented risk or approved eligibility reason, and show the estimate by identifying amount, currency, why ordinary budget is insufficient and the expected remaining reserve. Check authority, since approval may depend on amount, category, contract or funding source.
Record the decision as approved, declined, revised or pending, which are distinct states. Choose the denominator carefully, because all eligible draw requests with decisions or all requests submitted yield different rates, and choose the numerator by counting decisions by authorized approvers, not informal assent in project chat.
Check actual use, as a draw approval reserves budget but does not prove a purchase occurred. Avoid double allocation, since one risk event can generate two requests against the same exposure and they should be reconciled.
Track remaining reserve so that starting reserve, approved draws, releases and current available amount tie, and handle unused allocation by returning unused reserve under the process if the risk does not occur or actual cost is lower. Check the baseline, because drawdown can change forecast to complete without automatically changing the project's authorized scope, and protect contract rights, since a customer-requested change may need a separate change order even when internal contingency could fund it.
Show pending requests, as a high approval rate among decided requests can hide large requests awaiting review, and use value context, since a count-based approval rate can obscure a few very large draws. Assess urgency, because a safety response may need an emergency route with documented retrospective review, and avoid gaming, since splitting one draw into several small requests to evade an approval threshold defeats the control.
Check cost type, as an ordinary planned expense should not be relabeled a risk draw merely because its budget line is exhausted, and preserve evidence by keeping the risk event, cost estimate, approval, allocation and later actual spend. Reflect approved reserve use in the current forecast, compare periods because different project phases have different risk realization patterns, audit declined draws since they can lead to an alternate response or additional funding request, keep sponsors informed of material reserve consumption, compare later supplier charges with the approved allocation and escalate any excess separately, leave the customer funding decision to change control because internal reserve does not prove the customer owes additional payment, explain the underlying risk when reserve use rises quickly, and use the rate to monitor decision control without rewarding approval for its own sake.
In practice
Real-world examples.
Example
A risk response requests $10,000 from an approved contingency pool and gets signed authorization before allocation.
Example
A project lead splits one $50,000 need into five requests to avoid a threshold; an audit treats them as one decision issue.
Example
An approved draw is partly unused and the remainder is returned to available reserve.
Formula
Calculation
Illustrative approval rate = eligible contingency draw requests formally approved / eligible requests with final decisions x 100. Show pending requests, amounts and remaining reserve separately.
Worked example. A fictional project has a $200,000 contingency reserve and 14 eligible draw requests in a quarter. Twelve have final decisions: 9 approved and 3 declined, while 2 are still pending.
- Approval rate = 9 / 12 x 100 = 75%.
- If the approved draws total $120,000, remaining reserve is $200,000 - $120,000 = $80,000, before any unused allocation is returned.
- The report also shows the two pending requests and their amounts, so the 75% is not read as the whole picture.Case study
Seen in the real world.
This entirely fictional case follows Meridian Infrastructure. A supply risk materialized and the team requested reserve for alternative parts. Finance found that the initial request duplicated a cost already covered by a supplier credit. The team corrected the amount and obtained the proper approval before committing any expenditure. The example authorizes no real purchase or fund transfer.
Watch out
Common mistakes.
- Using contingency for ordinary planned work without a risk basis.
- Counting approval as evidence funds were actually spent.
- Splitting requests to avoid approval limits.
Questions
People also ask.
Is a high approval rate good?
Not necessarily. Review the quality and outcomes of risk decisions.
Is contingency the same as management reserve?
No. Control and purpose often differ by project governance.
Does approved allocation authorize a purchase?
Only if separate procurement and money approvals also cover it.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related