How to Write a Standard Operating Procedure (SOP)

How to Write a Standard Operating Procedure (SOP) That People Actually Follow

A standard operating procedure (SOP) is a written, step-by-step document that codifies how a specific task should be performed so any qualified person can execute it the same way, every time. Strong SOPs cut training time, reduce errors, and turn the tacit knowledge inside your best operators into transferable assets. This guide walks through the exact structure used by Toyota, the FDA, and ISO 9001-certified manufacturers — and shows how to write one yourself, with an Excel template-ready format at the end.

Most SOPs fail not because the author lacks process expertise but because the document is too long, too vague, or never gets updated. The fix is structural. The frameworks below come from regulated industries (FDA-cleared life sciences, ISO 9001 quality systems) and from Toyota's standardized work discipline, which Lean Enterprise Institute describes as the foundation of continuous improvement: "you cannot improve a process you cannot repeat." If you want repeatable results, you need a repeatable document.

What an SOP Is — And What It Isn't

An SOP is not a policy ("we treat customers with respect"), a work instruction ("click the green button"), or a process map ("requests flow from sales to finance to ops"). It sits between policy and work instruction: detailed enough to remove ambiguity, abstract enough to survive minor tool changes.

The FDA's official SOP Template Guideline defines the document as the controlled instruction that proves to a regulator the work was done the same way every time. ISO 9001:2015 takes a similar view — documented information must exist "to the extent necessary to support the operation of processes." In practical terms, that means an SOP needs to answer five questions in writing:

What is being done (the activity)
Why it matters (the outcome or risk)
Who is responsible (named role, not person)
When it triggers (frequency or event)
How it is executed (the numbered steps)

Takeaway: If your document does not answer all five, it is not an SOP — it is a memo. Audit any existing procedure against this five-question test before you publish it.

The Standard SOP Structure (Used by FDA and ISO 9001 Auditors)

Both the FDA's SOP Template Guideline and Johns Hopkins Medicine's IRB sample templates use a near-identical seven-section structure. This is the format you should use for any internal document that will be reviewed, audited, or onboarded against:

Header block — Document title, SOP number, version, effective date, owner, approver, review date. Without version control, every change creates risk.
Purpose — One or two sentences. What is this document for? The FDA explicitly recommends keeping the purpose statement short enough that an end user "can quickly recognize what the document covers."
Scope — Who and what this SOP applies to, and explicitly what it does not cover. Scope creep is the leading cause of stale SOPs.
Definitions and acronyms — Spell out every abbreviation on first use. If your SOP references "CAR," "CAPA," or "MRR," define them.
Roles and responsibilities — Map each step to a named role (e.g., "Accounts Receivable Specialist") not a person. People change; roles don't.
Procedure — The numbered steps. Each step starts with an imperative verb ("Open," "Verify," "Email," "Log"). One action per step.
References and records — Linked policies, forms, templates, and the system of record where evidence is stored.

Takeaway: Build an Excel template with these seven sections as locked rows. Every new SOP in your company starts from the same skeleton, which makes review fast and audit-ready.

The Toyota Standardized Work Discipline — Three Elements That Make Steps Real

Toyota's Toyota Production System Basic Handbook, published through Art of Lean, codifies standardized work as three elements: takt time, work sequence, and standard in-process stock. Translated into office or services SOPs, those become:

Cycle time — How long the task should take from start to finish. "Process refund: 4 minutes" is enforceable. "Process refund quickly" is not.
Sequence — The exact order of operations. Toyota writes sequences so that two operators performing the same task at the same workstation produce identical output. Your SOP should pass the same test.
Acceptance criteria — What "done" looks like. The standard in-process stock in a factory is the visible signal that the previous step was completed correctly. In an SOP, this is the evidence captured at each checkpoint.

The Lean Enterprise Institute notes that Toyota treats standardized work as a "living document" — operators are expected to challenge the standard every day and propose better methods. Your SOPs should carry the same expectation. Bake a "suggested improvements" field into the document and review submissions quarterly.

Takeaway: For every numbered step in your procedure, add three columns to your spreadsheet template: target cycle time, sequence position, and definition of done. This single addition is what separates an enforceable SOP from a wish list.

A Step-by-Step Workflow for Writing the SOP

