How to Write an SOP for Your Business, With a One-Page Template

Every growing business hits the same wall. The owner knows how everything should be done, but it lives in their head. Staff ask the same questions every week, quality depends on who is on duty, and the business stops the day the owner travels. Learning how to write an SOP is how you break through that wall.

This guide is for business owners, managers and team leads in Nigeria who want their teams to work consistently without constant supervision. It explains what an SOP is, gives you eight steps to write one, and includes a one-page template you can copy today.

By the end, you will be able to turn any repeated task into a clear written procedure your team can follow.

What is an SOP?

A standard operating procedure (SOP) is a written, step-by-step instruction for doing a repeated task the same way every time. It says what the task is for, who does it, what tools are needed, the exact steps in order, and how to check the work. A good SOP lets a trained person complete the task correctly without asking the owner.

Why do small businesses need SOPs?

Small businesses need SOPs because consistency is hard to keep when knowledge lives in one person's head. Written procedures reduce errors, make training faster, protect quality when staff leave, and free the owner from answering the same questions. They also make a business easier to grow, delegate and, one day, sell.

The power of simple written steps is well documented. In a study published in the New England Journal of Medicine in January 2009, hospitals in eight cities introduced a one-page surgical safety checklist. Major complications fell from 11% to 7% and inpatient deaths fell from 1.5% to 0.8%, according to the Pan American Health Organization.

The study was led by researchers from the Harvard School of Public Health with the World Health Organization, as reported by the Harvard Gazette. Your business is not an operating theatre, and an SOP is not a guarantee. But the principle holds: when steps are written down and followed, fewer important things are missed.

"If a task only works when you are in the room, you do not have a system. You have a dependency."

-Eze Maximus Chukwujindu

How to write an SOP: step by step

To write an SOP, follow eight steps: choose one repeated task, define its purpose and scope, watch the best person do it, write the steps in plain language, assign roles, add quality checks, test it with someone new, and set a review date. Start with one task. A finished SOP for one process beats a half-written manual for twenty.

1. Choose one repeated task. Pick a task that happens often, causes mistakes or depends on one person. Examples: handling a new enquiry, opening the shop, processing a payment.

2. Define the purpose and scope. Write one sentence on why the task matters and one on where it starts and ends.

3. Watch the best person do it. Ask your most reliable staff member to do the task while you note every step. Do not write from memory alone.

4. Write the steps in plain language. Number them. Start each step with a verb: "Open", "Confirm", "Send". Keep one action per step.

5. Assign roles. Name who does each step by role, not by person, so the SOP still works when staff change.

6. Add quality checks. Say what "done right" looks like, and what to do when something goes wrong.

7. Test it with someone new. Ask a person who has never done the task to follow the SOP alone. Every question they ask shows a gap to fix.

8. Set an owner and a review date. Name one person responsible for keeping the SOP current, and review it on a fixed schedule or whenever the process changes.

Writing tips that make SOPs usable

• Use short sentences and everyday words.

• Add screenshots or photos for steps that are hard to describe.

• Keep most SOPs to one or two pages.

What should a standard operating procedures template include?

A standard operating procedures template should include a title, an owner, a version and review date, the purpose, the scope, the roles involved, the tools needed, the numbered steps, quality checks, and what to do when something goes wrong. Keeping every SOP in the same format makes them faster to write and easier for staff to follow.

One-page SOP template

Worked example: responding to a new customer enquiry

• SOP title: Respond to a new customer enquiry

• SOP number and version: SALES-01, version 1

• Owner: Sales lead

• Purpose: Make sure every enquiry gets a fast, professional reply so no potential client is lost.

• Scope: Starts when an enquiry arrives on WhatsApp, phone, email or the website. Ends when the lead is logged and a next step is agreed.

• Roles: Sales executive replies and logs the lead. Sales lead reviews the log weekly.

• Tools: WhatsApp Business, the lead tracking sheet, approved reply templates.

• Steps:

  1. Reply to the enquiry within the agreed response time, using the approved greeting.

  2. Ask the qualifying questions on budget, timeline and purpose.

  3. Log the lead's name, contact, source and answers in the lead tracking sheet.

  4. Agree a next step, such as a call, a visit or sending information.

  5. Set a follow-up reminder for the agreed date.

• Quality checks: Every enquiry is logged with a next step and a follow-up date.

• Exceptions: If the enquiry is a complaint, forward it to the sales lead the same day.

For more on the qualifying step, see how to qualify leads and stop wasting time.

What are some SOP examples for a small business?

Good SOP examples for a small business are the tasks that repeat most often and cause the most problems when done badly. Most businesses start with SOPs for handling enquiries, taking payments, onboarding new staff, opening and closing, handling complaints and managing stock. Each one turns a daily habit into a standard anyone trained can follow.

How do you get your team to follow SOPs?

You get a team to follow SOPs by involving them in writing them, training them on each one, making the documents easy to find, checking the work against the SOP, and updating it when the team finds a better way. People follow procedures they helped shape and understand, and ignore documents that sit in a forgotten folder.

Five habits that make SOPs stick

1. Write them with the team, not for the team. The people doing the work know the real steps.

2. Train on every SOP. Walk new and existing staff through it, then watch them do it.

3. Make them easy to find. One shared folder, clearly named, and a printed copy where the task happens.

4. Check the work against the SOP. In reviews, ask "Did we follow the SOP?" before asking "Who made the mistake?"

5. Update them often. When someone finds a better way, change the SOP and tell the team.

Consistency in a business mirrors consistency in a person. Our piece on the daily discipline that builds success shows the same principle at an individual level.

From my desk: building the Win Realty operating manual

When I sat down to build the Win Realty employee operating manual, I learned quickly that writing procedures is really about making decisions. You cannot write how a task is done until you have decided how it should be done, who owns it and what "good" looks like.

The manual covered 11 roles across the business, our organisational structure, how we set and track objectives and key results (OKRs), and how our sales system works. Alongside it, we mapped out a hiring roadmap, so each new role would arrive with its responsibilities already written down.

The biggest lesson I took from it is this: start with roles and outcomes, then write the procedures. When people know what their role is responsible for and how success is measured, the SOPs make sense to them. Without that, even a well-written procedure feels like paperwork.

"Write the role before you write the procedure. People follow steps more willingly when they know what they own."

-Eze Maximus Chukwujindu

If you want help building systems, SOPs and structure for your team, book one-on-one coaching. You can also see how I work with leaders and teams, or read more about my background.