How to Write a Business SOP That Someone Else Can Actually Follow

The binder is on the shelf. The work still stops the minute you're out of the building.

That's the part nobody tests for. The SOP looks complete on paper, and the work only ran all year because you were standing there patching every gap in real time.

Who you wrote it for is the whole problem

Almost every SOP gets written by the person who already knows the job, for a reader they assume also knows it. So every judgment that person makes without thinking gets left off the page.

Before any formatting or software question, ask the one that counts. Could someone who's never done this task run it from your document while you're unreachable for two weeks?

If the honest answer is no, you've written a record of how you work. What you need is a procedure somebody else can follow, and that's what this is about.

What an SOP is for

You write a single process as a triggered sequence of steps, name who owns each decision inside it, and define what "done" means. Then you hand it to someone who's never run the task and confirm the work holds while you stay out of the room, and that last bit is the point. The document exists to move the work off you, which is the whole idea behind a business that runs without you.

Put plainly, an SOP is knowledge moved out of your head and into the company. Until it's written in a form someone else can run, the process is just something you happen to know how to do.

And a buyer reads it the same way. Undocumented work is one of the clearest signals that a business depends on its owner, and it gets priced as risk.

The five parts

Miss any of these and the SOP breaks the first time the owner isn't around to fill the gap. The gap is always the thing you do without thinking.

Notice two of the five have nothing to do with steps. The owner and the decision rights are about authority, and they're what turn a list of steps into a procedure.

That's also where delegation lives. Writing the steps is documention. Naming the owner and the decision rights is actually handing the work off.

Writing steps someone else can actually follow

Formatting's the easy part. The hard part is you can't see the small decisions you make on autopilot anymore, and those are exactly what everyone else trips on.

This is how you drag them into the open:

1. Write it while you do it. Run the task once and narrate every action as it happens, including the parts you'd normally skip. Memory smooths over the exceptions, and the exceptions are where a new person gets stuck.
2. Write to the new hire. Assume they know the trade but nothing about your business. Every "obviously" in your draft is a spot where the process stalls when you're gone.
3. Name the decisions you make in your head. For each judgment call, write down the rule you actually use and where it changes. That's the knowledge a buyer is scared will walk out with you.
4. Cut the steps that need you to interpret them. If a step only works because you're around to explain it, it isn't written yet. Rewrite until it stands on its own.
5. Document the most expensive process first. Start with whatever breaks worst when you're away, usually the bottleneck you've quietly become. One bottleneck handed off buys back more of your week than ten tidy checklists.

That fifth one adds up fast. Each process you really hand off is a piece of the path toward running the business in a handful of hours a week.

Then test it with you gone

A finished SOP is a guess. You think the work transfers, and the only way to know is to find out when you aren't there to prop it up.

Run the handoff test before you trust any of them:

1. Hand it to someone who's never done the task. The document and nothing else. No verbal walkthrough, because your explanation is the thing you're trying to take out.
2. Leave and stay unreachable. The absence is the test, so don't hover and don't answer questions. Every question they'd have to ask you marks a hole in the document.
3. Check the result against the done standard. Did the output meet the standard the SOP defined, without you? If not, the SOP failed, not the runner.
4. Fix the page and run it again. Every place they got stuck is a missing step, an unnamed decision, or a fuzzy standard. Patch it and try again with somebody new.

Once it passes twice with two different people, it's documented. If it only works when you're reachable it's still yours, however clean the formatting looks.

Then keep an eye on it. When a process runs without you, a simple dashboard of the few numbers that matter tells you it's still meeting the standard without you driving by to check.

Do that across your core processes and the business starts looking different to a buyer. Documented, owner-light operations are what make a company read as a semi-absentee business.

Doing one workflow yourself is the cheap version. What a business modernization involves is the same method run across all 13 stations at once, with the document set built into a live tenant your team works in every day.

FAQ

How do you write a business SOP that someone else can follow?

Write a business SOP by documenting one process as a triggered sequence of steps, naming who owns each decision, and defining what "done" looks like. Then hand it to someone who has never done the task and confirm the work holds while you stay out of the room.

What should a business SOP include?

A usable business SOP includes five parts: the trigger that starts the process, the role accountable for the outcome, the steps written for a new hire, the decision rights that say what the runner decides alone, and the done standard. The two most often missing are the decision rights and the done standard, and their absence is what keeps the owner in the loop.

How do you know if an SOP actually works?

You know an SOP works when someone who has never done the task completes it to the done standard from the document alone, while you are absent and unreachable. If they have to ask you questions, the document has gaps, and the work has not transferred off you yet.

You cannot transfer work off yourself until you know which work is discounting your value most.

Keystone is closed while we finish building it, and every page of the app points to a waitlist for now. You can join at https://app.trykeystone.io.

When it opens, you'll answer 18 questions in about four minutes and get three scores and your value range with the most likely figure locked, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records. It shows you where undocumented, owner-dependent work is pulling your number down.

Writing the SOPs is the work.

Doing all of that alone is a lot. A Full Operations Modernization sets up the decision routing, the written procedures, the manager structure and the owner dashboard for you, inside a live system your people run.

It is available now on a selective, scope-first basis, and it starts with a conversation rather than a checkout. The Full Operations Modernization page is where scoping begins.