SOP Generator

Turn a messy spoken or pasted explanation of how something gets done into a clean, formatted standard operating procedure with purpose, scope, numbered steps, roles, and exceptions, all in one pass.

For Operations Managers Knowledge Managers Team Leads Founders and Small Teams
Sample prompt to Joy's Assistant

Here's how we handle [process], roughly: [explanation]. Turn this into a clean standard operating procedure with purpose, scope, numbered steps, roles, and exceptions.

What it can look like

An illustrative example. Your output will reflect your own sources, data, and prompts.

Here's how we handle customer refunds, roughly: when someone emails asking for their money back, whoever's on support that day looks up the order and checks it's within 30 days. If it is, they approve it in the billing tool and the customer gets it back in about five business days. If it's over 30 days or more than $500 they're supposed to check with a team lead first. Oh, and season passes are non-refundable so those get declined. We log everything in the shared tracker. Turn this into a clean standard operating procedure with purpose, scope, numbered steps, roles, and exceptions.

I've turned your walkthrough into a standard operating procedure. It follows the format of the other SOPs in your Knowledge Center, with the steps in order, the roles named, and the edge cases you mentioned pulled out as exceptions.

Customer refund SOP: draft

Process: Customer Refunds
Owner: Support Team
Last reviewed: July 2026

Purpose: Ensure every refund request is handled consistently, within policy, and with a clear record.

Scope: Covers refund requests for standard orders received by the support team. Chargebacks and formal disputes follow the finance escalation process instead.

The procedure below covers a standard refund from request to confirmation.

Refund process flow

  1. Request received; locate order and confirm date.
  2. Within 30 days and $500 or under? If yes, approve; if no, route to team lead first.
  3. Approve refund, reply with timing, log the decision.
  1. Locate the order in the billing tool and confirm the purchase date.
  2. Check the request is within 30 days of purchase and the amount is $500 or under.
  3. If it qualifies, approve the refund in the billing tool; funds return to the customer in about five business days.
  4. Reply to the customer confirming the refund and the expected timing.
  5. Log the request, decision, and date in the shared refund tracker.
  • Support agent. Handles the request end to end for standard refunds that fall within policy.
  • Team lead. Reviews and approves refunds over $500 or older than 30 days before they proceed.

Exceptions: Requests over $500 or past 30 days need team-lead approval first. Season passes are non-refundable and should be declined with a polite explanation.

Want me to condense this into a quick-reference checklist for the support desk, or draft the refund confirmation email the steps refer to?

From explanation to SOP in a few steps

SOP Generator takes the way you actually explain a process, rambling, out of order, full of "oh, and if this happens," and turns it into a structured standard operating procedure. Joy, the JoySuite assistant, organizes it into purpose, scope, numbered steps, roles, and exceptions.

  1. Explain the process

    Tell Joy how something gets done in your own words, typed or pasted from an email or transcript. Out of order and incomplete is fine; that's what it's for.

  2. Say what you need

    Ask for a standard operating procedure and name the sections you want: purpose, scope, numbered steps, roles, exceptions. Joy fills in a sensible structure if you don't specify.

  3. Review the draft

    Get a clean SOP with the steps in logical order, roles assigned, and edge cases pulled out as exceptions. Check it against how the work really happens.

  4. Use it where your team works

    Ask for a tweak, "split step 3 in two" or "add a step for partial refunds," then copy the finished procedure into your wiki, Notion, or shared drive.

  5. Make it one click for your team

    Save this ask as a custom command on the assistant your ops team already uses, customize the sources and format, and anyone can turn a walkthrough into an SOP in one click.

Make it yours

Consistent Structure

Every SOP comes out in the same purpose, scope, steps, roles, exceptions shape, so your documentation library stays uniform.

Ordered Steps

Joy sequences the actions logically even when you explain them out of order, and numbers them for easy reference.

Roles Spelled Out

Each step names who does it, so there's no ambiguity about hand-offs when the SOP is put to use.

Edge Cases Captured

The "what if" asides you mention in passing get pulled into a clear exceptions section instead of getting lost.

Quick-Reference Checklist

Condense the SOP into a short checklist your team can keep open while they work.

Decision Points

Add if/then branches for steps where the right action depends on the situation.

New-Hire Version

Rewrite the same procedure with extra context and definitions for someone doing it for the first time.

Update an Existing SOP

Paste an outdated procedure and describe what changed to get a refreshed version.

Frequently Asked Questions

What is an SOP generator?

An SOP generator turns an informal explanation of a process into a structured standard operating procedure. With JoySuite, you describe how something gets done and Joy organizes it into purpose, scope, numbered steps, roles, and exceptions that you can review and copy into your documentation.

Can it turn a verbal explanation into a written procedure?

Yes. Paste a transcript or type out how the work happens in your own words, even out of order, and Joy sequences it into a clean, numbered procedure. You refine the wording and copy the result wherever your team keeps its documentation.

What sections does the SOP include?

By default the SOP covers purpose, scope, numbered steps, roles, and exceptions. You can ask for other sections, drop ones you don't need, or change the order, and Joy rebuilds the draft in the same conversation.

Does it keep our SOPs consistent with each other?

When your Knowledge Center already holds similar SOPs, Joy matches their structure and tone so new procedures read like the rest of your library. You can also point it at a specific example to follow.

Can I update an existing SOP instead of writing a new one?

Yes. Paste the current procedure and describe what changed, and Joy produces a refreshed version with the updates worked in. Copy the result back into your wiki or shared drive.

Related Recipes

Operations

Knowledge Gap Analyzer

Identify what's undocumented by analyzing support requests.
Operations

RACI Generator

Create responsibility matrices for projects and processes.
Operations

Clone Yourself

Create a virtual expert that answers routine questions.

Ready to get the process out of your head and onto the page?

Join the waitlist and be first to try this workflow when JoySuite launches.

Join the Waitlist Browse All Recipes