Small businesses often keep processes in someone's head. ChatGPT can help turn rough notes into a standard operating procedure, but the person who knows the process must review every step before the SOP is used by a team.
What to prepare
- The process name and purpose.
- Who owns the process and who performs the work.
- Inputs, tools, files, logins, forms, or templates needed.
- Steps in rough order, including what happens before and after.
- Common mistakes, quality checks, and when to escalate.
Copy this prompt
Turn these process notes into a standard operating procedure.
Process name:
[name]
Purpose:
[purpose]
Who performs it:
[role]
Process owner:
[person or role responsible for keeping this SOP updated]
Tools, files, logins, or templates needed:
[tools, files, links, forms, or systems]
Rough steps:
[paste steps]
Inputs:
[what must be ready before the process starts]
Final output:
[what finished work should look like]
Quality checks:
[checks]
Escalation rules:
[when to stop, ask a manager, contact a customer, or open a support ticket]
Return:
1. SOP overview
2. Scope: what this SOP covers and does not cover
3. Roles and responsibilities
4. Step-by-step procedure
5. Checklist for the person doing the work
6. Quality-control checks
7. Common mistakes and how to avoid them
8. Handoff notes for the next person
9. Questions I need to answer before this is complete
Rules:
- Do not invent tools, policy, deadlines, or approval steps.
- Mark missing details as "needs confirmation."
- Use plain language a new employee could follow.
- Keep each step tied to a clear action.
Example input
Process name: Publish a customer FAQ update
Purpose: Make sure support answers stay current after a policy change
Who performs it: Customer support lead
Process owner: Operations manager
Tools, files, logins, or templates needed: Help center CMS, policy change notes, support inbox, FAQ style guide
Rough steps: Read policy change, identify affected FAQ pages, rewrite answers, check for legal or pricing claims, publish, tell support team
Inputs: Approved policy change notes
Final output: Updated FAQ pages and a short Slack note to support team
Quality checks: No old prices, no unsupported promises, answers are under 120 words
Escalation rules: Ask operations manager before changing refund, legal, or warranty wording
What good output should include
- A clear owner for the SOP and a clear role for the person doing the work.
- Inputs, tools, and finished output so the task has a start and end point.
- Short steps that begin with action verbs.
- Quality checks that someone can actually verify.
- Escalation rules for unclear, risky, or exception-based cases.
Fix a weak SOP draft
Review this SOP draft and make it easier to follow.
SOP draft:
[paste draft]
Check for:
1. Steps that are too vague
2. Missing owner, input, tool, or final output
3. Missing quality checks
4. Missing escalation rules
5. Places where a new employee would need to guess
Rewrite only the weak parts. Do not add new policy or tools unless I provided them.
Common mistake
Do not publish an SOP without testing it. Give the draft to someone who does not already know the process and see if they can complete the work from the instructions. If they need to ask basic questions, feed those questions back into the prompt and revise the SOP.