What Is a Standard Operating Procedure?

A Standard Operating Procedure (SOP) is a documented, step-by-step description of how a specific task or process should be performed in your business. Done well, SOPs are one of the highest-leverage investments a growing SME can make — they reduce errors, ensure consistency, accelerate onboarding, and ultimately free the founder from being the only person who knows how things get done.

Done poorly, they sit in a shared folder and are never read. The difference lies in how they're written and embedded into your operations.

Why Most SOPs Fail

The most common reasons SOPs don't get used:

  • They're too long, written in dense paragraphs that no one wants to read.
  • They're written by managers who don't actually do the task day-to-day.
  • They're stored somewhere inconvenient or hard to search.
  • They're never updated and quickly become outdated.
  • There's no accountability for following them.

Which Processes Should You Document First?

Start where the pain is greatest. Prioritise processes that are:

  • High frequency — done daily or weekly.
  • High stakes — errors here are costly or damage client relationships.
  • Currently dependent on one person — single points of failure in your business.
  • Part of onboarding — tasks new team members need to learn quickly.

How to Write an Effective SOP

Step 1: Have the Person Who Does It Write the First Draft

The person who actually performs the task should document it — not just the manager or owner. They know the nuances, the shortcuts, and the common pitfalls. You can refine it, but start with their knowledge.

Step 2: Use a Consistent Template

A good SOP template includes:

  • Title and purpose: What this process is and why it matters.
  • Scope: When and to whom this procedure applies.
  • Roles: Who is responsible for each step.
  • Step-by-step instructions: Numbered, action-oriented, specific.
  • Resources/tools needed: Software, logins, templates referenced.
  • Version and review date: When it was last updated and when it should be reviewed.

Step 3: Use Visuals and Screenshots

For software-based processes, screenshots are worth a thousand words. Tools like Loom (for video SOPs) or Scribe (which auto-generates step-by-step guides from screen recordings) can dramatically reduce the time it takes to create and maintain SOPs.

Step 4: Test It With Someone Who Doesn't Know the Process

Before publishing, have someone unfamiliar with the task attempt to complete it using only your SOP. Where they get stuck or confused is where you need to add clarity. This is the single most valuable quality check.

Step 5: Store It Where People Actually Work

SOPs stored in rarely-visited folders are useless. Embed links in the tools where work happens — project management software, CRM systems, onboarding documents. The best SOP is the one that's one click away when someone needs it.

Keeping SOPs Current

Schedule a quarterly review of your SOP library. When processes change, update the document the same week — not later. Assign ownership of each SOP to a named individual who is responsible for its accuracy.

The Compounding Value of Documentation

Each SOP you write is a one-time investment that pays dividends every time the process runs. A business with well-documented processes is also significantly more attractive to investors and acquirers — it demonstrates that the business can operate independently of any single individual, including the founder.