Standard Operating Procedures: What Actually Gets Followed

Most standard operating procedure examples you find online are documents nobody would ever read twice. Twelve pages, a version history, an approvals table, and a level of detail that guarantees it goes out of date within a month of being written.

The test of an SOP is not whether it is thorough. It is whether someone follows it on a Tuesday when they are busy and nobody is watching.

By that test most of them fail, and they fail for three reasons that have nothing to do with how well they were written.

Why Most SOPs Are Never Opened Again

They are written by the wrong person. Usually a manager, describing how the job ought to be done, rather than the person who does it describing what they actually do. The gap between those two documents is where every unwritten workaround lives, and the workarounds are the useful part.

They are stored away from the work. A procedure in a shared drive three folders deep is a procedure that requires a decision to open. Anything that requires a decision loses to habit. The procedures that get followed live where the task happens: pinned to the screen, at the top of the template, inside the tool.

They try to cover every case. Completeness is the enemy here. A document that handles the ninety per cent case in one page beats one that handles every exception in twelve, because the second one will not be read at all and the first one will be read every time.

Three Standard Operating Procedure Examples That Get Followed

Short, specific, and written in the order the work actually happens.

1. Client onboarding, first 48 hours

The purpose is that nothing is forgotten in the window where a new client is forming their opinion of you.

Within 2 hours: send the welcome email from the template, with the named point of contact and their direct line.
Within 4 hours: create the client folder from the folder template. Do not create it from scratch.
Within 24 hours: send the kickoff invite with an agenda attached, offering two specific times.
Within 24 hours: send the intake form. One form, not three emails asking for things one at a time.
Within 48 hours: the named contact sends one short personal message that is not about logistics.
Before the kickoff call: read the sales notes. Never ask a question they already answered while buying.

Six lines. Anyone can hold that in their head after reading it twice, which is the point.

2. Publishing a piece of work

The purpose is that quality does not depend on who happens to be doing it or how tired they are.

Draft finished, then left alone for at least two hours before anyone edits it.
Read once out loud. Anything you stumble over gets rewritten, no exceptions.
Every number in the piece checked against its original source, not against a summary of it.
Every link opened and confirmed to load.
Title, description and images completed before publishing, never after.
Published, then the link opened on a phone to confirm it renders.

Notice what this is doing. Each step is a thing that has gone wrong before. That is where an SOP should come from: past failures, not imagined ones.

3. Handing a task to someone else

The purpose is that delegation stops producing work you have to redo.

State the outcome, not the method. What does done look like.
Name the deadline and say what it is driven by, so they can judge trade-offs without asking.
Give one example of a good previous version. One is enough, three is a research project.
Say explicitly what they can decide alone and what needs checking.
Agree a single check-in point before the deadline, not at it.
Confirm back in writing, in their words, so any misunderstanding surfaces now rather than at the end.

Most delegation failure is a specification failure and it happens in the first five minutes. This procedure is entirely front-loaded for that reason.

The Format That Survives

The standard operating procedure examples above share a shape, and it is not an accident.

A page or less. If it is longer, it is two procedures pretending to be one. Atul Gawande made the same case from operating theatres in The Checklist Manifesto: the checklists that changed outcomes were short enough to run in about a minute.

Written by whoever currently does the task best, in their own words, ideally while doing it. A recording of someone narrating the job, transcribed and tidied, produces a better document in twenty minutes than a manager gets in an afternoon.

Verbs at the start of every line. “Send the welcome email” rather than “the welcome email should be sent”. Passive voice is how procedures become ambiguous about who acts.

Stored where the work is. Inside the template, pinned in the channel, at the top of the checklist. Not in a documentation library.

Dated, with an owner’s name. An undated procedure is untrustworthy within six months, and one with no owner will never be corrected.

Write Them at the Right Moment

Do not schedule a week of documenting processes. It produces volume and no adoption, because procedures written in the abstract describe an imagined version of the work.

Write one when something goes wrong. The bad handover, the missed step, the client who was annoyed by a thing that was avoidable. That is the moment when the specifics are clear, the motivation is real, and everyone agrees it is worth ten minutes.

Write one when you are about to hand a job over. The act of explaining it to someone is the act of writing the procedure, so capture it while you are already doing the work.

Do not write one for a task done twice a year. Just do it carefully.

This is the same principle as any system that has to hold up under pressure: it works because it is small enough to survive a bad day, which is the argument in building a system that survives a bad week.

What Good SOPs Are Really For

Not compliance. Not control. Two things.

They make the business less dependent on specific people, which is the difference between an asset and a job. A firm where the procedures live in three people’s heads cannot be sold, cannot scale, and cannot let those three people take a holiday. That is a valuation question as much as an operational one, and it is one of the first things a buyer probes, as covered in how to value a small business.

And they raise the floor rather than the ceiling. A procedure will not make your best work better. It makes your worst work acceptable, on the bad weeks, when someone is covering for someone else. Most reputational damage happens on those weeks, not on the good ones.

Start with one. The task you most recently had to redo because it was done wrong. One page, written by whoever does it, stored where it happens, today.

Procedures cover the decisions you can predict. For the ones you cannot, people need a vision that actually works: a rule that settles the tradeoff without you in the room.