How to Create Standard Operating Procedures Staff Will Follow

Most owners already agree that their business needs SOPs. The difficulty is the next step: the document never gets written, or it arrives as a twelve-page essay that nobody opens twice. This guide sets out a one-page SOP layout, a one-week method for producing a procedure staff will follow, a worked example for closing a kopitiam, and the habits that keep SOPs current.

Decide what one SOP must contain

Fix the shape before you write a word. Every SOP in your business should use the same one-page layout so staff know where to look. A layout that works for most SMEs:

• Header: process name, version number, owner, date last reviewed.
• Purpose: one sentence on why this process exists.
• Trigger and end point: what starts the process and what “done” looks like.
• Who: the role that does it (not a person’s name) and who checks.
• Needs: keys, logins, forms, equipment.
• Steps: numbered, one action each, with a check after any step where mistakes happen.
• If this happens: a short table of exceptions and what to do.
• Records: what gets written down, where, and who signs.

Write the role, never the person’s name. The US Environmental Protection Agency’s long-standing SOP guidance describes an SOP as a set of written instructions that document a routine or repetitive activity, and its value as consistent work even when staff change, temporarily or permanently. A name in the header defeats that purpose the day that person resigns.

Keep policy out of the procedure. “We refund within seven days” is a policy. “How to process a refund at the counter” is the SOP. Mixing the two is the main reason SOPs grow long.

A one-week method for one process

Writing an SOP does not need a project plan. Give it five short sessions across one week.

Day 1: choose it and fence it

Choose a process that happens at least daily, then write its trigger and end point on the header. For a kopitiam, “closing the shop” starts when the last order is served and ends when the shutter is locked and the closing sheet is in the drawer. If you cannot state the start and the end in one line each, the process is too large. Split it.

Day 2: record the real way, not the ideal way

Ask the staff member who does the job most reliably to do it as normal while you film on a phone or photograph each stage. Do not interrupt. You are collecting the small steps nobody mentions in a meeting: which switch is awkward, which supplier crate must be kept, where the spare key lives.

Day 3: draft with the doer

Sit together for 30 minutes and turn the recording into numbered steps on the template. Start each step with a verb. Where the person said “and then I just check it”, write down exactly what is checked and what a pass looks like. Put the photos beside the steps they belong to.

Day 4: trial it on a real shift

Hand the draft to your least experienced staff member and let them run the process using the draft alone. Stand back and time it. Every question they ask is a gap in the document, so fix the wording that evening. A good SOP survives contact with a new hire.

Day 5: sign off, print, version 1.0

The process owner signs the header, the full SOP goes into the shared folder, and a one-page checklist version is laminated and placed where the work happens. Two layers, one source: the checklist is the SOP with the explanations removed.

Worked example: closing a kopitiam

Here is the outline of a closing SOP for a Klang Valley kopitiam with six staff. Your steps will differ, but the structure travels well.

Header: Closing the Shop, version 1.0, owner: Shift Supervisor, reviewed: October 2026.

Purpose: Leave the shop clean, safe, secure and ready to open at 7am without the owner being present.

Trigger: Last order served at 10pm. End point: Shutter locked, closing sheet completed and placed in the till drawer.

Steps

1. Turn the sign to Closed and stop taking orders. Let seated customers finish.
2. Clear and wipe every table and chair. Check under tables for rubbish.
3. Kitchen: close the gas at the cylinder valve, then at the stove. Confirm both are closed.
4. Wash, dry and store all utensils. Nothing stays in the sink overnight.
5. Wipe the counters and the drinks station. Empty the ice and switch off the machine as shown on the sticker.
6. Read the chiller temperature and write it on the closing sheet. If it is above the shop limit of 4°C, use the table below.
7. Tie and carry all rubbish bags to the bin area. Replace the liners.
8. Count the till with a second person. Record cash, card and e-wallet totals on the closing sheet. Put the float in the safe.
9. Switch off lights, fans and the water heater. Leave the chiller and CCTV on.
10. Lock the back door, then the front shutter. Pull both to test.
11. Sign the closing sheet and photograph it to the supervisor group.

If this happens

Records: closing sheet (kept three months), chiller log, cash variance log.

The cleaning steps are not optional extras. The Ministry of Health inspects food premises under the Food Act 1983 and the Food Hygiene Regulations 2009. During its 2024 Ramadan bazaar operation alone it issued 1,639 notices for breaches such as missing food handler training and typhoid vaccination, and it closed 910 food premises for unsanitary conditions between January and June 2024. A closing SOP that gets the kitchen right every night is inexpensive protection.

The same template handles a very different process. For a customer complaint at a car workshop, the trigger is “customer raises a problem with completed work”, the end point is “customer confirms the matter is closed and the complaint is logged”, and the exceptions table covers safety faults, refund requests above the service advisor’s limit, and complaints posted on social media.

Keeping SOPs alive without a quality department

• Version and change line. Every edit changes the version number and adds one line: what changed, who, when. Staff can see the document is current.
• Review on triggers, not only on the calendar. A new supplier, a new POS, a customer incident or a repeated mistake by a new hire each prompt a review of the affected SOP that same week.
• Fix it the same day. When a step fails on the floor, the document is wrong until proven right. The person who found the gap writes the correction and the owner approves it.
• Tie it to onboarding. A new staff member signs a training record against each SOP they have been walked through. This is also your evidence if performance later becomes a dispute.
• Spot-check in 60 seconds. Once a week, choose one SOP and watch one step being done. Praise what matches, correct what does not, update what has moved on.
• Retire dead SOPs. If a process has not run in six months, archive the document so the live folder stays short.

Common mistakes

• Writing for the owner’s level of knowledge instead of a first-week employee’s.
• No end point, so staff cannot tell when they have finished.
• Starting ten SOPs at once and finishing none.
• Keeping the only copy in a WhatsApp chat where it scrolls out of sight.
• Treating the first version as final instead of as version 1.0.

Key takeaways

• Use one layout for every SOP, with a role in the header, a trigger, an end point and an exceptions table.
• Record the process as it is really done, draft it with the person who does it, and test it on the newest staff member.
• Version every change and review on triggers, so the document stays trusted.

How Gusto Style can help

If your team is too stretched to run the one-week method, our SOP Development (3 Processes) project does it with you. We map three core processes with the staff who run them, write the step-by-step SOPs on a consistent template and walk your team through them, so you receive three SOPs with process maps in Word and PDF. It is a fixed-price project, so you know the cost before we start. See SOP Development