Standard operating procedures people actually use

A standard operating procedure, or SOP, describes how a task should be done. In many organisations the SOP manual is a thick document written for an audit and never opened again. The goal is the opposite: short, practical guidance people reach for in the moment.

Choose which tasks need one

You do not need a procedure for everything. Start with tasks that are:

• Repeated often, so consistency saves time.
• Risky, where a mistake affects safety, money or reputation.
• Often done wrong, or done differently by different people.
• Hard to hand over, where knowledge lives in one person's head.

Write for the person doing the job

Keep it to a page where you can. Use short numbered steps that start with a verb. Say who does it, what they need before they start, what "done" looks like and what to do if something goes wrong. Use photos or screenshots where words are clumsy.

Write it with the team

The people who do the task know where the real difficulties are. Sit with them, watch the work, and draft the steps together. Procedures written in an office without that input tend to describe an ideal version of the work that nobody follows.

Test it with a newcomer

Hand the draft to someone who has not done the task before and watch them follow it. Where they hesitate, the procedure is unclear. Fix those points. This is the cheapest and most effective check you can do.

Make it easy to find

A procedure no one can find does not exist. Keep them in one place, searchable, and accessible on a phone for field teams. Use clear names such as "Handling a water leak in a unit", not codes.

Give each procedure an owner

One named person is responsible for keeping it correct. Put the date of the last review on the page. Review at least once a year, and whenever something changes or goes wrong.

Use them in training and in reviews

New staff should learn from the procedures and be assessed against them. After an incident, look at whether the procedure was followed, and whether it needs to change. That turns a document into part of how the team improves.

Keep the tone helpful

Procedures are there to help people do good work, not to catch them out. When the team sees that, they contribute to improving them.