SOP & Process Documentation

What is SOP and process documentation?

Standard operating procedures (SOPs) describe how a business does things: step by step, who does what, which systems are used, and what checks apply. Process documentation maps how work flows across teams — from receiving an order to collecting cash, or from hiring someone to paying them.

Most growing businesses run on the knowledge in a few people's heads. Documenting processes makes the business consistent, trainable, auditable, and less dependent on any one person.

The key terms

What good documentation includes:

Process map

A visual flow of a process from start to end, across teams and systems.

SOP

Step-by-step instructions for a specific task, written for the person doing it.

Roles and responsibilities

Who performs, reviews, and approves each step.

Controls

The checks built into the process, like approvals and reconciliations.

Inputs and outputs

What each step needs and produces — documents, data, approvals.

Exceptions

What to do when things don't follow the normal path.

Version control

Keeping track of changes, so everyone uses the current version.

Why it matters

Documented processes pay off in several ways:

Less key-person risk

The business doesn't stall when someone is away or leaves.

Consistency

Work is done the same way every time, reducing errors.

Faster onboarding

New team members learn from documents, not just shadowing.

Audit and IFC support

Auditors rely on documented processes and controls.

Scaling

Processes can be replicated across new locations or teams.

Improvement

You can only improve a process you can see.

Outsourcing and automation

Documented processes are easier to outsource or automate.

Who is this for?

Documentation should reflect how work is actually done, not an idealised version nobody follows.

Documentation formats

Different formats for different needs:

What we'll need from you

Process owners

Access to the people who do the work.

System walkthroughs

Demonstrations of how systems are used.

Existing documents

Any current procedures, templates, or policies.

Priority processes

Which processes matter most to document first.

Control requirements

Audit or IFC points that need to be reflected.

Format preferences

Where documents will live and in what format.

Engagements are quoted by the number of processes documented.

How we document processes

Our approach:

1. 1

   Prioritise

   We agree which processes to document first, usually the highest-risk or most people-dependent.

2. 2

   Walk through

   Each process is walked through with the people who perform it.

3. 3

   Map

   Process maps show the flow, roles, and systems.

4. 4

   Write SOPs

   Step-by-step SOPs are written, with controls and exceptions.

5. 5

   Review

   Documents are reviewed with process owners for accuracy.

6. 6

   Roll out

   Documents are published, and the team trained.

Keeping documentation current

Documentation goes stale unless maintained:

Owners

Assign an owner to each document.

Review cycle

Review documents at least annually.

Update on change

Update when systems, people, or rules change.

Central location

Keep documents in one accessible place.

Version history

Track changes and approvals.

Use in training

Make documents part of onboarding.

Benefits and responsibilities