Failure Log and Root Cause Template for AI Workflows
Record each failure so patterns point to the real fix.
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.
Create a failure log for the AI workflow described here: [WORKFLOW_DESCRIPTION]. Who uses it: [USERS]. Failure types we have seen: [FAILURE_TYPES]. Design the log with columns for date, input summary, what went wrong, effect on the user, category (input problem, prompt problem, tool problem, model limit, process problem), fix tried, result and owner. Provide a short guide for choosing the category and a rule for when a failure becomes a new test case. Add a worked example using three invented failures, a monthly review agenda of 20 minutes, and three charts to draw from the log, each with the question it answers. Also add a column for whether the failure was caught by a person or by a check, and a quarterly question: which failure category is growing, and what one change would remove the most failures next quarter. Close with a rule on severity labels, such as harmless, annoying, costly or harmful, and how many of the last category should trigger an immediate pause for review.
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.