If HR, IT, marketing or sales keep asking the same question, the answer is usually a missing procedure. A standard operating procedure is a written, step-by-step instruction for a repeatable business process. It tells the person doing the work exactly what to do, when to do it, and what "done" looks like — in one place, without guessing. This article gives real examples by department and format, then provides a numbered checklist for writing one from scratch and a schedule for keeping it alive.
What an SOP Is and Why It Matters
An SOP is a written, step-by-step instruction for a repeatable business process. A new hire can follow it without guessing what to do next. Where a policy says "keep the workspace clean," an SOP says "at end of shift, wipe down surfaces, dispose of chemical waste in the blue bin, and log completion in the shared sheet." Where a policy says "handle customer complaints professionally," an SOP spells out the steps: acknowledge promptly, pull the order history, offer remedies, escalate if unresolved, and close the ticket with a summary note.
The point matters because growing businesses break at the seams where people are left to improvise. Training time shrinks because a new hire follows the document instead of learning from whoever happened to be at their desk that Tuesday. Compliance stays consistent because every team member executes the same sequence. And the owner stops firefighting daily because the work no longer lives in one person's head.
Consider a marketing team that needs to publish a paid campaign. The SOP says who prepares the ad copy (the copywriter), what assets they must include (brand-approved images, tracking links, UTM parameters), where they upload everything (the ad platform's campaign manager), who approves it (the marketing lead), and what counts as done (campaign live, tracking verified, first-day spend logged). Without that document, someone might skip the UTM link, someone else might use an unapproved image, and no one records the spend until the end of the week. With the SOP, the process runs on schedule and the owner never has to ask "where's my campaign?"
An SOP also sets boundaries. It tells you who owns each step, what tools to use, and when to escalate. That reduces the kind of friction where two people do the same task twice, or a task falls through because neither person assumed the other was handling it.
An SOP is a repeatable procedure written for a specific task — not a one-page policy document, a meeting agenda, or a job description. If a new hire could not carry out the task by following the document alone — with minimal supervision — it is not yet an SOP.
Before you start writing: Most teams skip the hardest part — deciding which processes are worth standardizing first and which ones are hiding a deeper workflow problem.
Examples of SOPs by Format and When to Use Each
SOPs come in four common formats, each suited to a different kind of task. The format you pick depends on whether the work is linear, conditional, visual, or a quick verification.
- Step-by-step: Best for: Tasks with a fixed sequence (onboarding, publishing a campaign, processing a return) · Who writes it: Process owner or team lead · Maintenance effort: Low to moderate; update when steps change · Where it lives: Shared drive or knowledge base
- Checklist: Best for: Verification-heavy tasks where missing one item causes a failure (ad copy approval, security setup, compliance review) · Who writes it: Anyone executing the task · Maintenance effort: Low; add items as gaps appear · Where it lives: A task-management app or a printed sheet
- Decision tree: Best for: Tasks where the next step depends on a condition (lead qualification, escalation paths, troubleshooting) · Who writes it: Subject matter expert · Maintenance effort: Moderate; update when conditions shift · Where it lives: Shared doc or embedded in workflow software
- Flowchart: Best for: Complex multi-department handoffs (new hire onboarding across HR, IT, finance, and facilities) · Who writes it: Process architect or operations lead · Maintenance effort: High; update when departments change · Where it lives: Diagram tool linked to the process doc
A concrete example for each department shows how the format fits the work.
HR — Onboarding a new hire. This is a decision-tree task because the path diverges: if the role is remote, IT provisions a laptop remotely; if on-site, IT schedules a workstation build. The SOP maps those branches clearly, reducing the calls between HR and IT.
IT — Setting up a new workstation. Step-by-step works best here. The task is linear: provision account, assign license, configure device, test connectivity, hand off to the manager. A checklist also works well because the tech can verify each item before closing the ticket.
Marketing — Publishing a paid campaign. Checklist format is common because the failure points are specific: brand-approved assets only, tracking links present, UTM parameters set, budget approved, deadline met. Missing one item breaks the campaign's attribution.
Sales — Lead handoff from marketing to sales. Decision tree fits because the handoff depends on the lead source (organic, paid, referral, event) and the lead score threshold. The SOP spells out what each score range triggers and who receives it.
A checklist works well for repeated steps where it is important to spot omissions. Use a decision tree when the next action changes depending on what you find at a given step. If a task has no conditional branching, a checklist is simpler and faster to follow. If skipping one branch could send a lead to the wrong person or miss a compliance requirement, a decision tree prevents that error.
What makes an SOP usable versus unusable comes down to three things. Clarity: a reader should understand the first step without asking a question. Scope: the SOP covers one process end to end, not part of it. Ownership: a named person or role is responsible for updating it, and the team knows where to find the current version. An SOP that lives in someone's inbox, is written in years of jargon, or stops halfway through is an unusable SOP.
How to Write an SOP from Scratch
Writing an SOP requires a clear scope, plain language, and a structure anyone can follow. Here is the numbered checklist for writing one, followed by a ready-to-copy template with filled-in fields.
- Name the process and define its scope — what it covers and what it does not.
- Identify who performs each step and who approves the output.
- Write each step in plain language using the format "who, what, when, what done looks like."
- Add a glossary of terms so a new hire understands the acronyms and product names.
- List additional resources — links to tools, forms, or related SOPs.
- Set a review cadence and assign an owner who updates it on schedule.
A ready-to-copy SOP template with filled-in fields makes the structure concrete. Use this as your starting point for any department.
``` SOP Title: [Process name] Process ID: [Number or code] Version: 1.0 | Date: [YYYY-MM-DD] Owner: [Role or name] Scope: [What this SOP covers — and what falls outside it]
Purpose: One sentence explaining why this process exists and what problem it solves.
Tools needed: [List the software, forms, or systems required]
Steps:
- [Who] does [what] by [when]. What done looks like: [the observable outcome].
- [Who] does [what] by [when]. What done looks like: [the observable outcome].
- [Who] does [what] by [when]. What done looks like: [the observable outcome].
Escalation path: [If Step X fails or takes longer than Y hours, notify Z and take action A.]
Glossary: [Term] = [definition in plain language] Additional resources: [Link to related SOP, form, or tool] ```
The scope is the part most people skip and then regret. An SOP that says "handle customer complaints" covers too much. An SOP that says "process a refund for an online order once the return shipping scan is recorded" covers one thing end to end. Scope the document to that single task. If the work branches into multiple distinct tasks, write separate SOPs. One document per process keeps the team from flipping between conflicting instructions.
Write steps in plain language. Avoid phrases like "ensure proper alignment" or "optimize the workflow." Write "send the invoice to the client by Friday 5 p.m. using the template in Drive folder 'Invoices'." The difference between a usable SOP and an unusable one is often the level of specificity in the step description.
Add a glossary when your team uses product names, acronyms, or internal jargon. A new hire should not need to ask what an acronym means while following the procedure, so define every term once at the top.
Link additional resources so the SOP does not become a dead end. If Step 3 requires pulling data from a specific report, link directly to that report's URL rather than describing where to find it in words.
How to Share, Maintain and Measure SOPs Over Time
Writing an SOP is the easy part. Keeping SOPs current and measuring whether teams follow them is where many businesses struggle. SOPs rot on the shelf because no one audits them and no one measures their impact. Here is how to avoid that outcome.
- Place every SOP in a shared knowledge base or document library with a clear naming convention (department — process name — version). Do not store them in personal drives or chat channels.
- Assign an owner for each SOP — the person responsible for keeping it accurate. That owner updates the document whenever the process changes and logs the change date.
- Set a review cadence. Every SOP gets reviewed quarterly by the owner and one team member who executes the task. The review asks: does this still match what happens? Is anything missing? Does any step confuse readers?
- Measure adoption by tracking error rates and training time. Compare the error rate for tasks before the SOP existed against the error rate after. Compare the average time a new hire takes to perform the task solo, before versus after. These are the two metrics that prove an SOP is working or failing.
- Version every update. When you change an SOP, bump the version number and archive the old one. Never overwrite without a record. A team member who followed last year's version should be able to find the current one and see what changed.
How to audit and update SOPs on a schedule follows a simple routine. The process owner runs through each SOP during a regular review window and checks three things: the steps still reflect reality, the links in "additional resources" still work, and no new compliance or tool requirement has emerged since the last update. If any answer is no, the SOP gets revised immediately and the new version is flagged as live.
Measuring SOP effectiveness does not require a dashboard. Track the metric that matters most to your operation: fewer errors, faster handoffs, or shorter training time. If a new hire goes from needing extended shadowing to quickly following the document, the SOP is working. If the same person still asks the same question after reading it, the SOP needs rewriting — likely because it skips a step or uses language the reader does not understand.
Keeping SOPs from becoming outdated depends on ownership and cadence. Without a named owner and a quarterly review, every SOP becomes a relic. With both, the document library stays current and the team trusts what they read. This kind of process and procedure work is exactly where process improvement delivers measurable results for growing businesses.
Frequently asked questions
How long should an SOP be?
An SOP should be as long as the task requires — typically three to ten steps. If the document exceeds fifteen steps, split it into separate SOPs rather than forcing one procedure into an unwieldy page.
Who should write company SOPs?
The person who performs the task daily writes the draft, reviewed by the team lead who oversees that function. The subject matter expert ensures accuracy; the team lead ensures clarity for new hires.
Can an SOP replace training entirely?
An SOP reduces training time but does not eliminate it entirely. Use the document as the primary reference, then have a new hire shadow the process once or twice before they execute independently.
Start with a Free Strategic Review
Writing SOPs is one piece of the operations puzzle. The next piece is deciding which processes are worth standardizing first and which ones are hiding a deeper workflow problem. Start with a free strategic review: Confluunt's advisors assess what's working, what's not, and recommend next steps.





