How TPAs and Brokers Use RTW Tools as a Client-Service Differentiator

The Claim That Falls Through the Cracks Between Renewals

Picture this: a manufacturing client of yours has a shoulder injury open in March. The treating physician approves light duty in April. The employer accepts the transitional assignment, the worker comes back on modified duty — and nobody files the state reimbursement application. The one-year window runs out quietly. The money is simply gone.

That scenario is not unusual. It happens at employers who manage workers' comp claims manually, who rely on a carrier portal that resets at renewal, or who assume their adjuster will prompt them. None of those assumptions hold reliably across a book of five, fifteen, or fifty clients.

For a TPA, broker, PEO, or safety consultant, that gap is the service problem you are positioned to solve — and the place where return-to-work documentation becomes a tangible retention argument, not a talking point. When you can show a client, in writing, that you recovered reimbursement dollars they would otherwise have left on the table, and that you documented their transitional assignments in a format that survives a carrier audit, you have moved from relationship vendor to operational partner.

This article explains how intermediaries structure RTW management across a book of clients — what the workflow looks like, what reporting matters, and what to look for in tools built for multi-client use.

---

Why RTW Documentation Is Harder Across a Book Than at a Single Employer

A single employer managing RTW has one set of state rules, one carrier contact, and one injury log. A TPA or broker managing RTW across twenty clients has twenty carriers, potentially eight or more active states, multiple renewal dates, and no single place where a missed transitional-duty day surfaces before it costs someone money.

The structural problems compound in predictable ways:

Carrier portals are client-specific and carrier-specific. Documentation and light-duty records stored in a carrier's system belong to that carrier relationship. When a client switches insurers — which happens — the RTW history, job descriptions, and reimbursement records do not transfer. The employer starts over, and so do you.

Reimbursement windows are unforgiving. Washington State's Stay-at-Work program requires the reimbursement application to be submitted within one year after the light-duty work is completed, per WA L&I (2025). Oregon's Early Return-to-Work (EAIP) program covers up to 66 work days within a consecutive 24-month period, per OR WCD (2025). Both windows run whether or not anyone is tracking them centrally. A broker managing a dozen Washington employers has a dozen independent one-year clocks running simultaneously.

Eligibility conditions are granular and easy to miss. In Washington, a light-duty day worked outside the attending provider's approved hours is ineligible for reimbursement — for example, if the provider approves four hours and the worker is present for six, that day does not qualify, per ERNwest (2025). That rule is invisible unless the coordinator who built the transitional job description also documented the approved hours and cross-checked timesheets.

ADA confidentiality creates coordination complexity. When medical restrictions travel between a TPA's adjuster, a broker's account team, and the employer's supervisor, the rules require that supervisors receive restriction and accommodation information only — not the underlying diagnosis (EEOC via Gordon Feinblatt, 2024). Managing that boundary across multiple client contacts, in writing, requires a documented workflow rather than informal email chains.

For multi-client intermediaries, these problems do not scale away with volume. They scale up.

---

What a Multi-Client RTW Workflow Actually Requires

The operational core of RTW management is the same whether you are serving one employer or fifty: document the transitional job description, get attending-provider written approval, track days worked against the approved restrictions, and file the reimbursement application before the window closes. The multi-client layer adds coordination, reporting, and audit-readiness requirements on top.

A structured case file per employer per claim. Each case needs a dated record of the job description submitted to the provider, the provider's written approval, the light-duty start date, the days worked (with hours logged against the approved schedule), and the reimbursement application with its submission date and confirmation. That record needs to survive the client's carrier change, because the audit exposure belongs to the employer, not the carrier.

State-rule awareness by claim, not by client. A single PEO client may have workers injured in Washington, Oregon, Texas, and Ohio within the same policy year. Each state program has distinct parameters:

State	Wage Reimbursement	Day Cap	Application Deadline
Washington SAW	50% of base wages	120 days worked (injuries on/after Jan 1, 2025)	Within 1 year after light-duty work is done
Oregon EAIP	50% of gross wages	66 work days	Within 24-month consecutive window
Texas BFOE	No wage reimbursement; benefit-suspension mechanism	N/A	BFOE must be written; carrier may reduce benefits on the earlier of rejection or the 7th day after deemed receipt (deemed 5 days after mailing)
Ohio BWC	Transitional Work Grants $3,700–$8,200 (effective July 1, 2023) by employee count	Grant-funded, not per-claim wage reimbursement	Re-apply every 5 years

Sources: WA L&I (2025); OR WCD (2025); 28 TAC §129.6 (2024); OH BWC via Dayton Chamber (2021) and Ironton Tribune (2023).

A workflow that does not track which state program applies to each claim — and what that program's specific documentation requirements are — will miss reimbursement for the same reason the shoulder-injury case described in the opening was missed: no one was watching the right clock with the right checklist.

Reimbursement-recovery reporting, per client. The retention argument for RTW service depends on being able to demonstrate what you recovered. A broker who can show a client a line-item summary — three claims, two SAW applications submitted, reimbursement recovered, one application pending — has a tangible renewal conversation. A broker who cannot produce that summary has provided a service the client cannot see or value.

Audit-trail documentation that travels with the employer. Carrier audits, state program audits, and OSHA 300 log reviews may occur years after a claim closes. The documentation needs to be accessible to the employer regardless of which carrier is currently on risk. That means the record cannot live exclusively in a carrier portal.

---

How RTW Tools Support Multi-Client Service Delivery

