# Estimate the delivery system, not only the hands-on work

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

Build project forecasts that preserve scope, active effort, waits, dependencies, rework, residual risk, confidence and historical error so priority and optimism do not silently become shorter dates.
Collection kind: collection
Source: https://vedokrok.com/collections/estimate-the-delivery-system-not-only-the-hands-on-work
Version: 0.1.0

---

## Define the estimate object before estimating it

ID: MHC-D-RESEARCH-0621 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/define-the-estimate-object-before-estimating-it

An estimate without an object is confidence attached to fog.

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

### Use when

- A number is requested before scope, completion state or exclusions are explicit.

### Avoid when

- Do not use scope wording to hide necessary work; exclusions still need an owner or a separate estimate.

### Explanation

Write what is being estimated: deliverable, completion criterion, included work, explicit exclusions and the date or cost dimension. Keep this scope snapshot beside the estimate so later changes are visible rather than mistaken for bad arithmetic.

### Template

Estimate for: [deliverable]. Done means: [criterion]. Includes: [scope]. Excludes: [scope]. Metric: [elapsed time / effort / cost].

### Example

'Three days' becomes 'three working days of consultant effort to prepare and validate the file; business approval and production import excluded.'

### Check

Another person can tell exactly what the estimate does and does not cover.

### Limits

- Do not use scope wording to hide necessary work; exclusions still need an owner or a separate estimate.

### Evidence and sources

- supports: IPA cost-estimating guidance recommends documenting assumptions and representing uncertainty with reasonably optimistic, most-likely and reasonably pessimistic positions where appropriate. — RS-B3FC6B5B65061AB3. Three-point estimates are inputs to judgment or modelling, not proof of a probability distribution. (Estimate ranges and assumptions)
- RS-B3FC6B5B65061AB3: Cost Estimating Guidance — https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/pin-the-scope-snapshot-to-every-material-forecast

---

## Estimate active effort and elapsed time separately

ID: MHC-D-RESEARCH-0622 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/estimate-active-effort-and-elapsed-time-separately

Two hours of work can still occupy three calendar days.

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

### Use when

- A task contains approvals, queues or external waits and one duration number hides them.

### Avoid when

- Wait times can dominate delivery and may be highly variable; do not pretend they are fixed just because the active work is well known.

### Explanation

Estimate hands-on effort separately from elapsed time. Then list the waits, calendars and dependencies that turn effort into delivery time. Use effort for capacity planning and elapsed time for stakeholder commitments; do not substitute one for the other.

### Example

A 90-minute data check needs a two-day elapsed window because the source owner may answer only next morning.

### Check

The forecast can explain why elapsed time differs from work effort.

### Limits

- Wait times can dominate delivery and may be highly variable; do not pretend they are fixed just because the active work is well known.

### Evidence and sources

- supports: IPA cost-estimating guidance recommends documenting assumptions and representing uncertainty with reasonably optimistic, most-likely and reasonably pessimistic positions where appropriate. — RS-B3FC6B5B65061AB3. Three-point estimates are inputs to judgment or modelling, not proof of a probability distribution. (Estimate ranges and assumptions)
- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- RS-B3FC6B5B65061AB3: Cost Estimating Guidance — https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance

### Vedokrok editorial review

Estimate the work and the calendar separately

Six person-hours of work do not promise a result six hours from now. A delivery forecast also needs the people’s availability, the sequence and the waits.

#### Give each number a unit

Record the required effort in person-hours or person-days. Separately state the forecast start and finish, the working calendar and the assumptions about available capacity. A hypothetical review needing three person-hours may wait until tomorrow because its only qualified reviewer is unavailable today.

#### Build the route to completion

Place required work and dependencies in order, identify what can genuinely run in parallel, and account for approval windows and other waits. Keep uncertain waits visible instead of treating them as fixed just because the active work is familiar. If more people are proposed, check that the work can be divided and that coordination does not consume the expected saving.

**Editorial takeaway:** Check that the forecast explains both the effort needed and the elapsed window. Do not silently switch between working days, calendar days and person-days, or assume twice the staff means half the duration.

