Checklist from SOP prompt: free ChatGPT template
Updated · By Robert Breen
An SOP is for learning the job. A checklist is for doing it, on a clipboard by the door or taped inside a van. Use this prompt when you already have an approved procedure and want the version people actually tick. It is told to copy, not improve: same order, same numbers, same roles, nothing new.
The prompt
Copy it into ChatGPT (or Claude, Gemini or Copilot) and replace every [BLANK] with your own details. It uses the four parts from Prompt Writing 101: Role, Context, Task and Format.
Role: You are turning [BUSINESS]'s written procedures into checklists people use while they work. Context: Below is our SOP for [PROCEDURE]. The checklist will be used [WHERE AND WHEN]. It must match the SOP exactly: same order, same numbers, same roles. Don't add steps, drop safety steps, combine things a person would check separately, or change any number. Task: Turn the SOP into a checklist. Keep every safety step and keep it first. Shorten each step to the action and the number that matters. Finish with a sign-off line based on the SOP's Check line. Format: A title line, then one line per item starting with "[ ]", each under 10 words. Put the role in parentheses only where it changes from one person to another. The sign-off line last. Plain text that prints on half a page. Here is the SOP: [SOP TEXT]
Fill in the blanks
[BUSINESS]- Your business name.
[PROCEDURE]- The name or code of the SOP, so the checklist title matches it.
[WHERE AND WHEN]- Where the list lives and who ticks it: "taped by Docks 1 and 2, ticked by the Dock Associate for every truck." This sets how short each line must be.
[SOP TEXT]- The approved SOP, pasted in full. If it isn't approved yet, fix the SOP first so the two never disagree.
Example, filled in
A made-up example from the free lesson Build an AI SOP Writer with a Custom GPT. Ridgeline Supply Co. is the made-up warehouse in the SOP writer lesson. This is the receiving SOP its Custom GPT wrote in that lesson, now turned into a dock checklist.
Role: You are turning Ridgeline Supply Co.'s written procedures into checklists people use while they work. Context: Below is our SOP for SOP-REC-01, receiving an inbound shipment. The checklist will be used taped by Docks 1 and 2 and ticked by the Dock Associate for every truck. It must match the SOP exactly: same order, same numbers, same roles. Don't add steps, drop safety steps, combine things a person would check separately, or change any number. Task: Turn the SOP into a checklist. Keep every safety step and keep it first. Shorten each step to the action and the number that matters. Finish with a sign-off line based on the SOP's Check line. Format: A title line, then one line per item starting with "[ ]", each under 10 words. Put the role in parentheses only where it changes from one person to another. The sign-off line last. Plain text that prints on half a page. Here is the SOP: SOP-REC-01: Receiving an Inbound Shipment Owner: Receiving Lead | Docks 1-2 | 20-40 min per truck 1. Chock the trailer wheels and check the dock plate. (Dock Associate) 2. Match the carrier and PO to today's dock schedule. (Receiving Lead) 3. Check the seal and pallet count. Write any damage on the bill of lading before the driver leaves. (Dock Associate) 4. Scan every carton against the PO in the WMS. Off by more than 2%? Stop and call the Receiving Lead. (Dock Associate) 5. Label each pallet and stage it in the green lane. (Dock Associate) 6. Put away to the WMS location the same shift. (Forklift Operator) Check: The PO shows "Received" in the WMS. If something goes wrong: Damaged or short freight goes to the hold rack with a claim form the same day.
What a good answer looks like
- "[ ] Chock trailer wheels" and "[ ] Check dock plate" as two separate first lines, since a person checks them separately.
- The 2% rule kept word for word in meaning: "Over 2% off? Stop, call Receiving Lead."
- The role only where it changes, such as "(Receiving Lead)" on the schedule match and "(Forklift Operator)" on put-away.
- A last line like "Sign-off: PO shows Received in WMS," taken from the Check line.
How to check it before you use it
An AI draft can sound right and still say something you never told it. Use the habit from the Reply Faster lesson: check every promise, name, date and number against what you gave it before anything goes out.
- Count the steps in the SOP and the lines in the checklist. Fewer lines means something got merged or dropped; find out which.
- Compare every number and place: 2%, the green lane, the same shift, the hold rack. A rounded or missing number is the most common slip.
- Look for anything added, like "wear gloves" or "notify the manager." If you want it, add it to the SOP first so the two stay in sync.
- Try it on the next real truck. If someone can't tick a line without asking a question, the line is too short.
Why this prompt works
Most of this prompt is about what not to change. A checklist that quietly differs from the SOP creates two versions of the truth, so the Context forbids edits and the Format only asks for shorter wording.
Practice it in the free lesson
Build an AI SOP Writer with a Custom GPT: See why generic prompts give generic results, then build a Custom GPT that knows your operations handbook and writes clear, numbered SOPs and checklists your team can follow. You do every step yourself in a practice copy of ChatGPT, and nothing touches your real accounts.
Terms used here
Related prompts
- SOP writer prompt: Turn a manager's rough notes into a numbered SOP with real roles, real numbers, safety steps first, a Check line, and CONFIRM…
- Training quiz from SOP prompt: Turn an SOP or handbook page into a short quiz for new hires: scenario questions, believable wrong answers, and an answer key…
- Shift handoff notes prompt: Turn end-of-shift scribbles into a clear handoff for the next shift: what to do first, work in progress, promises to customers…
- New hire onboarding checklist prompt: Build an onboarding checklist from before day one to day 30: every task with an owner and due date, gaps marked Not stated, and…