By Rovaryn Digital · 10 min read
When the Coordinator Leaves, Does the Program Leave With Them?
Picture this: your RTW coordinator — the person who knows which carrier rep to call, which form goes to the state agency first, and which supervisor needs the most reminding about restriction compliance — gives two weeks' notice on a Monday morning. You have two open cases. One involves a restriction that expires in eleven days; the other has a state wage-reimbursement application deadline approaching. The knowledge to manage both of those cases lives almost entirely in that person's head.
This is the single most common way a return-to-work program collapses. Not a bad policy, not a hostile carrier — just turnover. The coordinator was diligent, but the program was built on relationships and memory rather than documented process. When they left, the cases stalled, the deadlines slipped, and the next hire spent the first month reconstructing what had already been built.
Defining the return-to-work coordinator role precisely — in writing, with clear inputs and outputs at every handoff point — is what converts a program from one person's expertise into organizational property. This article explains what the role actually covers, where the boundaries sit, and how to structure the handoffs so the program survives turnover.
What the Return-to-Work Coordinator Role Actually Covers
The return-to-work coordinator role is the operational center of an employer's RTW program. The coordinator does not adjudicate claims, determine benefit eligibility, set medical restrictions, or make legal compliance rulings — those authorities belong to the carrier, the treating physician, and qualified legal counsel, respectively. What the coordinator does is manage the employer's side of the RTW process: initiating contact, assembling documentation, tracking restriction windows, communicating with internal stakeholders, and making sure no deadline passes unnoticed.
In practical terms, the role spans five recurring functions:
1. Injury intake and early contact When an injury is reported, the coordinator is the employer's first mover. They confirm the injury report is filed with the carrier, initiate early contact with the injured worker (following the employer's established protocol), and open the case record. Early contact — a brief, supportive check-in within the first day or two — is a documented RTW best practice. The coordinator is responsible for making it happen consistently, not leaving it to the supervisor's judgment on any given day.
2. Transitional duty identification and offer Working from the treating physician's restrictions, the coordinator identifies which transitional duties are available, whether they fall within those restrictions, and whether a formal written offer should be made. This is a coordination and documentation function, not a medical determination. The coordinator does not decide what the worker can do — the physician does. The coordinator's job is to match what the employer can offer to what the physician has cleared, document that match, and present it correctly. For a deeper look at how that matching process works within a structured program, see our return-to-work case management guide.
3. Restriction tracking and timeline management Restrictions change. An initial restriction may be modified at the next provider appointment, expanded if recovery is slower than expected, or lifted entirely when the worker reaches maximum medical improvement. The coordinator maintains a running record of the current restriction status, the dates those restrictions were issued, when the next provider appointment is scheduled, and what transitional duty assignment is in place. This is the part of the role most likely to go wrong when it lives in someone's memory rather than a tracked case file.
4. State program documentation (where applicable) Several states operate employer-side wage-reimbursement programs — Washington's Stay-at-Work program, Oregon's Employer-at-Injury Program, Ohio's Transitional Work Grant, and Texas's modified-duty framework, among others. Where these apply, the coordinator is responsible for understanding the documentation requirements, submitting the correct forms to the correct agency, and meeting the filing windows. Missing a reimbursement deadline is a recoverable mistake — but only once. Repeated misses are a program failure. Always confirm the current form versions, deadlines, and program parameters directly with the administering state agency, as these details change.
5. Stakeholder communication The coordinator is the conduit between the injured worker, the direct supervisor, HR, the carrier's claim representative, and — through generated correspondence — the treating provider. Each of those relationships has a different communication register and a different set of things they need to know. The supervisor needs to know the restrictions and the approved schedule, not the diagnosis. HR needs to know the accommodation status for ADA recordkeeping purposes. The carrier needs to know when transitional duty starts and stops. Keeping those channels current, consistent, and documented is a core coordinator function.
Where the Role Ends: Boundaries That Matter
Scope creep in the coordinator role creates two distinct risks. The first is operational: the coordinator ends up doing work that belongs to someone else (claim adjudication decisions, HR disciplinary calls, scheduling decisions that require supervisor authority) and stops doing the work that is actually theirs. The second is legal: a coordinator who makes statements that could be read as medical or legal opinions, or who handles medical information outside the proper channels, creates compliance exposure for the employer.
A few boundaries worth writing explicitly into the role definition:
Diagnosis information stays out of supervisor conversations. The supervisor receives the restrictions and the accommodation, not the diagnosis or the underlying medical detail. This is an ADA requirement, not a best practice. Medical information must be kept in a separate medical record, accessible only to those with a legitimate business need. Supervisors are not among them for diagnostic detail.
The coordinator does not adjudicate the claim. If the carrier disputes compensability, that is a claims process. The coordinator may be asked to provide documentation; they are not a participant in the coverage decision.
The coordinator does not replace the physician's judgment. If a transitional duty assignment looks like it may exceed what the restriction allows, the coordinator flags it and seeks clarification — they do not decide unilaterally that the work is acceptable. The attending provider's written approval governs the assignment.
The coordinator does not make legal compliance determinations. They can flag that a situation may implicate ADA, FMLA, or a state program rule and route it to HR or counsel. They are not the authority on whether a specific situation is legally compliant.
These boundaries are worth stating plainly in the role description, not just in training. When a coordinator is new, they are most likely to drift into these areas by trying to be helpful.
The Handoffs That Break Programs
Most RTW program failures are handoff failures. Something that one person knew did not get transferred to the next person at the right moment. Here are the four handoffs that most commonly break:
Supervisor → coordinator (injury reported) The supervisor learns of the injury. Does the coordinator find out the same day? What information arrives with that notification — mechanism, affected body part, estimated work capacity, witness names? Without a defined intake trigger and a minimum data set, the coordinator may be starting a case days late with incomplete information.
Carrier/provider → coordinator (restrictions updated) The treating physician issues updated restrictions at each appointment. Does that information reach the coordinator in time to adjust the transitional duty assignment before the next scheduled shift? If the carrier's claims rep is the conduit, is there a standing protocol for how and when they pass restriction updates? A restriction change that arrives after the fact creates a documented compliance gap.
Coordinator → supervisor (transitional duty parameters) The coordinator has confirmed the transitional duty assignment and the restriction window. Does the supervisor know the exact parameters — approved tasks, hours, physical limits, and the date the assignment expires or is next reviewed? A supervisor who is guessing at what the coordinator approved is a supervisor who will unintentionally put the employer's documentation at risk. This handoff should produce a written document the supervisor signs or acknowledges. For more on what that supervisor relationship looks like in practice, see our guidance on the supervisor role in transitional duty.
Coordinator turnover → successor coordinator When the coordinator role changes hands, what transfers? If the answer is "whatever the outgoing coordinator thought to mention," the program is at risk. A proper transition requires: open case files with full restriction and assignment history, pending deadlines (state filings, provider appointments, assignment expiration dates), carrier contact information for each open claim, and the employer's written RTW policy and transitional duty job inventory. If any of those elements exist only in the departing coordinator's memory or personal files, the transition is incomplete.
Making the Role Organizational Property
The difference between a coordinator-dependent program and an organization-owned program is documentation infrastructure. The coordinator's expertise stays valuable — experience with how a particular carrier operates, judgment about when to escalate a case, understanding of which supervisors need more structured communication — but the program's continuity does not depend on that expertise remaining in the building.
Three structural decisions support this:
Define the case record standard. Every case should contain the same minimum set of documents in the same structure: injury report, restriction history (with dates), transitional duty offer letters, provider approvals, any state program forms, and a running case log of contacts and decisions. The coordinator maintains this record; the record belongs to the employer.
Document the role, not just the person. A written role description that specifies inputs (what triggers each function), outputs (what documentation each function produces), and handoff recipients (who receives each output) means a new coordinator can locate themselves in the process quickly. See RTW roles and responsibilities for a broader look at how the coordinator fits within the full program structure.
Separate the program's assets from the coordinator's tools. If case files live in the coordinator's personal email or a spreadsheet only they know how to navigate, the employer does not actually own those files in any operational sense. Program documentation, job task inventories, form libraries, and case records should exist in a system the organization controls, accessible to whoever holds the coordinator role at any given time.
Building that infrastructure from scratch is the hard part. Our RTW Program Kit — Essentials packages the foundational document templates — role definitions, intake checklists, transitional duty offer letters, case log formats — so employers can establish the standard without rebuilding it from a blank document each time. For a broader framework on how to structure the full program, see our guide to building a transitional duty program.
The Coordinator as Program Owner, Not Program Sole Practitioner
One final framing worth carrying into how this role is described internally: the coordinator is the program's operational owner, but not its sole practitioner. Supervisors play a defined role. HR plays a defined role. The carrier plays a defined role. The treating provider plays a defined role. The coordinator's job is to keep all of those participants informed and moving at the right moments — not to absorb every function that touches a case.
When the coordinator tries to do everything, two things happen: the program scales poorly beyond a handful of concurrent cases, and the organization's other participants never develop the competency they need to support the program when the coordinator is unavailable. A coordinator who has documented the role, trained the supervisors, and established clean handoffs has built something that works when they are out sick, on leave, or eventually promoted.
That is the measure of whether the return-to-work coordinator role has been built correctly: not whether the current coordinator is good at their job, but whether the program would still function if they were not there tomorrow.
Want this delivered as a monthly reference rather than a one-time read? Subscribe to the Transitional Duty Manager newsletter for practical RTW guidance sent directly to your inbox.
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
