How to Document Your Business Processes: A Small Business SOP Guide

Why document processes at all

A standard operating procedure (SOP) is a written description of how a recurring task gets done. In a small business, SOPs are what let someone cover for a sick coworker, let a new hire become useful without shadowing the owner for a month, and let the owner step away without the business stalling. They are also the raw material for improving a process — you can't fix a step nobody has written down.

Which processes to document first

Don't try to document everything. Start where a mistake is expensive or where only one person knows how it's done:

• Money in. Quoting, invoicing and following up on overdue payments.

• Money out. Approving and paying bills, including subcontractor invoices.

• Payroll. Collecting hours, running payroll and recording it correctly.

• Client or project onboarding. Everything that has to happen between a signed agreement and the first day of work.

• Closeout and handoff. Final billing, documentation and follow-up when a job or engagement ends.

• Recurring admin. Month-end tasks, renewals and anything else that happens on a schedule and gets forgotten.

Step by step: writing an SOP

1. Pick one process and define where it starts and ends.
2. Ask the person who does it today to walk through it on a real example, out loud.
3. Write down each step as it happens — screenshots and links to the actual files or systems help.
4. Note the decisions and exceptions: what happens when something is missing or wrong.
5. Clean it up into short, numbered steps that start with a verb.
6. Have someone who has never done the task follow the draft, and fix every place they get stuck.
7. Name an owner and a review date, then store it where the team already works.

What a good SOP includes

• Title and purpose. One line on what the process is and why it matters.

• Trigger. What starts it: a date, an email, a signed contract.

• Owner. The one person responsible for it being done and kept current.

• Tools and systems. Which software, folders or forms are used, with links.

• Steps. Numbered, short, one action each.

• Definition of done. How you know it's finished correctly.

• Exceptions. What to do when something doesn't fit the normal path.

• Last reviewed. A date, so everyone can tell whether it's still trustworthy.

Keeping SOPs current

An outdated SOP is worse than none, because people follow it confidently. Review each one on a schedule and whenever the underlying system changes — a new accounting tool, a new approval step, a new person in the role. The person who owns the process should update the document as part of changing the process, not as a separate project.

Common mistakes

• Writing a novel. Long documents don't get read. If a step needs a paragraph, it may be two steps.

• Writing it without the person who does the work. The owner's version of a process is often not what actually happens.

• Never testing it. A process isn't documented until someone else can follow it successfully.

• Storing it where nobody looks. Put SOPs in the system your team already opens every day.

• Documenting everything at once. Five accurate SOPs for the processes that matter beat fifty nobody trusts.

Getting help documenting your processes

Workflow and process documentation is one of the services Campbell Operations provides to small businesses and contractors in Boise and the Treasure Valley — usually alongside the bookkeeping, admin or project administration those processes support, so the documents describe how the work is really done.

Fractional COO and operations support in Boise