# Give the lesson a verifiable finish

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

---

## Give the lesson a verifiable finish

ID: MHC-D-RESEARCH-0729 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/give-the-lesson-a-verifiable-finish

A corrective action needs a finish line that can be inspected.

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

### Use when

- A review has produced actions but they can remain open forever or be declared done after a document edit.

### Avoid when

- Verification does not prove the original root cause was correct; monitor recurrence and side effects.

### Explanation

For each action, write an owner, a change, a due condition and a verification signal. Prefer a signal that tests the workflow, not only the existence of a new policy or slide. If the change cannot be verified, it is still an intention.

### Template

Owner: [person/role]. Change: [system or behavior change]. Done when: [observable condition]. Verify by: [test, metric or audit].

### Example

Owner: release lead. Change: add pre-import schema validation. Done when: pipeline blocks malformed files. Verify by: a known-bad fixture fails before import.

### Check

Someone outside the review can tell whether the action worked without asking the action owner.

### Limits

- Verification does not prove the original root cause was correct; monitor recurrence and side effects.

### Evidence and sources

- supports: Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation. — RS-C63447C9710D56FD. AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work. (Introduction; RCA2; action hierarchy discussion)
- RS-C63447C9710D56FD: The Evolution of Root Cause Analysis — https://psnet.ahrq.gov/perspective/evolution-root-cause-analysis

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/prefer-a-system-strengthening-action-over-another-reminder
