How to Write SOPs: The 7-Part Template, the Third-Time Rule, and the 20-Minute Claude Method

A business that lives in your head is a job. A business that lives in its procedures is an asset.

Every operator knows the moment. A client asks how onboarding works and you explain it for the fortieth time, slightly differently from the thirty-ninth. You take a week off and come back to three things done the way you would never do them, because the way existed only in you.

Standard operating procedures are the fix, and most service businesses avoid them for one reason: the first attempt takes an afternoon, produces a document nobody reads, and goes stale in a month.

This article gives you the definition the professionals use, the rule for when a task earns an SOP, a one-page seven-part template, a twenty-minute drafting method with Claude, the versioning habit that keeps it alive, and the ten SOPs a service business should write first.

What an SOP is, according to the people who write them for a living

The clearest definition comes from an agency that lives on documented procedure. The US Environmental Protection Agency's Guidance for Preparing Standard Operating Procedures states: "A Standard Operating Procedure (SOP) is a set of written instructions that document a routine or repetitive activity followed by an organization."

Three words carry the definition. Written: not remembered. Routine: the activity recurs. Followed: the document describes what actually happens, not what should happen in theory.

The EPA is blunt about why this matters. The use of SOPs "minimizes variation and promotes quality" through consistent execution of a process, "even if there are temporary or permanent personnel changes." That last clause is the operator's whole problem in one line. The business should run the same way when you are training, travelling or sick.

A review in PLOS Neglected Tropical Diseases of SOP guidelines for laboratories puts it in operational terms: "SOPs are written step-by-step instructions on how to carry out procedures correctly. SOPs are meant to ensure consistency, accuracy, and quality of data." Swap "data" for "client outcomes" and nothing else changes.

The World Health Organization's laboratory quality guidance compresses the discipline into one instruction: "you have to write what you do and do what you write" (WHO LQSI).

The EPA adds the warning to pin above the desk: "If not written correctly, SOPs are of limited value." And then: "the best written SOPs will fail if they are not followed."

The third-time rule: when a task earns an SOP

Not everything needs one. The WHO guidance says so directly about lab equipment: "Not all the equipment present in the laboratory needs to be supplied with an SOP." The EPA says the organisation "should have a procedure in place for determining what procedures or processes need to be documented."

For a service business the procedure is a rule of three.

• The third time you do a task, write it down. Once is an experiment. Twice is a coincidence. Three times is a process, and the third run is when the steps are still fresh enough to capture.
• The first time someone else will do it, write it down before they start. A contractor, a new hire, an AI assistant. Delegation without a procedure is a request for your own methods to be reinvented badly.
• Anything with a cost of failure gets one on sight. Invoicing, client data, anything that touches a payment or a promise.

The EPA also gives you the standard for how much detail is enough. An SOP should be written with enough detail "so that someone with limited experience with or knowledge of the procedure, but with a basic understanding, can successfully reproduce the procedure when unsupervised." That is the test. Not whether you could follow it. Whether a competent stranger could, alone.

The seven-part template

The EPA's technical SOPs "will consist of five elements: Title page, Table of Contents, Procedures, Quality Assurance/Quality Control, and References," and its procedure section lists topics from "Scope and Applicability" to "Personnel Qualifications/Responsibilities" to "Equipment and Supplies." That is built for laboratories. A service business needs the same logic in a lighter frame.

Seven parts, one page, the same headings in the same order on every SOP in the business.

1. Purpose. One sentence on what this procedure produces and why it exists. The EPA's "Scope and Applicability" in plain language. If you cannot write the sentence, the procedure is not yet understood.
2. Trigger. The event that starts the procedure. A discovery call is booked. A client's payment fails. It is Friday at 3 p.m. A procedure with no trigger never runs.
3. Owner. Who runs it and who is accountable if it does not happen. One name. In a small business this is the field that stops everything falling back to you.
4. Inputs. What must exist before step one: the form submission, the signed agreement, the template, the login.
5. Steps. Numbered, in order, one action each. Where a step happens inside a tool, name the tool and the exact screen or field.
6. Output and definition of done. What exists at the end and how you know it is finished. Client has received the welcome email, the first session is booked, and the CRM stage reads Onboarded.
7. Exceptions. The two or three ways this goes wrong and what to do about each. The EPA lists "Cautions" and "Health & Safety Warnings" at "the critical steps in the procedure"; your version is if the client has not paid, stop at step 3 and run the payment SOP.

