At some point in almost every growing company, the same process gets done differently by different people and nobody has a clean answer for which way is correct. Or someone senior leaves and takes with them years of knowledge that was never written down. Or an audit surfaces that a routine compliance step has been missed because it depended on one person remembering to do it.
That’s the problem SOPs solve.
A Standard Operating Procedure is a documented, step-by-step guide for completing a recurring task in a consistent and compliant way – regardless of which specific person is executing it on a given day. It’s not a policy, which tells you what the rules are. It’s not a guideline, which gives you principles to apply. An SOP tells you exactly how to do something: who does what, in what sequence, using which tools, and what happens if something goes wrong.
What Every SOP Should Have
- Purpose: Why this procedure exists and what problem it prevents when followed properly.
- Scope: Which roles, teams, or situations it applies to – and what’s outside its scope. Clarity here avoids a lot of “wait, does this apply to me?” conversations.
- Step-by-step instructions: Numbered, sequential, written clearly enough that someone new to the role can follow them without needing to ask for help.
- Roles and responsibilities: Who owns each step. Ambiguity here is exactly where things fall through.
- Tools and resources: Every system, form, template, or access credential needed to actually complete the process.
- Exceptions and escalations: What to do when something deviates from the standard path. Every process has edge cases; good SOPs account for them.
The SOPs HR Departments Actually Need
- Recruitment and selection: Full hiring workflow from requisition through to offer acceptance.
- Onboarding: Document collection, system setup, access provisioning, and the induction programme.
- Payroll processing: Monthly payroll steps, approval checkpoints, and statutory compliance requirements.
- Leave approval: How leave gets applied for, approved, and escalated when the usual approver isn’t available.
- Exit management: From resignation acceptance through knowledge transfer, asset return, and Full and Final Settlement.
- Grievance handling: How a complaint is received, who investigates it, what the timelines are, and how resolution gets documented.
Why Writing Them Is Worth the Effort
- The same process runs the same way regardless of who’s doing it on a given day. Quality stops depending on any one person’s memory.
- New team members get up to speed faster when the process is written rather than transmitted through informal conversations that may or may not include the important details.
- Compliance gaps are harder to miss when required steps are documented and followed consistently.
- When someone moves on, their process knowledge doesn’t move with them – it’s already captured.
- Internal or external audits become far less stressful when the documentation already exists and is current.
Making Sure People Actually Use Them
- Write in plain language. Jargon makes SOPs feel authoritative. It also makes people skim past the parts they should read carefully.
- Number every step individually. “Complete the form and email it to finance” is two distinct steps – write them separately.
- Add visuals where they actually help. Some processes make more sense as a flowchart than as a numbered list.
- Review them on a schedule and update immediately when a related policy, system, or regulation changes. An outdated SOP is a false sense of compliance, not a real one.
- Store them somewhere people can find them without a 10-minute search. A centralised knowledge base works. A subfolder on a shared drive that nobody remembers the path to does not.
FAQs: Standard Operating Procedure (SOP)
How often do SOPs need updating?
At minimum once a year – but more importantly, immediately whenever a related policy, system, or regulatory requirement changes. An SOP that no longer reflects how the process actually works is arguably worse than no SOP, because it creates the appearance of compliance without the reality of it.
Who should actually write them?
Typically the person who owns the process – an HR manager for a hiring SOP, a payroll lead for the payroll cycle. The drafter usually validates with senior leadership or a compliance function before it’s finalised and put into use.
Small companies don’t need these, right?
Actually the opposite tends to be true. Informal processes that run fine with a small team start breaking down quickly as headcount grows. The best time to document is before the inconsistencies become visible problems. Most companies wait too long on this.
What’s the actual difference between a policy and an SOP?
A policy sets the rules and explains why they exist – the what and the why. An SOP provides the step-by-step instructions for executing a process in line with those rules – the how. You need both. One without the other leaves gaps.