How to Write Standard Operating Procedures for a Small Business

If the business only runs properly when you are in the room, you do not have a business yet, you have a job. Standard operating procedures are how you get the way you do things out of your head and into a form anyone on the team can follow. Here is how to write them without drowning in paperwork.

A good SOP is short enough to follow at the counter and clear enough that a new hire gets it right the first time.

Key takeaways

• An SOP is a written, repeatable way of doing one task, so the result is the same whoever does it.
• Start with the tasks that happen often, go wrong often, or depend on one person.
• Write for the newest person on the team. Short steps, plain words, one action per step.
• Checklists, step lists and short videos each fit different kinds of work. Pick the lightest format that works.
• Every SOP needs an owner and a review date, or it quietly goes out of date.

Most small businesses run on tribal knowledge. The owner knows how to close out the register, which supplier to call when the usual one is late, and exactly how a customer complaint should be handled. The staff know some of it. New hires learn by watching and asking, and they make the same mistakes everyone made before them.

A standard operating procedure, or SOP, fixes that by writing the task down once, clearly, so it can be done the same way every time. SOPs make training faster, make quality consistent, and make it possible for the owner to take a week off. This playbook covers which procedures to write first, how to structure them, and how to keep them from becoming shelf decoration.

What an SOP is, and what it is not

An SOP describes how to complete one specific task from start to finish: opening the store, onboarding a client, processing a refund, backing up the accounting file. It states who does it, when, with what tools, in what order, and what "done" looks like.

It is not a policy ("we treat customers with respect"), a job description ("the manager is responsible for the store"), or a training manual that explains why the business exists. Those documents have their place. An SOP is narrower and more useful: it is the thing someone opens at 6:55 a.m. to make sure the shop opens correctly.

11% to 7% The drop in major surgical complications across eight hospitals after introducing a 19-item checklist, in the World Health Organization study published in the New England Journal of Medicine in 2009. In-hospital deaths fell from 1.5% to 0.8% Surgeons already knew every step; the checklist made sure none were skipped

That study, which surgeon Atul Gawande wrote about in The Checklist Manifesto, is the strongest argument for SOPs in any business. The people involved were highly trained experts. The checklist did not teach them anything new. It simply removed the gap between knowing the right steps and doing them every time, under pressure, with distractions. Your team faces the same gap every day.

Which procedures to write first

Do not try to document everything. A business with 200 SOPs that nobody reads is worse off than one with 12 that everyone uses. Score each candidate task against four questions and start with the ones that score highest.

Question	Why it matters	Example
How often does it happen?	Daily tasks give the SOP the most chances to pay off	Opening and closing, daily cash-up, order fulfillment
How costly is a mistake?	Rare but expensive errors deserve a procedure	Payroll, tax filings, handling a food allergy request
Does it depend on one person?	Single points of failure are the biggest risk to a small team	Monthly invoicing that only the owner knows how to run
Will a new hire do it soon?	Writing it now saves repeating the training later	Customer greeting and table service in a café

Common mistake

Starting with the most complex process in the business because it feels most important. Complex processes take weeks to document and change often. Start with three or four simple, frequent tasks. You will learn how to write SOPs on easy material, and the team will see quick wins.

The anatomy of a usable SOP

A simple template keeps every procedure consistent, which makes them faster to write and easier to follow. Each SOP should have these sections.

Header

Title, a short ID (for example, OPS-003), the owner's name, the version number and the date of the last review. This block is what turns a note into a document someone is responsible for.

Purpose and scope

One or two sentences on what the procedure achieves and when it applies. "This procedure covers processing a product return in store. It does not cover online returns, which are in OPS-007."

Who does it and what they need

