How to Write SOPs for Your Small Business (With Template)

Every owner has said it: "Kitni baar samjhaun?" The same mistake in dispatch, the same missing detail on a quotation, the same new hire who needs a month of hand-holding. The fix is not another lecture. It is a written way of doing the task. This guide shows you how to write SOPs for your small business that people actually follow: one page each, written with your team, tested before they go live, and kept current without a quality department.

Why most SOPs fail

Most owners have tried SOPs once. A consultant or a keen manager wrote a thick file, it was printed, and nobody opened it again. That fails for three reasons:

• Too long. A 12-page procedure for packing an order will not be read on the floor.
• Written by the wrong person. If the owner or an outsider writes it, it describes how the task should work in theory, not how it works.
• Nobody owns it. Six months later the process has changed and the SOP hasn't, so people stop trusting it.

A good SOP is short, written from the real work, and has a named owner.

Step 1: Pick the right tasks first

Don't try to document the whole business. Make a list of recurring tasks and score each one on two questions:

1. Does this task go wrong often, or cost real money when it does?
2. Does only one person know how to do it properly?

Tasks that score high on either are your first 10 to 15 SOPs. In most owner-run businesses, the list looks something like this:

• Replying to a new enquiry and sending a quotation
• Checking incoming material against the purchase order
• Packing and dispatching an order
• Raising an invoice and sending it
• Following up on overdue payments
• Handling a customer complaint
• Onboarding a new employee in the first week
• Month-end stock count

If one key employee holds the whole process in their head, start there. My post on reducing dependency on one key employee explains why that risk comes first.

Step 2: What goes on a one-page SOP

Every SOP uses the same format, so people know where to look. The free SOP template has nine parts. For your first few SOPs, start with the short version below: the five parts that carry most of the weight. Add the other four once the habit sticks.

1. Title and trigger

What the task is and what starts it. "Dispatch of an order: starts when accounts marks the order as payment-cleared."

2. Owner and backup

One named role does the task. One named role covers when that person is away.

3. Steps, in order

Numbered, one action per line, starting with a verb. "Check the order quantity against the packing list." Keep it to eight steps or fewer. If you need more, it is probably two tasks, so split it.

4. The standard

What "done properly" looks like, in a way someone can check. "Every box labelled with order number and customer name. Photo of packed goods sent to the customer's WhatsApp before dispatch." A photo of a correctly finished result is often the best standard you can write.

5. Check and record

Who checks, how often, and where it is recorded. "Dispatch in-charge checks every order before loading. Entry made in the dispatch register with vehicle number and time."

The other four parts: a "done when" line (the visible result that proves the task is finished), a time limit, what to do if something goes wrong, and a version number with the next review date. The full nine-part SOP template lays out all nine with a worked example, ready to fill.

Step 3: Write it with the person who does it best

The fastest way to a good SOP takes about 45 minutes per task:

1. Ask the person who does the task best to do it once while explaining each step out loud.
2. Someone else writes it down, or records a voice note and types it up later.
3. Ask: "What goes wrong most often here?" and "What do new people forget?" The answers become steps or standards.
4. Write it in the language the doer reads best. Hindi, English or a mix is fine. Plain words beat formal ones.
5. The owner reads it once and approves the standard, not the wording.

When the team writes the SOP, they also own it. That matters more than perfect grammar.

Step 4: Test it before you call it done

An SOP is ready when someone who has never done the task can follow it without calling anyone. Hand it to a newer team member and watch them do the task once. Every time they stop or ask a question, the SOP is missing a step or a standard. Fix it and test again.

This test usually adds two or three lines. Those lines are exactly the knowledge that used to live in one person's head.

A worked example: quotation SOP

Illustration only: a generic example to show the format. Your steps and standards will differ.

Trigger: a new enquiry is assigned in the CRM. Owner: sales executive. Backup: sales head.

1. Call or message the buyer within 15 minutes in working hours.
2. Confirm product, quantity, delivery location and required date.
3. Check stock or production slot with the store or production head.
4. Prepare the quotation from the standard price list.
5. If the discount needed is above your limit, send it to the sales head for approval.
6. Send the quotation as a PDF on WhatsApp and email, with a three-line summary in the message.
7. Mark the CRM stage as "Quoted" and set follow-up dates for Day 1, 3, 5, 7, 14 and 30.

Standard: quotation sent within 24 hours of the enquiry, every field filled, validity date stated. Check: sales head reviews all open quotations every Monday.

Step 5: Make SOPs easy to find

An SOP nobody can find doesn't exist. Keep them where the work happens:

• A shared folder on everyone's phone, with one file per SOP and clear names.
• Printed and laminated at the workstation for floor tasks: packing table, store, machine.
• Linked from the task in your CRM or ERP, so the steps sit next to the work.
• Short videos or photo sequences for physical tasks. A 60-second phone video often teaches packing better than a page of text.

Step 6: Keep them alive

SOPs decay. Three habits stop that:

• Owner and date on every SOP. "Owner: dispatch in-charge. Last reviewed: (date)." When the date is more than a year old, it gets reviewed.
• Change the SOP when the work changes. New packaging, new software, new customer requirement: update the page the same week.
• Use mistakes as updates. When something goes wrong, ask, "Did we follow the SOP?" If yes, the SOP needs fixing. If no, the training does. Either way, nobody needs a lecture.

A 30-day rollout plan

You don't need a project team. One coordinator, usually an office manager or a senior executive, and about three hours a week from each team lead is enough.

• Week 1: list recurring tasks, score them and pick the first ten. Share the one-page format with team leads.
• Week 2: write five SOPs using the 45-minute method above. Test each with a newer team member.
• Week 3: write the next five and test them. Put the first five where the work happens: phone folder, workstation, CRM task.
• Week 4: train the team on all ten in short sessions of 15 minutes per SOP. From now on, every mistake is checked against the SOP first.

Illustration only: a typical pace, not a promise. Businesses with many shifts or locations take longer.

Say a new dispatch helper used to need three weeks of someone's time to learn the job. With five clear SOPs and a few photos, that might come down to one week. The time saved goes back to the person who used to do all the training, often the owner.

Common mistakes

• Writing SOPs for tasks that never go wrong, while the painful ones stay undocumented.
• Mixing policy and procedure. "We give 30 days credit" is a policy. How to check a customer's credit limit before dispatch is the SOP.
• Writing for an auditor instead of the person doing the task.
• Skipping the test with a new person.
• Treating SOPs as a one-time project instead of a habit.

Where SOPs fit

SOPs are part of the Operate layer of the Self-Running Business System, alongside a delegation map, approval limits and a daily report. Together they let work move without you chasing it; the full sequence is in how to make your business run without you. Once SOPs are stable, the repetitive steps in them are the best candidates for automation.

The SOP format and 14 other templates come with my book, Jugaad Is Not a System. If you'd like an outside view of which processes are costing you most, take the free Automation Scorecard or book a Growth Diagnostic.

Go further: read the free one-page SOP template, with a worked example.