1. Home
  2. Blog
  3. Operations
Operations

How to write SOPs your team will actually use

Most SOP files are written once, printed, and never opened again. Here is how to write short procedures that match the real work, so staff use them and new hires learn faster.

By the HumbleBear team · · 8 min read

Cover: How to write SOPs your team will actually use
Short answer

To write an SOP your team will use, pick one task that must be done the same way every time, watch someone do it, and write numbered steps that start with a verb, with one action per step. Keep it to a page, test it on someone new, give it an owner, and review it after changes.

Many Malaysian SMEs have a file of SOPs that someone wrote for a certification audit or a bank loan. It's thick, it describes how work was done three years ago, and nobody opens it. Meanwhile new staff learn by watching whoever is free, and each person teaches a slightly different version. A short procedure that matches the real work fixes that. Here is how to write one.

What is an SOP?

An SOP (standard operating procedure, or prosedur operasi standard) is a written set of steps for carrying out a routine task the same way every time, so that the result is consistent whoever does it. It says what to do, in what order, who does it, and what "done" looks like.

SOPs are different from the documents around them:

DocumentWhat it answersExample
PolicyWhat we've decided and why"We don't give credit to new customers for their first three orders."
WorkflowWhich steps happen, in what order, across peopleEnquiry → quotation → order → delivery → invoice
SOPHow one routine task is done, step by step"How to issue a quotation"
ChecklistDid we do every item?Shop closing checklist
Form or templateWhere the information goesQuotation template

An SOP often refers to the others: it follows a policy, sits inside a workflow and may end with a checklist.

Which tasks need an SOP first?

Write SOPs first for tasks that are risky, frequent, or done by only one person. Those are where inconsistency costs the most money, causes injuries, or stops the business when someone is away.

Good first candidates:

  • Tasks with safety risk: operating machinery, handling chemicals, working at height, food handling.
  • Tasks that touch money: issuing quotations and invoices, receiving payments, approving purchases, petty cash.
  • Tasks with compliance deadlines: e-invoice submissions, SST returns, statutory contributions.
  • Tasks only one person knows: the stock count, the monthly supplier reconciliation.
  • Tasks new staff get wrong: whatever your supervisors keep correcting.

Don't write SOPs for judgement work, such as negotiating with a difficult customer. Write principles and examples for those instead.

What does Malaysian law say about written procedures?

For safety, the Occupational Safety and Health Act 1994 (Act 514) doesn't use the word "SOP", but several of an employer's duties are easiest to meet with written procedures. Under section 15(2), an employer's general duty includes:

  • providing and maintaining plant and systems of work that are, so far as is practicable, safe and without risks to health (paragraph (a));
  • providing the information, instruction, training and supervision needed to ensure, so far as is practicable, employees' safety and health at work (paragraph (c)); and
  • developing and implementing procedures for dealing with emergencies that may arise while employees are at work (paragraph (f)).

Section 18B, added by the Occupational Safety and Health (Amendment) Act 2022 (Act A1648), requires every employer, self-employed person and principal to conduct a risk assessment of the safety and health risks posed to anyone affected by their work, and to implement the controls it shows are needed. A safe-work SOP is often where those controls are written down. Under section 19, breaching sections 15, 16, 17, 18, 18A or 18B can lead to a fine of up to RM500,000, imprisonment of up to two years, or both.

Section 16 separately requires most employers to prepare a written safety and health policy and bring it to employees' notice. That is a policy, not an SOP, but the two should agree. For the wider picture, see building a healthy workplace in Malaysia.

How do I write an SOP step by step?

Watch the task being done, write down what actually happens, then cut it to the fewest clear steps that still get the right result. Test it on someone who has never done the task.

  1. Define the scope. Write one sentence: what the task is, where it starts and where it ends. "Issuing a quotation, from receiving a complete enquiry to sending the PDF to the customer."
  2. Name the owner and the users. The owner keeps the SOP correct; the users follow it.
  3. Watch it done. Sit with the person who does it best and note every action, including the ones they don't think to mention.
  4. Write numbered steps. Start each with a verb: "Check", "Enter", "Send". One action per step.
  5. Add the "why" only where it prevents mistakes. "Enter the customer's TIN (needed if an e-invoice is issued)."
  6. Mark decision points. "If the discount is above 5%, get the sales manager's approval before sending."
  7. Show, don't describe. A photo of the correct label or a screenshot of the right screen beats a paragraph.
  8. State what "done" looks like. "The quotation is sent and its status is 'Sent'."
  9. Test it. Hand it to someone new, watch them follow it without help, and fix every point where they hesitate.
  10. Publish it where the work happens and record the version and review date.

