Guide · Process

How to write an SOP people will actually follow

Quick answer

To write an SOP people follow, walk through the process with the person who does it, then write short numbered steps that each name the role, the action and the system screen. Add the trigger, the controls and approvals, the records kept and what to do with exceptions. Keep it to two or three pages, give it an owner and a version number, and review it at least once a year.

TopicsProcess design & SOPs

Last reviewed by the NeX team: 29 September 2026

The nine sections of a good SOP

SectionWhat to write
1. HeaderSOP number, title, owner, version, effective date
2. PurposeOne or two sentences on why the process exists
3. ScopeWhat the SOP covers and what it does not
4. TriggerThe event that starts the process
5. RolesWho does, approves, is consulted and informed (from the RACI)
6. StepsNumbered actions with role and system screen
7. ControlsApprovals, checks and reconciliations, clearly marked
8. RecordsWhat evidence is kept and where
9. Exceptions and change logWhat to do when it does not fit; version history

A worked example: vendor bill processing

  1. Accounts executive receives the vendor bill by email and saves it to the bills inbox.
  2. Accounts executive matches the bill to the purchase order and goods receipt in the accounting system.
  3. Control: if quantity or price differs by more than the agreed tolerance, the bill is placed on hold and the buyer is informed.
  4. Accounts executive records the bill with the correct tax and TDS section.
  5. Finance manager approves bills in line with the delegation of authority.
  6. Accounts executive schedules the bill in the next weekly payment run.

Common mistakes

  • Writing the process as people wish it ran, without walking through it.
  • Describing menus instead of decisions.
  • No owner, so nobody updates it.
  • Burying the controls in paragraphs.
  • One giant document for the whole finance function.

Want SOPs written for you? See SOP documentation.

Frequently asked questions

How long should an SOP be?
Usually two to three pages. If it runs longer, split it into separate SOPs for each sub-process.
What is the difference between a policy and an SOP?
A policy states the rule, such as who can approve purchases up to what value. An SOP states the steps to follow the rule in practice.
How often should SOPs be reviewed?
At least once a year, and whenever the process, the system or the organisation changes.

General information only, not legal, tax or software licensing advice. Zoho features, editions and prices change, so confirm the current position with Zoho or with our team before you commit. See our disclaimer.

Which process slows you down most?

Book a free 30-minute process review. We will walk through one workflow with you and tell you whether it needs a fix, a system, or both.

WhatsApp us