A Standard Operating Procedure (SOP) is simply the agreed, written way a task is done in your business. When it works, a new employee can do the job correctly in days rather than months, quality stops depending on who is on shift, and you stop being the person everyone calls when something goes wrong.
When it fails, it is usually for one of three reasons: it is too long, it was written by someone who does not do the job, or nobody checks whether it is followed. The method below avoids all three.
Step 1: Pick the 10 processes that hurt most when they go wrong
Do not try to document the whole business. Start with the processes that are repeated daily and expensive when they fail. In most MSMEs these are:
- Order booking and order confirmation
- Dispatch, loading and invoice checking
- Raw material receiving and quality inspection
- Machine start-up, changeover and shutdown
- Payment follow-up and collections
- Purchase requisition and approval
- Stock entry and issue from the store
- Customer complaint handling
- New employee induction
- Daily reporting to the owner
Ask a simple question for each: "When this went wrong last time, what did it cost us?" Rank them and write the top three first.
Step 2: Use a one-page SOP format
If an SOP does not fit on one page, people will not read it on the shop floor. Use this structure:
| Section | What to write |
|---|---|
| Title and SOP number | e.g. "SOP-DSP-03: Dispatch checking before loading" |
| Purpose | One line: why this process exists and what goes wrong without it |
| Owner | The single person accountable (a role, not "everyone") |
| Trigger | What starts the process (e.g. "Invoice printed in Tally") |
| Steps | 5 to 12 numbered steps, each starting with a verb |
| Checkpoints | What must be verified, and where it is recorded |
| Output | What "done" looks like (e.g. "Signed dispatch checklist filed") |
| Escalation | Who to call, and when, if something is wrong |
| Version and date | So everyone knows which copy is current |
Step 3: Write it with the person who does the job
The most common mistake is the owner or a consultant writing SOPs from an office. Sit with the person who actually performs the task, watch them do it twice, and write down what they do, including the small checks they do from experience but never mention. Then improve the steps together. People follow what they helped write.
Rule of thumb: each step should be specific enough that a new joiner could do it without asking. "Check the material" is not a step. "Weigh 3 random bags and record the weight in the GRN register" is.
Step 4: Add checkpoints and a record
An SOP without a record is a suggestion. For every critical step, decide where the proof lives: a checklist, a register, a photo in a WhatsApp group, a field in your software. This is what lets a supervisor (or you) verify the SOP was followed without standing over anyone.
Step 5: Train, test and sign off
- Walk the team through the SOP on the floor, not in a meeting room.
- Have each person perform the task once while someone checks against the SOP.
- Collect a signature that they have been trained.
- Display a short version (steps only) at the workstation.
Step 6: Review monthly for the first three months
SOPs improve through use. For the first three months, review each new SOP once a month: where did people skip steps, which steps were unclear, what new problem came up? Update the SOP and the version number. After that, a quarterly review is usually enough.
Example: a dispatch checking SOP
SOP-DSP-03: Dispatch checking before loading. Owner: Dispatch Supervisor. Trigger: invoice printed.
- Print the invoice and the packing list together.
- Match item code, quantity and batch number for every line.
- Check packaging for damage and correct labelling.
- Count cartons on the vehicle against the packing list.
- Photograph the loaded vehicle with the invoice visible and post it in the dispatch group.
- Sign the dispatch checklist and file it with the invoice copy.
- If any mismatch is found, stop loading and call the Sales Coordinator.
Common reasons SOPs fail (and the fix)
| Why it fails | Fix |
|---|---|
| Too long and too general | One page, numbered steps, verbs first |
| No owner | Name one accountable role per SOP |
| No record or proof | Add a checklist or register for each checkpoint |
| Written by people who don't do the job | Co-write with the operator |
| Never reviewed | Monthly review for 3 months, then quarterly |
| Owner bypasses it | The owner follows the SOP too, or it dies |
If you want SOPs designed, written and installed with your team, see our operations and SOP consulting. For the reporting side, read how to set up a daily MIS report.
Want this built for your business?
TBS installs these systems inside MSMEs and stays until your team runs them without you. Start with a 45-minute strategy session with the founder, or take the 20-minute Business Depth Assessment to see where you stand.
Frequently asked questions
How many SOPs does a small business need?
Start with 8 to 12 SOPs covering the processes that repeat daily and cost the most when they fail: orders, dispatch, purchase, stores, collections and quality. Add more only after these are being followed.
Who should write SOPs in a company?
The person who performs the task should co-write it with a supervisor or consultant. The owner approves it. SOPs written only by management are rarely followed on the floor.
How long should an SOP be?
One page for most tasks: purpose, owner, trigger, 5 to 12 numbered steps, checkpoints and escalation. Longer technical procedures can have an annexure, but the working steps should still fit on one page.
How often should SOPs be updated?
Review new SOPs monthly for the first three months, then quarterly, and immediately whenever the process, machine or software changes.
Munishh Latawa is the founder of The Business Studio, an execution-first MSME consulting firm in Ludhiana that builds sales, operations, HR and costing systems for manufacturers, traders and service businesses across North India. About TBS