How to write a standard operating procedure employees use

A standard operating procedure (SOP) helps a new employee only if it tells them what to do at the next decision point, including when to stop and ask for help. “Respond promptly and professionally” is a value statement, not an operating instruction. This one-page template covers a recurring task; test it with someone unfamiliar with the work and revise the step where they hesitate.

Which process should you document first?

Choose a task that happens often, has a clear trigger and can cause a customer or compliance problem when handled inconsistently. A customer enquiry is a useful example: someone writes in, the team identifies the request, checks what may be promised and sends a reply. Give the SOP a title, owner and review date. State where it starts and ends. Do not try to describe sales, billing, fulfilment and complaints in one giant flow; link to separate procedures where the handoff occurs.

Begin with the tools and information the employee may use. For example: shared inbox, current product sheet, approved price list, escalation contact and customer-recording system. Explain how to identify the right version of each. If personal data is handled, refer staff to the firm's privacy and access rules. The PDPC obligations overview sets the official context for handling personal data; the SOP should implement the organisation's reviewed policy rather than invent a legal rule from a template.

What does a usable one-page example say?

Here is an illustrative SOP for a fictional catering business, not a live company process. Trigger: an enquiry arrives asking for lunch for 40 people on a given date. Step 1: record the customer's name, contact, date, location, guest count and dietary questions in the approved system. Step 2: check whether the service area and date are available. Step 3: use the current menu and price sheet, but send no quote until the event lead confirms delivery and staffing. Step 4: reply using the approved template, naming any missing information. Step 5: assign an owner and next reply date. Exception: if the customer reports a food-safety issue or asks for a refund, stop the ordinary sales sequence and hand the message to the named manager immediately.

That example is stronger than “answer within two hours” because it tells the employee what information to gather and what not to promise. If you do set a response-time target, make it achievable during the stated working hours and explain what happens when the owner is away. For price communication, the CCCS price-transparency guidance is a reason to keep required charges and conditions visible; use your current approved price sheet and the actual service terms, not a copied example number.

How should you test the SOP?

Give a new employee a fictional enquiry and the one-page process. Do not coach them while they run it. Watch where they cannot find a document, are unsure who can approve a price, or do not know what to do with an unusual request. Ask them to draft the reply, then compare it with the product sheet and escalation rule. Change the SOP at the step that failed, rather than adding a vague paragraph at the end. Keep a version date and note who approved the change.

Review the SOP when the product, price, system, responsible person or relevant rule changes. Archive an old version so staff can see which instructions applied to an earlier case. The customer-enquiry approval guide gives a more detailed decision rule, the process-writing guide covers wider process design, and operations guides collect related practices. You may send Methodology a process question as an editorial enquiry; we do not promise to implement or certify your SOP. An external adviser would need a separate scope and your consent before receiving internal details.

Common questions