Turn a Messy Process Description into a Clear Standard Operating Procedure
Get a complete SOP with numbered verb-first steps, an owner for each step, inputs, outputs, a troubleshooting table and a list of open questions.
You getTitle and one-line purpose, scope and roles involved
Prompt
You are an operations analyst who writes standard operating procedures that new hires can follow on day one.
I will paste a messy description of a process right after this message: notes, a chat thread or a voice-memo transcript. Turn it into a clear SOP.
Rules:
1. Number every step. Each step starts with a verb, names one owner (a role, not a person's name) and covers one action only.
2. If my notes don't say who owns a step or what triggers it, write "Owner: unclear" and add it to Open questions instead of guessing.
3. Write decision points as if/then lines inside the step.
4. Keep each step under 30 words. Move background detail to a short Note line under the step.
5. Build the troubleshooting table only from failures mentioned or clearly implied in my notes, and mark implied ones "(implied)".
Output format:
- Title and one-line purpose
- Scope: when this SOP applies and when it does not
- Roles involved
- Inputs: what must exist before step 1
- Procedure: numbered steps
- Outputs: what exists when done and where it is stored
- Troubleshooting table: Problem | Likely cause | Fix | Owner
- Open questions
End with one line naming the biggest gap or risk in the process as described.Example output
Tips and common edits
Why this works
- Verb-first steps with one owner each make the SOP easy to follow and show exactly who is accountable.
- Marking unclear owners instead of guessing exposes real gaps rather than hiding them in plausible text.
- Limiting troubleshooting to failures in your notes keeps the table grounded in what actually goes wrong.
Use this when a process lives in someone's head or a long Slack thread. Paste the raw notes into ChatGPT, Claude or Gemini right after the prompt; rough transcripts work fine.
Common edits
- Ask for a one-page checklist version to print or pin in a shared channel.
- Add a column for tools or systems used in each step if your process spans several apps.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Turn a Long Report into a One-Page Executive Summary That Leads with the Ask
Returns a one-page executive summary that opens with the decision needed, keeps every source number exact, and lists claims the report does not back up.
Turn a Task Description Into a Step-by-Step SOP a New Hire Can Follow
You get a complete standard operating procedure with verb-first numbered steps, decision points, a quality checklist and a common-mistakes table.
Process Transcript to Standard Operating Procedure
Converts a pasted process description or transcript into an SOP with purpose, roles, numbered steps, checklists and common mistakes.
Build a 30-Day Learning Plan for a New Skill with Weekly Project Milestones
You get a 30-day plan sized to your daily time, with one small, checkable project each week, day-by-day tasks with minutes, and a catch-up plan.
Build a Practice Quiz with Answer Key from Your Course Notes
Paste your course material and get a practice quiz that mixes recall, application and misconception questions, plus a separate answer key that explains every wrong option.
Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged
Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.