The template
Copy this SOP template for each procedure and keep the section numbers the same, so every SOP on the site reads the same way and auditors know where to look.
Header block
| Field | Entry |
|---|---|
| SOP title | |
| SOP number | |
| Revision | |
| Effective date | |
| Site / area / equipment | |
| Owner | |
| Approved by | |
| Next review date |
1. Purpose. One or two sentences: why this procedure exists and what result it protects.
2. Scope. The task, equipment, area and people it covers, and what it does not cover.
3. Responsibilities
| Role | Responsibility |
|---|---|
4. Materials, tools and PPE. Everything needed before starting, including the PPE and any permits or isolations.
5. Procedure
| Step | Action | Key point | Reason |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
6. Checks
| Check | Standard or limit | When | What to do if it fails |
|---|---|---|---|
7. Records. What is recorded, where, and how long it is kept.
8. Revision history
| Revision | Date | Change | By | Approved |
|---|---|---|---|---|
What goes in each section of an SOP?
The header block makes the document controllable: anyone can see whether the copy in their hand is the current revision and who to ask about it. Purpose and scope stop the procedure being stretched to tasks it was never written for. Responsibilities name roles, not people, so the SOP survives a change of staff.
The procedure is the core. Write each step as an action starting with a verb, in the order it is done. The key point column holds what makes the step safe, right or easy, such as "torque to 25 Nm" or "check the seal is seated all the way round", and the reason column says why, which is what helps people follow it when nobody is watching. Checks and records turn the SOP into something that can be audited; the revision history shows what changed and why.
An SOP example: starting up a filling line
| Step | Action | Key point | Reason |
|---|---|---|---|
| 1 | Confirm the line clearance record is signed | Previous product and labels removed | Prevents mix-ups |
| 2 | Fit the change parts for the product | Match the colour code on the parts board | Wrong parts cause jams and short fills |
| 3 | Run ten containers and check fill weight | Within the limits on the product specification | Underfill is a legal issue; overfill is waste |
| 4 | Check the label and date code on the first container | Against the batch sheet | Wrong date code means a product withdrawal |
| 5 | Record the start-up checks and release the line | Supervisor signs the record | Evidence the line was right before production |
Header: SOP-FL-004, revision 3, owner: filling team leader, approved by: production manager. Checks: fill weight every 30 minutes, label check at every reel change. Records: start-up sheet kept with the batch record.
Which SOP format should you use?
A step-by-step list, as above, suits most routine tasks. A hierarchical format, with sub-steps under each main step, suits longer tasks with decisions inside them, such as a changeover. A flowchart suits processes with several branches, such as handling a failed check. Many sites use the step table for the work and add a small flowchart for the reaction plan.
How do you write an SOP with this template?
- Pick one task and the person who does it best.
- Watch the task being done and draft the steps, key points and reasons at the workplace.
- Fill in the header, purpose, scope, responsibilities, materials and PPE.
- Add the checks, the reaction to a failed check and the records.
- Test it: someone who did not write it does the task from the draft. Fix what they stumble over.
- Approve it, train the people who do the task, and set a review date.
An effective SOP stays alive after that. Review it after any incident, defect or improvement, check it is followed through layered process audits and leader standard work, and keep it where the work is done, not on a shared drive nobody opens.
Step by step
- Pick the task. One task and the person who does it best.
- Draft at the workplace. Watch the task and write the steps, key points and reasons where it is done.
- Complete the sections. Header, purpose, scope, responsibilities, materials and PPE, checks, reaction plan and records.
- Test the draft. Someone who did not write it does the task from the draft; fix what they stumble over.
- Approve, train, review. Approve it, train the people who do the task, set a review date and audit that it is followed.
A worked example
A drinks bottling site found that start-up checks were done differently on each shift: one checked fill weight on five containers, another on twenty, and nobody checked the date code. The filling team leader and two operators wrote one SOP in this format at the line, tested it with a new starter, and the production manager approved it. Layered process audits now check that the start-up record is complete, and a missed date code check became an action within a week of the SOP going live.