How to write the steps

The EPA's style rules were written for chemists and apply unchanged. Concise, step by step, easy to read. "The information presented should be unambiguous and not overly complicated. The active voice and present verb tense should be used." And: "Keep it simple and short."

The laboratory review's writing table adds specifics worth adopting: "sentences with a maximum of 25 words," "Do not use more than two levels of headings," "Put warnings/precautions before the action," and "First put the instruction, then the reasoning."

The two sources disagree on one point. The EPA says "The term 'you' should not be used, but implied." The review says "Use active voice, use 'you'." Pick one and apply it everywhere. For a small team, "you" reads faster and leaves no doubt about who acts.

The 20-minute Claude method

SOPs do not get written because a blank page is slow and dull. Never start from one. Start from a recording of the work itself.

1. Record one run of the task (5 minutes). Next time it comes up, start a screen recording with the microphone on and narrate what you are doing and why. If the task is not on a screen, dictate into your phone while you work. Do not perform. Just do the task and talk.
2. Get the transcript. Most recording tools produce one. The quality does not need to be high; Claude will be reading it, not a client.
3. Draft with Claude (10 minutes). Paste the transcript into a fresh conversation with this prompt, adjusted to your business: You are helping a small coaching business document a procedure. Below is a transcript of me doing the task once while narrating. Write it as an SOP using exactly these seven headings: Purpose, Trigger, Owner, Inputs, Steps, Output and definition of done, Exceptions. Steps are numbered, one action per step, active voice, present tense, sentences under 25 words, and name the tool and screen where each step happens. Where I was unclear or skipped something, insert the marker UNCLEAR and ask me about it at the end rather than guessing. Keep the whole SOP under one page.
4. Correct it (5 minutes). Resolve every UNCLEAR marker and fix any step Claude inferred. The EPA is specific that SOPs should be written by people "knowledgeable with the activity," the "subject-matter experts who actually perform the work." Claude drafted; you are the author of record.
5. Test it on someone else (later, 15 minutes of their time). The EPA: "It is especially helpful if draft SOPs are actually tested by individuals other than the original writer before the SOPs are finalized." Hand the page to a contractor or peer, say nothing, and watch where they stall. Every stall is a missing step.

Twenty minutes per SOP, plus a test. Ten SOPs is a weekend of mornings, not a quarter of avoidance. The Claude workflows for small business article covers the wider set of tasks this method suits.

Versioning, review, and the SOP for SOPs

An SOP is a living document or it is a dead one. The EPA: "SOPs need to remain current to be useful. Therefore, whenever procedures are changed, SOPs should be updated and re-approved." Its cadence for stable laboratory processes is a periodic review "e.g. every 1-2 years." A service business changes faster, so the Apex rule is two triggers: update the day the process changes, and review every SOP at a fixed quarterly session.

Three habits make the system hold.

• Control notation on every SOP. The EPA suggests "A short title and identification (ID) number can serve as a reference designation," plus a revision number and date. For you: title, number, version and date at the top of every page. SOP-07 Client Onboarding v3, 2026-10-01.
• Archive, never delete. The laboratory review lists the full lifecycle: SOPs "are subject to version control (e.g., version number and date), review and approval, distribution and implementation, update and revision, and archiving of superseded versions."
• A read-and-understand record. The WHO guidance has staff sign a "Read and Understand List" for each new SOP. For a team of two, one line in the change log: who read version three, and when.

One more EPA distinction worth keeping: "the checklist is not the SOP." The checklist is used while running the procedure. The SOP explains it. Keep both.

The first SOP to write is the SOP for writing SOPs: the seven headings, the style rules, the control notation, the review cadence. One page, numbered SOP-01.

Turn the SOP into a Claude Skill

Once a procedure is written, the next step is to stop re-explaining it to your AI as well. As of October 2026, Anthropic's documentation describes Agent Skills as "modular capabilities that extend Claude's functionality. Each Skill packages instructions, metadata, and optional resources (scripts, templates) that Claude uses automatically when relevant."

A prompt is to a Skill what a verbal explanation is to an SOP: "Unlike prompts (conversation-level instructions for one-off tasks), Skills load on demand, so you don't have to repeat the same guidance across conversations." The documentation describes a Skill's folder as "organized like an onboarding guide you'd create for a new team member," which is what an SOP already is.

