Contingency, Management Reserve, and a Workaround That Creates New Risk

The $95,000 comes from the contingency reserve. Reasons:

1. It is an identified risk. 'Failed network cutover' was in the register with a 20% probability and a $180,000 impact. Contingency reserve exists for the residual risk of identified risks; the response plan should have named a pre-approved vendor and a trigger condition.
2. Management reserve is for unknown-unknowns - work outside the baseline scope and outside the identified risk set. This event is neither; it was forecast.
3. Classification has governance consequences. Contingency draws are typically approved by the project manager within delegated authority and logged; management reserve draws require sponsor approval and usually a baseline or scope change. Misclassifying this would bypass the PM's authority and distort the cost baseline.

Practical steps:

• Record the draw in a reserve log: date, risk ID, amount, approver, remaining balance ($240k − $95k = $145k).
• Reconcile the vendor invoice against the emergency purchase order before release.
• Since the schedule slipped two weeks, raise a change request so the baseline and EAC reflect reality.
• Give the controller the classification and supporting register extract before the change board, not at it.

The sponsor is directionally right that this draw belongs to contingency, but 'draw it all' is not a blank cheque - each draw must still be tied to a risk ID, an approver, and a logged balance.

It is a secondary risk: it did not exist until the workaround created it, so it is not covered by the original cutover response and must be assessed on its own merits.

Quantify:

• EMV if simply accepted = 0.40 × $60,000 = $24,000.
• Compare against the cost of proactive treatment. If reconciliation can be done now for $15,000–$20,000, that is cheaper than the EMV and removes the tail. If the only mitigation costs $50,000, accepting with a reserve allocation may be rational - but tolerance for customer-record errors in a bank is likely low because of regulatory reporting.

Process:

1. Add it to the register with an owner, trigger, probability, impact, and chosen response.
2. Decide on mitigation cost versus EMV and on non-financial exposure - the $60,000 estimate may understate regulatory and reputational cost.
3. If mitigated, fund from contingency and log the draw. If accepted, hold the $24,000 EMV as a reserve allocation so the remaining reserve forecast stays honest.
4. Re-examine the workaround for further secondary risks before formally closing the original risk.

Reserve forecast after both items: $240k − $95k = $145k remaining in contingency, against a $24k expected exposure from the secondary risk plus whatever else remains live on the register. Send that forecast to the sponsor with the change board pack so the draw decision is made against a balance, not an impression.

If remaining known risks exceed the reserve:

1. Quantify before escalating. Run a quantitative risk analysis - Monte Carlo on cost and schedule, or at minimum an EMV roll-up plus a worst-case scenario. Report reserve need at P50 and P80 rather than a single point, so the conversation is about tolerance, not optimism.
2. Escalate to the sponsor for management reserve. That is exactly what management reserve covers: identified exposure beyond the contingency. Present it as a decision with options - release reserve, reduce scope, accept the risk, or a combination - not as a request for money without a trade-off.
3. Re-rank the register by EMV and proximity. Some low-probability, long-dated risks can be accepted with documented rationale, freeing reserve for near-term exposure. Do not cut responses to risks with regulatory or safety consequences.
4. Look beyond acceptance: transfer (insurance, fixed-price subcontracts, warranty clauses) or avoid by resequencing. Transfer usually costs less than the EMV of a large tail risk.
5. If no further funding is available, reduce scope or extend schedule with the sponsor's written acceptance, and record each accepted risk with an owner. An unfunded risk that is merely 'noted' is not managed.
6. Feed back into method. A 7.5% contingency on a migration whose top risk alone carried a $36k EMV was thin once secondary risks appeared. Capture that for the next project's reserve calculation.