The role responsible (not the person's name, because people leave) and the tools, logins, forms or materials required before starting.

Steps

The heart of the SOP. Numbered, in order, one action per step, starting with a verb. Include the specific detail that makes the difference: the exact menu item to click, the exact temperature, the exact phrase to use with the customer. If a step has a decision, spell out both branches.

Definition of done

What the result looks like when the task is complete. "The refund appears in the POS report, the item is tagged and on the returns shelf, and the customer has a printed receipt."

What to do when it goes wrong

The two or three most likely problems and the response to each, including who to contact. This section saves more phone calls to the owner than any other.

How to write one, step by step

1. Watch the task being done. Have the person who does it best perform it while you take notes, or record it on a phone. Do not write from memory; memory skips steps that have become automatic.
2. Draft the steps in plain language. Short sentences. One action per step. "Click Reports, then Daily Summary" instead of "Generate the appropriate end-of-day reporting."
3. Add the specifics. Quantities, times, settings, file names, the location of the key, the name of the supplier portal. Vague steps create vague results.
4. Test it on someone who has never done the task. Hand them the draft and watch, without helping. Every place they pause or ask a question marks a step that needs fixing.
5. Fix, then test once more. A second test with a different person catches what the first missed.
6. Publish it where the work happens. A laminated sheet by the register, a pinned document in the team chat, a page in a shared drive. The SOP nobody can find is the SOP nobody uses.
7. Set a review date. Six months for most procedures, sooner for anything tied to software that updates often.

Worked example: closing a small café

Title: Evening close. ID: OPS-002. Owner: shift supervisor. Purpose: close the café so it is secure, clean and ready to open at 7 a.m. Needs: closing checklist, cash bag, keys, cleaning kit. Steps: (1) At 5:45 p.m. switch the door sign to Closed and lock the front door. (2) Run the end-of-day report on the POS and place the printout in the cash bag. (3) Count the drawer and record the total on the report; if it differs from the POS figure by more than $5, recount once and note the difference. (4) Put the cash bag in the safe and spin the dial. (5) Empty, wash and dry the milk jugs and leave them inverted on the rack. (6) Run the cleaning cycle on the espresso machine. (7) Wipe all tables and the counter, sweep and mop. (8) Take out trash and recycling to the alley bins. (9) Turn off the display fridge lights, leave the fridge on. (10) Set the alarm and lock the back door. Done when: the checklist is signed, the safe is locked and the alarm shows armed. If the alarm will not arm, call the owner before leaving.

A dozen procedures the team actually uses beat a shelf of binders that nobody opens.

Choose the lightest format that works

Not every procedure needs a multi-page document. Match the format to the task.

• Checklist: for tasks where the steps are known but easy to skip. Opening, closing, pre-delivery checks, monthly bookkeeping.
• Numbered step list: for tasks a new person has never done. Most SOPs fall here.
• Flowchart: for tasks with several decision points, such as handling a complaint or qualifying a sales lead.
• Short screen recording or video: for software tasks and physical techniques. A three-minute recording of "how to issue an invoice in our accounting app" often beats a page of text. Pair it with a written step list so people can skim.

Signs an SOP is working

• New hires complete the task correctly in their first week
• The owner gets fewer "how do I" messages
• The same mistake stops recurring
• Staff suggest edits because they actually use it

Signs it needs a rewrite

• It runs past two pages for a simple task
• People keep a "real" version in their notes
• Steps refer to software screens that no longer exist
• Nobody can say who owns it

Pro tip

Write SOPs in the tools you already use rather than buying a dedicated system on day one. A shared folder with one document per procedure, named by ID and title, and a single index page listing them all, is enough for most teams under 20 people. Upgrade to specialist software when you need version control, sign-off tracking or audit trails.

Keeping SOPs alive

The hard part is not writing procedures. It is keeping them true six months later when the supplier changed, the software updated and a better way was found. Three habits keep them current.

One owner per SOP. Ownership means the person responsible for that task, not necessarily the owner of the business. They approve changes and lead the review.

Edit at the point of pain. When something goes wrong, the fix is a change to the SOP, not just a conversation. If a step was unclear, rewrite it that day. If the process changed, update the document before the next shift. A quick note of what changed and when, under the header, keeps the history.

Review on a schedule. Put every SOP's review date on the calendar. At the review, the owner asks three questions: Is every step still accurate? Has anyone found a better way? Is anything missing that caused a problem recently? Most reviews take ten minutes.

Businesses working toward a formal quality standard such as ISO 9001 will find that this discipline of controlled documents, owners and reviews is most of what the standard asks for. For everyone else, it is simply how you stop re-solving the same problems.

Your 30-day SOP plan

• Days 1 to 3: list every recurring task in the business and score each on frequency, cost of error, dependence on one person and new-hire relevance
• Days 4 to 5: pick the top five and assign an owner to each
• Days 6 to 12: watch each task being done, record it and draft the steps using the template
• Days 13 to 18: test each draft on someone new to the task and fix every stumble
• Days 19 to 21: publish all five where the work happens and build a one-page index
• Days 22 to 28: use them for a full week and collect edits from staff
• Days 29 to 30: set review dates, then pick the next five procedures

Frequently asked questions

How long should an SOP be?

As short as it can be while still letting a new person complete the task correctly. Most fit on one page. If a procedure runs past two pages, it is probably two procedures, or it includes background that belongs in training material instead.

Who should write the SOPs, the owner or the staff?

The person who does the task best should supply the content, and ideally write the first draft. The owner's job is to set the template, decide which procedures come first and make sure testing and reviews happen. SOPs written by people who do the work are more accurate and more likely to be followed.

What if staff ignore the SOPs?

Usually it means the document is hard to find, hard to follow or out of date. Fix those first. Then build the procedures into the work: a checklist signed at close, a step list opened during onboarding, a flowchart on the wall by the phone. Procedures that live inside the task get used.

Do I need special software?

Not to start. A shared drive, a document template and an index page cover most small businesses. Dedicated SOP or knowledge-base tools add search, version history and read receipts, which become useful once you have dozens of procedures and more than one location.

The bottom line

Standard operating procedures are the difference between a business that depends on you and a business that can run without you. Pick the tasks that happen often or hurt when they go wrong, write them down in plain steps, test them on someone new, and give each one an owner and a review date. Start with five this month. The rest get easier.