#### Editorial evidence

- supports: GAO distinguishes work or effort from activity duration and makes duration depend on resource availability and the applicable working calendar. — gao-schedule-assessment-16-89g. Selected passages inspected on 2026-10-04, PDF pages62–63 and76. This directly supports the time distinction; the prior cost-range evidence alone was less specific. The review example is hypothetical. (Best Practice3, Resources, Effort, and Duration, printed pp49–50; Best Practice4, printed p63)
- limits: GAO warns that doubling available resources need not halve duration and that complex work may take longer as coordination increases. — gao-schedule-assessment-16-89g. This limits simple effort-to-time arithmetic. No staffing intervention or delivery improvement was tested here. (Best Practice3, Labor Resources, printed p50 / PDF page63)
- gao-schedule-assessment-16-89g: Schedule Assessment Guide: Best Practices for Project Schedules — https://www.gao.gov/assets/gao-16-89g.pdf

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/put-the-slow-external-dependency-on-the-forecast

---

## Put the slow external dependency on the forecast

ID: MHC-D-RESEARCH-0623 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/put-the-slow-external-dependency-on-the-forecast

The calendar belongs partly to whoever must answer next.

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

### Use when

- A plan estimates only work controlled by the team.

### Avoid when

- Do not turn dependency tracking into blame; the goal is to model the real system and improve it.

### Explanation

Name approvals, vendor responses, environments, data deliveries and other dependencies that can block progress. For each, record owner, expected response window and fallback or escalation. If one dependency can dominate delivery, surface it in the headline forecast.

### Checklist

- External dependencies named.
- Owner or provider named.
- Expected response window recorded.
- Fallback or escalation path exists.
- Dominant dependency visible in the delivery forecast.

### Example

A transport can be prepared today but production import depends on a change manager's approval window; the forecast states that dependency explicitly.

### Check

A missed delivery can be decomposed into controlled work and dependency latency.

### Limits

- Do not turn dependency tracking into blame; the goal is to model the real system and improve it.

### Evidence and sources

- supports: IPA cost-estimating guidance recommends documenting assumptions and representing uncertainty with reasonably optimistic, most-likely and reasonably pessimistic positions where appropriate. — RS-B3FC6B5B65061AB3. Three-point estimates are inputs to judgment or modelling, not proof of a probability distribution. (Estimate ranges and assumptions)
- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- RS-B3FC6B5B65061AB3: Cost Estimating Guidance — https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance

No review details supplied.

---

## Use a range when the uncertainty is asymmetric

ID: MHC-D-RESEARCH-0624 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/use-a-range-when-the-uncertainty-is-asymmetric

A symmetric plus-or-minus can hide a long tail.

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

### Use when

- The most likely duration is known but delays can be much larger than early finishes.

### Avoid when

- Three points do not establish exact probabilities; avoid fake precision unless you have a defensible distribution.

### Explanation

When the downside and upside are not balanced, record reasonably optimistic, most-likely and reasonably pessimistic values rather than a central estimate with a cosmetic symmetric margin. State what assumption changes between the points.

### Example

A data cleanup may take 1 day if errors are already classified, 2 days most likely, and 5 days if manual reconciliation is required.

### Check

The range explains why the high side is wider or narrower than the low side.

### Limits

- Three points do not establish exact probabilities; avoid fake precision unless you have a defensible distribution.

### Evidence and sources

- supports: IPA cost-estimating guidance recommends documenting assumptions and representing uncertainty with reasonably optimistic, most-likely and reasonably pessimistic positions where appropriate. — RS-B3FC6B5B65061AB3. Three-point estimates are inputs to judgment or modelling, not proof of a probability distribution. (Estimate ranges and assumptions)
- 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/sweep-one-uncertain-assumption-across-a-plausible-range

---

## 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

---

## Keep mitigation work out of the hidden buffer

ID: MHC-D-RESEARCH-0626 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/keep-mitigation-work-out-of-the-hidden-buffer

Planned risk reduction is still planned work.

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

### Use when

- A known prevention task is buried inside contingency because it may not feel like 'real work.'

