What Is an SOP? Meaning, Format, Examples and How to Write One
The Coavon team · · 25 min read
An SOP (standard operating procedure) is a written set of step-by-step instructions for doing a routine task the same way every time. It says what the task is for, who does it, what they need, the exact steps in order, and how to check the result. Businesses use SOPs so work comes out right no matter who does it, so new people can learn a job without shadowing someone for weeks, and so a process does not live only in one person's head.
This guide explains what an SOP is and is not, what goes in one, the four common formats, a complete worked example you can copy, how to write one step by step, and how to keep SOPs up to date once you have them.
Short on time? Jump to the parts of an SOP, the formats, the full example, the blank template or how to write one. Want a ready-made file? Download the free SOP template for Word.
What does SOP stand for?
In business, SOP stands for standard operating procedure. Each word does a job:
- Standard: everyone does it this way. It is the agreed method, not one person's preference.
- Operating: it covers the everyday running of the business, such as handling a refund, opening a shop, onboarding a client or releasing a batch.
- Procedure: a fixed series of steps, in order, with a clear start and end.
The plural is SOPs. People say it as letters (“ess-oh-pee”) and write “an SOP”, because the letter S is spoken with a vowel sound. “A SOP” is also seen, but “an SOP” is more common in writing.
SOP has other meanings outside business operations. If you arrived here looking for one of these, this is the short version:
| Where you saw it | What SOP means there |
|---|---|
| University and graduate school applications | Statement of purpose: an essay about your goals and why you are applying |
| Car and manufacturing industries | Start of production: the date a new model or product starts coming off the line |
| Spanish-language health information (“SOP en mujeres”) | Síndrome de ovario poliquístico, known in English as PCOS (polycystic ovary syndrome) |
| Everyday English (lowercase “sop”) | Something small given to keep someone quiet or happy, or a piece of bread dipped in liquid |
| Business planning (written S&OP) | Sales and operations planning, a monthly process for matching demand and supply. It is a different thing from an SOP |
The rest of this guide is about standard operating procedures.
What is an SOP in business?
In a business, an SOP is the written answer to “how do we do this here?” for a task that happens again and again. It turns know-how that sits in people's heads into a document anyone on the team can follow. A good SOP is specific enough that a capable person who has never done the task can do it correctly on the first try, with only the SOP and the tools it lists.
Some everyday examples:
- A coffee shop's opening procedure: what to switch on, in what order, what to check and what to log.
- An agency's client onboarding: the kickoff call, the access to request, the folders to set up and the welcome email to send.
- An accounts team's month-end close: which accounts to reconcile, in what order, and who signs off.
- A support team's refund process: who can approve which amounts, how to issue the refund and what to tell the customer.
- A lab's procedure for calibrating a balance, or a factory's procedure for changing over a machine.
What an SOP is for
- Consistency: the result is the same whether the task is done by your most experienced person or someone in their first week.
- Fewer mistakes: steps that are easy to forget, and checks that catch errors, are written into the procedure instead of left to memory.
- Faster training: a new person can learn from the SOP and ask better questions, instead of watching someone for days.
- Delegation: a business owner can hand a task over without having to stay involved in every repeat of it.
- Safety and compliance: in some industries, written procedures are required by law or by a certification standard (more on that below).
- Improvement: you cannot reliably improve a process that everyone does differently. Once it is written down, you can change one step and see whether it helps.
- Resilience: when the one person who knows how something works is off sick, leaves or is on holiday, the work does not stop.
SOP vs policy vs process vs work instruction vs checklist
These words are often mixed up. They are related documents at different levels of detail:
| Document | What it answers | Example |
|---|---|---|
| Policy | What the rule is and why. It sets the boundaries, not the steps | “Refunds are offered within 30 days of purchase. Refunds over $500 need a manager's approval.” |
| Process | What happens, in what order, and who is involved, at a high level | “Customer asks for a refund → support checks eligibility → approval if needed → finance issues the refund → customer is told.” |
| SOP | How one routine task is done, step by step, so it is done the same way every time | The refund procedure with every step, the screens to use, the checks and the message to send |
| Work instruction | How to do one very specific part of a task in fine detail, often at one machine, screen or workstation | How to issue a partial refund in the payment system, with each field to fill in |
| Checklist | A memory aid for someone who already knows the job, so nothing is skipped | A ten-line list a support agent ticks through before closing a refund ticket |
In small businesses, the SOP often absorbs the others: one document holds the rule, the steps and a checklist at the end. That is fine. The useful distinction to keep is that a policy says what must be true, and an SOP says how to make it true.
You may also hear runbook (an SOP for running or fixing a system, common in IT) and playbook (a looser guide to handling a situation, such as a sales objection or a security incident, where judgment matters more than fixed steps).
When do you need an SOP?
Not every task needs one. Writing and maintaining SOPs takes time, so put them where they pay back. A task is a good candidate when one or more of these is true:
- It repeats: it happens weekly, daily or many times a day.
- Mistakes are costly: an error loses money, upsets a customer, causes an injury, breaks the law or is hard to undo.
- Several people do it: and they currently each do it slightly differently.
- It is being handed over: to a new hire, a contractor, another team or a cover person during holidays.
- It is done rarely but matters: such as a year-end task or an emergency shutdown, where nobody remembers the steps when the day comes.
- It is required: a regulator, customer contract, insurer or certification asks for written procedures.
A task probably does not need an SOP when it is done once, when it changes every time, or when it depends mostly on expert judgment (such as designing a logo or negotiating a contract). For those, a short guide to the principles or a checklist of things to consider works better than fixed steps.
A practical way to start: list the ten tasks that interrupt you most with “how do I…?” questions, or that went wrong in the last few months. Those are your first SOPs.
What are the parts of an SOP?
There is no single official layout that every SOP must follow, and the right amount of detail depends on the task. Most good SOPs contain these parts, in roughly this order:
| Part | What it contains | Needed? |
|---|---|---|
| Title and header | A clear title that names the task, an ID number, the version, the owner, the date it takes effect and the next review date | Always |
| Purpose | One or two sentences on why the procedure exists and what result it produces | Always |
| Scope | What the procedure covers and what it does not: which teams, locations, products or situations | Always |
| Roles and responsibilities | Who does each part, who approves, who to ask for help. Use job titles, not people's names | Always |
| Definitions | Any terms, abbreviations or internal names a new person might not know | If there is jargon |
| What you need | Tools, systems, logins, materials, forms and information to have ready before starting | Usually |
| Safety and warnings | Hazards, protective equipment, and things that must never be done | If there is any risk |
| Procedure | The numbered steps, in order, including decision points (“if this, then that”) | Always |
| Checks | How to confirm the task was done correctly, and what to do if it was not | Always |
| Records | What to log, save or update when you finish, and where | Usually |
| References | Links to related policies, SOPs, forms and work instructions | If they exist |
| Revision history | Each version, what changed, who approved it and when | Always |
What are the 5 parts of an SOP?
When people ask for “the five parts”, they usually mean the core every SOP needs even if you drop everything else: (1) a title and header with the owner, version and date, (2) the purpose and scope, (3) roles and responsibilities, (4) the step-by-step procedure with its checks, and (5) records and revision history. Different organizations group the parts differently, so you will see other lists of five, six or ten. What matters is that someone can tell what the SOP covers, who does what, exactly how, and whether they are reading the current version. Our free SOP template has every one of these parts laid out and ready to fill in.
SOP formats: which one to use
The format is how the procedure section is laid out. Choose it by how complicated the task is and whether it involves decisions:
| Format | What it looks like | Best for |
|---|---|---|
| Simple steps | A single numbered list of short steps | Short, straightforward tasks with no decisions, such as shutting down a till |
| Hierarchical steps | Numbered main steps, each with lettered sub-steps (1, 1a, 1b, 2…) | Longer tasks where each main step has several detailed actions, such as onboarding a client |
| Flowchart | Boxes and arrows with yes or no branches | Tasks with decisions and different paths, such as handling a complaint or approving a refund |
| Checklist | A list of items to tick, with little explanation | Experienced staff who know the job but must not skip anything, such as a pre-flight or pre-launch check |
You can combine them. A common pattern is hierarchical steps for the main procedure, a small flowchart for the one step with a decision in it, and a checklist at the end for the final checks. Photos, screenshots and short screen recordings help with any format when a step is about where to click or what something should look like. The SOP template comes in a standard version with a procedure table, a simple one-page version and a checklist version, so you can start from the format you need.
SOP example: processing a customer refund
Here is a complete SOP for a common small-business task, written in the hierarchical format. Use it as a model for the level of detail to aim for. The company, systems and amounts are examples; replace them with your own.
| Field | Value |
|---|---|
| Title | Processing a customer refund |
| SOP ID and version | CS-004, version 3 |
| Owner | Customer support lead |
| Effective date | 4 November 2026 |
| Next review | 4 November 2027, or sooner if the refund policy or payment system changes |
| Approved by | Head of operations |
1. Purpose. To refund eligible customers quickly and correctly, keep an accurate record of every refund, and make sure refunds over the approval limit are approved before money is returned.
2. Scope. Covers refunds for online orders paid by card. Does not cover exchanges (see CS-005), chargebacks raised through a customer's bank (see FIN-011) or wholesale accounts.
3. Roles. Support agent: checks eligibility, issues refunds up to $500, tells the customer. Support lead: approves refunds over $500 and any exception to the policy. Finance: reviews the refund log each week.
4. What you need. Access to the help desk, the order system and the payment dashboard; the refund policy (POL-002); the refund log.
5. Procedure.
- Find the order. Open the customer's ticket and search the order system for the order number. If there is no order number, search by the customer's email. If you cannot find the order, reply using the “Order not found” saved reply and stop here.
- Check eligibility. Confirm the order was placed within 30 days and has not already been refunded. Check the order notes for earlier refunds or exceptions.
- Decide the amount. Full refund for unused items or our mistake (wrong or damaged item). Partial refund as set out in POL-002 section 3 for anything else. Shipping is refunded only when the mistake was ours.
- Get approval if needed. If the refund is over $500, or outside the policy, assign the ticket to the support lead with a one-line summary and wait for approval in the ticket. Do not issue the refund before approval is recorded.
- Issue the refund. In the payment dashboard, open the payment, choose Refund, enter the amount and select the reason. Copy the refund ID.
- Update the order. In the order system, mark the order as Refunded (or Partially refunded) and paste the refund ID into the order notes.
- Tell the customer. Reply using the “Refund issued” saved reply. Fill in the amount and tell them it usually takes 5 to 10 business days to appear, depending on their bank.
- Log it. Add a line to the refund log: date, order number, amount, reason, refund ID, who approved it (if anyone).
- Close the ticket with the tag “refund”.
6. Checks. Before closing the ticket: the refund ID appears in both the order notes and the log; the amount matches what the customer was told; approval is recorded for anything over $500. Finance compares the log with the payment dashboard every Monday and raises any mismatch with the support lead.
7. Records. The ticket, the order notes and the refund log are kept for at least the period set by the company's records policy.
8. Revision history. v1 (Jan 2025) first version. v2 (Aug 2025) approval limit raised from $250 to $500. v3 (Nov 2026) added the weekly finance check after two refunds were logged with the wrong amount.
Notice what makes this work: every step starts with a verb, each step is one action, decisions are spelled out (“if…, then…”), the steps say where to click and which saved reply to use, and the checks and records make mistakes visible. The revision history also explains why each change was made, which stops someone from “simplifying” a step that exists for a reason. You can download this example as a Word file, laid out in the standard SOP template.
More SOP examples by department
Short versions of SOPs most small and mid-sized businesses end up writing. Each line is the procedure's title and the steps it would cover:
| Team | SOP | What the steps cover |
|---|---|---|
| Operations | Opening and closing the premises | Alarm, lights and equipment in order; safety checks; cash or stock count; what to log; who to call if something is wrong |
| Customer support | Handling a complaint | Acknowledge within a set time; gather facts; decide using the policy; escalate when needed; reply; record the cause |
| Sales | Qualifying a new lead | Questions to ask; what makes a lead qualified; where to record it; when to book a call and who takes it |
| Client services | Onboarding a new client | Welcome email; kickoff call agenda; access and files to request; project set-up; first deliverable date |
| Marketing | Publishing a blog post | Brief; draft; edit and fact-check; SEO checks; images and alt text; approval; publish; share; update the content calendar |
| Finance | Month-end close | Reconcile bank and card accounts; review unpaid invoices; accrue expenses; run reports; review and sign-off |
| Finance | Paying a supplier invoice | Match invoice to order and delivery; check bank details by a known phone number before any change; approval limits; pay; file |
| HR | Onboarding a new employee | Paperwork before day one; equipment and accounts; first-week schedule; training; check-ins at 30, 60 and 90 days |
| HR | Offboarding a leaving employee | Final pay; return equipment; remove access on the last day; hand over work and files; exit conversation |
| IT | Resetting a user's password | Verify the person's identity; reset; force a change at next sign-in; check two-step verification; record the request |
| IT | Restoring from a backup | Who can authorize it; which backup to use; restore to a test location first; check the data; switch over; record it |
| Warehouse | Receiving a delivery | Check the delivery against the order; inspect for damage; count; record discrepancies; put away; update stock |
Notice that two of these exist mainly to stop fraud and security problems: checking a supplier's new bank details by phone, and verifying identity before a password reset. Some of the most valuable SOPs are the ones that make the safe way the normal way.
A blank SOP template you can copy
Copy this outline into a document and fill it in. Delete any section that does not apply to the task. Prefer a formatted file? The free SOP template has this outline as a Word document in four versions: standard, simple one-page, checklist, and the refund example above filled in.
- Title: [The task, starting with a verb, such as “Issuing a customer refund”]
- SOP ID, version and dates: [ID] · version [number] · effective [date] · next review [date]
- Owner and approver: [Job title of the person who keeps it current] · approved by [job title]
- Purpose: [Why this procedure exists and the result it produces, in one or two sentences]
- Scope: [What it covers] · Does not cover: [related situations, with links to their SOPs]
- Roles: [Job title]: [what they do] · [Job title]: [what they approve]
- Definitions: [Term]: [plain meaning]
- What you need: [Systems, access, tools, materials, forms]
- Safety and warnings: [Hazards, protective equipment, never-do items]
- Procedure: 1. [Verb + action] · 2. [Verb + action] · If [condition], then [action]; otherwise go to step [n]
- Checks: [How to confirm it was done correctly, and what to do if not]
- Records: [What to log or save, and where]
- References: [Related policies, SOPs and forms]
- Revision history: v[number], [date], [what changed and why], approved by [job title]
How to write an SOP in 10 steps
1. Pick one task and name its start and end
An SOP covers one task. Write down exactly where it starts (“a customer asks for a refund”) and where it ends (“the refund is issued, logged and the customer told”). If you cannot name a clear start and end, the task is probably several procedures, and each needs its own SOP.
2. Write the purpose and scope first
Before any steps, write one sentence on why the procedure exists and one on what it does and does not cover. This stops the SOP growing to include every related situation, and tells a reader within seconds whether they have the right document.
3. Get the people who do the work involved
The person who does the task every day knows the real steps, the workarounds and the things that go wrong. Ask them to write the first draft, or interview them. An SOP written by a manager from memory usually describes how the task should work, not how it does, and people quietly ignore it.
4. Watch the task being done
Sit with someone (or share a screen) while they do the task for real, and note every action, including the small ones they no longer notice: the tab they always open first, the field they always double-check. Recording the screen with their permission makes it easy to write the steps afterwards and to grab screenshots.
5. Choose the format
Use simple steps for a short task with no decisions, hierarchical steps for a long one, a flowchart where the path branches, and a checklist for experienced people who just must not skip anything. See the formats table above.
6. Write the steps
Keep to these rules and most SOPs come out clear:
- One action per step. If a step has “and” in it twice, split it.
- Start each step with a verb: open, check, enter, send, record.
- Say who does it when more than one role is involved.
- Be exact: name the screen, button, field, form, amount or time, not “update the system” or “in good time”.
- Spell out decisions: “If the amount is over $500, go to step 4. Otherwise, go to step 5.”
- Put warnings before the step they apply to, not after it.
- Explain the why for any step that looks unnecessary, so nobody removes it.
- Use plain words and short sentences. Write for the newest person on the team, and for people reading in a second language.
- Show, don't describe, where a screenshot, photo or diagram is clearer than words.
| Unclear step | Clear step |
|---|---|
| Make sure the order is OK | Check that the order was placed within 30 days and has not already been refunded |
| Process the refund in the system | In the payment dashboard, open the payment, choose Refund, enter the amount and copy the refund ID |
| Get sign-off for big refunds | If the refund is over $500, assign the ticket to the support lead and wait for approval in the ticket |
| Let the customer know ASAP | Within one business day, reply with the “Refund issued” saved reply |
| Be careful with bank details | Before changing a supplier's bank details, call the supplier on the number already on file (never the number in the email) to confirm |
7. Add the checks and records
Decide how someone will know the task was done correctly, and write that down as the last step or a short checklist. Then say what to record and where: a log, a field in a system, a saved file. Checks catch mistakes before they reach a customer; records let you find and fix them afterwards.
8. Test it with someone who has never done the task
This is the step most people skip, and the one that matters most. Give the draft to a capable colleague who has never done the task, and ask them to do it using only the SOP while you watch without helping. Every time they hesitate, ask a question or do something unexpected, the SOP needs fixing. Repeat until they can finish it without help.
9. Review, approve and publish it where the work happens
Have the owner and anyone affected review it, then record who approved it and when. Publish it where people will actually find it at the moment they need it: linked from the task, the project, the ticket type or the workstation, not buried in a shared drive folder. Tell the team it exists, walk them through any changes, and remove old copies.
10. Give it an owner and a review date
Every SOP needs one named owner (a role, not a person, so it survives people leaving) and a next review date. Review it on that date, and also whenever the tool, the policy, the team or the law behind it changes, or when a mistake shows that the steps did not work.
How to keep SOPs up to date
An out-of-date SOP is worse than none, because people follow it and get it wrong, or learn that the documents cannot be trusted and stop reading them all. A few habits keep them alive:
- One home for all SOPs, searchable, with one current version of each. If there are copies in email, printouts and personal folders, people will use the wrong one.
- Version numbers and a change log on every SOP, so readers can see what changed and when.
- A review date on each one, with a reminder sent to the owner. Many teams review each SOP once a year, and more often for anything high-risk or fast-changing.
- Change the SOP when the process changes, as part of the change, not afterwards. A new tool or policy is not finished until its SOPs are updated.
- An easy way to report a problem, such as a comment on the SOP, so the person who finds a wrong step can flag it in seconds.
- Retire SOPs that no longer apply instead of leaving them in the folder.
- Learn from mistakes: when something goes wrong, ask whether the SOP was missing, unclear or not followed, and fix the right one.
SOPs in regulated industries
For most businesses, SOPs are a choice. In some industries they are required, and the rules set what they must contain and how they are controlled. A few examples from US rules and international standards:
- Medicines: the FDA's good manufacturing practice rules for drugs (21 CFR Part 211) require written procedures for production and process control, and require them to be followed.
- Meat and poultry: USDA rules (9 CFR Part 416) require plants to write and follow Sanitation SOPs describing their daily cleaning procedures.
- Workplace safety: OSHA's lockout/tagout standard (29 CFR 1910.147) requires employers to develop, document and use procedures for shutting off hazardous energy before machines are serviced.
- Quality management: ISO 9001:2015 asks organizations to keep the “documented information” they need to run their processes well. It no longer lists specific required procedures, so the company decides which SOPs it needs.
Regulated SOPs usually also need formal document control: approval signatures, controlled distribution, training records showing who has read each version, and audit trails. If you are in one of these industries, check the exact requirements with your regulator, auditor or a qualified consultant, and use a system built for controlled documents. The writing advice in this guide still applies.
Common SOP mistakes
- Writing it from memory at a desk instead of watching the task being done. Steps get missed and the SOP describes an ideal nobody follows.
- Too vague to follow: “update the records” or “check the account” without saying which, where or how.
- Too long to use: a 20-page document for a 10-minute task. If an SOP runs past a few pages, it is usually several procedures, or it contains background that belongs in a policy or training guide.
- Covering every possible case. Write the normal path and the few common exceptions, then say who to ask for anything else.
- Names instead of roles: “send it to Sam” breaks the day Sam leaves.
- No owner and no review date, so it slowly goes out of date and nobody notices.
- Hidden where nobody looks at the moment they need it.
- Never tested with someone new, so the gaps only show up when it matters.
- Written once, then ignored. An SOP that is not used in training and not checked in practice is just a file.
Where to keep your SOPs
Many small teams start with documents in a shared drive, and that works up to a point. The problems come as the number grows: copies drift apart, nobody knows which version is current, and the SOP is in one place while the work is in another. Whatever tool you use, look for:
- One searchable home where every SOP lives, organized by team or area.
- Version history, so you can see what changed and bring back an earlier version.
- Comments, so people can flag problems and suggest changes on the page itself.
- Links from the work, so the SOP is one click from the task, project or ticket it explains.
- A way to turn steps into tasks, so a repeated procedure becomes a checklist someone ticks off, with an owner and a due date.
- Reminders for reviews and repeating procedures, so month-end, quarterly checks and annual reviews do not depend on memory.
How SOPs work in Coavon
In Coavon, you can write the SOP, link it to the work and turn it into tasks people follow. The Library, the team wiki in Flow (on Pro and Business), holds your SOPs as pages in a tree, with a space for the whole organization and one for each workspace. Pages are written in the Docs editor with headings, numbered lists, tables, images, comments and live editing, and they can be linked to the projects and tasks they explain. Docs keeps version history, so you can see earlier versions and bring one back.
To make a procedure something people actually do, save it in Flow as a task template with each step as a subtask, the owner and the files they need. Then start a new task from the template whenever the procedure begins, such as each new client or each refund over the limit. For procedures that run on a schedule, such as month-end close or a weekly safety check, make it a recurring task so Flow creates it on each date. A step that needs sign-off can use approvals: the approver approves, asks for changes or rejects, and the task cannot be marked done until they have answered.
What Coavon does not do: it has no electronic signatures and does not keep training records of who has read each version. If a regulator or auditor needs those for your SOPs, use a dedicated document control system for the controlled documents and Coavon for the day-to-day work around them. See pricing for what each plan includes.
SOP checklist
Before you publish an SOP, check that it has:
| Check | Done when |
|---|---|
| One task | There is a clear start and end, and the title names the task |
| Header | ID, version, owner (a role), effective date and next review date are filled in |
| Purpose and scope | A reader can tell in seconds what it covers and what it does not |
| Roles | Every step says who does it, using job titles |
| Steps | Each step is one action that starts with a verb, and names the exact screen, form or amount |
| Decisions | Every “if” has a “then”, and the reader knows where to go next |
| Warnings | Each warning comes before the step it applies to |
| Checks and records | The reader knows how to confirm the result and what to log |
| Tested | Someone who had never done the task completed it using only the SOP |
| Published | It is in one shared home, linked from the work, with old copies removed |
Frequently asked questions
What is an SOP?
An SOP, or standard operating procedure, is a written set of step-by-step instructions for doing a routine task the same way every time. It usually includes the purpose, the scope, who does what, what you need, the numbered steps, how to check the result and a revision history.
What does SOP stand for?
In business, SOP stands for standard operating procedure. In university applications it means statement of purpose, in manufacturing it can mean start of production, and in Spanish health information SOP is the abbreviation for polycystic ovary syndrome (PCOS).
What is an example of an SOP?
Common examples are a procedure for processing a customer refund, opening and closing a shop, onboarding a new client or employee, paying a supplier invoice, running the month-end close, resetting a user's password or receiving a delivery. Each lists the exact steps, who does them and how to check the result.
What are the 5 parts of an SOP?
There is no single official list, but the core parts most SOPs need are: a title and header (owner, version, dates), the purpose and scope, roles and responsibilities, the step-by-step procedure with its checks, and records and revision history. Many SOPs also add definitions, equipment, safety warnings and references.
What is the difference between an SOP and a policy?
A policy states the rule and why it exists, such as refunds are allowed within 30 days. An SOP explains exactly how to carry out a task in line with that rule, step by step. A policy says what must be true; an SOP says how to make it true.
What is the difference between an SOP and a process?
A process describes what happens at a high level, in what order and who is involved, often across several teams. An SOP zooms in on one task within that process and gives the detailed steps for doing it the same way every time.
What is the difference between an SOP and a work instruction?
An SOP covers a whole routine task: purpose, roles and the steps. A work instruction goes deeper on one specific part of it, such as how to operate one machine or fill in one screen, often with photos or screenshots. Larger organizations use both; small businesses often fold the detail into the SOP.
How do you write an SOP?
Pick one task and name its start and end, write the purpose and scope, involve the people who do the work, watch the task being done, choose a format, write one action per step starting with a verb, add decisions, checks and records, test it with someone who has never done the task, get it approved and published where the work happens, and give it an owner and a review date.
How long should an SOP be?
As short as it can be while someone new can still follow it correctly. Many SOPs fit on one or two pages. If an SOP runs past a few pages, it usually covers several tasks and should be split, or it contains background that belongs in a policy or training guide.
How often should SOPs be reviewed?
Many organizations review each SOP at least once a year, and more often for high-risk or fast-changing tasks. An SOP should also be updated straight away whenever the tool, policy, team or law behind it changes, or when a mistake shows the steps did not work. Regulated industries may have set review rules.
Who should write an SOP?
The people who do the task every day should write the first draft or be interviewed for it, because they know the real steps and the common problems. A manager or process owner then reviews and approves it, and one role is named as the owner who keeps it current.
Is there a free SOP template?
Yes. Coavon's free SOP template for Word comes in four versions: a standard template with every section, a simple one-page version, a checklist version with a sign-off, and a filled-in example for processing a customer refund. Download it at coavon.com/templates/sop-template, with no account needed.
What format should an SOP use?
Use simple numbered steps for short tasks with no decisions, hierarchical steps (main steps with sub-steps) for longer tasks, a flowchart for tasks with decisions and different paths, and a checklist for experienced staff who must not skip anything. Many SOPs combine formats.