To write SOPs for a small business, start with the three to five processes where a mistake costs you money or where only one person knows how the job is done. Have the person who actually does the job write the steps, not the owner, on a single page in plain language. Then test it by having someone else follow it, translate it into Gujarati or Hindi if that’s what your team reads, and attach it to a daily or recurring task so it gets used instead of filed.
That’s the whole method. Below is how to do each step, a one-page SOP template you can copy, a filled-in example for dispatching an order, and the habits that keep SOPs alive in a growing Indian business.
What an SOP is, and what it isn’t
A standard operating procedure (SOP) is a short written description of how a recurring job is done in your business: who does it, what starts it, the steps, and what “done” looks like. It exists so the job is done the same way whether it’s your senior storekeeper or last month’s new joiner doing it, and whether you are in the office or not.
An SOP is not:
- A 40-page quality manual written for an auditor and never opened again.
- A list of rules (“Staff must be punctual”).
- A job description.
Which processes to document first
You don’t need fifty SOPs. You need the right five. Score each recurring process from 1 (low) to 3 (high) on three questions:
| Process | How often it happens | Cost of a mistake | Depends on one person? | Total |
|---|---|---|---|---|
| Dispatching an order | 3 | 3 | 2 | 8 |
| Preparing a quotation | 3 | 2 | 3 | 8 |
| Attending a service call | 3 | 2 | 2 | 7 |
| Monthly attendance and salary | 1 | 3 | 3 | 7 |
| Receiving material at the gate | 3 | 2 | 1 | 6 |
| Onboarding a new employee | 1 | 1 | 2 | 4 |
These scores are illustrative. Fill in your own.
Start with the top scorers. In most trading, manufacturing and service businesses, they turn out to be the processes where money changes hands or goods leave the premises: quotations, order processing, dispatch, receiving, service visits, billing and salary. A simple rule of thumb: if you get an angry phone call when it goes wrong, it needs an SOP.
Who should write the SOP
The person who does the job every day should write it. Not the owner, not an outside consultant, not the IT person.
Owners describe how the job should be done. The person doing it knows how it is actually done, including the workarounds and the step that always gets skipped. This method works even for staff who don’t enjoy writing:
- Record it. The person does the job once while a colleague records a phone video or voice note of them explaining each step, in whatever language they’re comfortable with.
- Write it down. Someone who writes clearly, such as an office assistant or supervisor, turns the recording into the one-page format below.
- Review it together. The doer, their supervisor and, briefly, the owner read it and correct anything wrong or missing.
- Test it. Someone who has never done the job follows the SOP while the doer watches without helping. Every place they get stuck is a gap in the SOP.
- Sign off and date it. Mark it version 1.0, with the date and the name of the person responsible for keeping it current.
For most processes this takes an hour or two.
The one-page SOP template
Copy this. If your SOP doesn’t fit on one page, you’re describing two processes; split it.
| Field | What to write |
|---|---|
| SOP title | Verb plus object, e.g. “Dispatching a customer order” |
| SOP no. and version | e.g. DSP-01, v1.0 |
| Process owner | The role responsible, not only a person’s name |
| Trigger | What starts this process |
| Inputs needed | Documents, data or material needed before starting |
| Steps | 5 to 12 numbered steps, each starting with a verb |
| Done means | How anyone can check it was done correctly |
| Records kept | What proof is saved, and where |
| If something goes wrong | Who to call, and what not to do |
| Last reviewed | Date and name |
Write steps the way you’d explain them to a sharp new joiner on day one. One action per step. Use the names your team actually uses (“the blue file”, “Tally”, “the dispatch group”) rather than formal terms nobody says out loud.
Example: an SOP for dispatching an order
Here is a filled-in example for an illustrative 30-person engineering components trader. Your steps will differ; use it as a model, not a copy.
- SOP title: Dispatching a customer order
- SOP no.: DSP-01, v1.0
- Process owner: Dispatch in-charge
- Trigger: Sales order marked “ready to dispatch” by stores
- Inputs needed: Sales order, packing list, customer’s GSTIN and delivery address, transporter details
Steps:
- Check the material on the dispatch table against the sales order: item code, quantity, grade. If anything doesn’t match, stop and inform sales.
- Pack as per the customer’s packing instructions. Label each box with the order number and box count (Box 1 of 3).
- Photograph the packed material with the labels visible.
- Ask accounts to raise the tax invoice and, where applicable, the e-invoice and e-way bill. Don’t load until the invoice is in hand.
- Confirm the transporter, vehicle number and driver’s mobile number.
- Load the vehicle and count boxes against the packing list in front of the driver.
- Record the LR (lorry receipt) or docket number and take the driver’s signature in the dispatch register.
- Send the customer the invoice copy, LR number, vehicle number and expected delivery date on WhatsApp or email.
- Update the order status to “Dispatched” and file the photos and LR copy in the order folder.
- Done means: The customer has the invoice, LR number and photos; the order shows “Dispatched”; the dispatch register is signed.
- Records kept: Photos, invoice copy and LR copy, in the order folder.
- If something goes wrong: Shortage or damage before loading: stop and inform the sales head. Transporter delay: inform the customer the same day.
- Last reviewed: 07-10-2026, Dispatch in-charge
Notice what isn’t there: no paragraph on “the importance of timely dispatch”. Every line is something someone does or checks.
Checklists vs SOPs: which do you need?
- An SOP explains a process from start to finish. You use it to train someone and to settle “how are we supposed to do this?”
- A checklist is the short version used every single time the job is done: a tick-box list of the critical steps, usually five to ten items.
Most processes need both: the SOP for training, the checklist for daily use. The dispatch SOP above becomes this checklist:
- Material matched to order (code, quantity, grade)
- Packed and labelled (order no., box x of y)
- Photo of packed material taken
- Invoice (and e-way bill, if applicable) in hand
- Boxes counted in front of the driver
- LR number recorded
- Customer sent invoice and LR details
- Order status updated
Making SOPs stick
Writing SOPs is the easy part. Most die in a file within weeks. These habits keep them alive.
Write them in the language your team reads
If your dispatch staff or technicians read Gujarati or Hindi more comfortably than English, give them a Gujarati or Hindi version. Have a bilingual colleague translate it, then ask someone from the team to read it back so you know it means what you intended. Keep technical words like item codes, “e-way bill” and “LR” in the form people actually use, even if that’s English.
Train with the SOP, not around it
A new joiner first watches the job with the SOP in hand, then does it while being watched, then signs the SOP to confirm they’ve been trained. Keep that signed record.
Put it where the work happens
A laminated copy at the dispatch table. The PDF pinned in the team’s WhatsApp group. A QR code on the machine that opens the SOP on a phone.
Link it to the daily task
This is the habit that matters most. The checklist becomes part of the task itself: the dispatch isn’t “done” until the checklist is ticked and the photo is attached. On paper, that’s a checklist stapled to every order file. In software, it’s a task template.
Audit lightly, and review twice a year
Once a month, the supervisor picks three random completed jobs and checks them against the SOP. The aim isn’t to catch people; it’s to find where the SOP and reality have drifted apart. Every six months, or whenever the process changes (a new transporter, a new compliance requirement, a new machine), the process owner updates the SOP and bumps the version. For many Gujarat businesses, the week after the Diwali shutdown is a natural moment to do this.
How Stagewise ERP turns SOPs into tasks people actually follow
Linking the SOP to the daily task is where most small businesses stall, because paper checklists get lost and WhatsApp reminders get ignored. That’s the gap Task & Ticketing in Stagewise ERP is built for:
- Task templates with checklists. Your SOP’s checklist becomes a task template, so every time the job comes up, the task carries the same checklist and you can see what’s done and what’s left.
- Recurring tasks for routine work such as weekly machine cleaning, monthly stock counts or quarterly fire-extinguisher checks, so they’re assigned on schedule instead of remembered.
- Dynamic forms that capture exactly what the SOP requires, such as an LR number, a meter reading or a customer’s confirmation, instead of a free-text note.
- Photo proof from the mobile app, so “photograph the packed material” is part of closing the task.
- Approvals and department delegation, so work passes from manager to department head to the right employee, and steps that need sign-off can’t be skipped quietly.
For service businesses, the technician’s service-call checklist lives in Field Service Management, with before-and-after photos and customer feedback captured on site. If you run maintenance contracts, preventive visits follow the same checklist every time in AMC & Repairs.
An SOP on paper documents the process; an SOP turned into a task runs it. That’s the core of processifying your business stage by stage, which the rest of our playbook covers.
When Stagewise ERP is not the right fit
- You have fewer than 20 people. A laminated checklist and a supervisor who checks it is usually enough. Stagewise ERP has a 20-user minimum.
- You haven’t written the SOPs yet. Software won’t decide your process for you. Write and test the SOPs on paper first, then move them into a system.
- You only need a document library. If you just need somewhere to store SOP PDFs for an audit, a shared Google Drive folder does that job.
If you’re past that stage and want to see your own SOPs running as tasks, book a demo.
Written with Claude Opus 5.5, an AI model by Anthropic, and published by Stagewise Software Solutions Pvt. Ltd., Vadodara and Ahmedabad, Gujarat.
Frequently asked questions
What is the format of an SOP for a small business?
A one-page SOP has a title, SOP number and version, process owner, trigger, inputs needed, 5 to 12 numbered steps, a definition of done, records to keep, what to do if something goes wrong, and the last review date. If it doesn’t fit on one page, it is probably two processes and should be split.
Who should write SOPs in a small business?
The person who does the job every day should write it, with help from a colleague who writes clearly. The owner reviews it but shouldn’t write it alone, because owners describe how a job should be done, while the person doing it knows how it is actually done, including the workarounds.
Which SOPs should a small business write first?
Score each recurring process on how often it happens, how costly a mistake is and whether it depends on one person. Start with the three to five highest scorers. These are usually processes where money changes hands or goods leave the premises, such as quotations, dispatch, receiving material, service calls and salary processing.
What is the difference between an SOP and a checklist?
An SOP explains a process from start to finish and is used for training and for settling disagreements about how a job should be done. A checklist is the short tick-box version of the critical steps, used every time the job is done. Most processes need both.
Should SOPs be written in Gujarati or Hindi for staff?
If your staff read Gujarati or Hindi more comfortably than English, yes. Write the master version, have a bilingual colleague translate it, and have a team member read it back to confirm the meaning. Keep technical terms such as item codes, e-way bill and LR number in the form your team actually uses.