# Compare expected and actual before explaining the gap

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

---

## Compare expected and actual before explaining the gap

ID: MHC-D-RESEARCH-0726 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/compare-expected-and-actual-before-explaining-the-gap

Start the review with two columns, not a culprit.

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, decision, incident or experiment has ended and the group is already telling a story about why it went well or badly.

### Avoid when

- A timeline can still be incomplete. Missing logs or observations should be marked as unknown, not filled with a plausible story.

### Explanation

Write what was expected to happen and what actually happened using observable outcomes, dates, thresholds or artifacts. Mark the first meaningful divergence. Only then discuss explanations. This separates reconstruction from hindsight and gives the review a shared object to inspect.

### Steps

1. Another person can point to the same first divergence without needing your interpretation of motive.

### Example

Expected 98% of records to validate before import. Actual 81% validated; the first divergence appeared after mapping rule 4 changed.

### Check

Another person can point to the same first divergence without needing your interpretation of motive.

### Limits

- A timeline can still be incomplete. Missing logs or observations should be marked as unknown, not filled with a plausible story.

### Evidence and sources

- supports: Structured debriefs or after-action reviews have been studied as a way to support learning from experience, with meta-analytic evidence of improved performance on average across varied settings. — RS-6A2E6BA2CE371BB3. Average effects across studies do not predict the benefit of a particular review; facilitation, task and implementation matter. (Abstract: objective, method, results and application)
- supports: After-action review effectiveness varies with design features; alignment to the person or team and objective review media were among the recurring contributors in a later meta-analysis. — RS-6A2B05A2CE34388A. The analysis covers training-evaluation outcomes and interacting moderators; it does not establish one best debrief format for every setting. (PubMed abstract)
- RS-6A2E6BA2CE371BB3: Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis — https://journals.sagepub.com/doi/10.1177/0018720812448394
- RS-6A2B05A2CE34388A: A meta-analysis of the effectiveness of the after-action review (or debrief) and factors that influence its effectiveness — https://pubmed.ncbi.nlm.nih.gov/32852990/

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/bring-objective-traces-into-the-debrief