### Avoid when

- Organizations use different accounting conventions; preserve the conceptual distinction even if financial labels differ.

### Explanation

Put deliberate prevention and mitigation activities—tests, rehearsals, backups, reviews, compatibility checks—into the base plan when you intend to perform them. Reserve contingency for uncertainty that remains. This keeps essential safety or quality work from being squeezed out to 'save buffer.'

### Example

A canary run is scheduled as normal delivery work; extra repair time if the canary exposes unexpected defects sits in contingency.

### Check

The base plan contains the risk-reduction work you actually intend to do.

### Limits

- Organizations use different accounting conventions; preserve the conceptual distinction even if financial labels differ.

### Evidence and sources

- 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

No review details supplied.

---

## Separate the forecast from the commitment

ID: MHC-D-RESEARCH-0627 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/separate-the-forecast-from-the-commitment

A forecast describes uncertainty; a commitment adds a decision and consequence.

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

### Use when

- A probabilistic estimate is repeated as a promise, or a management date is presented as the statistically expected date.

### Avoid when

- A label does not excuse chronic missed commitments; committed dates still need feasibility and accountability.

### Explanation

Label which statement you are making. A forecast says what the evidence suggests. A commitment says what the organization chooses to stand behind, possibly with scope, priority or reserve changes. If the commitment is tighter than the forecast, name the intervention that makes it plausible.

### Example

'Most likely 8–10 days' can coexist with 'we commit to the 15th by cutting optional scope and reserving reviewer capacity.'

### Check

Stakeholders can tell whether a date came from evidence, a management choice or both.

### Limits

- A label does not excuse chronic missed commitments; committed dates still need feasibility and accountability.

### Evidence and sources

- supports: The 2026 Green Book recommends explicitly accounting for optimism bias in cost, benefit and duration estimates and using historical forecast errors from similar proposals where available. — RS-F874002E4A58CC3B. The guidance is for UK public appraisal; the transferable principle is empirical correction, not a universal percentage uplift. (Optimism bias)
- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- 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.

---

## Attach confidence to the evidence, not to your tone

ID: MHC-D-RESEARCH-0628 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/attach-confidence-to-the-evidence-not-to-your-tone

Confidence should describe what is known, not how strongly the estimator speaks.

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

### Use when

- A date is delivered confidently even though key inputs are still unknown.

### Avoid when

- Ordinal confidence labels are editorial aids, not calibrated probabilities unless the team has defined and tested them.

### Explanation

State the evidence maturity behind the forecast: known scope, validated dependencies, available historical analogues and unresolved unknowns. Use a wider range or lower confidence when important inputs are still speculative, then narrow it when real uncertainty has been removed.

### Steps

1. A confidence statement names the evidence that supports it and what is still missing.

### Example

A draft integration estimate stays wide until the external API and sample payload are tested.

### Check

A confidence statement names the evidence that supports it and what is still missing.

### Limits

- Ordinal confidence labels are editorial aids, not calibrated probabilities unless the team has defined and tested them.

### Evidence and sources

- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- 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/let-ranges-narrow-only-when-uncertainty-is-actually-removed

---

## Pin the scope snapshot to every material forecast

ID: MHC-D-RESEARCH-0629 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/pin-the-scope-snapshot-to-every-material-forecast

A forecast can be wrong; it can also be about a different job.

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

### Use when

- A forecast is later judged against a project that changed shape.

### Avoid when

- Do not freeze harmless wording changes into formal re-estimation; use a materiality threshold appropriate to the work.

### Explanation

Store the estimate with its scope version or a short snapshot of included deliverables, assumptions and dependencies. When scope changes materially, create a new forecast and preserve the old one for learning rather than silently editing history.

### Steps

1. Forecast date recorded.
2. Scope/version recorded.
3. Key assumptions recorded.
4. Material change creates a new forecast.
5. Old forecast preserved for calibration.

### Example

The original estimate covered 1,000 records; after the scope grows to 1,800, the revised estimate is a new forecast rather than a rewrite of the original.

### Check

Forecast error can be separated from scope change.

### Limits

