4.3 Safe Systems of Work (SSoW)

4.3 Safe Systems of Work (SSoW)

Quick Answer: A safe system of work (SSoW) is a formal method of carrying out a task that turns risk-assessment findings into a safe sequence of steps, roles, controls, and emergency actions. It is essential for high-risk, non-routine, or complex work and only works when people are competent and supervised.

Risk assessment tells you what can go wrong and what controls are needed. Those controls do not implement themselves. For many jobs — especially non-routine or high-hazard work — managers need a written, taught, and enforced method: the safe system of work. In ERICPD terms, SSoW is a core Control (administrative) measure.

Definition — formal method, safe sequence

A safe system of work is a formal, systematic way of doing a job so that residual risks are controlled throughout the task. It sets out how the work will be done safely from preparation to completion and handback, not only what PPE to wear.

Key features:

• Based on risk assessment (and method statements where used)
• Describes a logical sequence of safe steps
• Names who does what and what competence is required
• Integrates engineering controls, isolation, PPE, and emergency plans
• Is communicated, understood, and followed
• Is reviewed when the job, plant, or people change

An SSoW is more than a vague instruction such as “take care” or “use common sense.” Common sense is not a system.

Why informal custom is not enough

Many workplaces “have always done it this way.” Informal methods fail when:

• The task is infrequent so memory fades
• Contractors or new staff do not share tribal knowledge
• Several trades must coordinate (isolation, hot work, entry)
• A single mistake has severe consequences
• Production pressure tempts shortcuts

Writing the system down forces managers to think the job through, spot missing controls, and train people consistently.

When is an SSoW needed?

Not every routine low-risk task needs a lengthy document. Prioritise SSoW where risk or complexity is high:

For simple routine work with low residual risk, shorter procedures, training, and supervision may be enough — but if something feels “obviously dangerous,” formalise it.

Typical contents of an SSoW

Exact templates vary by organisation. Managing Safely expects you to know the usual ingredients:

Isolation deserves special attention

Many fatal incidents happen because plant was not isolated or isolation was incomplete. A good SSoW states:

• What energy sources exist (electrical, mechanical, pneumatic, hydraulic, thermal, chemical, gravity)
• How each is isolated and proved safe (prove dead, depressurise, support loads)
• Who controls locks/tags
• How work resumes only after controlled reinstatement

SSoW, training, and supervision — the three-legged stool

A written document alone is not a safe system. Three things must work together:

1. Documented method — clear SSoW / procedure / method statement
2. Training and competence — people understand why steps exist and can perform them
3. Supervision and monitoring — managers check that the system is used under real pressure

If any leg is missing, residual risk rises. A brilliant SSoW ignored on night shift is paper, not control. Under ERICPD, training and time limits sit under Control; checking compliance edges into Discipline.

Manager behaviours that make SSoW real

• Involve experienced workers when writing the method (they know the shortcuts and traps)
• Brief the team before the job starts; check understanding, not just signatures
• Watch the first run of a new method; correct gaps immediately
• Stop work if conditions leave the SSoW’s assumptions (different plant state, missing kit, wrong people)
• After incidents or near misses, update the SSoW — do not only retrain on the old version
• Audit whether contractors follow the host’s system or an approved equivalent

SSoW and risk assessment — relationship

Exam point: An SSoW does not replace risk assessment. Assessment comes first (or is reviewed); the SSoW implements the controls. For exceptional high-risk steps, a permit to work may further authorise the residual-risk window.

Worked example — clearing a jam on guarded plant

Without SSoW: operator opens a guard while machine is live, reaches in, serious injury.

With SSoW:

1. Stop production request and inform supervisor
2. Isolate power and apply lock-off; prove dead
3. Only then open interlocked guard
4. Use designated tools; never hands near residual stored energy
5. Clear jam; check no tools left inside
6. Close guard; remove locks under controlled procedure
7. Test run clear of personnel; hand back to production

The sequence is the control. PPE still helps, but isolation order saves lives.

Common failures

Manager checklist — building or reviewing an SSoW

1. Is there a current risk assessment for this task?
2. Is the task high-risk, non-routine, or complex enough to need a formal SSoW?
3. Does the document cover scope, hazards, competence, isolation, sequence, PPE, emergencies, and completion?
4. Are permit requirements explicit where relevant?
5. Have workers been trained and can they demonstrate the method?
6. Is supervision planned for critical steps?
7. How will we know the system is being followed (observations, audits, PTW records)?
8. What triggers a review (incidents, plant change, new people, audit findings)?

Master SSoW and you are ready for permits to work — the tighter authorisation layer for specific high-risk activities within a defined time window.