The conversion is mechanical. The SOP's Purpose and Trigger become the Skill's description, which the documentation says "must say both what the Skill does and when to use it." The seven-part body becomes the instructions. Your templates go in as resources. As of October 2026, custom Skills can be created in Claude Code, uploaded through the Claude API, or added in claude.ai settings. The Claude Skills guide walks through the file format and five Skills to build first.

Write the SOP for humans first, test it on a human, then package it. A Skill built on an untested procedure automates the mistakes.

The 10 SOPs every coaching or service business needs first

Write these in order. Each one removes a category of question that currently reaches you.

1. SOP-01: Writing SOPs. The template above, the style rules, the control notation and the quarterly review.
2. SOP-02: Lead intake. What happens between a form submission and a booked call, including the response-time standard and CRM stage changes, inside the GoHighLevel CRM configuration.
3. SOP-03: Discovery call. Preparation, questions, qualification criteria, the close, and the follow-up sent within the hour.
4. SOP-04: Proposal and pricing. Which package goes to whom, the approved prices, who can discount and by how much.
5. SOP-05: Client onboarding. Agreement, payment, welcome sequence, intake data, first session booked. The definition of done is the "Onboarded" stage.
6. SOP-06: Weekly client check-in. Trigger day, what is reviewed, what is sent, and what happens when a client goes quiet.
7. SOP-07: Session preparation. What is reviewed and prepared before any client-facing session, and how far in advance.
8. SOP-08: Invoicing and failed payments. When invoices go out, the reminder cadence, and the exact message on days one, seven and fourteen of a failed payment.
9. SOP-09: Content publishing. From draft to live: review, formatting, scheduling, and the pre-publish checks.
10. SOP-10: Offboarding and testimonial. How a client engagement ends, what is asked for, and how the relationship is kept warm.

With these ten written, the business can be audited. The Apex business audit asks ten questions most coaches cannot answer until the procedures exist. And the day you hire an operator, these ten pages are the job description.

Frequently asked questions

What is an SOP?

A standard operating procedure is, in the US EPA's definition, "a set of written instructions that document a routine or repetitive activity followed by an organization." It exists so a task is done the same way every time, by anyone, including when the owner is absent. The WHO's guidance compresses the discipline into one line: write what you do and do what you write.

What should an SOP include?

For a service business, seven parts on one page: purpose, trigger, owner, inputs, numbered steps, output with a definition of done, and exceptions. This mirrors the EPA's structure of scope, responsibilities, equipment, procedure and quality checks, in a lighter form. Add a title, ID number, version and date at the top so the version in use is never in doubt.

How long should an SOP be?

One page is the target. The EPA's style guidance calls for a concise, step-by-step format in active voice and present tense, and says the document "should not be wordy, redundant, or overly lengthy." If a procedure will not fit on a page, it is usually two procedures, and should be split at the point where the owner or the trigger changes.

How often should SOPs be reviewed?

Whenever the process changes; the EPA says SOPs "should be updated and re-approved" when procedures change, and reviewed periodically, suggesting every one to two years for stable processes. A service business changes faster than a laboratory, so a fixed quarterly review of every SOP, plus same-day updates when a step changes, is the practical cadence.

Can AI write SOPs?

AI can draft them well from a recording or transcript of you doing the task, which removes the blank-page problem that stops most operators. It should not author them unsupervised. The EPA specifies that SOPs be written by the people who actually perform the work and tested by someone other than the writer. Use Claude to draft in twenty minutes, then correct, test and sign.

Write what you do, then do what you write

The gap between an operator who is busy and one who is building is procedure. The busy operator carries every process in working memory and pays for it in interruptions and the inability to step away. The builder writes the process down the third time it happens, tests it on someone else, and stops being the only place it lives.

The same discipline runs through everything else here. A training program is an SOP for the body. A morning protocol is an SOP for the first ninety minutes. The Stoics kept written procedures for the mind and reviewed them nightly. All of it has to be written down and followed.

To install the daily version of that discipline first, the free 5-Day Stoic Operator Challenge gives you a fixed training block, a written evening review and a day with defined edges. Five days of following a procedure makes writing the next one easy.