Post-Incident Action Item Tracker
Make sure the follow-up actually happens.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design a system for tracking incident action items. Tracking tool: [TOOL]. Number of incidents per quarter: [INCIDENT_COUNT]. Past problem with follow-up: [PAST_PROBLEM]. Provide a ticket template with fields (incident link, type: prevent, detect, mitigate, process), a rule that each item has one owner and a due date, a priority scheme, and a target of completion within a stated period. Define a weekly 10-minute review and a monthly dashboard of open items by age and owner. Add rules for rejecting items with a documented reason, for handling items that become irrelevant, and escalation after 30 days. Include a sample set of five action items for a fictional database outage, showing good versus vague wording. Add a short guide on writing good action items using the pattern of verb, object, and measurable outcome, with five poor items rewritten. Include a process for dealing with action items that need a decision from management, and an example monthly report for leadership that lists completion rates and incidents repeated due to unfinished actions.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.