Use this ChatGPT SOP prompt when a process is stuck in someone's head, scattered across notes, or captured in a rough walkthrough. It helps turn messy source material 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.
- The source material: rough notes, a transcript, a checklist, or a walkthrough summary.
- Inputs, tools, files, logins, forms, or templates needed.
- Steps in rough order, including what happens before and after.
- The format your team already uses, if the SOP must match a template.
- Common mistakes, quality checks, and when to escalate.
- Recent process changes or repeated team questions that should update the SOP.
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]
Audience:
[new employee, contractor, support agent, manager, or experienced teammate]
Source material:
[rough notes, transcript, screen-recording summary, checklist, or existing draft]
Tools, files, logins, or templates needed:
[tools, files, links, forms, or systems]
Required SOP format:
[paste your template headings, or write "no required format"]
Rough steps:
[paste steps]
Decision points and exceptions:
[choices, edge cases, approval moments, or "not sure yet"]
Inputs:
[what must be ready before the process starts]
Final output:
[what finished work should look like]
Quality checks:
[checks]
Proof of completion:
[where the finished work is saved, submitted, sent, logged, or reviewed]
Escalation rules:
[when to stop, ask a manager, contact a customer, or open a support ticket]
Recent changes or repeated questions:
[new policy, recurring staff questions, customer issues, tool changes, or "none"]
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. Review date and SOP owner
10. Update triggers: when the SOP should be revised again
11. Readiness check: ready to test, needs more source material, or needs owner review
12. 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."
- Keep the required format if I provided one.
- Use plain language a new employee could follow.
- Keep each step tied to a clear action.
- If repeated team questions reveal a missing step, add that gap to the revision notes instead of pretending the SOP is complete.
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
Source material: Notes from a 12-minute walkthrough by the support lead
Tools, files, logins, or templates needed: Help center CMS, policy change notes, support inbox, FAQ style guide
Required SOP format: Overview, tools needed, steps, quality checks, escalation rules, owner, review date
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
Recent changes or repeated questions: agents keep asking whether refund wording changed after the new policy update
What good output should include
- A clear owner for the SOP and a clear role for the person doing the work.
- A faithful conversion of the notes, transcript, or walkthrough without adding steps that were not provided.
- Inputs, tools, decision points, and finished output so the task has a start and end point.
- Short steps that begin with action verbs.
- The same structure or template your team already uses, if you provided one.
- Quality checks that someone can actually verify.
- Escalation rules for unclear, risky, or exception-based cases.
- Clear update triggers so the SOP improves when policies, tools, or repeated team questions change.
- A readiness check so the draft is tested before a team relies on it.
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 the draft ignored my required format
6. Places where a new employee would need to guess
7. Missing update triggers for policy changes, tool changes, or repeated team questions
Rewrite only the weak parts. Do not add new policy, tools, deadlines, or approval steps 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.