The distinguishing capability for multi-client intermediaries is cross-client visibility with per-client segregation. You need to see the whole book at a portfolio level — open cases, reimbursement windows closing within 30 days, missing provider approvals — while maintaining clean separation between clients so that one employer's data is not accessible to another.

A tool built for this environment supports:

• Per-employer, per-claim case files that persist through carrier changes and are owned by the employer, not the insurer.
• State-program parameter awareness embedded in the workflow — the tool surfaces the applicable reimbursement window and documentation checklist for the state of injury, rather than requiring the coordinator to look it up manually each time.
• Duty-matching that is explainable and acted on by a person. Transitional job descriptions should match the injured worker's physical restrictions against available modified tasks and produce a ranked, documented recommendation. That recommendation is reviewed and approved by the coordinator and the attending provider — never auto-assigned. The paper trail reflects the human decision.
• Reimbursement-application assembly that pulls the documented days, approved hours, and wage data into the format required by the state program, reducing the assembly time per application and the risk of a documentation error that delays or disqualifies the claim.
• Cross-client reporting that produces a per-client reimbursement summary, an open-case list, and a window-expiry alert — the outputs you need to demonstrate the service's value at renewal.

For a deeper look at how case management workflows are structured at the claim level, see the return-to-work case management guide. For an overview of how portfolio-level RTW management differs from single-site operations, the multi-site RTW portfolio management article covers the coordination layer in more detail.

---

The Carrier-Bundled Tool Problem for Intermediaries

A common default is to rely on whatever RTW tools the client's carrier provides. For an individual employer with a stable carrier relationship, that arrangement is workable at the margins. For an intermediary managing a book across multiple carriers, it creates a fragmentation problem that compounds over time.

Carrier-bundled tools are built around the carrier's claim-closure interest, not the employer's program continuity. The job descriptions, transitional-duty records, and reimbursement history stored in a carrier platform belong to that policy relationship. At renewal, that data does not transfer to the new carrier — and in a competitive market where employers shop coverage, renewals happen. Each time a client changes carriers, the RTW history resets, the documentation evaporates from your view, and the new carrier's tool starts from scratch.

For a TPA or broker whose retention argument depends on demonstrating the cumulative value of the RTW program over time — reimbursement recovered across multiple years, EMR trajectory supported by documented medical-only claim handling, audit-ready files for a three-year experience window — a carrier-dependent tool undermines the story you are trying to tell. The carrier-bundled RTW tools vs. independent platforms article covers this tradeoff in more detail.

The solution is a tool the employer (or the intermediary on behalf of the employer) owns independently of any carrier. That portability is structural — it means the record is available for the audit that arrives two years after the claim closed and two carriers ago.

---

What to Evaluate When Selecting RTW Tools for a Multi-Client Practice

When reviewing tools for multi-client RTW management, the RTW software buyer's guide provides a full evaluation framework. For intermediaries specifically, the critical criteria are:

Multi-employer architecture. Can the tool maintain separate case files and separate user access for each employer client, with no cross-client data exposure? This is a basic data-governance requirement for any TPA or broker managing client information.

Carrier independence. Is the case record owned by the employer and accessible to you regardless of which carrier is currently on risk? Or does it live inside a carrier portal?

State-program rule coverage. Does the tool surface the applicable reimbursement parameters and documentation checklists for the states where your clients have injuries? Or does the coordinator have to maintain that knowledge manually?

Reimbursement-assembly capability. Can the tool produce the documentation package required for a WA SAW, OR EAIP, or TX workplace-modification application? Or is it a document repository that still requires manual assembly?

Reporting outputs. Can you produce a per-client reimbursement-recovery summary, an open-case list, and a window-expiry alert in a format you can share with the client at renewal?

Scope clarity. The tool should document and track the RTW process — it should never adjudicate a claim, determine benefit eligibility, or replace the attending provider's judgment. Any tool that implies auto-assignment of workers to transitional duties or auto-filing of claims documents should be evaluated skeptically; those functions require human review at every step.

---

Making RTW Documentation a Visible Service Deliverable

The final piece is communication. RTW documentation is operationally valuable, but it only becomes a retention argument when the client can see what was done and what it recovered.

At a minimum, a multi-client RTW practice should produce:

1. A case-open summary for each new transitional assignment — the job description submitted, the provider approval received, the light-duty start date, and the applicable reimbursement program.
2. A mid-assignment check at 30 days or at the program's midpoint — days worked to date, days remaining in the reimbursement window, any restriction changes from the provider.
3. A close-out report per claim — total days worked on transitional duty, reimbursement application submitted (with date and confirmation), and outcome when available.
4. An annual client summary — all claims with transitional-duty assignments during the policy year, reimbursement recovered or pending, and open cases carrying into the next year.

That reporting cadence turns an operational process into a documented service. It is the difference between a client knowing they have RTW support and a client being able to quantify what that support returned.

---

Start Managing RTW Across Your Client Book

Transitional Duty Manager is built for employer-side RTW documentation and tracking — carrier-independent, state-program-aware, and structured for multi-employer use. It documents the process, tracks the reimbursement windows, and produces the per-client reporting that makes RTW service visible at renewal.

View pricing for multi-client access or start a free trial to see how the workflow runs across a book of clients. If you are evaluating the complete documentation package for a new client program, the RTW Program Kit — Complete includes the job-description templates, provider-approval forms, and reimbursement-application checklists your coordinators need to run the process from day one.