Standard Operating Procedure Template: The 9 Fields, a Filled-In Example, and the Cold-Run Test That Proves It Works

A standard operating procedure template is only worth the time if a stranger can run the task from it, alone, on a bad day.

Most operators download a template, fill in the title, and stop. The document lives in a shared drive nobody opens. The task still runs out of one person's head, and that person is usually you.

The fix is not a prettier template. It is a template with the right fields, a rule for how much detail each field needs, and a test that proves the document works before anyone relies on it. This page gives you all three, plus a filled-in example you can copy.

If you want the writing process itself (when to document, how to interview the person who does the work, how to draft with Claude), read the companion piece on how to write SOPs with the third-time rule. This article is the template.

What a standard operating procedure actually is

The clearest public definition comes from the US Environmental Protection Agency's guidance on the subject: "A Standard Operating Procedure (SOP) is a set of written instructions that document a routine or repetitive activity followed by an organization." That is from the EPA QA/G-6 guidance for preparing SOPs, which was written for laboratories and field teams but applies cleanly to a coaching business, an agency or a store.

Two words in that definition do the work: routine and repetitive. A one-off project does not need an SOP. A task you will run fifty times this year does. The same guidance is blunt about the failure mode: "the best written SOPs will fail if they are not followed." A template solves the writing problem. Only management, meaning you, solves the following problem.

The EPA document also sets the standard of detail worth adopting. An SOP should be detailed enough that someone with limited experience but a basic understanding "can successfully reproduce the procedure when unsupervised." Unsupervised is the operative word. If the task still needs you on Slack while it runs, the SOP is not finished.

The standard operating procedure template: 9 fields

The EPA guidance notes there is no single correct format, and that the level of detail should depend on how critical the process is, how often it runs and how many people use it. The nine fields below are distilled from its recommended sections and trimmed for a small team. Copy them into a doc, a Notion page or an Airtable record. The container does not matter. The fields do.

Field	What goes in it	Rule
1. Title and ID	Verb plus object, plus a short code: OPS-004 Onboard a new coaching client	Starts with a verb. One task per SOP.
2. Owner and version	Who maintains it, version number, last reviewed date	One named role, never "the team".
3. Purpose	One sentence on what this procedure is for and what result it protects	If you cannot write it in one sentence, split the SOP.
4. Scope	When this applies and when it does not	Name at least one exclusion.
5. Trigger	The event that starts the procedure	Observable: a form submit, a date, a payment.
6. Inputs and tools	Logins, files, templates, equipment needed before step 1	Link every one. No hunting.
7. Steps	Numbered actions in order, with decision points marked	One action per step, imperative voice.
8. Done criteria	What must be true when the task is complete	Checkable by someone who did not do the work.
9. Exceptions and escalation	Known failure cases, what to do, who to contact	Every exception names a next action.

Fields 3 and 4 come almost directly from the federal workplace safety rule on lockout procedures. The OSHA standard 29 CFR 1910.147 requires written energy control procedures to include "A specific statement of the intended use of the procedure" and specific steps for shutting down, isolating and verifying. When a regulator writes requirements for a procedure where errors injure people, the structure is worth borrowing for procedures where errors only cost you a client.

How to write the steps field

The steps field is where most templates fail. The EPA guidance asks for a concise, step-by-step format in the active voice and present tense. Translate that into five rules:

1. Start every step with a verb: open, check, send, tag, move.
2. One action per step. If a step contains "and then", it is two steps.
3. Put the exact location in the step: which tab, which field, which folder.
4. Mark decisions as branches: If the payment failed, go to step 9. Otherwise continue.
5. Put warnings at the step where they matter, not in a preamble nobody reads.

Keep a single SOP under roughly fifteen steps. Past that, the task usually contains two procedures, and splitting them makes both easier to follow and to fix.

A filled-in example: onboarding a new coaching client

A template is easier to use once you have seen it completed. Below is a sample built for a solo coach with one assistant. Swap the tools for your own stack.

• Title and ID: OPS-004 Onboard a new coaching client.
• Owner and version: Client success assistant. v1.3. Reviewed first Monday of the quarter.
• Purpose: Every paying client receives a welcome, an intake form and a booked kickoff call within 24 hours of payment.
• Scope: All paid programs. Excludes free challenge sign-ups and refunds.
• Trigger: Payment confirmation lands in the CRM.
• Inputs and tools: CRM login, welcome email template, intake form link, calendar booking link.

Steps:

1. Open the new contact record in the CRM from the payment notification.
2. Check the program field matches the product purchased. If it does not, go to Exceptions.
3. Apply the tag for the program and the start month.
4. Move the contact to the Onboarding stage of the client pipeline.
5. Send the welcome email template, with the intake form and booking link included.
6. Create a task due in 48 hours: confirm intake form received.
7. When the kickoff call is booked, add the date to the contact record.

• Done criteria: Contact tagged, in Onboarding stage, welcome email sent, follow-up task exists. All four are visible on the record.
• Exceptions and escalation: Wrong program on the record: fix it, note the change, tell the owner the same day. No booking after 48 hours: send the reminder template once, then flag to the owner.

If your stack runs on a CRM pipeline, the stage names in step 4 should match the pipeline exactly. The setup behind that is covered in the GHL pipeline setup guide for coaches.

SOP, checklist or decision tree: pick the right format

Not every task deserves the full nine fields. The EPA guidance makes a distinction worth keeping: "Remember that the checklist is not the SOP, but a part of the SOP." The SOP holds the context, the reasons and the exceptions. The checklist is the stripped-down list someone ticks while doing the work.

Use this rule to choose:

