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

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

At a glanceCustomer refund SOP: 8 stepsOwner for each step of the refund procedure
  1. Log the requestRefunds tab of support tracker - Support Agent
  2. Check the order dateOver 30 days gets outside window reply - Support Agent
  3. Request a damage photo48 hoursWait up to 48 hours before one follow-up - Support Agent
  4. Decide refund typeDamaged: no return; unwanted: return label - Support Agent
  5. Inspect returned items1 business dayMark resellable or scrap - Warehouse Lead
  6. Approve refunds over $150Operations Manager
  7. Issue refund and update stockRefund by Support Agent; stock update owner unclear

Example for: a 6-person online candle shop documenting how customer refunds are handled, from a pasted Slack thread.

Customer Refund Processing

Purpose: Refund eligible orders within 3 business days and keep inventory and accounts accurate.

Scope: Applies to orders placed on the web store within the last 30 days. Does not apply to wholesale orders or Etsy sales.

Roles involved: Support Agent, Warehouse Lead, Operations Manager

Inputs
  • Refund request email or contact-form ticket
  • Order number and order record in Shopify
  • Photo of damage (for damaged-item claims)
Procedure
  1. Log the request in the Refunds tab of the support tracker. Owner: Support Agent
  2. Check the order date in Shopify. If over 30 days, send the "outside window" reply and close the ticket. Owner: Support Agent
  3. Request a photo if the claim is for damage. Note: wait up to 48 hours before following up once. Owner: Support Agent
  4. Decide refund type: if damaged, refund without return; if unwanted, issue a prepaid return label. Owner: Support Agent
  5. Inspect returned items within 1 business day of arrival and mark them resellable or scrap. Owner: Warehouse Lead
  6. Approve any refund over $150. Owner: Operations Manager
  7. Issue the refund in Shopify and send the confirmation template. Owner: Support Agent
  8. Update stock counts for resellable items. Owner: unclear
Outputs
  • Refund issued in Shopify
  • Tracker row marked Closed with refund amount
  • Inventory adjusted in the stock sheet
Troubleshooting
ProblemLikely causeFixOwner
Customer charged again after refundSubscription not cancelledCancel subscription in Recharge, refund second chargeSupport Agent
Return arrives with no order numberCustomer reused old boxMatch by name and email in ShopifyWarehouse Lead
Refund over $150 stuck for daysManager not notified (implied)Tag manager in #ops with order linkSupport Agent
Stock count wrong after returnsStep 8 skippedRecount SKU on Friday stock checkWarehouse Lead
Open questions
  • Who updates stock counts after a resellable return?
  • Do partial refunds follow the same $150 approval rule?
  • Is there a cutoff for returns of opened candles?

Biggest gap: No owner for inventory updates, so returned stock may never be resold.

Written by AI from this prompt. Your results will vary.

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 in Productivity