Home / SOPs & Documentation
01 · SOPs & Documentation

What Is a Standard Operating Procedure (and What It Isn't)

The Ops Manual · Updated 2026-07-18

A standard operating procedure is the written, agreed way a recurring task gets done in your business. Not the way the owner does it on a good day, not the way the newest hire guessed it should be done — the way the business has decided it is done, captured somewhere everyone can find it.

That's the whole idea. Everything else — formats, templates, software — is decoration on top of that one decision: this task has one right way, and we wrote it down.

The working definition

A useful SOP has three properties:

  • It's for a recurring task. One-off projects get plans, not procedures. If the task won't happen again in roughly the same shape, an SOP is wasted effort.
  • It's executable by someone other than the author. The test of an SOP is whether a competent person who has never done the task can follow it to an acceptable result without asking questions.
  • It's owned. Someone is responsible for keeping it true. An SOP nobody owns quietly rots until it's more dangerous than no SOP at all.
If the answer lives only in someone's head, the business doesn't own the process — the person does.

What an SOP isn't

Plenty of documents get called SOPs without earning the name:

  • A policy. Policies say what the business will and won't do ("we back up client data"). Procedures say how, step by step, with the actual button clicks and file names. You need both; they're different documents.
  • A training manual. Training explains why and builds skill. An SOP assumes basic competence and gets a specific task done. Mixing them produces twelve-page documents nobody opens on a busy Tuesday.
  • A checklist. A checklist is the memory-jogging summary of a procedure, useful once someone already knows the work. Checklists are often the most-used artefact of an SOP — but on their own they can't onboard anyone.
  • A flowchart on the wall. Diagrams help people see a process, but a diagram without the written steps behind it is a poster, not a procedure.
Common failure: writing "SOPs" that are really vague policies ("handle complaints promptly and professionally"). If a new starter can't act on it without asking a question, it isn't a procedure yet.

When an SOP pays off — and when it doesn't

Write an SOP when a task is done repeatedly, done by (or handed to) more than one person, or carries real consequences when done wrong — invoicing, onboarding a client, closing up a site, granting and removing system access. The moment you hire, subcontract or delegate, SOPs stop being optional paperwork and become the mechanism that makes delegation possible.

Skip the SOP when the task is genuinely one-off, still changing week to week, or trivially obvious. Documenting an unstable process locks in the wrong version of it; let a process settle before you formalise it.

In practice: most Australian small businesses need fewer, better SOPs than they think — usually ten to twenty covering money, customers, staff and security — not a wiki with three hundred stubs. Start with the tasks that would hurt most if the person who does them was away for a month.

FAQ

How is an SOP different from a work instruction?

In large organisations, procedures describe a whole process and work instructions zoom into one step. In a small business the distinction rarely earns its keep — call everything an SOP and keep each one scoped to a single task.

Do SOPs have legal weight?

They can matter in disputes, workplace safety and employment contexts because they show what the business's standard practice was. For obligations around employment records, safety and privacy, check the Fair Work Ombudsman, your state's work health and safety regulator and business.gov.au rather than assuming a written SOP alone covers you.

Official sources