Applying the Hierarchy of Controls to Ergonomic Risk

How to use the hierarchy of controls — elimination, substitution, engineering, administrative and PPE — to reduce ergonomic risk and musculoskeletal disorders in manufacturing.

Ergonomics programBeginner6 min read

Key takeaways

  • Higher-level controls remove or reduce the hazard at the source and are more reliable than relying on behaviour.
  • Engineering controls such as lift assists and adjustable workstations are the backbone of most ergonomic programs.
  • Administrative controls and PPE are useful supplements, not substitutes for redesign.
  • Re-score the task after every change to prove the risk has actually fallen.

The hierarchy applied to ergonomics

LevelErgonomic examplesEffectiveness
EliminationAutomate a heavy lift; redesign part flow to remove a reachHighest
SubstitutionLighter containers, smaller pack sizes, lighter toolsHigh
Engineering controlsLift tables, vacuum lifters, tool balancers, tilt fixtures, height-adjustable benchesHigh
Administrative controlsJob rotation, rest breaks, training, two-person liftsModerate
PPEAnti-vibration gloves, knee padsLowest
NIOSH has found insufficient evidence that back belts prevent back injuries in workers who have never been injured — do not rely on them as a control.

Using RULA scores to prioritize

Start with stations at RULA action level 4 (score 7) and action level 3 (scores 5–6). Consider how many people work the station, how many shifts it runs and any injury or discomfort history. This gives a defensible, data-driven priority list for your EHS and engineering teams.

Verify every change

After implementing a control, record the task again and re-score it with the same method. A before/after comparison makes improvements visible to leadership and helps the operators see that their feedback led to change.

Practical checklist

  • Score the current task and record the action level
  • Brainstorm at least one option at each level of the hierarchy
  • Prefer elimination, substitution and engineering options
  • Pilot with operators before rolling out
  • Re-score after the change and document the result