- Do not freeze harmless wording changes into formal re-estimation; use a materiality threshold appropriate to the work.

### Evidence and sources

- supports: The 2026 Green Book recommends explicitly accounting for optimism bias in cost, benefit and duration estimates and using historical forecast errors from similar proposals where available. — RS-F874002E4A58CC3B. The guidance is for UK public appraisal; the transferable principle is empirical correction, not a universal percentage uplift. (Optimism bias)
- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- 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 (use_before): https://vedokrok.com/knowledge/re-estimate-when-evidence-changes-not-when-anxiety-spikes

---

## Re-estimate when evidence changes, not when anxiety spikes

ID: MHC-D-RESEARCH-0630 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/re-estimate-when-evidence-changes-not-when-anxiety-spikes

A forecast should move because the model changed.

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 repeatedly changes the date in response to pressure without new information.

### Avoid when

- Sometimes a commitment must change for business reasons even without new delivery evidence; label that as a commitment change, not a forecast discovery.

### Explanation

Define evidence triggers that justify revision: scope change, dependency delay, measured throughput, failed test, discovered rework or resolved uncertainty. Record the changed input and its effect on the range. Pressure can trigger a review, but it is not itself evidence.

### Steps

1. Every material forecast change points to a changed input, assumption or risk state.

### Example

A failed data-quality check adds a reconciliation step, so the forecast moves; a manager asking twice does not.

### Check

Every material forecast change points to a changed input, assumption or risk state.

### Limits

- Sometimes a commitment must change for business reasons even without new delivery evidence; label that as a commitment change, not a forecast discovery.

### Evidence and sources

- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- RS-B3FC6B5B65061AB3: Cost Estimating Guidance — https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance

No review details supplied.

---

## Count rework as a forecast component

ID: MHC-D-RESEARCH-0631 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/count-rework-as-a-forecast-component

The second pass still consumes the calendar.

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

### Use when

- Plans assume work flows forward once, even when review and correction are normal.

### Avoid when

- Do not normalize chronic avoidable defects as inevitable rework; use the data to improve the process.

### Explanation

For work with known review loops, estimate expected correction and revalidation effort explicitly rather than pretending first-pass acceptance is the default. Track why rework occurred so avoidable defects can be separated from normal iteration.

### Checklist

- Review step included.
- Typical correction loop included.
- Revalidation included.
- Avoidable defect rework tagged separately.
- Unexpected rework captured for later learning.

### Example

A data migration estimate includes one validation-and-correction cycle instead of treating every failed row as an unforeseeable surprise.

### Check

The plan includes the repeat work that normally occurs in comparable deliveries.

### Limits

- Do not normalize chronic avoidable defects as inevitable rework; use the data to improve the process.

### Evidence and sources

- supports: The 2026 Green Book recommends explicitly accounting for optimism bias in cost, benefit and duration estimates and using historical forecast errors from similar proposals where available. — RS-F874002E4A58CC3B. The guidance is for UK public appraisal; the transferable principle is empirical correction, not a universal percentage uplift. (Optimism bias)
- supports: Supplementary Green Book optimism-bias guidance recommends basing adjustments on data from past or similar projects and collecting local data to improve future estimates. — RS-3AABED087865223D. Reference classes must be genuinely comparable; irrelevant historical projects can make an estimate worse. (Introduction and making adjustments)
- 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-3AABED087865223D: Supplementary Green Book Guidance: Optimism Bias — https://assets.publishing.service.gov.uk/media/5a74dae740f0b65f61322c72/Optimism_bias.pdf

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/explain-forecast-error-by-component

---

## Estimate approvals and integration as deliverables

ID: MHC-D-RESEARCH-0632 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/estimate-approvals-and-integration-as-deliverables

A feature is not delivered when only its middle is done.

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

### Use when

- The implementation is estimated, while review, approval, import and verification are treated as administrative afterthoughts.

### Avoid when

- Some approvals are outside the delivery team's control; include them as dependencies without inventing control.

### Explanation

Treat required approval, integration, deployment, validation and handoff as work packages with owners and dependencies. They may contain little build effort but substantial elapsed risk. Include them in the done definition when the outcome depends on them.

