By Rovaryn Digital · 8 min read
The Day the Coordinator Leaves
A mid-sized warehouse operation had eight open light-duty assignments when its RTW coordinator gave two weeks' notice. The transitional job descriptions were in a personal email thread. The restriction windows were tracked in a spreadsheet only she knew how to read. The approved-hours log for one employee — the one closest to triggering the employer's Stay-at-Work reimbursement window — existed in a paper folder in her desk drawer.
Two weeks is not enough time to reconstruct four months of institutional knowledge. The incoming coordinator — an HR generalist promoted sideways — spent her first month answering questions she had no way to answer, guessing at approval dates, and hoping a carrier audit didn't land until she found her footing.
This scenario is not unusual. RTW coordination is one of the more exit-prone roles in a mid-market HR or safety department: the work is demanding, the liability is real, and the title rarely comes with commensurate pay. The question is not whether your organization will experience RTW coordinator turnover — it is whether the program survives it intact.
This article explains how to design an RTW program that belongs to the organization, not to the person holding the coordinator title. By the end, you will have a concrete checklist for making case files, task banks, restriction logs, and audit trails durable across any personnel change.
Why RTW Programs Are Fragile by Default
Most RTW programs at smaller and mid-market employers were not designed — they accumulated. A claim came in, a coordinator improvised a response, and the improvisation became the de facto process. Over time, that improvisation lives almost entirely inside one person's head or personal files.
The operational risks of this fragility are concrete:
Open cases stall. An injured worker on light duty is still a worker the employer is responsible for managing. Restriction windows expire. Approved-hours limits must be honored. Physician-approved task descriptions can lapse if a follow-up isn't scheduled. When the person tracking all of this leaves, active cases lose their thread. RTW likelihood drops sharply after extended time off work — gaps in coordination during a transition can extend time away from full duty in ways that compound long after the new coordinator is oriented.
Reimbursement windows close. State programs like Washington's Stay-at-Work program and Oregon's Early Return-to-Work program have filing deadlines tied to dates of work, not dates of awareness. If the incoming coordinator does not know a program-eligible claim exists — or cannot reconstruct the approved days worked — reimbursable wages go uncollected. These are not small sums; the library figures are substantial, and the filing deadlines are fixed regardless of who is sitting in the coordinator's chair.
Carrier audits expose gaps. A carrier or TPA requesting documentation of a transitional duty assignment does not accept "the previous coordinator had that." The audit trail must be complete, timestamped, and accessible by whoever is responding to the request — whether that is the original coordinator or someone who started last month.
Supervisor confusion fills the vacuum. When coordination breaks down, supervisors default to what they know: either keeping the injured worker at full duty beyond their restrictions, or telling them to stay home. Both outcomes carry cost and potential liability. Neither is a safe fallback.
What Makes a Program Coordinator-Proof
"Coordinator-proof" does not mean the coordinator is unimportant. It means the program's working memory — its case files, task descriptions, restriction logs, and process documentation — lives in a structure the organization controls, not in the coordinator's personal files, inbox, or memory.
The four components that accomplish this are:
1. A Written RTW Program Policy
A policy document is the first defense against institutional amnesia. It answers the questions a new coordinator will ask in week one: Who triggers the RTW process and when? Who approves transitional job descriptions? What is the employer's light-duty offer timeline? Who notifies the carrier?
A policy does not need to be long. It needs to be explicit about roles, timing, and decision authority — written as if the reader has never seen the program before, because eventually someone will read it for exactly that reason.
If you do not have a written policy, the RTW Program Kit — Complete includes a policy template designed for mid-market employers across manufacturing, construction, healthcare, and warehousing operations.
2. A Maintained Task Bank
A task bank is a pre-documented library of transitional duty assignments keyed to physical demands: sit/stand tolerance, lift limits, reach range, push/pull, and duration. When a physician-approved restriction arrives, the coordinator matches it against the bank rather than improvising from scratch.
The value of a task bank during turnover is significant: a new coordinator who inherits a well-organized bank can make defensible light-duty offers on week one, without needing to know the operation's full job matrix from memory. The departing coordinator's judgment about which tasks are appropriate is preserved in writing, in a form the incoming coordinator can use.
Task banks should be reviewed when physical operations change and updated any time a task description is approved by a treating physician — because that approval itself is a record worth keeping.
3. A Case File Structure That Anyone Can Navigate
Each open RTW case should have a file that a reasonable person could pick up and understand without prior context. That means:
- The injury date, claim number, and carrier contact on the cover
- A chronological log of every contact: when the employer reached out, when the physician responded, when the carrier was notified
- The current approved restriction, in writing, with the physician's signature and the effective date
- The transitional job description the physician approved, matched to the restriction
- A log of days worked under the transitional assignment, with hours, against the approved schedule — particularly important in states where reimbursement eligibility turns on approved-hours compliance
- Any documentation of offers made, accepted, or declined
- Upcoming deadlines: next physician appointment, restriction review date, program filing window
This structure exists so that when a coordinator leaves mid-case, the incoming coordinator — or a supervisor, or an attorney, or a carrier auditor — can reconstruct what happened and what needs to happen next without interviewing the departing employee.
4. A Handoff Protocol
Even with good documentation, an unplanned departure leaves gaps. A handoff protocol closes them by making the transfer of open cases a formal, time-bounded process:
- Case-by-case walk-through. The departing coordinator reviews each open case file with the incoming coordinator or interim point of contact, confirming that every field above is complete and current.
- Deadline audit. Every open case is checked for approaching deadlines — restriction review dates, program filing windows, offer-response deadlines — and those dates are flagged in whatever tracking system the organization uses.
- Carrier and physician notification list. Every active carrier contact and treating provider for open cases is documented so the incoming coordinator can establish contact immediately, not after spending a week hunting for a fax number.
- Supervisor briefing. Each supervisor managing a worker on transitional duty is told in writing that the coordinator contact has changed and who to reach with questions — this prevents supervisors from managing restrictions informally when they cannot reach the person they know.
When turnover is planned, this protocol takes a few hours. When it is unplanned, the protocol forces whoever is covering to conduct the same audit — on day one, not after a problem surfaces.
The Underlying Problem: Program-as-Person vs. Program-as-System
The scenarios above share a structural cause. When an RTW program lives primarily in a person — their email, their memory, their personal spreadsheet — it is not really an organizational program. It is an individual practice that happens to serve an organizational function.
Managing even two or three concurrent RTW cases exposes the limits of person-held programs quickly: tracking restriction windows, approved hours, filing deadlines, and carrier communications across multiple claims in a spreadsheet is feasible for a skilled coordinator who built the spreadsheet. It is nearly impenetrable for anyone who inherits it.
The structural solution is to move the program's working memory into a shared system that enforces the case file structure described above, tracks deadlines automatically, and produces the kind of audit trail a carrier expects — one that does not depend on the continuity of any single employee to remain coherent.
Transitional Duty Manager is built specifically for this problem. It gives mid-market employers a case-management structure where open cases, restriction logs, approved task descriptions, and filing-deadline tracking live in the organization's account, not in the coordinator's personal files. When a coordinator transitions out, the incoming coordinator logs in to a complete, current record of every open case — no archaeology required.
If your organization is still running RTW in a spreadsheet or shared drive, start a free trial and see what a system-held program looks like in practice.
What to Do Before the Next Coordinator Leaves
Even if your current coordinator is not going anywhere, the time to build continuity is before you need it. The checklist is short:
- Write the policy. One document, explicit about roles and timing, accessible to anyone in HR or safety.
- Build and maintain the task bank. Document transitional assignments by physical demand; update when operations change or a physician approves a new description.
- Standardize the case file. Every case, same structure, same fields — so any case can be handed off mid-stream without loss.
- Document the handoff protocol. Treat coordinator transition like any other operational procedure: steps, timeline, owner.
- Move tracking out of personal files. Email threads, personal spreadsheets, and desk-drawer folders are not organizational records. They leave with the person who created them.
The RTW program your organization runs exists to keep injured workers connected to productive work and to protect the organization's claim economics over time. That function is too important to depend on the tenure of any single employee.
Build the program so the organization holds it — and the coordinator can walk out without taking the program with them.
Get the next RTW guide in your inbox
Practical guides and WA Stay-at-Work updates — no spam.
Automate the full RTW workflow
Transitional Duty Manager replaces manual RTW documentation with O*NET duty matching, WA SAW reimbursement packet export, and an immutable audit trail.
See how it works
