How to Write an SOP for Your Coaching Business (Even If You Hate Documentation)

There’s a Google Doc in your Drive called “SOPs, start here.” You opened it with real hope last spring. It has one heading and a blinking cursor. You know the one.

An SOP is a short, written set of steps that lets someone else do a recurring task the way you would. To write one, pick one task, talk it through out loud, turn it into numbered steps, follow it once using only the document, then add an owner and a review date. One page, one task. That’s the whole method.

And please hear this before anything else: the blank doc isn’t proof you’re “not a systems person.” You know your business cold. What’s been missing is a way to get it out of your head that fits inside a regular Tuesday.

You don’t need a binder. One page you’ll actually open beats it every time.

What actually counts as an SOP in a coaching business?

An SOP covers one task from start to finish, clearly enough that someone else gets the same result you would.

It helps to know what it isn’t. A checklist confirms items; an SOP explains how to do them. A training manual covers a whole role; an SOP covers one task. And a brain dump is everything you know about a topic, while an SOP is only what’s needed to finish this one thing.

Small wins. “How we send the weekly newsletter” is an SOP. “Marketing” is a book you’ll never finish, and I say that with love, because I have a Notion graveyard of ambitious half-written ones.

Which tasks should you write down first?

Start with tasks that repeat often, break often, or that only you know how to do. Those carry the most weight.

Good first candidates in a coaching or course business:

• Client onboarding after someone pays
• The weekly newsletter send
• Posting a call replay for your group program
• Launch-week checks
• Weekly community prompts and moderation

Planning a first hire? Run a quick tally first. For four weeks, jot down every task you’d love to hand off and how many minutes it took. The low-judgment tasks eating the most time are the ones worth documenting first. Everything else can wait.

How do you write an SOP without staring at a blank page?

Talk it out loud, turn the transcript into numbered steps, follow it once using only the page, then add a header.

1. Talk it out. Record a voice memo or a quick screen recording while you do the task, narrating as you go. “First I open Flodesk. Then I duplicate last week’s email…” Google announced a Docs feature that drafts from speech (Google, October 2026; check plan availability first), but any transcription tool works. The point is getting it out of your head without a blank page staring back.

2. Number the steps. Clean the transcript into a list. One action per step, and name the tool and where to click: “Flodesk > Emails > Duplicate last week’s newsletter.”

3. Follow it once, exactly as written. This is the step everyone skips, and it’s the one that makes the SOP real. Each hesitation means a step is missing. And whenever you do something the page doesn’t mention, add it.

4. Add the header. Four lines, below. They keep it true after today.

5. Store it where people look. One home and one naming pattern, like “SOP: Weekly newsletter send.” An SOP nobody can find doesn’t exist.

Why do SOPs quietly go out of date?

SOPs go stale because nobody owns the update. Tools change, steps change, and no one is named to notice.

A process usually outlives its accuracy long before it outlives its author. The tool gets a new layout. The welcome packet gets a new page. Someone fixes a step on a busy Tuesday, tells no one, and now two versions exist while the official one sits on the shelf looking very confident.

The fix is a four-line header at the top of every SOP:

• Owner: one name
• Why this exists: one sentence on the outcome
• Last reviewed: a date
• To change this, tell: a name

That “why” line does more work than it looks like. When the steps run out or something odd happens, it lets the person make a good call based on what you actually want.

Then put a review on your quarterly planning day. A few minutes per SOP: run it, update what changed, change the date. AI can draft the update. A person reads it before it replaces anything.

How do you make an SOP clear enough for an AI agent?

An AI-ready SOP states what starts the task, what information it needs, what proves it worked, and when a person steps in.

There’s a lot of “feed your SOPs to an agent” advice going around, and I get the appeal. But vague steps become confident, vague answers. Before you hand anything to an agent, add four answers to the page:

1. What starts it? A new form, a tag added, Monday at 9.
2. What does it need? The client record, the template, your tone notes.
3. What proves it worked? A row filled in, a draft saved, a message waiting for review.
4. When does a person step in? Money, complaints, anything health or legal, and anything the agent isn’t sure about.

A regular workflow fits when	An agent earns its place when
The steps never change	The task needs a judgment call
Inputs always look the same	Inputs vary, like free-text replies or DMs
You want it to run silently	You want a draft a person reviews

Walk the task by hand once with one real record before any automation touches it, then have someone read the agent’s first ten results. That’s Human First, AI Second™ doing exactly what it promises: the agent handles the repeats, and your voice stays yours.

For healing-work practitioners: keep client information out of any AI tool until you’ve confirmed the rules with your licensing board or a privacy professional. I’m an operations partner, not a lawyer or clinician, so this is one to ask the right person.

The One-Page SOP (Rooted Revenue Framework™, Pillar 4)

The saveable version:

1. Header: owner, why it exists, last reviewed, who to tell about changes
2. Trigger: what starts the task
3. Steps: numbered, one action each, tools named
4. Done looks like: what proves it worked
5. Hand-off point: where a person decides
6. Tested: the date someone followed it exactly as written

Pillar 4 is the run-the-business spine of the framework, and SOPs are its backbone. They’re also the part that stays yours if any partnership ever ends.

Your first SOP, this week

• Today: pick one task from the list above.
• Next time you do it: record yourself narrating.
• That evening: turn the transcript into steps and add the header.
• The time after: follow it exactly as written and fill the gaps.

One SOP a week, and by spring you’ll have the start of a real operations library. Maybe with a mug of something warm while the West Michigan weather does its thing outside.

What you’ve been told vs. what’s actually true

What you’ve been told: you need to document everything before you can delegate, so block off a weekend and build the binder.

What’s actually true: you need one page for the task that’s costing you the most, written in your own words and tested once. The binder was never the goal. A business that holds without you carrying every step is.

Frequently asked questions

How long should an SOP be?

One page, one task. If an SOP grows past a page, it usually covers more than one task and should be split. Short SOPs get used; long ones get skimmed and ignored.

How often should I update an SOP?

Give every SOP a review date and review important ones quarterly. Review any SOP right away when a tool it uses changes, and update the date so people know it’s current.

Can I use AI to write my SOPs?

Yes, for the first draft. Record yourself doing the task, let AI turn the transcript into steps, then follow the draft yourself once before anyone else uses it. A person should approve every version.

Can an AI agent follow my SOPs?

It can if each SOP states what starts the task, what information it needs, what a finished result looks like, and when a person must step in. Test it by hand first and review the agent’s early work.

When you’re ready

If you’d rather have a partner build the whole library with you, from the SOPs to the automations they power, the Content-to-Clients Roadmap shows the audit I run on every new partnership. Grab it whenever you’re ready.

In your corner,
Jenn