The most expensive mistake is writing an SOP from a conference room. The second most expensive is writing it without a deadline. Follow this six-step workflow to produce a draft in under a week:

Shadow the work for one full cycle. Sit next to the operator and observe. Note every click, every decision, every wait state. Do not interrupt.
Map the process before drafting prose. Use a flowchart or swimlane diagram. The Smartsheet SOP guide and most ISO 9001 implementation guides recommend process mapping as the pre-writing step that prevents missed branches.
Draft in the seven-section template. Numbered steps only. One verb per step. No nested logic deeper than two levels.
Have a non-expert execute the draft. Hand the document to someone who has never done the task. If they get stuck, your SOP is wrong. If they finish, the SOP is ready for review.
Route for approval with a hard deadline. The FDA's SOP guidance assumes a named approver and a recorded approval date. Set the review window to five business days; without a clock, SOPs sit in inboxes for months.
Set a recurring review date. ISO 9001 expects controlled documents to be reviewed at defined intervals — annually for most office processes, more frequently for regulated work.

Takeaway: Treat the draft as a hypothesis to be tested by a non-expert, not as a finished artifact. The non-expert test catches more ambiguity in 30 minutes than three rounds of internal review.

Where SOPs Break — And the Five Common Failure Modes

McKinsey's research on next-generation operating models found that companies executing structured process improvement see "step-change improvements on the order of 30 to 50 percent" on key operational metrics. The companies that do not see those gains share predictable failure patterns. Watch for these:

Wall of text. Long, dense paragraphs hide decision points. The FDA Group's guidance is explicit: use bullets and lists; they "focus attention and slow the reader's pace." If a step has more than two sentences, split it.
Named people instead of named roles. "Send the invoice to Sarah" breaks the day Sarah leaves. "Send the invoice to the Accounts Payable team" survives turnover.
No version control. Two operators executing two different versions of the "same" SOP is how compliance findings happen. Version every change, even typos.
No owner. An SOP with no named owner is an SOP no one updates. Assign a role-based owner and a calendar review date.
Written from memory. Authors who write from the conference room miss the steps the operator does without thinking — the keyboard shortcut, the email follow-up, the manual reconciliation. Shadow the work.

Takeaway: Build a simple SOP audit checklist with these five failure modes and run every new SOP through it before publishing. The checklist takes two minutes per document and prevents the most common reasons SOPs get ignored.

From Document to System: Making SOPs Stick

Writing the SOP is the first 20 percent of the work. Adoption is the other 80. A few mechanics make the difference between an SOP that lives in a binder and one that runs the business:

One source of truth. Pick one location — a shared drive folder, a wiki, a quality management system — and ban duplicates. ISO 9001 calls this "controlled document" status; the principle applies even if you are not pursuing certification.
Onboarding hooks. Every new hire's first-week checklist should include the SOPs they own. New role + missing SOP read = first preventable error.
Quarterly process audits. Pick three SOPs per quarter and observe the work being done. Compare to the document. Update the document, not the operator.
Kaizen feedback loop. Toyota's standardized work explicitly invites operators to challenge the standard. Add a one-click suggestion mechanism. Review suggestions monthly.
Metrics tied to outcome. Every SOP should map to a measurable outcome: cycle time, error rate, customer wait time, days to close. If the outcome is not improving, the SOP needs work.

Takeaway: An SOP without a feedback loop decays. Set a 90-day review on every new SOP, observe the work, and update the document — that single discipline is what separates ISO-certified operators from companies that re-train new hires from scratch every quarter.

The Excel Template Advantage

A well-built Excel SOP template gives you the seven-section FDA structure, locked headers, version-control cells, role-based responsibility columns, and Toyota-style cycle time and definition-of-done fields — all in one file your team can clone for every new procedure. The ModelStack SOP template kit ships with the format used in this guide: a master SOP template, a process map worksheet, an audit checklist, and a sample completed SOP you can use as a reference example. It is the same skeleton FDA-regulated companies and ISO 9001 auditors expect to see, ready to download and adapt to your business in minutes. If you have ever written an SOP from a blank page on Monday and watched it die in a draft folder by Friday, the right template removes that failure mode entirely — your team starts from a known-good structure and spends their time on the content that matters: the actual steps, the actual owners, the actual outcomes.

How to Write a Standard Operating Procedure (SOP)