Keep it to one page if you can. If an SOP needs five pages, it probably covers several tasks and should be split.

What should an SOP template include?

A simple, consistent header and numbered steps are enough for most SMEs. Use the same layout for every SOP so staff know where to look.

  • Title, written as a task: "How to receive goods from a supplier".
  • Purpose and scope, in one or two sentences.
  • Owner, version number and next review date.
  • Who does it, by role.
  • What you need: tools, forms, system access, protective equipment.
  • Steps, numbered, with decision points and photos.
  • Done when: the finished state.
  • If something goes wrong: who to call and what not to do.

Example: An Ipoh food manufacturer's SOP "How to receive raw materials" fits on one page: check the delivery against the purchase order, check the temperature of chilled items and reject anything above the limit in the policy, check expiry dates, record any shortfall on the delivery order before signing, label and store items first-expiry-first-out, and file the delivery order. Before the SOP, three storekeepers did this three ways, and shortfalls were often discovered only when the supplier bill arrived.

How do I get staff to actually follow SOPs?

Involve them in writing it, make it easy to find at the moment of work, and make following it the normal standard that supervisors check. An SOP that is imposed and filed away is ignored.

  • Write it with the people who do the work. They know the real steps and will defend a procedure they helped write.
  • Put it where the work is. A laminated card at the machine, a link pinned in the team's chat, a checklist inside the job record.
  • Train on it. Walk through the SOP with each new person, then watch them do it.
  • Check it lightly but regularly. A supervisor spot-checks one task a week against the SOP.
  • Fix the SOP, not just the person. When someone deviates, ask whether the SOP is wrong before blaming them.

Some SOP steps fit naturally into the tools the team already uses. If jobs move across a kanban board, for example, the board's stages can mirror the main steps of the SOP. In HumbleBear, Spaces let you set your own stages and link a job's quotation, purchase orders and invoice to its card, so a "quotation sent" or "invoiced" step is visible on the job itself.

How often should SOPs be reviewed?

Review an SOP whenever the task changes, such as new equipment, a new system, a new legal requirement or a repeated mistake, and otherwise at least once a year. Each SOP's owner should have the review date in their calendar.

A quick review takes fifteen minutes: watch someone do the task, compare it with the SOP, and update either the SOP or the practice. Record the new version and date, and remove the old copies so nobody follows an outdated version. SOPs live best inside a company knowledge base, and they're easier to write once the workflow has been mapped.

Frequently asked questions

How long should an SOP be?

As short as it can be while still getting the right result, usually one page or fewer than fifteen steps. If it runs longer, it probably covers several tasks and should be split into separate SOPs linked from a workflow.

What is the difference between an SOP and a work instruction?

The terms are often used loosely. Where a business uses both, an SOP usually describes a whole routine task and who does each part, while a work instruction gives the detailed steps for one specific operation, such as setting up a particular machine. For most SMEs, one well-written SOP format is enough.

Are SOPs required by law in Malaysia?

There's no general law requiring every business to have SOPs. However, the Occupational Safety and Health Act 1994 requires employers to provide safe systems of work, emergency procedures and the information, instruction and training employees need, and written procedures are a practical way to show you've done that. Some industries and licences have their own documentation requirements.

Should SOPs be written in English or Bahasa Malaysia?

Write them in the language your staff read most comfortably, and translate SOPs for safety-critical tasks if your team is mixed. Photos and simple numbered steps help readers whose first language is different.

Who should approve an SOP?

The SOP owner, usually the supervisor or manager responsible for the task, should approve it after it has been tested on someone new. For safety-related SOPs, the person responsible for safety and health at the workplace should also review it.

Sources