Documents & SOPs · Starter

Turn a messy process into an SOP

The steps for a job live in one person's head or a rambling voice memo, and you need a checklist anyone can follow.

  • Claude
  • ChatGPT
  • Copilot
  • Grok

For: Owner, Office manager · Updated October 25, 2026

A starting point: fill in the [brackets] with your own details, and check the answer before you use it. Tool screens change often, so yours may look a little different.

The prompts

Copy the version for the tool you use, then replace every [bracket].

CLAUDE OR CHATGPT
Record yourself talking through the job, paste the transcript, and let the AI find the gaps. Tested as written in Claude and ChatGPT (free plans), Oct 25, 2026.
Turn this description of our [process name] into a standard operating procedure for [who does it]. Notes: [paste notes or transcript] Format:
1) Purpose (one sentence) and when to use it.
2) What you need before starting ([tools and places]).
3) Numbered steps, one action each, starting with a verb.
4) "Stop and ask" points where a new person should get help.
5) A short checklist version for printing. Then list every gap or contradiction you noticed in my notes as questions for me. Don't fill gaps with guesses. If a role's duties aren't in my notes, write [not described] instead of making them up.
COPILOT
In Word: paste the notes into a blank document, then use Draft with Copilot or ask Copilot to rewrite it.
Rewrite these notes as an SOP for [who does it]: purpose, what you need, numbered steps that each start with a verb, when to stop and ask for help, and a printable checklist. List any missing steps as questions. Don't fill gaps with guesses; if a role's duties aren't in my notes, write [not described].
GROK
Make a clear numbered SOP for [process name] from these notes: [paste notes or transcript]. Audience: [who does it]. Add a printable checklist at the end and list anything unclear as questions. Don't fill gaps with guesses; if a role's duties aren't in my notes, write [not described].

Fill in these [brackets]

BracketWhat to put there
[process name] e.g. After-hours emergency call intake
[who does it] e.g. the on-call technician and the office coordinator
[paste notes or transcript]A voice-memo transcript is fine. Messy is fine.
[tools and places] e.g. the on-call phone, the scheduling app, the price sheet in the van binder

Real example (Claude, free plan, tested Oct 25, 2026):

  1. Tell the customer the after-hours fee: [$150 or $175 – confirm current amount].

…

  1. Call the owner before committing to the job if it looks like a big job. [“Big job” is not yet defined.]
  2. Confirm Devon is not being sent out alone. Devon is an apprentice and cannot go to a call by himself.

Office coordinator

  1. Review the after-hours entries in the scheduling app each morning. [Everything the coordinator does after that (customer follow-up, scheduling, invoicing, insurance paperwork) was not described and needs to be added.]

Questions for the owner

  • The after-hours fee: is it $150 or $175? When did it change?
  • What counts as a “big job”? Is it a dollar amount, job type, or time estimate?
  • The price sheet is in the van binder, but steps 1 to 6 happen on the phone, probably before the technician reaches the van. Should the fee and prices be written into this SOP or the app?

Answer given with our fictional inputs (Kettle Creek Plumbing & Drain, a made-up plumbing company). Excerpt trimmed; “…” marks cuts. AI answers vary, so yours will be different. Check it before you use it.

Watch for: In the same test, ChatGPT wrote out the office coordinator’s duties on its own, though our notes never described them. The prompt above now asks for [not described] instead.

Check before you send

  • Have the newest person on the team follow it once, out loud
  • Every 'stop and ask' point names who to ask
  • No steps were invented to fill gaps
  • Safety or legal steps match your real rules

Privacy note: what not to paste

Leave out customer names, door codes, and passwords. Write 'see the office binder' instead.