SOPs for Small Business: How to Write Procedures People Follow

A standard operating procedure (SOP) is a written set of steps for a task that repeats, clear enough that someone other than you can do the task the way you would. That’s all it is. It isn’t a binder on a shelf or a project for a quiet month. It’s the answer to “how do we do this here?” written down once, so you stop giving it out loud.

If you’re the only one who knows how invoicing works, how a quote gets priced or which supplier needs a phone call instead of an email, your business depends on you in ways that cost you every week. SOPs are how that knowledge moves out of your head and into the business. This guide covers which processes to document first, a simple format, how to write procedures people actually follow, and how to keep them current.

Why Do SOPs Matter in a Small Business?

In a small business, SOPs do three practical jobs:

• They let you hand work off without handing off the quality. When the steps are written down, a task comes back done the way you’d do it, not the way someone guessed.
• They make a new hire or assistant useful sooner. Instead of shadowing you for weeks, they work from the document and ask about the gaps.
• They make the business something you can step away from, or sell. A buyer can read a written procedure. They can’t read your memory. More on that in how to make your business run without you.

Which Processes Should You Document First?

You don’t need SOPs for everything. Start where the payoff is fastest. Look for tasks in your own business that are:

• Repeated. Daily or weekly work: intake, scheduling, appointment confirmations, invoicing, collections, vendor ordering.
• Tied to money. Anything where a missed step costs you cash, such as billing, quoting and following up on past-due invoices.
• Only in your head. The task nobody else can do if you’re out sick.
• Next in line to hand off. If you’re about to delegate it, write it down first, or write it down while you hand it over.

A quick way to build the list: for two weeks, note every task you do and every question someone brings to you. Anything that shows up more than once is a candidate. Rank them by how much time they take you and what it costs when they go wrong, and start at the top.

A Simple SOP Format

Keep each SOP to one task and, where you can, one page. A format that works for admin tasks:

• Title. The task, in plain words: “Sending the monthly invoices.”
• Purpose. One sentence on why it matters: “So every client is billed by the 1st and nothing is missed.”
• When. What triggers it: a date, a new customer, a form submitted, an email received.
• Who. The person responsible, and who to ask if something is unclear.
• Tools and access. The software, logins (by role, never the passwords themselves) and files needed.
• Steps. Numbered, one action per step, in the order they happen. Include screenshots where a screen is confusing.
• Exceptions. The customers with special terms, the supplier who has to be called, the “unless it’s a Friday” rules. This section holds the knowledge that lives only in your head.
• Done looks like. How the person knows the task is finished and correct.
• Last updated. The date and who changed it.

You don’t need special software. A shared folder of documents, named consistently and listed in one index document, does the job. If you want ready-made wording for handing off work and defining “done right,” our free delegation guide has email scripts and quality standards you can copy.

How Do You Write SOPs People Actually Follow?

Capture the work while it’s being done. Don’t block off a day to “write the manual.” The next time you do the task, do it slowly and narrate each step to someone writing it down, or record your screen while you talk through it. Writing from memory leaves out the steps you do without thinking, and those are the steps a new person misses.

Write for someone who has never done it. Use plain verbs at the start of each step: open, check, send, file. Say exactly where things are: which folder, which tab, which button. If a step needs judgment, say what to look for and when to ask you.

Put the exceptions in. A procedure that covers only the normal case breaks the first time something unusual happens. Every time you hear yourself say “except when,” add it to the Exceptions section.

Test it with someone else. A procedure is proven only when someone other than the person who wrote it can follow it without asking. Hand it over, watch where they get stuck, and fix those steps. Each gap is a missing step, not a failure.

Store them in one place. Keep one index of every SOP, with the task name, owner and last-updated date. If people can’t find the procedure, they’ll ask you instead.

How Do You Keep SOPs Current?

An SOP that no longer matches how the work is done is worse than none, because people follow it. Keep yours current with three habits:

