How to document a process step by step (an SOP)

Picture not being able to come in tomorrow. Would anyone else know exactly how the register is closed, how an appointment is confirmed, or how an upset customer should be handled? If the answer is "only I know how," you have a problem that stays invisible until it turns urgent. The fix is called an SOP: a standard operating procedure, which is nothing more than a written recipe for how a task gets done, step by step, the same way every time.

This is not bureaucracy. It is the difference between a business that depends on your memory and one that runs whether you are there or not. A good SOP trains faster, cuts errors, and lets you stop explaining the same thing twenty times. Here is how to write one people will actually use.

What an SOP is and what it is for

An SOP is a document that lays out the steps needed to complete a specific task consistently. The key word is consistently: the goal is the same result no matter who does it or what day it is. It is for tasks that repeat and where a mistake costs something: taking payment, scheduling, serving, dispatching, onboarding a new client.

The practical rule is simple. If you do a task often, if someone new keeps asking how it is done, or if a mistake on it costs you money or reputation, that task deserves an SOP. Do not document everything; document what hurts when it goes wrong.

The parts that cannot be missing

Procedure-writing guides agree on a basic structure. You will not need every section for a simple task, but it helps to know them.

• Header: a clear title, a document number or code, and a version, so you always know which copy is current.
• Purpose: in one or two sentences, what this procedure achieves and why it exists.
• Scope: who and what situations it applies to, and which it does not.
• Definitions: clarify terms or abbreviations a newcomer might not know.
• Roles and responsibilities: who does what within the procedure.
• The steps: the heart of the document, only the steps needed to reach the objective, in order.

For a small business, title, purpose, and steps are often enough. The rest gets added as the team grows or as the task gets more delicate.

Pick a format that fits the complexity

Not every process is written the same way. Writing guides describe three main formats, and choosing well saves confusion.

• Simple steps: a numbered list with short sentences. Ideal for routine, straightforward tasks, like closing the register at the end of the day.
• Hierarchical steps: main steps with sub-steps underneath. Useful when there are decisions or detail inside each step.
• Flowchart: when the process branches depending on what happens. Good for situations with several possible outcomes, like handling a complaint based on the reason.

One formatting tip every source repeats: avoid long, dense paragraphs. Lists and numbered steps focus attention and slow the reader down, which is exactly what you want when someone is following instructions.

How to write it without overcomplicating

Before writing, truly understand the process. The best way is not to sit and imagine it; it is to watch how it is done today. Observe whoever performs it, note every real step (including the ones nobody mentions because they are taken for granted), and ask where people get stuck. That is where the steps you would have forgotten are hiding.

Then write in the imperative, speaking to whoever will do the task: "Open the register," "Confirm the customer's name," "Send the message." One verb per step. If a step has three actions, it is probably three steps. And always name a document owner by role, not by person: "the shift lead," not "Maria," because Maria leaves someday and the role stays.

A process that lives only in your head is not a business asset; it is a risk that walks out the door with you every time you leave.

Test it before calling it done

A freshly written SOP is almost never complete. That is why you test it with two kinds of readers, as the guides recommend. First, someone who already does the task: they will catch missing steps or wrong details. Second, someone who has never done it: they will find the confusing or ambiguous parts, because they have to follow your words literally without filling gaps from experience.

If the new person can complete the task using only the document, it works. If they get stuck and ask you, that exact spot needs more clarity. Fix it and test again.

Keep it alive or it is useless

The most common mistake is not writing an SOP badly: it is writing it once and forgetting it. Processes change, and an outdated procedure is worse than none because it creates false confidence. So every SOP needs an owner by role responsible for keeping it current and a periodic review, even every six months, to confirm it still matches reality.

Technology helps here: if an assistant like Lidia answers and books over WhatsApp, the "how an appointment gets booked" SOP should also describe what the assistant does and where a person takes over, so the human and the automated hand follow the same script.

Takeaway

Start with a single task: the one that interrupts you most or causes the most errors. Watch it, write it in short imperative steps, test it with someone who does not know it, and give it an owner who keeps it current. An SOP is not made to be filed in a folder; it is made so your business keeps running without leaning on your memory. The first one costs an afternoon. The tenth gives you back your weeks.

Sources

• The FDA Group — https://www.thefdagroup.com/blog/a-basic-guide-to-writing-effective-standard-operating-procedures-sops
• Smartsheet — https://www.smartsheet.com/content/standard-operating-procedures-manual
• Lucidchart Blog — https://www.lucidchart.com/blog/how-to-write-a-standard-operating-procedure
• Penn State Extension — https://extension.psu.edu/standard-operating-procedures-a-writing-guide
• Atlassian (Loom) — https://www.atlassian.com/blog/loom/how-to-write-an-sop