# Keep the probability in a delivery forecast

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

---

## Keep the probability in a delivery forecast

ID: MHC-D-RESEARCH-0171 · Version: 0.1.0 · Kind: concept
Source: https://vedokrok.com/knowledge/keep-the-probability-in-a-delivery-forecast

A forecast loses its meaning when its uncertainty is edited out.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A service-level expectation is repeated as a guaranteed deadline for every item.

### Avoid when

- Changing the workflow or work mix can weaken the historical basis. Contractual commitments need their own explicit agreement and capacity assessment.

### Explanation

A Kanban service-level expectation combines elapsed time with a probability, based on relevant historical flow when available. State the work type and boundaries as well as the number.

### Example

A fictional forecast says 85% of comparable requests finish within eight days. It does not promise that every request will finish on day eight.

### Check

Does the recipient understand the probability, population and start point behind the forecast?

### Limits

- Changing the workflow or work mix can weaken the historical basis. Contractual commitments need their own explicit agreement and capacity assessment.

### Evidence and sources

- supports: The Kanban Guide defines started-but-unfinished work, item age and a probabilistic service-level expectation against explicit workflow boundaries. — kanban-guide-2025. Claim basis: technical_definition. Claim limit: Counts and forecasts need a stable meaning of work item and start/finish; they are not automatic performance targets.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Definition of Workflow; active management; flow metrics"].
Source note: Only short original explanations and new examples are used. The page contains differing CC BY-SA and CC BY notices; commercial publication must resolve applicable rights rather than assume unrestricted copying.
Agent release review: Checked the named definitions in the May 2025 Kanban Guide, LEI and Meadows. Non-manufacturing examples are editorial applications. The text preserves safe-stop, ownership and contextual boundaries. (Definition of Workflow; Flow Metrics)
- kanban-guide-2025: The Kanban Guide, May 2025 — https://kanbanguides.org/the-kanban-guide/2025.5/

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