• Update when the work changes. A new software, a new supplier or a new pricing rule means the SOP changes the same week. Make updating the document part of making the change.
• Review on a schedule. Put a short review on the calendar every quarter. Read each procedure against how the task is actually done today.
• Give each SOP an owner. One person is responsible for keeping it accurate, even if they aren’t the one doing the task.

Mistakes to Avoid in Your Own SOPs

Check your own procedures against this list:

• Writing them all at once. A burst of documentation goes stale before anyone uses it. Write them as you hand work off.
• Writing from memory. Steps you do on autopilot go missing. Capture the task while doing it.
• Leaving out the exceptions. The special cases are the part only you know, and the part a buyer or new hire can’t get anywhere else.
• Too much at once. One SOP per task. A ten-page document covering five tasks won’t be read.
• No owner and no date. Without them, nobody knows whether the procedure is still right.
• Putting passwords in the document. Note which access is needed and grant it separately, so you can revoke it at any time.

Where a VRA Assistant Fits

SOPs take time, and time is what you’re short on. A VRA assistant can take on the administrative side of the work. VRA assistants are trained in administrative documentation and SOP work as part of the program: drafting the procedures as they learn the work, recording how it is actually done with the exceptions included, and keeping them current as the work changes, so they still describe the business when someone reads them.

Your assistant works under your direction: the judgment calls, pricing and decisions stay with you. Access is determined by you, scoped to the work, and revocable at any time. Every VRA assistant signs a confidentiality agreement and VRA will sign yours on request. The procedures written for your business belong to your business.

Here’s how one client describes working with VRA assistants once they know the client’s procedures:

“I have no reservations about them communicating with clients with minimal to no oversight, once they are trained and they learn our SOPs and how we like to communicate.”

Quinton Randel, EIDLexit · client check-in · Watch the check-in

What it costs:

• Full-time: $1,500 a month, 40 hours a week. An assistant who works for your business and no one else.
• Part-time: $800 a month, 20 hours a week. Your own named assistant, with reserved hours; a part-time assistant may hold one other part-time placement.

No setup or onboarding fees. Every assistant completes a mandatory 4-week, instructor-led training program; only 0.89% of our latest applicant cohort passed. We commit to 90% proficiency in your systems within 5 business days of starting with you. Once you select your assistant, they can start within 24 hours of selection, and if the fit is wrong you can swap in a different assistant at any point, at no extra cost: no trial window, no fine print. Full pricing → How that compares: virtual assistant cost by model.

If you’re preparing to sell, written procedures are part of getting the business ready. If you’ve just bought one, your first 100 days after buying a business covers getting the seller’s process onto paper.

Questions Owners Ask

What is an SOP in a small business?

A written set of steps for a task that repeats, clear enough that someone other than the owner can do it the same way. In a small business, SOPs cover work like intake, scheduling, invoicing, collections and vendor ordering.

Which SOPs should I write first?

Start with tasks in your business that repeat, are tied to money, live only in your head, or are next in line to hand off. Billing, quoting and past-due follow-up are good candidates because a missed step costs cash.

How long should an SOP be?

One task per SOP, and one page where you can. Include the purpose, the trigger, who is responsible, tools and access, numbered steps, exceptions, what done looks like, and the last-updated date.

Do I need special software for SOPs?

No. A shared folder of documents with consistent names and a single index works. What matters is that people can find the current version and that each SOP has an owner.

When should SOPs be updated?

Whenever the work changes, in the same week as the change, plus a short review of every procedure each quarter.

Can a virtual assistant write my SOPs?

VRA assistants are trained in administrative documentation and SOP work as part of the program. They draft the procedures as they learn the work and keep them current as it changes. The judgment and the decisions in each procedure stay with you.

These answers are general guidance, not legal, tax or financial advice.

Procedures are what let the work leave your desk, whether you run a trade or a sales and service team.