Why most SOPs go unused
SOPs fail when they are written by someone who does not do the work, run to 30 pages, or describe a process that no longer exists. People go back to asking the one colleague who knows.
We write SOPs from walkthroughs with the people who run the process, test them against real transactions, and keep each one short enough to use at the desk.
What every NeX SOP contains
| Section | What it covers |
|---|---|
| Header | SOP number, title, owner, version and effective date |
| Purpose and scope | What the SOP covers and what it does not |
| Trigger | The event that starts the process |
| Roles | Who does, approves and reviews each step (from the RACI) |
| Steps | Numbered steps, each with the system screen or form used |
| Controls | Approvals, checks and reconciliations, marked clearly |
| Records | What evidence is kept and where |
| Exceptions | What to do when something does not fit |
| Change log | Version history and approver |
Typical SOP packs
- Finance: purchase to payment, sales invoicing, collections, bank reconciliation, month-end close, fixed assets, TDS and GST compliance.
- Operations: goods receipt, stock transfers, cycle counts, dispatch, returns.
- People: onboarding, attendance and leave, payroll inputs, salary revisions, exits.
SOPs are part of the Document stage of our 5D method. Read our guide on how to write an SOP.
Frequently asked questions
What should an SOP include?
Do you write SOPs from scratch or improve our existing ones?
What format do you deliver SOPs in?
How much does an SOP Pack cost and how long does it take?
How many SOPs does a growing company need?
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.