From Chaos to SOPs: When to Write Things Down

Every business starts as chaos held together by two or three people who know how everything works. Then it grows, the two or three people get busier, and slowly the knowledge stops travelling. The person who knows how to fix the till is on holiday. The person who knows the supplier's email is in a meeting. The process that used to take an hour now takes a day because someone has to rediscover how it was done last time. Standard Operating Procedures, or SOPs, are the antidote. But writing one for everything is a waste of time, and writing none is a time bomb. Here is how to know when to write things down, and how to do it without drowning in documents.

1. What an SOP Actually Is

An SOP is a written, repeatable description of how to do a task correctly. It is not a policy, which tells you what you must achieve. It is not a strategy document, which tells you where you are going. An SOP is a recipe: do this, then this, then this, and the outcome will look like this. The best ones are short, written in plain language, and assume the reader has never done the task before. A good test: could a new hire follow it at 2 am without calling anyone? If yes, it is a real SOP. If no, it is a memo.

2. The Cost of Not Writing Things Down

The cost of missing procedures is invisible until it is huge. Every time a task depends on one person's memory, you have a single point of failure wearing a human face. That person gets sick, quits, or simply does it slightly differently every time, and the business wobbles. The classic symptom is the "quick question": your phone buzzes with the same five questions every week, asked by different people, because the answer exists nowhere but in your head. Multiply that by every task in the company and you are paying a knowledge tax on everything you do. Worse, you are paying it forever, because the questions never stop.

3. When to Write One: The Triggers

You do not need an SOP for everything, but you should write one when any of these is true. First, when the task is done regularly: anything weekly or more often deserves a written version, because the savings compound. Second, when the task is expensive to get wrong: a single mistake in payroll, compliance, or safety can cost more than a year of documentation effort. Third, when the task is complex enough that people forget steps: if it has more than five steps or takes more than an hour, write it down. Fourth, when someone asks you the same question twice: that is the cheapest possible signal that a procedure is missing. Fifth, when a task has legal or audit requirements: if you must prove how something was done, an SOP is your proof.

4. When Not to Bother

Writing an SOP is also a way to waste time, and you should be honest about it. Do not write one for a task that changes every week, because the document will be wrong before it is printed. Do not write one for a task done once a year by the same person, unless it is expensive to get wrong. And do not write one just because it feels productive. Documentation is a maintenance burden: every SOP you create must be reviewed, updated, and eventually deleted when the process dies. A shelf of outdated procedures is worse than none, because people learn to ignore all documents, even the current ones. Start with the five triggers above and ignore the rest.

5. How to Write an SOP People Actually Use

Most SOPs fail because they are written like essays. Yours should be written like a recipe. Start with the outcome and the tools needed. Then list the steps in order, one action per line, in the present tense: open the app, select the month, click export. Add screenshots or photos where a step is hard to describe, because a picture survives translation better than prose. Keep it under one page whenever possible; if it is longer, split it. End with the most common mistakes and what to do when something goes wrong. Then, and this is the step everyone skips, test it: hand it to someone who has never done the task and watch them follow it. The places they stumble are the places your document is lying to you.

6. Keep Them Alive

An SOP that is not reviewed is a liability. Assign each document an owner and a review date, and treat the review like any other recurring task: once a quarter for fast-changing processes, once a year for stable ones. When a procedure changes, update the document the same day, not next month. Keep versions simple: one current version, no folders of old drafts. And store everything in one obvious place, a shared drive folder or a wiki, so the answer to "where is the procedure" is always the same. The moment documents live in five places, they live in none.

The Bottom Line

Procedures exist to make the business work without you. Write them when the task is regular, expensive to get wrong, complex, or repeatedly asked about. Write them like recipes, test them on fresh eyes, and review them on a schedule. The goal is not a beautiful library of documents. The goal is that the fifth question stops coming, the new hire stops calling at 2 am, and the knowledge that lives in people's heads starts living in the company. Chaos is free, but it is not cheap.