# Audit the reference class before trusting its base rate

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

---

## Audit the reference class before trusting its base rate

ID: MHC-D-RESEARCH-0403 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/audit-the-reference-class-before-trusting-its-base-rate

A base rate is only as relevant as the cases allowed into its denominator.

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

### Use when

- A reference-class forecast produces a compelling percentile or average and the class itself has not been challenged.

### Avoid when

- No reference class is perfectly homogeneous; the goal is a useful outside view with visible limitations, not a claim of exact exchangeability.

### Explanation

Inspect the class boundary before using its distribution. Ask which factors genuinely determine comparability, whether selection excluded inconvenient failures, whether the measurement definitions match, and whether structural changes make old cases less relevant. If different reasonable classes give different answers, show that sensitivity.

### Question

What rule put a past case inside or outside the class? · Were failed or cancelled cases captured? · Are duration, cost and completion defined the same way? · Has technology or process changed enough to weaken comparability? · Would another defensible class materially change the forecast?

### Example

A 'similar SAP migration' class may become misleading if it mixes greenfield programs with small remediation runs.

### Check

The forecast includes a defensible class definition and at least one noted limitation or alternate-class sensitivity.

### Limits

- No reference class is perfectly homogeneous; the goal is a useful outside view with visible limitations, not a claim of exact exchangeability.

### Evidence and sources

- supports: Reference class forecasting uses outcomes from comparable past projects as an outside view, but recent review work highlights unresolved issues around reference-class selection and applicability. — RS-E9B25C78E7287B34. A badly chosen class can give a confident but irrelevant base rate. (Systematic literature review and limitations)
- RS-E9B25C78E7287B34: Reference class forecasting: promises, problems, and a research agenda moving forward — https://www.tandfonline.com/doi/full/10.1080/09537287.2025.2578708

No review details supplied.