### Example

'Code complete' is not the delivery estimate when transport, business validation and production confirmation are still required.

### Check

The forecast ends at the actual usable outcome, not at the team's favorite internal milestone.

### Limits

- Some approvals are outside the delivery team's control; include them as dependencies without inventing control.

### Evidence and sources

- supports: IPA cost-estimating guidance recommends documenting assumptions and representing uncertainty with reasonably optimistic, most-likely and reasonably pessimistic positions where appropriate. — RS-B3FC6B5B65061AB3. Three-point estimates are inputs to judgment or modelling, not proof of a probability distribution. (Estimate ranges and assumptions)
- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- 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/put-the-slow-external-dependency-on-the-forecast

---

## Let ranges narrow only when uncertainty is actually removed

ID: MHC-D-RESEARCH-0633 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/let-ranges-narrow-only-when-uncertainty-is-actually-removed

Time passed is not evidence gained.

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

### Use when

- A project gets older, so forecasts become narrower by convention even though key unknowns remain.

### Avoid when

- A wide range can be unhelpful if it never supports a decision; pair uncertainty with the next information that can reduce it.

### Explanation

At each stage, identify which uncertainties were resolved and which remain. Narrow the range only when scope, design, dependencies or throughput have become materially better known. If new uncertainty appears, the honest range can widen again.

### Example

After a prototype validates the interface and throughput, the range narrows; after an unexpected compliance review appears, it widens again.

### Check

The width change has an evidence explanation.

### Limits

- A wide range can be unhelpful if it never supports a decision; pair uncertainty with the next information that can reduce it.

### Evidence and sources

- supports: IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature. — RS-B3FC6B5B65061AB3. A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved. (Estimate maturity and range)
- RS-B3FC6B5B65061AB3: Cost Estimating Guidance — https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance

No review details supplied.

---

## Keep priority pressure separate from feasibility evidence

ID: MHC-D-RESEARCH-0634 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/keep-priority-pressure-separate-from-feasibility-evidence

Importance can buy resources or scope changes; it cannot repeal dependencies.

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

### Use when

- A high-priority request is assumed to require less time.

### Avoid when

- Throwing more people at tightly coupled or unfamiliar work can increase coordination cost; added capacity is not automatically added throughput.

### Explanation

When priority rises, first recompute the feasible options: add capacity where work is parallelizable, remove scope, shorten approval paths, accept explicit risk or move other commitments. Do not simply shrink the estimate because the task became important.

### Example

A Monday deadline is met by splitting validation and dropping a nonessential report, not by changing 'five days' to 'two' in the spreadsheet.

### Check

Any accelerated commitment points to a concrete system change.

### Limits

- Throwing more people at tightly coupled or unfamiliar work can increase coordination cost; added capacity is not automatically added throughput.

### Evidence and sources

- supports: The 2026 Green Book recommends explicitly accounting for optimism bias in cost, benefit and duration estimates and using historical forecast errors from similar proposals where available. — RS-F874002E4A58CC3B. The guidance is for UK public appraisal; the transferable principle is empirical correction, not a universal percentage uplift. (Optimism bias)
- 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

No review details supplied.
Related (compare_with): https://vedokrok.com/knowledge/separate-the-forecast-from-the-commitment

---

## Explain forecast error by component

ID: MHC-D-RESEARCH-0635 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/explain-forecast-error-by-component

One error number can hide five different systems.

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

### Use when

- A project was late and the only lesson is 'we underestimated.'

### Avoid when

- Categories are models; keep them simple enough to use and refine them only when they change decisions.

### Explanation

After delivery, compare forecast with actual by components such as active work, wait/dependency time, rework, scope change and realized risks. Keep categories stable enough to compare across projects. Fix the component that repeatedly dominates instead of applying one global pad.

### Steps

1. The post-estimate review identifies the dominant source of forecast error.

### Example

A two-day slip turns out to be almost entirely approval latency, so the next improvement targets the review queue rather than adding 20% to development effort.

### Check

The post-estimate review identifies the dominant source of forecast error.

