Free SOP Template for Small Business (Word DOCX)
Six free SOP templates: simple, HR, small business with no HR, checklist, hierarchical, and IT. Editable Word DOCX, no signup and no email required.
Most SOP templates you will find are a blank form with the word Purpose at the top. The six here are free, editable Word documents, including two worked examples you can adapt instead of starting from nothing. The procedures I would write down first are the ones that only work when one particular person is around.
Finding a form is the easy part. The hard part is knowing which format fits the procedure you are documenting, what to put in the scope section so people stop asking, and how to get the thing written at all when nobody has a spare afternoon.
The templates come in three formats, and the two worked examples are a complete HR onboarding procedure and an IT backup procedure. None of the downloads sits behind an email form. There is also a version written specifically for a business where the owner is also the manager and the trainer, a situation the large template libraries do not address at all.
What an SOP Template Is
An SOP is a set of written instructions documenting a routine or repetitive activity followed by an organization. That definition comes from federal SOP guidance published by the U.S. Environmental Protection Agency (EPA) in 2007, not from a software vendor. It is worth keeping because it sets a deliberately low bar: an SOP is instructions for something you do repeatedly, not a formal quality-management artifact.
An SOP template is the reusable structure around those instructions. It supplies the sections, so you fill in specifics rather than re-deciding the shape each time. It also keeps a set of procedures consistent with each other, which is what turns a pile of documents into something people actually use.
Which Format to Choose
Choose the format from the shape of the work, not from what the last template you saw looked like. It is the first decision you make about an SOP, and it is usually made by accident.
| Format | Use it when | Typical example |
|---|---|---|
| Step-by-step | Each step is a single action and the order is fixed | Processing a refund, closing the month, running payroll |
| Checklist | Every task must happen but the order does not matter | Opening and closing a store, event setup, equipment checks |
| Hierarchical | Main steps break into sub-steps, or the procedure is long | Onboarding a new hire, installing and configuring a system |
| Flowchart | The path genuinely branches on a condition | Handling a customer complaint, incident escalation |
Most procedures are step-by-step, and most SOPs that go unread are hierarchical documents describing work that was step-by-step all along. If every item under a main step is a single action, flatten it. Length is the main reason people stop opening a procedure.
What Every SOP Includes
Every SOP includes eight elements, and they sort into four groups. The first three groups are what every template covers. The fourth is what separates a document you can rely on from one you cannot.
Two elements are skipped more than any others, and both cause the same kind of trouble later. The scope exclusions, which say what the procedure does not cover, are what stop people from applying a refund SOP to a situation it was never written for. The version history tells the next reader whether they are looking at something current or something abandoned two systems ago.
Which Template to Use?
Pick by format for a general procedure, or take one of the two worked examples if it matches what you are documenting and adapt from there. The templates cover the step-by-step, checklist, and hierarchical formats, and the hierarchical one has decision points built in for a path that branches.
6 Free SOP Templates
Download all six together or copy an individual template. Each is an editable Word document with no email form. Fill in the brackets, delete the sections that do not apply, and change anything that does not match how you actually work.
The files come as Word documents rather than PDFs, because a procedure is meant to be changed. When you need a fixed copy, save the finished document as a PDF from Word and print that. The version people follow should be the one pinned up where the work happens.
Template 1: Simple SOP (One Page)
A title block and eight sections, nothing more: purpose, scope, roles, prerequisites, numbered steps, verification, what to do if it goes wrong, and version history. The right starting point for most procedures.
Template 2: HR SOP for New Hire Onboarding
A complete worked example rather than a blank form. Trigger, systems, owner per step, the sequence from before day one through day 30, and compliance notes on I-9 timing, new hire reporting, and record retention.
U.S. Citizenship and Immigration Services states in its Handbook for Employers (M-274) that Section 2 of Form I-9 is due within three business days of the date employment begins. For new hire reporting, federal law (42 U.S.C. 653a) allows at most 20 days after the hire date, or two monthly transmissions for electronic filers, and some states set a shorter deadline.
Template 3: Small-Business SOP, No HR Department
For a business where the owner is also the manager and the trainer. No approval chain, plus two sections nobody else includes: the step people get wrong, and the situations where the answer is to stop and ask.
Template 4: Checklist SOP
For tasks that all have to happen but not in a fixed order. Includes a line for what was not done and why, and a note for anything the next person should know about, which is the part that gets acted on.
Template 5: Hierarchical SOP
For longer procedures with sub-steps and decision points. Adds definitions, explicit branches that rejoin, a failure table, and a related documents section for the forms and policies the procedure depends on.
Template 6: IT SOP for Data Backup and Recovery
A worked technical example with a schedule table, a monthly restore test, a recovery sequence that stages before overwriting, and an escalation rule for a failed backup.
Standard Operating Procedure Examples
The procedures small businesses actually write down are a short list, and the same ones turn up in every industry. Below are nine, with what triggers each, the format that fits, and the step people skip when they are rushed. Use the list as a starting inventory rather than a target.
| Procedure | What starts it | Format that fits | The step people skip |
|---|---|---|---|
| New hire onboarding | A signed offer comes back | Hierarchical | Completing I-9 Section 2 inside the three business days after the first day of work |
| Opening and closing | The start and end of every shift | Checklist | Writing down what was not done, and why |
| Customer refund | A refund is requested | Step-by-step | Recording the reason, which is what makes the monthly total explainable |
| Month-end close | The last business day of the month | Step-by-step | Reconciling before the numbers go out rather than after |
| Payroll run | Each pay period | Step-by-step | The pre-submit check on new hires, rate changes, and unapproved hours |
| Complaint handling | A customer or employee raises a complaint | Flowchart | Writing down the date and the words used, on the day |
| Offboarding | A resignation or a termination decision | Hierarchical | Removing system access on the last day, not the following week |
| Backup check | The scheduled job finishes | Checklist | The restore test |
| Equipment or vehicle check | Before each use | Checklist | Reporting the fault instead of working around it |
The last column is the part worth copying into your own documents. Every procedure has one step that gets dropped under pressure, and naming it inside the SOP does more for consistency than the rest of the document combined. Ask whoever runs the task which step they would skip on a bad day.
A Step-by-Step Procedure Example
Here is the refund procedure from that list, filled in rather than described. This is what a finished step-by-step SOP looks like: a verb at the front of each action, and a check on the right that makes completion visible to someone who was not in the room.
| Step | Action | How you know it worked |
|---|---|---|
| 1 | Find the purchase in the sales system and note the order number | The order is on screen with its original date |
| 2 | Check the request against the refund window, and stop and ask the owner if it falls outside | Either the date qualifies or you have written approval |
| 3 | Issue the refund to the original payment method only | The confirmation shows the same card or account |
| 4 | Record the reason and a one-line note on the order | The note answers why, not only how much |
| 5 | Email the customer the confirmation and the expected clearing time | The sent message sits in the shared inbox |
Five steps, one page, no preamble. That is the normal size of a working procedure. Anything running past about ten steps is usually two procedures that got merged, and splitting them makes both more likely to be followed.
How to Write an SOP
The template solves the structure. The writing is a different problem, and the failure is nearly always the same one: describing the procedure as it is supposed to work rather than as it does.
Having someone else follow the draft is the step worth insisting on. The author cannot see the steps they perform without thinking, and a first-time reader stumbles on exactly those. Twenty minutes of watching is worth more than an hour of revision.
On writing style, three rules cover most of it. Start every step with a verb. One action per step, so anything containing the word "and" is probably two steps. And write for someone in their first week, not for the person who already knows, since that is who will be reading it.
SOP vs Policy vs Instruction
A policy, an SOP, and a work instruction sit at different levels. They get used interchangeably until someone asks where a rule lives.
| Document | Answers | Changes | Example |
|---|---|---|---|
| Policy | What is required, and why | Rarely | Expenses over $200 need pre-approval and must be submitted within 30 days |
| SOP | How the task is performed, step by step | When tools or people change | Which form to open, what to attach, who approves, how to confirm receipt |
| Work instruction | How one specific task is done in detail | Often | How to scan a receipt on the office printer and name the file |
Small businesses routinely collapse all three into one document, which is fine as long as the requirement and the steps are visually separated. The reason to keep them distinguishable is the Changes column: a policy changes rarely and the steps change every time a tool does, so mixing them means republishing the policy to fix a button name.
Process Documentation, Workflow Documentation, and SOPs
Process documentation is the umbrella term: any written record of how work gets done, from a one-line checklist to a full manual. An SOP is one document inside that set, covering a single procedure. A workflow document sits between the two and maps a process that crosses people, showing who hands what to whom.
The same templates cover all three. Use the simple format for a single procedure, and the hierarchical format when you are documenting a business process that spans roles, adding two things to each step: who owns it, and who receives the output. Handoffs are where multi-person processes fail, and naming them is most of the fix.
Without an HR Department
Every large template library writes for a company that has a process owner, a document controller, and an approval workflow. At a small business, one person owns the process, controls the documents, and approves the changes, while also serving customers. Three things go wrong, and they are the same three every time.
The practical answer is smaller than it looks: four finished documents, not a library. Start with onboarding a new hire, since it is the procedure most likely to be run by whoever is free that week.
Versions and Records
An SOP with no version control is a document with an unknown expiration date. Federal guidance on this is more specific than most employers realize, and it is worth borrowing even if you are nowhere near a regulated activity.
For a small business, that translates into three habits. Number every version and record what changed, who changed it, and when. Keep one master copy that people read rather than several copies they each edit. And set a review date in the title block, because an undated procedure gives nobody a way to judge whether it is still true.
Retention is the other half. Where an SOP covers a regulated activity or produces a record, the record retention rule usually comes from elsewhere and the SOP has to match it, which is why the HR and IT templates here both carry a retention line rather than leaving it implied.
Store, Sign, and Update
The templates work on their own, printed and filled in. What tends not to work is the storage: a shared drive folder that people were told about once, containing several versions of the same procedure with names ending in final and final-v2.
Two things fix most of it. Put the SOP where the work is rather than where documents live, so the onboarding procedure is attached to the onboarding task and the safety procedure to the safety training. And capture an acknowledgment when it matters, so you can show who read which version and when.
That is what FirstHR handles: SOPs and training documents attach to the role and the onboarding workflow rather than sitting in a folder, acknowledgments come back e-signed with a dated record, and the current version is the one people see. FirstHR is an onboarding and HR platform, not a document control system for regulated manufacturing and not a law firm, so it does not validate procedures, manage quality-system compliance, or advise on retention law. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What is an SOP template?
An SOP template is a ready-made structure you reuse each time you write a standard operating procedure. The U.S. Environmental Protection Agency describes an SOP as written instructions for a routine or repetitive activity that an organization follows, and the template gives those instructions the same shape every time. It holds the sections each procedure needs, so you only add the details: a title block with the SOP number, owner, version, and effective date; a purpose that explains why the procedure exists; a scope that says what is in and what is out; roles and responsibilities; the numbered steps; a check that confirms the work was done correctly; and a version history. Using one template for every procedure matters more than finding the perfect one, because a consistent set of SOPs is something people can use, while a mix of shapes is just a pile of documents.
What are the four types of SOP format?
The four formats are step-by-step, checklist, hierarchical, and flowchart, and together they cover almost every procedure. A step-by-step SOP is a plain numbered list for work where every step is one action and the sequence never changes, and it is the format most procedures should use. A checklist uses checkboxes for tasks that all need doing but in no set order, which suits opening and closing routines and equipment checks. A hierarchical SOP nests sub-steps, numbered 1a, 1b, and so on, under each main step, which works for longer procedures with detail at every stage. A flowchart draws the decision points, so it fits work whose path splits depending on conditions. SOP guidance from the U.S. Environmental Protection Agency says plainly that there is no single correct format and that formatting differs from one organization, and one type of SOP, to the next.
What should an SOP include?
Eight elements. A title block carrying the SOP number, version, owner, department, effective date, and review date. A purpose stating why the procedure exists, written as a reason rather than a restatement of the title. A scope naming what it applies to and, importantly, what it does not. Roles and responsibilities, including who approves. Prerequisites: the access, equipment, or information needed before starting. The numbered procedure steps, each beginning with a verb and covering one action. A verification step describing how you know it worked. And a version history table recording what changed, when, and by whom. Scope exclusions and version history get left out more often than anything else on the list, and those two gaps are the ones that cause problems later.
How do you write an SOP for a small business?
Begin with the task that falls apart most often when the person who normally handles it is out. Sit down with that person and record what they really do, not what you assume happens, since the working version usually includes a workaround nobody thought to mention. Aim for a single page. Next, hand the draft to someone who has never done the job and let them attempt it while you watch: each pause shows you a missing step, and those twenty minutes reveal more than any amount of rereading. Give the document a version number and a date, and keep it next to the work rather than in a folder no one opens. Forty SOPs are not the goal. Four solid ones that cover the tasks that cost money when they go wrong handle most of the risk a small business carries.
What is the difference between an SOP and a policy?
A policy sets out what the organization requires and the reason for it; an SOP explains how one particular task gets done, in order. Take expenses: the policy might say that anything above a set threshold needs approval in advance and that claims go in within thirty days. The SOP then names the form to use, what to attach, who receives it, and how you confirm it arrived. Below the SOP sits the work instruction, which covers a single task in fine detail, often for one role or one piece of equipment. Plenty of small businesses keep all three in a single document, and that works if the rules and the steps are clearly set apart on the page, because the rules rarely change while the steps shift whenever a tool does.
Are SOP templates free to download?
The six on this page are free: they download as editable Word documents, with no email form and no account. That is worth checking elsewhere, because several widely linked SOP template pages route the download through a lead capture form, and some template libraries offer a free tier alongside a paid one where the more complete versions sit behind the upgrade. Free also does not mean finished: any template is a structure, and the value is in the specifics you add, which is why the templates here include worked examples for HR onboarding and IT backup rather than only blank forms. Choose the format that suits your procedure, replace the bracketed prompts with your own details, and adjust whatever does not reflect the way your team really works.
How often should SOPs be reviewed?
Once a year by default, and right away whenever the process itself changes. A change matters more than the calendar: a new system, a new person taking over the task, or a change in the rules can each leave the document wrong, and nobody notices until someone follows it. SOP guidance from the EPA adds a control step, recommending that an organization name the person responsible for making sure nobody works from anything but the current version, and that outdated versions be archived so they cannot stay in use. The cheapest way to put that into practice is a next-review date at the top of every SOP, because a procedure with no date on it leaves the reader no way to judge whether it still holds.
Do I need an SOP for every process?
No, and trying to write one for everything is the most common reason small businesses abandon the effort entirely. Write an SOP where at least one of three things is true: the task is done by more than one person and needs to come out the same way each time; the task is done rarely enough that nobody remembers the steps; or getting it wrong costs real money, breaks a rule, or upsets a customer. Onboarding a new hire, closing the month, handling a refund, and responding to a complaint usually qualify. Tasks that one person does daily and never gets wrong usually do not, at least until that person is the only one who can do them, at which point they qualify for a different reason.
Make HR the easy part of running your business
Onboarding, e-signatures, training and core HR in one place. Up and running in 5 minutes.
- 7-day free trial
- No credit card required
- Cancel anytime