Turn a rough process into a reusable checklist
Create an operating checklist with prerequisites, exceptions, and a clear finish condition.
Start with these inputs
- Your actual steps for a repeated task
- Known exceptions and failure cases
- Who performs and checks the task
Follow the workflow
- Write down the process as you perform it, including where you stop to check something.
- Paste the notes and exceptions into Claude with the prompt.
- Remove suggested policy that has not been approved and answer the blocking questions.
- Walk through the checklist with a harmless sample before adopting it.
Your starting prompt
Convert my process notes into a practical SOP for a new teammate. Include: purpose, prerequisites, numbered steps, expected result at each checkpoint, exceptions, escalation questions, and a final completion checklist. Preserve the sequence where dependencies matter. Identify missing information as a question instead of inventing company policy. Clearly label any suggested improvements as proposals. Do not add integrations or automation that I have not described. Task: [describe task] Process notes: [paste notes] Exceptions: [paste known exceptions]
What the output could look like
Illustrative example, not a recorded test result.
Illustrative example using invented sample inputs:
Checkpoint: after exporting the report, confirm the date range and row count.
Exception: if the export is empty, check the filter settings before continuing.
Finish condition: report saved in the agreed folder and reviewed by the named owner.
Review before you use it.
The checklist needs a real walkthrough before it becomes an operational SOP. AI can omit a critical exception. Time is an approximate planning estimate, not a measured result. Free access has usage limits; features can vary by account.
The checklist needs a real walkthrough before it becomes an operational SOP. AI can omit a critical exception. Time is an approximate planning estimate, not a measured result. Free access has usage limits; features can vary by account.
Sources & review notes
By AI Flow Finder · Reviewed October 14, 2026. Documented means this guide is based on the sources above. It has not yet passed a recorded end-to-end workflow test. Tool access and limits can change.