# Build contingency from named residual risks

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Build contingency from named residual risks

ID: MHC-D-RESEARCH-0625 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/build-contingency-from-named-residual-risks

A round buffer is easy to add and hard to learn from.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A team adds 20% to every estimate because projects are uncertain.

### Avoid when

- Not every risk supports a credible numeric probability; qualitative contingency governance can be more honest than false precision.

### Explanation

List material risks that remain after planned mitigation. For each, state trigger, plausible impact and whether the impact is already inside the base estimate. Use these residual risks—plus empirical forecast error where appropriate—to justify contingency instead of hiding a generic pad in every task.

### Steps

1. Risk is named.
2. Mitigation is named.
3. Residual impact is described.
4. Double counting against base estimate is checked.
5. Contingency rationale is recorded.

### Example

A migration reserve covers possible manual repair after a reconciliation failure, while normal validation effort remains in the base estimate.

### Check

A reviewer can trace contingency to uncertainty rather than a habitually padded number.

### Limits

- Not every risk supports a credible numeric probability; qualitative contingency governance can be more honest than false precision.

### Evidence and sources

- supports: The Green Book treats contingency as an allowance for residual risk and remaining optimism bias rather than as an unexamined extra percentage. — RS-F874002E4A58CC3B. How contingency is funded, governed and released depends on organization and project type. (Contingency)
- supports: IPA guidance treats identified risks, mitigation costs, residual probability and impact as part of estimating rather than hiding all uncertainty inside the base estimate. — RS-B3FC6B5B65061AB3. Qualitative or poorly evidenced probability estimates should not be dressed up as precise expected values. (Accounting for risk)
- supports: The Green Book distinguishes prevention or mitigation costs from contingency for risks that remain after mitigation. — RS-F874002E4A58CC3B. Organizations may use different accounting labels; the useful distinction is planned work versus allowance for residual uncertainty. (Optimism bias and contingency)
- RS-F874002E4A58CC3B: The Green Book (2026) — https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government/the-green-book-2026
- RS-B3FC6B5B65061AB3: Cost Estimating Guidance — https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/keep-mitigation-work-out-of-the-hidden-buffer
