Home›PathPilot›Resources›State of SOP Management 2026
GuideAxonave · 2026

The State of SOP Management 2026

Where SOP programs usually break down, what the teams whose SOPs actually get used do differently, and a ten-question check you can run on your own. A guide, not a survey: there are no percentages here, because we haven’t run a study that would back any.

By Axonave team·Published January 2026·Updated November 2026·~9 min read

The six problems this guide covers

Coverage
SOPs exist for the processes someone chose to write up, not always the ones that matter most.
Findability
The document exists, but nobody can find it in the minute they need it.
Freshness
The process changed and the SOP didn’t, so staff stop trusting it.
Format
A long document for a branching decision. People skip it and ask a colleague.
Ownership
Owned by “the team”, which in practice means nobody.
Measurement
Nobody can tell whether an SOP is followed, so nobody knows which one to fix.

Introduction

Standard operating procedures are how operations, support and IT teams stay consistent as they grow. Yet the gap between a team’s SOP plan and what happens on the floor is often wide: documents that are hard to find, processes that change without anyone updating the SOP, and staff who have quietly stopped opening SOPs because they’ve learned not to trust them.

This guide walks through the patterns behind that gap, what the teams with working SOP programs do instead, and where each function should start. It ends with ten questions you can answer about your own SOPs in an afternoon.

There are no survey numbers in it. A benchmark with no study behind it would only tell you how you compare with nobody. Your own numbers are the ones that matter, and the check at the end shows where to find them.

Five patterns behind SOPs that don’t get used

1

Coverage follows whoever had time, not where the risk is

Most SOP libraries grow one document at a time, when someone has a quiet week or an audit is coming. The result is selective documentation: thorough for some departments, nearly absent for others, and rarely matched to where an error costs the most. Start from a list of processes ranked by how often they run and what a mistake costs, and write the top of that list first.

2

SOPs fail at the moment of need

When an SOP isn’t followed, the cause is often not the writing. The person who needed it couldn’t find it in time. Documents kept in general-purpose tools like Confluence or Notion tend to collect in project spaces instead of one searchable library, so the SOP exists but is invisible at the point of use. Put SOPs where the work happens: a link in the helpdesk macro, a QR code on the machine, a pinned link in the team channel.

3

Format decides whether a procedure gets followed

The same procedure can be followed or ignored depending on how it’s presented. A long PDF asks the reader to find their place, skip what doesn’t apply and remember the exceptions. A step-by-step or branching format shows one decision at a time. Match the format to the process: a short list for simple, uniform tasks, a decision tree where the right step depends on the situation.

4

Ownership is vague

In many teams an SOP is owned by “the team”, which in practice means nobody. When the process changes, the person making the change rarely updates the document, and the gap between the written and the actual procedure grows month by month. Name one person per SOP, and make “update the SOP” part of the change itself, not a follow-up task.

5

Nobody measures whether SOPs are used

Most teams can say how many SOPs they have. Few can say which ones are opened, finished or abandoned halfway. Without that, the library grows but doesn’t get better. Even a rough signal helps: views a month, completions, and the step where people stop.

Where to start, by function

Each function has a few processes that pay back first when they’re written down. These are the usual starting points, and why.

IT Support

Incident runbooks and access requests

An error shows up fast and costs downtime.

Operations

Hand-offs between teams

The steps between departments are the ones nobody owns.

Customer Support

Escalations and refunds

An inconsistent answer reaches the customer directly.

Finance & Compliance

Month-end close and approvals

Auditors ask for evidence that the steps were followed.

HR

Onboarding, leave and offboarding

Each runs rarely for any one person, so nobody remembers the steps.

What teams with working SOP programs do

The teams whose SOPs get used tend to share a handful of habits. None of them is a software feature; any team can adopt them.

Named ownership for every SOP

Each SOP has a single named owner responsible for keeping it current — not "the team" or "the manager." This person is told when the underlying process changes.

SOPs are accessible at point of use

They put SOPs in the tools where work happens (the helpdesk, the HR system, the ticketing system) instead of making staff go and look in a separate wiki.

Format matches the audience

Linear step lists for simple, low-variance procedures. Branching decision trees for complex, situation-dependent processes. The format is chosen on purpose, not by default.

Compliance is observable

They use tools that show how often SOPs are opened, where staff drop off, and which procedures are abandoned most. That turns SOPs from static documents into something you can improve.

Update triggers are documented

The process for updating SOPs is itself written down: who is told when a related policy changes, what review is needed before publishing, and who approves the change.

The most common SOP failure patterns

The phantom SOP

The SOP exists in a document somewhere, but no current team member knows where it is or whether it's accurate. Many processes end up here once the original author leaves the team.

The encyclopaedia SOP

Documents that contain every possible piece of context, background, and exception in a single file. Too long to read at point of use, staff quickly learn to skip them and rely on colleagues instead.

The first-draft SOP

An SOP written once and never updated. The process has evolved in practice, but the document still reflects how things worked eighteen months ago. Staff follow the outdated document or quietly ignore it.

The aspirational SOP

Documents that describe how the process should ideally work, not how it actually works. Often written during an audit or compliance review, these SOPs create a documented fiction that diverges from reality.

Check your own SOPs: ten questions

Answer yes or no for your team. Each “no” points at one of the patterns above, and the first one on the list is usually the place to start.

  1. 1Is there a list of your critical processes, ranked by how often they run and what a mistake costs?
  2. 2Does each process on that list have a written SOP?
  3. 3Can someone find the right SOP in under a minute, from where they’re working?
  4. 4Does every SOP have one named owner?
  5. 5Is “update the SOP” part of changing the process?
  6. 6Has each SOP been checked against how the work is done today since the process last changed?
  7. 7Do processes with decisions in them use a branching format, not a long document?
  8. 8Does each SOP cover the exceptions people actually hit, not only the normal case?
  9. 9Can you see whether people open and finish each SOP?
  10. 10When someone stops partway, can you see which step?

About this guide

Written by the Axonave team, who build PathPilot. It isn’t based on a survey or a sample, so it quotes no percentages and no benchmarks. First published in January 2026 and rewritten as a guide in November 2026.

Frequently asked questions

Which processes should an SOP program cover first?

The ones that run often and where a mistake is expensive: escalations, month-end close, incident response, onboarding. Rank your processes by those two things and write the top of the list first, instead of documenting whatever someone has time for.

Why don’t people follow SOPs?

Usually because they can’t find the SOP when they need it, they don’t trust it to be current, or it’s too long to use in the middle of a task. Fixing where the SOP lives and who keeps it current tends to matter more than polishing the writing.

How often should SOPs be updated?

Whenever the process changes. A calendar review (quarterly for busy procedures, yearly for stable ones) catches the changes nobody flagged. It backs up updating at the time; it doesn’t replace it.

What tools do teams use to manage SOPs?

Most teams start in shared documents: Google Docs, Notion, Confluence or PDFs on a shared drive. Dedicated SOP software adds what documents lack: step-by-step or branching formats, version history, and analytics on whether each SOP is opened and finished.

How can I tell whether my SOPs are being followed?

Start with what you can see today. If the SOP is a document, you usually know only that it was opened. An interactive SOP in a tool like PathPilot shows views, completions and the step where people leave, so you can find the step that needs fixing.

Fix your SOP discoverability problem

PathPilot turns static SOP documents into interactive flows your team can find and follow — with analytics to see where they drop off.

Start building free