Opens in a new tab

Postmortem action tracker

Assign owners, record verification evidence and track remaining risk.

Free to use. Save a file draft or explicitly enable storage on this device.

Working draft · v2

Postmortem action tracker

Save / export

Current result

1 actions · 0 overdue · 1 need review

Incomplete or uncertain. Review the fields and warnings.

Review results

Start with your data or try an illustrative example.

File drafts are available without browser storage. Current draft matches the last save or initial state.

Inputs & calculation

1 actions · 0 overdue · 1 need review

Today uses UTC. Delivered actions remain overdue until verified or their residual risk is explicitly accepted.

Action 1

Assign an owner

Results

Review and export

This is incomplete or has review issues. You can save a draft; exports retain unknowns and warnings.

Postmortem action tracker report

Postmortem action tracker
User-entered draft; verify against source evidence.
Tool version 2 · https://aiopssre.com/postmortem-action-tracker/
Name: Untitled

1 actions; 0 overdue as of current UTC date; 1 with review issues.
Verified means a test and evidence have been recorded, not independently confirmed by this tool. Delivered work may still need verification.
Filter: All; report includes 1 actions.
ScenarioTreatmentOwnerDueStatusVerification testEvidenceResidual risk / acceptanceReview issues
OpenAssign an owner

Continue the incident workflow

Carry one action’s scenario, owner, proposed change and verification into a runbook draft. Transfer uses this browser tab’s temporary storage, not a shared URL.

Following a configuration fix through verification

The illustrative action follows checkout failures caused by a stale configuration. The proposed change adds a configuration validation gate. Shipping that gate moves the action to Delivered; replaying the stale configuration in a controlled test can show whether the gate rejects it. The example leaves evidence blank because the test has not been run.

Deciding whether an action can close

A Verified status requires a recorded test and result, which the action owner must assess against the original failure scenario. If a test covers only stale configuration, other causes of checkout failure may remain. Describe that remaining exposure in the register. Risk accepted records a different decision and needs both the residual risk and the person accepting it. Delivered actions remain overdue after their due date until verification or risk acceptance is recorded.

Read the accompanying guide · Source and further reading

Calculation and worksheet review: September 29, 2026.

Full Incident Response Toolkit · Get new guides by email