• Checklist only: the task is short, the person already knows how, and the risk is forgetting a step. A weekly backup check is a checklist.
• Full SOP: the task will be done by someone new, involves several tools, or has a cost when it goes wrong. Client onboarding is an SOP.
• SOP with a decision tree: the task branches on conditions the person must judge. Refund handling is a decision tree inside an SOP.

The power of a short checklist is well documented outside business. The World Health Organization reports that its Surgical Safety Checklist has been shown to "reduce complications and mortality by over 30 percent" and can be completed in under two minutes, per the WHO safe surgery programme page. Your client onboarding is not surgery. The principle carries: a short list run every time beats expertise that skips steps under pressure.

The Stoic filter: document less, but document it properly

An operator who discovers SOPs often tries to document everything. That produces a library nobody maintains. Marcus Aurelius gave the better filter in Meditations Book IV, section 24:

For the greatest part of what we say and do being unnecessary, if a man takes this away, he will have more leisure and less uneasiness. Accordingly, on every occasion a man should ask himself, Is this one of the unnecessary things?

That passage, in the George Long translation on Wikisource, is a protocol in itself. Before you write an SOP, ask whether the task should exist at all. Delete it, automate it, or document it, in that order. Writing a careful procedure for a task that should have been cut is discipline pointed in the wrong direction.

The same filter applies inside the document. Every step that does not change the outcome is noise that makes the real steps harder to find. Short procedures get followed. Long ones get skimmed, and a skimmed SOP is the same as no SOP.

Test, review and version: the protocol that keeps a template alive

A template filled in is a draft, not a procedure. The EPA guidance recommends that "It is especially helpful if draft SOPs are actually tested by individuals other than the original writer before the SOPs are finalized." It also suggests reviewing SOPs on a periodic basis, giving every one to two years as an example, and withdrawing any SOP that describes a process no longer followed. OSHA requires its energy control procedures to be inspected at least annually. A small business moves faster than a laboratory, so tighten both.

The Apex SOP protocol

1. Day 1, 30 minutes: Record yourself doing the task once, screen and voice. Draft the nine fields from the recording.
2. Day 2, one run: Hand the SOP to someone who has never done the task. Do not help. Note every question they ask.
3. Day 2, 15 minutes: Every question becomes an edit to a step, an input or an exception. Bump the version.
4. Day 3, one run: Second cold run by the same or a different person. If they finish without asking, mark it live.
5. Quarterly, 10 minutes per SOP: The owner opens it, runs it against reality, and updates the reviewed date or retires it.
6. On any failure: When the task goes wrong, fix the SOP before you fix the person. Most failures are missing steps.

Keep a master list: ID, title, owner, version, last reviewed. The EPA guidance recommends the same thing for the same reason. Without a list, nobody knows which procedures exist, and duplicates appear.

Where AI fits, and where it does not

AI is leverage for the slowest part of this work, which is turning a messy recording into clean fields. Paste a transcript of you doing the task into Claude, give it the nine-field template, and ask it to fill the fields and list every step where the transcript is ambiguous. The ambiguity list is the valuable part. It shows you the gaps a new hire would hit.

What AI cannot do is the cold-run test. A model can make a procedure read well. Only a person running it unsupervised proves it works. The same verification rule applies to any delegated output, a point made in detail in verifying AI agent work before it reaches a decision.

The template also travels beyond the business. A training program is an SOP for the body: a trigger (the calendar block), inputs (the equipment), steps (sets and reps), done criteria (the session logged). Operators who run their mornings on a written protocol, like the 90-minute Train, Think, Build morning, are already using the format without calling it one.

Frequently asked questions

What should a standard operating procedure template include?

A practical template includes nine fields: title and ID, owner and version, purpose, scope, trigger, inputs and tools, numbered steps, done criteria, and exceptions with escalation. The EPA's SOP guidance adds title pages, tables of contents and references for regulated settings. A small business can skip those, but should never skip purpose, scope, steps or done criteria, because those are what let a new person run the task unsupervised.

How long should an SOP be?

Long enough that someone with basic knowledge can complete the task alone, and no longer. For most small-business tasks that means one page and under roughly fifteen numbered steps. If a procedure runs past that, it usually contains two separate tasks. Split it into two SOPs and link them, so each one stays short enough to be followed rather than skimmed.

What is the difference between an SOP and a checklist?

An SOP explains the full procedure: why it exists, when it applies, what tools it needs, the ordered steps and what to do when something goes wrong. A checklist is the short list of steps someone ticks off while working. The EPA guidance treats the checklist as part of the SOP, not a replacement for it. Use checklists for familiar tasks and full SOPs for tasks a new person must learn.

How often should SOPs be reviewed?

The EPA guidance gives every one to two years as an example for periodic review, and says SOPs should be updated whenever the procedure changes. OSHA requires its lockout procedures to be inspected at least annually. A small business changes tools and offers faster than a laboratory, so a quarterly ten-minute review by the named owner is a sensible default, plus an immediate update after any failure.

Can AI write my SOPs for me?

AI can draft them quickly. Give Claude or a similar model a transcript of the task being done and your template, and it will fill the fields and flag unclear steps. It cannot prove the procedure works. That requires a cold run by a person who has never done the task, without your help. Treat the AI draft as version zero and the cold run as the real test.

Write one this week

Pick the task you have explained more than twice this month. Record it once, fill the nine fields, and hand it to someone for a cold run. One working SOP is worth more than a folder of templates, and each one compounds: every procedure you document is a task that no longer needs your attention to run.

The discipline behind this is the same discipline behind training and Stoic practice. Decide the protocol in calm, then execute it without renegotiating. If you want to install that operating system across body, mind and business, start the free 5-Day Stoic Operator Challenge.