Policy, Procedure, SOP, Handbook or Contract - What Goes Where and Why It Matters
Most businesses use policy, procedure and handbook as if they meant the same thing. They do not, and the differences are not academic: putting content in the wrong document type is how procedures become unenforceable and handbooks become contracts by accident.
This guide gives each document type a one-line job description, then covers the mix-ups that cause real problems and how to get the architecture right.
The Five Document Types at a Glance
| Document | The question it answers | The test |
|---|---|---|
| Policy | What is our position, and why | Principles and commitments, few or no steps |
| Procedure | How do we do it, and who does what | Steps, owners and timescales |
| SOP | How is this one task done, every time | Operator-level instructions for a single task |
| Handbook | What does a member of staff need to know | A curated, readable collection pointing to the rest |
| Contract | What have we legally agreed | Terms both sides are bound by |
Policies Set the Position
A policy states what the organisation commits to and why: we will manage health and safety risks, we will not tolerate harassment, we will protect personal data. The HSE's health and safety policy guidance captures the shape well, with a statement of intent backed by responsibilities and arrangements.
A policy stuffed with step-by-step detail dates quickly and binds you to trivia. The position rarely changes; the steps often do, which is exactly why they belong one level down.
Procedures Make It Operable
A procedure turns the position into named steps: who does what, in what order, by when, with what records. It is the document a tribunal or auditor tests you against, because it promises specific behaviour.
That is also its risk. A procedure that promises three warning stages, or a response within five days, is a promise; write only the steps you actually follow, and keep discretion where you need it.
SOPs Go One Level Deeper
Standard operating procedures are task-level: how this machine is cleaned, how this medicine is dispensed, how this order is picked. They are written for the person doing the task, not the manager supervising the area, and sectors from food manufacturing to pharmacy run on them.
Our guide to standard operating procedures covers the format in full, so here the point is placement: an SOP inside a policy makes the policy unmanageable, and a policy inside an SOP buries the commitment where nobody looks for it.
The Handbook Question - Contractual or Not
The handbook is where the legal consequences of mixing document types show up. A staff handbook is meant to be the readable, curated layer: what a new starter needs to know, pointing to the underlying policies. But wording matters, because parts of a handbook can acquire contractual status, and a contractual disciplinary procedure means departing from it can become a breach of contract claim.
The working rule: contractual terms live in the contract, the handbook states that it is non-contractual and can be updated, and the two never contradict each other. A handbook promising one notice period while the contract states another is the classic accumulated-library failure, and our employee handbook service exists largely to untangle it.
Why the Mix-Ups Cost Money
Three failure patterns account for most of the damage. Procedures written as vague policy commitments give tribunals nothing to credit you for following. Policies written as rigid procedures get breached by their own authors within months. And handbooks written without contractual-status care hand employees terms nobody intended to grant.
Free sources such as Acas templates are sound on content but silent on architecture, because architecture depends on your structure, your contracts and your sector.
Getting the Architecture Right
Start from the reader. Regulators and auditors read policies and procedures; staff read the handbook; both sides read the contract when things go wrong. Each document should know its reader, do one job, and cross-reference rather than duplicate, because duplicated content is where contradictions breed.
When we build or consolidate a document set, the architecture is the first decision, not an afterthought, which is why the same content organised properly is shorter, more consistent and easier to keep current.
Policy and Procedure Writers
Policy Pros writes all five document types for UK businesses, with the boundaries between them drawn deliberately: policies that state positions, procedures that match practice, SOPs staff actually use, handbooks with their contractual status handled, and contracts that agree what they mean to. Contact us for a free quote, or call 020 3951 2875.
Frequently Asked Questions
What is the difference between a policy and a procedure?
A policy states the organisation's position and commitments; a procedure sets out the steps, owners and timescales that deliver them. Policies change rarely and procedures change often, which is the practical reason for keeping them as separate documents.
Is a staff handbook legally binding?
It can be, in part. Handbook provisions can acquire contractual status depending on their wording and how they are presented, which is why well-drafted handbooks state they are non-contractual and keep genuine terms in the employment contract. Contradictions between handbook and contract are where disputes start.
Where do SOPs fit alongside policies and procedures?
One level below procedures: an SOP describes how a single task is performed, written for the person doing it. Regulated and audited sectors, from food manufacturing to pharmacy, effectively run on SOPs, with policies and procedures providing the framework above them.
Can one document serve as both policy and procedure?
For a very small business a combined document can work, provided the position and the steps are clearly separated within it. The combined format stops working as soon as the steps change more often than the position, or more than one team follows different procedures under the same policy.
