Process design

SOP documentation

Quick answer

NeX writes standard operating procedures (SOPs) that people actually follow: short, step-by-step, with a named owner for each step, the approval or check that applies, and the system screen where it happens. SOPs are delivered in a consistent numbered format with version control, either platform-neutral or mapped to your Zoho setup.

Last reviewed by the NeX team: 29 September 2026

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

SectionWhat it covers
HeaderSOP number, title, owner, version and effective date
Purpose and scopeWhat the SOP covers and what it does not
TriggerThe event that starts the process
RolesWho does, approves and reviews each step (from the RACI)
StepsNumbered steps, each with the system screen or form used
ControlsApprovals, checks and reconciliations, marked clearly
RecordsWhat evidence is kept and where
ExceptionsWhat to do when something does not fit
Change logVersion 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?
Purpose and scope, the trigger that starts the process, roles, the numbered steps, the controls and approvals, the records produced, exceptions, and a version history. Our guide on how to write an SOP explains each part.
Do you write SOPs from scratch or improve our existing ones?
Both. Where SOPs exist we test them against how work really happens, then rewrite or fill the gaps. Where they do not, we write them from the process design.
What format do you deliver SOPs in?
Editable documents in the format your team is comfortable with, most often Word or PowerPoint, with a process map for each SOP and a master index. We can also publish them to an internal knowledge base.
How much does an SOP Pack cost and how long does it take?
An SOP Pack starts at ₹60,000 (SGD 800) per process and takes 3 to 4 days per process. These are starting prices. The actual fee depends on scope and is agreed case by case before work starts.
How many SOPs does a growing company need?
Usually 15 to 40 across finance, procurement, sales, inventory and HR, depending on size and complexity. We start with the processes that carry the most transactions and risk.

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