Food production
Named case study · Insight that changed the program
The rotation that wasn't rotating — and the redesign that fixed it.
How a body-region breakdown exposed a rotation that wasn't actually rotating — and drove a redesign that brought claims down.
Every site
platform now deployed across all Alliance facilities after the rotation redesign
Situation
Alliance Farmers' Produce ran job rotation on its production lines — the standard administrative control for spreading physical load across a shift — and expected it to bring injury claims down.
Complication
Despite the rotation, production-line claims weren't falling. On paper the workers were moving between tasks; the injuries said something else was going on.
Response
- Etiscope assessments revealed that the rotated tasks were still loading the same body regions — the rotation looked like variety but was biomechanically the same work.
- Management used the body-region breakdown to redesign rotation across genuinely different physical demands.
- The redesign was driven by evidence of where load actually fell, not by the task labels.
Outcome
Despite implementing job rotation, Alliance Farmers' Produce's production-line claims weren't falling. Etiscope assessments revealed the rotated tasks were still loading the same body regions. Management used the body-region breakdown to redesign rotation across genuinely different physical demands; injuries and claims fell. The platform is now deployed across all Alliance facilities.
How this generalises
Job rotation only works if the tasks rotated through load different body regions — otherwise it's the same exposure wearing a different name. The Alliance pattern shows why a body-region breakdown matters: it tells you whether a control you already trust is actually doing anything.
Solutions by industry →