Turn rough process notes into a clear standard operating procedure
Organise an informal process into steps another person can follow and verify.
Best for
- Recurring administrative or operational tasks
- Documenting a process known by one person
What you need
- Raw notes from someone who performs the process
- Required inputs, systems and outputs
- Known exceptions and approval points
Limitations
Not suitable as the sole basis for safety-critical, medical, financial or regulated procedures.
Recommended tool
Claude
Claude can structure long notes while retaining exceptions and flagging missing operational detail.
AI4E may earn a commission from partner links. This never affects which tool we recommend. Read the affiliate disclosure →
Pick your stack
Do it for nothing, or move faster with a paid tool.
AI4E may earn a commission from partner links. This never affects which tool we recommend. Read the affiliate disclosure →
Your copy-paste prompt
Fill in the blanks on the left and the prompt updates as you type.
Fill in your details
0 of 3 fields filled — every matching placeholder updates as you type.
Act as an operations documentation specialist. Convert [PROCESS NOTES] into an SOP for [INTENDED USER] with this structure: purpose, scope, prerequisites, roles, numbered procedure, decision points, exceptions, quality checks, escalation path and revision record. Use only the supplied notes and label every missing detail as [CONFIRM]. Do not invent system names, permissions, timings, policies or compliance requirements. Separate stated facts from proposed wording. Ask questions where missing information could cause failure or harm.
Step-by-step instructions
- 1
Observe the process once and collect screenshots or exact field names where safe.
- 2
Run the prompt and resolve every [CONFIRM] marker with the process owner.
- 3
Have a second person follow the SOP without verbal help.
- 4
Correct failures, approve the document and assign an owner and review date.
Check the result
- A new user can identify all required inputs
- Decision points and exceptions are explicit
- No invented system step remains
- Owner and review date are assigned
If the result is poor
- If steps are generic, add exact inputs and expected outputs for each stage.
- If the order is wrong, number the raw notes before running the prompt again.
Privacy and accuracy
- A qualified owner must validate procedures that affect safety, money, privacy or compliance.
Sample input
Bullet notes for onboarding a new retail supplier, including two approval paths.
Expected output
A structured SOP with prerequisites, 11 numbered steps, two decision points, quality checks and unresolved details clearly marked.
What people do next
Three recipes chosen for the task that usually follows this one, not just for sharing a category.
Business Automations
Turn an informal business process into a repeatable SOP
40 mins · Claude
Start this workflow →
Writing & Editing
Turn meeting notes into decisions, action items and owners
12 mins · Claude
Start this workflow →
Business Automations
Qualify incoming leads with a transparent scoring rubric
35 mins · ChatGPT
Start this workflow →