What to Do When a Light-Duty Assignment Falls Through

When a Light-Duty Assignment Becomes Unavailable Mid-Case

The line that made the sorting-table task possible shut down for a retooling, and nobody told the RTW coordinator until the worker showed up for his modified shift and had nowhere to stand. He'd been three weeks into a six-week light-duty assignment, restrictions on file, supervisor sign-off documented, everything clean. Now the task itself was gone, the worker was standing in a break room waiting for someone to tell him what to do, and the clock on his wage-reimbursement eligibility was still running whether anyone was tracking it or not.

This is one of the most common failure points in a transitional duty program, and it rarely gets attention until it happens. Most RTW processes are built to handle the beginning of a case — intake, restrictions, the first duty match — and assume the assignment holds steady until the worker is released. It doesn't always. Lines shut down, supervisors change, seasons end, a task bank entry turns out to violate a restriction nobody caught the first time. When a light duty assignment is unavailable and no one has a documented next step, the case doesn't pause — it just goes undocumented, which is worse. This article walks through what to capture and what to do in the first hours after a task falls through, so the gap doesn't become a reimbursement problem or a compliance one.

Why Light-Duty Tasks Disappear

A light-duty assignment can fall through for reasons that have nothing to do with the worker or the injury:

• Operational change. A line closes, a shift is cut, a department is restructured, and the specific task the worker was matched to no longer exists in that location.
• Supervisor turnover. The person who agreed to host the modified assignment leaves or is reassigned, and no one else on the floor was briefed on the accommodation.
• A task turns out to be unsafe or non-compliant. Sometimes a task that looked fine on paper — in a task bank entry, or against a physical-demands checklist — doesn't hold up once observed in practice. A "sedentary inspection" task might require more standing, reaching, or repetitive motion than the write-up suggested.
• The physician narrows the restriction. A follow-up visit can tighten a restriction that the original task was matched against, even if the task itself hasn't changed.
• Seasonal or project-based work ends. Some light-duty tasks exist only because a specific short-term project created temporary capacity — inventory counts, a facility move, a packaging surge. When the project ends, so does the task.

None of these are failures of the RTW program. They're normal operational churn. The failure only happens if there's no documented process for what happens next.

The First 24 Hours: What to Document Before You Reassign

Before jumping to a replacement task, capture what happened and when. This record matters for two reasons: it protects the integrity of the case file if anyone — an auditor, a claims adjuster, the worker's attorney — asks what happened during the gap, and it determines whether the time between tasks counts as worked time at all.

Document, at minimum:

1. The date and time the task became unavailable, and who identified it.
2. The reason, in plain operational language — "line 4 shut down for retooling," not just "task ended."
3. Whether the worker performed any work on the day the task disappeared. This matters directly for wage-reimbursement programs: Washington's Stay-at-Work program, for example, will not reimburse an employer for days the worker did not actually perform approved light-duty work, regardless of why. If the assignment ends mid-shift, the hours actually worked that day are what counts, not the scheduled hours.
4. The current restriction set on file, confirmed against the most recent physician documentation — not the version attached to the original, now-defunct task.
5. Any interim status — paid, unpaid, sent home, reassigned to an unrelated task temporarily — and who authorized it.

This is also the moment to check whether the worker's restriction window itself is approaching expiration independent of the task change. A task falling through sometimes surfaces a separate problem that had been quietly building — restriction dates running close to expiry without a scheduled follow-up. It's worth cross-checking against your restriction expiry and max-duration flags before assuming the only open issue is finding a new task.

Finding a Replacement Task Without Breaking the Duty Match

Once the gap is documented, the next step is finding a task that still matches the current restrictions — not a task that's simply available. This is where programs get into trouble: under time pressure, it's tempting to put the worker on "whatever's open" rather than re-running the match.

A sound replacement process looks like this:

• Pull the current, active restriction set — not the one attached to the original assignment, in case anything changed in the interim.
• Re-run the match against your task bank, the same way the original assignment was selected. If your task bank is thin or hasn't been updated since the last reorg, this is a good moment to refresh it — a documented, current task bank guide is the difference between a five-minute reassignment and a half-day scramble.
• Cross-check physical demand factors systematically, not from memory. This is exactly the gap that O*NET-based duty matching is built to close: standardized physical-demand data points — strength, posture, environmental conditions — checked against the restriction, rather than a supervisor's best guess about whether a task "seems okay."
• Get the new task approved through the same chain as the original — physician sign-off where required, supervisor confirmation, worker acknowledgment. A reassignment that skips the approval step creates a documentation gap that looks, on paper, identical to an assignment that was never authorized at all.
• Log a new assignment record with its own start date. Don't edit the old record to reflect the new task — that erases the history of what actually happened and when. Close out the original assignment with its end reason, then open a new one.

Treat a reassignment as a new assignment, not an edit to the old one. The moment you overwrite history to make the file look continuous is the moment the file stops being trustworthy.

Keeping Wage-Reimbursement Eligibility Intact Through the Change

Reimbursement programs generally key off actual approved work performed on a given day — not off the existence of a plan. That means a gap between tasks, if not handled carefully, can quietly cost reimbursement eligibility for days where no approved work occurred, even if the worker was willing and the employer was trying to find something.

The practical response is speed and clean records, not retroactive paperwork. If a task disappears on a Tuesday and a replacement isn't approved until Thursday, that gap is real, and padding the record to suggest otherwise is a bigger risk than the two lost days. Document the gap honestly, document the date the replacement task was approved, and keep the two assignment periods as separate, clearly dated entries. A clean record with an honest gap is far easier to defend than a record that's been smoothed over to look like nothing happened.

When No Replacement Task Exists

Sometimes there's genuinely nothing available that fits the current restrictions. That's a real outcome, not a documentation failure, as long as it's handled transparently:

• Document the search — what was considered and why it didn't fit the restriction.
• Loop in the physician if the restriction itself might need review.
• Follow your state's and your program's process for what happens when no transitional work exists — this typically shifts the case toward a different wage-replacement track, and the specific mechanics vary by jurisdiction and policy. Confirm the applicable rule with your state agency or TPA rather than assuming it mirrors a different state's process.
• If the worker declines an offered alternative that you believe is appropriate, that's a separate documentation track entirely — handled the same way as any other light-duty refusal, with its own written offer, response, and record.

Building a Process So This Doesn't Catch You Off Guard Next Time

A light-duty assignment falling through isn't rare — it's a normal part of running a transitional duty program over enough cases and enough time. The programs that handle it well aren't the ones that never lose a task. They're the ones with a documented, repeatable sequence: stop and log the moment the task ends, confirm the current restriction, re-run the match, get it re-approved, and keep the file's timeline honest rather than smoothed over.

If you're managing this across more than a case or two at a time, doing it consistently by memory is where things slip. The Transitional Duty Case Tracking Workbook is built around exactly this kind of event — tracking assignment start and end dates, reassignment reasons, and approval status in one place, so a disappearing task doesn't become a disappearing record.