Writing standard operating procedures (SOPs) that people actually follow

A standard operating procedure (SOP) is a written description of how a recurring task is done in your business, step by step, so that anyone who has been trained can do it the same way. People follow SOPs that are short, written with the people who actually do the work, kept where the work happens and updated when the work changes. They ignore SOPs that are long, vague, written to impress an inspector or stored in a file nobody opens.

What an SOP is, and what it is not

An SOP covers one task with a clear start and finish: packing an order, opening the shop, closing the cash, onboarding a new client, cleaning a machine. It is not a policy, which states a rule such as who may approve a refund. It is not a job description, which lists a person's responsibilities. A policy says what must happen; an SOP says how it happens.

Good candidates for your first SOPs:

• Tasks done often, by more than one person.
• Tasks where a mistake is costly or upsets customers.
• Tasks only one person knows, which would stall if that person were away.

Why SOPs get ignored

• Written from memory by the owner, not with the person who does the job, so the steps do not match reality.
• Too long. If a task takes five minutes, its SOP should be readable in about one.
• Vague words such as "properly" and "carefully", which mean different things to different people.
• Hidden away in a cupboard or a forgotten folder.
• Never updated. Staff learn the "real way" from each other, and the document turns into fiction.

The parts of a useful SOP

Use the same short layout for every procedure, so people always know where to look:

• Title and purpose: one line on what the task is and why it matters.
• Who and when: the role, what triggers the task, and how often.
• What you need: tools, logins, materials.
• Steps: numbered, one action per step, each starting with a verb.
• Checks: what "done correctly" looks like, ideally something you can see.
• If something goes wrong: what to do, and whom to call.
• Owner and last review date, so people know it is current.

Writing one, step by step

1. Watch the task being done by the person who does it best. Note each step as they work, or record it on a phone.
2. Draft it in their words, in the language the team uses every day. In many Bangladeshi workplaces that means Bangla, with English labels only where the software shows English menus.
3. Cut every word that does not change what someone does.
4. Replace vague words with visible checks. Not "pack carefully" but "wrap each glass item separately; when you shake the box gently, nothing should move."
5. Test it with someone new. Ask them to follow it without help, and note every question they ask. Each question shows a gap.
6. Fix it, publish it and train people on it. Put it where the work happens.
7. Review it on a fixed schedule, and whenever a mistake reveals a gap.

Choosing a format

Mixing formats is fine. Many teams keep a short written checklist and link it to a video for training.

Keeping SOPs alive

Give every SOP an owner who keeps it current. Store all of them in one shared place that opens easily on a phone, since many of your staff may never sit at a computer. Mention SOPs when you train, when you review mistakes and when you praise good work, so they become part of how the business talks.

Once you have a solid set, an internal AI assistant that answers staff questions from your own SOPs can help people find the right step quickly. A person still owns the content and approves every change.

SOPs also make delegation and training much easier, and they are the foundation of a sales process that does not depend on the owner.

Start with one

Choose the task that causes the most repeated mistakes. Watch it, write it, test it with someone new and put it where the work happens, all this week. Then move on to the next one. If you want help documenting your key processes, that is part of my business development work.