### Limits

- Categories are models; keep them simple enough to use and refine them only when they change decisions.

### Evidence and sources

- supports: The 2026 Green Book recommends explicitly accounting for optimism bias in cost, benefit and duration estimates and using historical forecast errors from similar proposals where available. — RS-F874002E4A58CC3B. The guidance is for UK public appraisal; the transferable principle is empirical correction, not a universal percentage uplift. (Optimism bias)
- supports: Supplementary Green Book optimism-bias guidance recommends basing adjustments on data from past or similar projects and collecting local data to improve future estimates. — RS-3AABED087865223D. Reference classes must be genuinely comparable; irrelevant historical projects can make an estimate worse. (Introduction and making adjustments)
- 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-3AABED087865223D: Supplementary Green Book Guidance: Optimism Bias — https://assets.publishing.service.gov.uk/media/5a74dae740f0b65f61322c72/Optimism_bias.pdf

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/maintain-a-local-forecast-error-baseline

---

## Maintain a local forecast-error baseline

ID: MHC-D-RESEARCH-0636 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/maintain-a-local-forecast-error-baseline

Your own misses are a dataset if you keep them.

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

### Use when

- Teams repeatedly estimate similar work but every new estimate starts from intuition.

### Avoid when

- Small or changing samples can mislead; audit comparability before treating history as a stable base rate.

### Explanation

For recurring work, store original forecast, scope snapshot, actual outcome and major error components. Periodically summarize bias and spread for comparable work. Use this local history as one input to future forecasts and to check whether estimation changes are actually improving calibration.

### Steps

1. Original forecasts preserved.
2. Actuals recorded.
3. Comparable work grouped.
4. Systematic over/underforecast checked.
5. Spread, not only average error, inspected.
6. Method changes evaluated over time.

### Example

A migration team learns that approval wait is consistently underforecast even when build effort is accurate, so future elapsed forecasts reflect that history.

### Check

A new estimate can cite comparable local forecast errors instead of relying only on memory.

### Limits

- Small or changing samples can mislead; audit comparability before treating history as a stable base rate.

### Evidence and sources

- supports: The 2026 Green Book recommends explicitly accounting for optimism bias in cost, benefit and duration estimates and using historical forecast errors from similar proposals where available. — RS-F874002E4A58CC3B. The guidance is for UK public appraisal; the transferable principle is empirical correction, not a universal percentage uplift. (Optimism bias)
- supports: Supplementary Green Book optimism-bias guidance recommends basing adjustments on data from past or similar projects and collecting local data to improve future estimates. — RS-3AABED087865223D. Reference classes must be genuinely comparable; irrelevant historical projects can make an estimate worse. (Introduction and making adjustments)
- 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-3AABED087865223D: Supplementary Green Book Guidance: Optimism Bias — https://assets.publishing.service.gov.uk/media/5a74dae740f0b65f61322c72/Optimism_bias.pdf

### Vedokrok editorial review

History helps only when the past is actually comparable

A record of forecast misses can turn estimation from memory into evidence. The catch is that a local base rate is useful only when the old work is similar enough to the new work, and when changes in process have not made the old distribution obsolete.

#### Keep the original forecast, not the remembered one

HM Treasury's 2026 Green Book recommends measuring historical forecast errors and using evidence from similar proposals, preferably from the originating organisation when that evidence exists. That principle is easy to weaken in practice: if the old estimate is overwritten after scope changes, the team loses the error it is trying to learn from. Preserve the forecast as it was known at the decision point, the scope and assumptions behind it, and the actual outcome. Then the gap is evidence rather than a story reconstructed after delivery.

#### The outside view is a correction, not an oracle

Reference class forecasting formalises the same move at a larger scale: compare a new forecast with the actual outcomes of comparable past projects instead of relying only on the plan for this project. Flyvbjerg argued that this outside view can reduce optimism and strategic distortion in major-project forecasts. The transfer to ordinary knowledge work should stay modest. A local baseline is not proof that the next project will repeat the average miss; it is a prior check on whether the current estimate is unusually optimistic or pessimistic compared with relevant history.

