Find where errors are likely in a process and prevent them
Scores each step of a business process for error risk, explains why mistakes happen there, and suggests error-proofing and checks.
The prompt
Identify where errors are most likely to occur in this process and how to prevent them.
Process: [NAME and what it produces]
Steps: [PASTE the steps with who does them and the systems used]
Errors we already see: [EXAMPLES with rough frequency, if known - e.g. "wrong PO numbers on ~5% of invoices"]
Impact of errors: [rework, customer complaints, financial loss, compliance exposure]
Steps:
1. For each step, list what could go wrong. Look for common error sources: manual data entry or re-keying, copy-paste between systems, unclear instructions, missing or late inputs, judgment calls without criteria, handoffs, time pressure, rare or complex cases, and spreadsheets with formulas nobody checks.
2. Rate each failure on likelihood, impact, and how likely it is to be caught before it causes harm (high / medium / low). Rank by combined risk.
3. For the highest-risk points, suggest prevention first, then detection:
- Prevent: remove the step, use dropdowns or validation, templates, checklists, defaults, automation of transfers.
- Detect: reconciliations, peer review, exception reports, sample checks.
4. Note where the current checks are in the wrong place (too late, or checking something that rarely fails).
Return:
1. A table: Step | What could go wrong | Cause | Likelihood | Impact | Chance of detection | Risk rank | Prevention | Detection.
2. The top 5 error hotspots with a one-line explanation each.
3. Quick fixes versus fixes that need system changes.
4. Metrics to track whether error rates fall.
Base the ratings on what I described; mark guesses [ESTIMATE - CONFIRM WITH TEAM]. Talk about causes in the process, not individual blame.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- NAME and what it produces
- PASTE the steps with who does them and the systems used
- ESTIMATE - CONFIRM WITH TEAM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.
- Define roles and responsibilities (RACI)A RACI matrix and role descriptions so everyone knows who does what.
- Plan an event from start to finishTimelines, budgets, logistics, run-of-show, and checklists for work or personal events.
- Redesign a process for speed and quality with a future-state mapRedesigns a current process into a faster, higher-quality future-state workflow and compares the two side by side so you can get approval.