Skip to content

How to build SOPs your team will actually use

You do not need a giant operations manual. Pick one process, watch it being done, write down the few things that matter, and test it with the people who do the work.

By Dillon Smith ·

Short answer: start with one process that goes wrong often or depends on one person. Watch someone do it, then write a one-page standard operating procedure (SOP) that names the owner, what triggers it, what you need, the steps, how to check quality, what to do when something is off, and when it will be reviewed. Train with it, test it, and fix it before writing the next one.

Why most SOPs go unused

SOPs usually fail for predictable reasons: they are written from memory by the owner, they are too long to use while working, they live somewhere nobody looks, and they are never updated once the process changes. The fix is not better formatting. It is a smaller scope and a better process for writing them.

Choose the first process

Pick one process that matches at least one of these:

  • It goes wrong often enough that you notice.
  • Only one person really knows how to do it.
  • A mistake affects a customer directly.
  • It is repeated daily or weekly.

Opening or closing routines, handling a new inquiry, booking changes, and end-of-day cash or reporting are common starting points. Avoid starting with the rarest, most complex thing you do.

Observe the work

Ask the person who does it best to walk you through it while actually doing it. Take notes on what they do, not what they say they do. Look for:

  • The small checks experienced people do without thinking.
  • The places where they make a judgment call.
  • The tools, logins, and supplies they reach for.

Define the parts that matter

A useful SOP answers seven questions:

  1. Owner — who is responsible for this being done and done well?
  2. Trigger — what starts it? A time, an event, a request?
  3. Inputs — what do you need before starting?
  4. Steps — the actions, in order, written as instructions.
  5. Quality check — how do you know it was done right?
  6. Exception path — what to do when something is missing or wrong, and who to tell.
  7. Review date — when someone will check it still matches reality.

Short SOP template

Copy and adapt:

FieldFill in
Process
Owner / backup
Trigger
You need
Steps1. … 2. … 3. …
Done right means
If something is wrong(and who to tell)
Next review

Fictional example: opening shift

This example is invented to show the format. It is not taken from a real business.

FieldExample
ProcessOpening shift
Owner / backupOpening lead / shift manager
TriggerScheduled opening time; arrive 30 minutes before
You needKeys, alarm code, opening checklist on the tablet
Steps1. Disarm alarm, switch on lights and equipment. 2. Check the day's bookings and note anything unusual. 3. Walk the customer area and fix anything out of place. 4. Confirm today's staff have arrived or messaged.
Done right meansDoors open on time, bookings reviewed, area customer-ready
If something is wrongEquipment fault or missing staff: message the shift manager before opening
Next reviewEnd of next quarter

Train and test it

Hand the SOP to someone who does not usually do the process and ask them to follow it while the experienced person watches. Every point where they hesitate is a gap in the document, not a failure by the person. Fix the SOP, then try again.

Keep it alive

Put SOPs where the work happens: a shared folder linked from the tool the team already uses, or a printed sheet at the station. When the process changes, the owner updates the SOP the same week. On the review date, ask the team whether it still matches what they do.

What to do next

One working SOP is worth more than a binder nobody opens. If you are not sure which process to start with, operations and SOPs is where Rally usually begins, and team development helps make sure the people using them know what they own.

Identify the first process worth documenting

Tell us where things are getting stuck and we will suggest a sensible place to start.

Talk to Rally

Dillon Smith

Founder, Rally

Dillon Smith is the founder of Rally, a marketing and operations partner for owner-operated businesses. Rally helps owners connect how they attract customers with how they follow up, deliver, and lead their team.

Related articles