# Give every postmortem action 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 every postmortem action a verifiable finish

ID: MHC-D-RESEARCH-0306 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/give-every-postmortem-action-a-verifiable-finish

'Improve reliability' is a wish wearing an action-item field.

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

### Use when

- A postmortem produces follow-ups such as 'improve monitoring' or 'be more careful.'

### Avoid when

- A completed action is not proof the same class of incident cannot recur; risk should be reassessed separately.

### Explanation

Rewrite each follow-up so a reviewer can determine whether it is complete without interpreting intention. Name the artifact or system change, the condition it should create, an owner and a completion check. Prefer changes to the system or process over telling people to remember harder.

### Checklist

- The action names a concrete change or artifact.
- An owner is explicit.
- A reviewer can observe a pass condition.
- The action addresses prevention, mitigation or detection rather than only restating the incident.
- Completion does not depend on someone claiming they will 'be more careful.'

### Example

Replace 'monitor queue growth better' with 'alert when queue age exceeds the agreed threshold for the defined service window.'

### Check

A person who did not attend the incident can say whether the action is done.

### Limits

- A completed action is not proof the same class of incident cannot recur; risk should be reassessed separately.

### Evidence and sources

- supports: Google SRE postmortem guidance treats a verifiable end state as a quality criterion for follow-up action items. — RS-19D9542665BD7033. A measurable completion state does not by itself prove that recurrence risk has been eliminated. (Measurability; action items)
- RS-19D9542665BD7033: Postmortem Culture: Learning from Failure — https://sre.google/workbook/postmortem-culture/

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/mine-postmortems-for-repeated-failure-patterns