#### Comparability is the hard part

A recent systematic review of reference class forecasting makes the central trade-off explicit. Broad reference classes provide more data but can mix projects that behave differently. Narrow classes improve similarity but leave fewer observations and therefore less stable estimates. The review also reports evidence that reference class forecasting can lose its advantage when similarity between the target project and the reference projects is weak. This is the strongest reason not to turn every past estimate into one company-wide correction factor. Group work by the features that plausibly change delivery behaviour, and keep the uncertainty visible when the sample is small.

#### Use the baseline to diagnose the system

The most useful local history often shows which component keeps missing. A migration team may estimate build effort well but repeatedly miss approval wait; another team may be accurate until late rework appears. Keep error components such as active effort, waiting, rework, scope change and realised risks when they can be recorded consistently. When tools, workflow, team structure or definition of done changes materially, keep the old data for history but start a visibly new comparison cohort. This is an editorial application of the evidence, not a validated universal forecasting formula.

#### Three questions before you reuse the baseline

How many past cases are enough? There is no universal cutoff. A few highly comparable cases can be informative, but they do not justify a precise stable base rate; report the spread and keep confidence low.

What if the process changed? Do not delete the older cases, but do not pool them automatically. Mark the change and compare recent work separately until you know whether the old error pattern still applies.

Should I add the average historical miss to every new estimate? Not by default. Historical error is an input to judgment or a formal reference-class method. A single uplift can hide different causes and can be misleading when the reference cases are heterogeneous.

**Editorial takeaway:** Keep original forecasts and actual outcomes, then compare like with like. Use local error history to challenge the current estimate and find recurring failure components; do not promote a small, mixed or obsolete sample into a universal correction factor.

#### Editorial evidence

- supports: The 2026 Green Book recommends explicit optimism-bias adjustments informed by historical forecast errors from similar proposals, using the originating organisation's evidence where available. — hm-treasury-green-book-2026. This is UK public-sector appraisal guidance, not a universal estimation standard. The transferable point is to compare forecasts with actual outcomes from relevant historical work rather than rely only on current-plan confidence. (Optimism bias)
- supports: Reference class forecasting uses the actual performance of comparable projects to provide an outside-view correction to project forecasts. — flyvbjerg-2006-reference-class. The paper's practical application is large transport infrastructure. It supports the logic of using comparable historical outcomes, not a claim that the same statistical procedure or uplift applies unchanged to small software or knowledge-work tasks. (Abstract; reference class forecasting method)
- limits: A systematic review of reference class forecasting literature identifies a trade-off between larger but more heterogeneous reference classes and narrower but less statistically reliable classes, and reports that forecast performance depends materially on similarity between the target project and its reference class. — cantarelli-et-al-reference-class-review. This directly limits the idea that more historical cases automatically create a better baseline. Reference-class construction is itself a judgment problem, especially when projects are rare, changing or poorly classified. (Methodology; reference-class construction and similarity discussion)
- challenges: The same review finds continuing debate about how much project underperformance is caused by optimism bias versus complexity, uncertainty and forecasting error, and warns against over-promising reference class forecasting as a complete correction. — cantarelli-et-al-reference-class-review. Historical error data can expose a pattern without identifying its cause. A local baseline should therefore support diagnosis and calibration rather than replace causal analysis of scope, dependencies, rework and process changes. (Origins and critiques; 'It is important not to over-promise the advantages offered by RCF')
- hm-treasury-green-book-2026: The Green Book (2026) — https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government/the-green-book-2026 — HM Treasury
- flyvbjerg-2006-reference-class: From Nobel Prize to Project Management: Getting Risks Right — https://doi.org/10.1177/875697280603700302 — Bent Flyvbjerg
- cantarelli-et-al-reference-class-review: Reference class forecasting: promises, problems, and a research agenda moving forward — https://doi.org/10.1080/09537287.2025.2578708 — Chantal C. Cantarelli, Kate Davis, Jeffrey K. Pinto, Neil Turner

Editorial version: 1.0.0 · evidence checked 2026-09-25 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/build-an-outside-view-reference-class
