
By Rovaryn Digital · 10 min read
The Problem Is Rarely the Injury — It's the Gap Between Desks
A workers' comp claim opens on a Monday. The HR generalist emails the safety manager to ask who is handling it. The safety manager assumes HR is coordinating with the supervisor. The supervisor hasn't been told anything except that the employee is out. By Thursday, the attending provider has faxed a work-status report with restrictions, and it's sitting in a shared inbox that three people monitor and none of them own.
That one week of drift costs more than most employers realize. A case that could have moved to a light-duty assignment in days instead accumulates lost-time indemnity, builds toward a modifier impact, and leaves the injured worker without a clear point of contact — which tends to extend the absence further.
The scenario above is not a failure of intent. Every one of those people was willing to help. The failure was structural: no one had been assigned a specific, unambiguous step at the moment the claim opened.
This article maps return-to-work roles and responsibilities across the four functions that typically share a transitional duty program — HR, safety, supervisors, and risk — so that every handoff has a named owner before the next claim opens.
Why Role Clarity Is a Program Prerequisite, Not a Nice-to-Have
A transitional duty program is a chain of handoffs. Each step depends on someone completing the prior one on time and passing the right information — not all the information, just the right information — to the right person. When ownership is ambiguous, two failure modes appear with roughly equal frequency:
Duplication. Two people attempt the same step independently, produce conflicting documents, and create confusion for the treating provider or carrier.
Abandonment. Each person assumes the other is handling it. Neither does.
Both delay the return date. Both create gaps in the documentation record that become problems if the case is later disputed or audited.
Role clarity also governs the ADA medical-confidentiality line — arguably the highest-stakes boundary in a transitional duty program. Federal requirements under the ADA specify that medical information must be kept on separate forms, in a separate medical record, accessible only to personnel with a legitimate business need. Supervisors and managers are entitled to know the restrictions and accommodations — not the diagnosis, not the treatment, not the mechanism of injury in clinical terms. That boundary has to be built into the role map structurally, not left to the judgment of whoever happens to be in the room. For a detailed treatment of what can and cannot be shared at each level, see our guide to ADA medical confidentiality in RTW programs.
The Four Functions and What Each One Owns
The descriptions below assume a mid-sized employer — roughly 50 to 500 employees — without a dedicated full-time RTW coordinator. At smaller operations, one person often holds more than one of these roles. At larger operations, each function may have multiple staff. The ownership principles hold either way; only the headcount changes.
HR: Program Ownership and Medical-Record Custody
HR's role in a transitional duty program is administrative and structural, not supervisory or medical. HR owns:
- Program governance. The written transitional duty policy, the procedure for activating a case, and the documentation templates are HR artifacts. HR ensures they exist, are current, and are accessible to everyone in the chain.
- Medical-record custody. The work-status report from the attending provider, the signed release, and any restriction documentation belong in a separate, controlled medical file — not the personnel file, not a shared drive folder. HR typically holds custody of this file and controls access. Under ADA requirements, that access is limited to personnel with a direct operational need.
- Accommodation process. When a restriction triggers an ADA interactive-process obligation (not every restriction does, but many do), HR coordinates that process — documenting the request, facilitating the dialogue, and keeping the record.
- Leave integration. HR tracks how transitional duty interacts with FMLA, state leave laws, and any employer-sponsored paid-leave program. These intersections are fact-specific; HR ensures they are documented and reviewed with counsel as needed.
What HR does not own: day-to-day supervision of the transitional duty assignment, physical task observation, or claim-file management with the carrier.
Safety: Job Analysis and Task Matching
Safety's contribution is operational and technical. Safety owns:
- Physical demands analysis. A transitional duty assignment is only defensible if someone has documented the physical requirements of the proposed modified job — the weights, postures, durations, and environmental conditions — and verified that they fall within the restrictions the provider has approved in writing. That analysis is a safety function.
- Transitional task inventory. Safety (often in coordination with operations) maintains or builds the list of available light-duty or modified tasks across departments. This inventory is the raw material the coordinator or HR uses to match a restriction profile to an assignment.
- Worksite modification. When a modification to equipment, posture, or workflow is needed to bring a task within restriction limits, safety designs and documents it. State programs in Washington, Oregon, Ohio, and Texas each offer reimbursement or grant funding for qualifying modifications; safety's documentation of what was changed and why is the evidentiary record for those applications.
- Incident documentation. The first report of injury, the hazard investigation, and any corrective actions are safety records. They feed the carrier's claim file and the employer's experience record. Accuracy at this step affects everything downstream.
What safety does not own: the medical file, the accommodation dialogue, or the carrier communication. Safety provides technical input; HR and risk handle the administrative and financial channels.
For a fuller treatment of how to build and maintain the transitional task inventory, see how to build a transitional duty program.
Supervisors: Daily Oversight and Restriction Compliance
The supervisor is the closest person to the work, which makes the supervisor both the most operationally important actor and the one most exposed to confidentiality errors.
Supervisors own:
- Assignment confirmation. Once HR and safety have confirmed a match between the employee's restrictions and a transitional task, the supervisor confirms that the task is genuinely available, that the hours align with the approved schedule, and that the worksite is prepared.
- Daily compliance monitoring. The supervisor observes whether the employee is working within the approved restrictions — not as surveillance, but as a safety function. If the employee is performing tasks outside the approved job description or working hours beyond those the provider approved, the supervisor flags it immediately. A day worked outside approved parameters is not a reimbursable day under state programs and may represent a safety and liability exposure.
- Communication upward. If the restriction changes, if the employee reports difficulty with the assignment, or if the transitional task becomes unavailable, the supervisor reports that change to the RTW coordinator or HR — the same day, not at the next scheduled check-in.
What supervisors do not own: the medical record, the diagnosis, or the accommodation decision. The supervisor's information set is bounded to restrictions and schedule — what the employee can and cannot do on shift. A supervisor who asks about the diagnosis or treatment is crossing the ADA confidentiality line, regardless of intent. See the supervisor's role in transitional duty for a practical guide to that boundary conversation.
Risk: Carrier Coordination and Program Economics
Risk (or whoever manages the workers' comp program — this may be an HR director, a CFO, or a TPA relationship manager at smaller operations) owns the financial and carrier-facing dimensions of the RTW case.
Risk owns:
- Carrier communication. The carrier's claim adjuster needs to know when a transitional duty assignment begins, what restrictions are being accommodated, and when the employee returns to full duty. Timely, accurate communication affects indemnity reserve management and the eventual claim closure.
- State-program applications. Washington's Stay-at-Work program, Oregon's EAIP, Ohio's Transitional Work Grant, and Texas's workplace-modification fund each have application deadlines, documentation requirements, and approved-format submissions. Risk assembles the application, working from documentation that safety and HR have produced. Missing a filing window forfeits reimbursement that cannot be recovered retroactively.
- EMR and premium monitoring. The experience modification rate is a three-year rolling calculation. A lost-time claim affects that calculation differently than a medical-only claim. Risk tracks how active cases are trending and whether transitional duty is converting lost-time cases to medical-only before the experience period closes.
- Audit readiness. If the carrier or a state agency audits the RTW program, risk coordinates the response and ensures the documentation record HR and safety have maintained is complete and producible.
What risk does not own: the accommodation decision, the physical task design, or the daily supervision of the assignment.
A Practical RACI Summary
The table below maps the core RTW activities to the function that owns each one. "R" = responsible (does the work); "A" = accountable (signs off); "C" = consulted; "I" = informed.
| Activity | HR | Safety | Supervisor | Risk |
|---|---|---|---|---|
| Maintain written RTW policy | R/A | C | I | C |
| Receive and file work-status report | R/A | I | I | I |
| Physical demands analysis of transitional task | C | R/A | C | I |
| Match restriction profile to available task | R/A | C | C | I |
| Confirm task availability and schedule | C | C | R/A | I |
| Daily restriction-compliance observation | I | C | R/A | I |
| Accommodation documentation (ADA) | R/A | I | I | C |
| Carrier communication and reserve updates | C | I | I | R/A |
| State-program reimbursement application | C | C | I | R/A |
| Escalate restriction change or assignment gap | I | C | R | A |
This matrix is a starting point, not a final answer. At some operations, safety runs the RTW coordinator function entirely. At others, a TPA fills the risk column. Adapt the ownership assignments to your structure — then write them down, because an unwritten RACI is not a RACI.
The RTW Coordinator: Where All Four Functions Connect
In organizations where someone carries a formal RTW coordinator title, that role sits at the center of this matrix — not above it. The coordinator does not replace HR's medical-file custody, safety's task analysis, the supervisor's daily observation, or risk's carrier communication. The coordinator facilitates the handoffs: tracking case status, moving documents between functions at the right time, flagging delays, and ensuring that no step is orphaned.
If your organization does not have a named RTW coordinator, the practical question is which existing role absorbs that facilitation function. The answer varies; what matters is that someone owns it explicitly. For a detailed look at what the coordinator role entails day to day, see the RTW coordinator role guide.
Making the Map Operational
A role map on paper becomes a real program when two conditions are met: everyone named in the map knows they are named in it, and the handoff triggers are defined in advance.
Before the next claim opens, take these steps:
- Identify the person who will fill each of the four functional roles for your operation. Name individuals, not job titles — titles change and people need to know who to call.
- Define the trigger for each handoff. When does HR notify safety? When the first report of injury is filed, or when the work-status report arrives with restrictions? When does safety notify the supervisor? When the task match is confirmed in writing, not before.
- Confirm where the medical file lives and who has access. If you are not confident that the restriction documentation and the personnel file are separated, fix that before the next claim.
- Confirm whether your state has an active RTW reimbursement program and what its application deadline is. Risk needs a calendar reminder, not a note to look into it later.
If you are building the underlying program infrastructure — the policy, the forms, the task inventory, the procedure — the RTW Program Kit – Complete bundles the core employer-side documents into a structured starting point.
Stay Current on RTW Practice
Return-to-work program requirements shift with state legislation, ADA guidance updates, and carrier practices. Our newsletter covers those changes as they happen — practical, practitioner-focused, without the noise.
Subscribe below to receive new articles, state-program updates, and documentation guidance as they publish.
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

