Two professionals discuss workplace documents and a laptop during a meeting.

The plan named a role, not a task

Light duties in the warehouse is not a plan. It is an aspiration. Nobody on the warehouse floor at six in the morning knows what it means, so the default happens: the worker stands around, or does their old job badly, or is sent home.

The person who decides was never in the room

Plans are agreed with human resources, or with a return to work coordinator, or with a manager who attended the meeting. The person who actually decides what the worker does that morning is a shift supervisor who was not there and has not seen the plan.

By the time anyone notices, the pattern has set and the worker has learned that the plan is not real.

The roster made it impossible

Four hours a day, three days a week, sounds reasonable in a meeting room. It is not always compatible with a twelve-hour shift pattern, a site that runs nights, or a worker who relies on a lift from a family member who works days.

Discovered in week four, failed in week one

A four-weekly review is a compliance rhythm, not a management one. Almost every failed graduated return failed in the first few days and was discovered a month later, by which point the employer has drawn conclusions, the worker has drawn conclusions, and the file records a problem that is not the problem.

None of this is exotic. It is the ordinary friction of a plan meeting a workplace, and it is the reason the same well-drafted plan succeeds at one site and fails at another.

Building a return to work plan that survives contact with an actual workplace, and catching it early when it does not, is a large part of what we do on every file.