By Rovaryn Digital · 11 min read
When the Carrier Leaves, So Does Your Program
Picture the scenario: your renewal comes up, your broker shops the market, and you move your workers' compensation policy to a new carrier. The premium savings are real. What you did not account for is what disappears on the day the old policy expires.
Every case file you built in the outgoing carrier's return-to-work portal — the transitional job descriptions your physician reviewed and signed, the restriction-tracking history, the documented offers of modified duty, the record of which days were logged and which were approved — lives inside that carrier's system. You cannot export it. You cannot import it into the new carrier's tool. In many cases, you cannot even read it after the policy ends. Your institutional memory of how you managed RTW evaporates with the relationship.
This is not a hypothetical edge case. Carrier relationships change. Brokers renegotiate. Markets harden. Any employer running five or more workers' comp claims a year and relying on a carrier-bundled RTW tool is building program equity on rented ground.
This article explains exactly what carrier-bundled RTW tools provide, what they structurally cannot provide, and what an employer-owned, carrier-independent system does differently — so you can make a clear-eyed decision before you need to switch carriers, not after.
What Carrier-Bundled RTW Tools Actually Are
Carrier-bundled return-to-work tools are software features or toolkits that a workers' compensation insurer provides at no additional charge alongside a commercial policy. Pinnacol Assurance, Texas Mutual, and Kinetic Rapid RTW are examples of this model. The basic value proposition is straightforward: you pay for the policy, and the carrier includes RTW documentation support as a perk.
In practice, what these tools include varies widely by carrier. Some center on form generation — light-duty job offer letters, transitional duty agreements, physician communication templates; some pair the policy with adjuster- or specialist-guided return-to-work support; and some are tech-managed tools that produce compliant light-duty offers. Confirm what any specific carrier's program actually provides before relying on it. The forms themselves are often current and well-designed. For an employer managing one or two straightforward claims a year with a stable carrier relationship, that can be enough.
The structural constraints, however, are not bugs. They are features — of the carrier's business model, not the employer's.
The tool is aligned to the carrier's claim-closure interest. A carrier-bundled RTW tool exists, in part, to help the carrier resolve claims efficiently. That is not a cynical observation; it is the honest description of why carriers invest in building these tools. Faster return to work means shorter indemnity exposure, which benefits the carrier. When the carrier's interest and the employer's interest align — and they often do — the tool works well. When they diverge, the tool is not designed to serve the employer's side.
The data does not belong to the employer in any portable sense. Case files, job description histories, restriction logs, and correspondence records are stored in the carrier's infrastructure. Access is contingent on the policy relationship. This is not a technical limitation that will be solved; it reflects the carrier's legitimate interest in not maintaining infrastructure for former policyholders.
The program is non-transferable. An employer's return-to-work program — the institutional knowledge of which transitional tasks are available in which departments, how restrictions are typically accommodated, which job descriptions have already been physician-approved — should grow and compound over time. Built inside a carrier's tool, that compounding stops at renewal.
The Portability Problem in Practice
The portability gap is most visible in three specific situations: carrier switches, multi-carrier books, and audit requests.
Carrier switches. The scenario described in the opening is the most common. An employer who has spent two or three years refining transitional job descriptions and building a case history inside a carrier's portal starts from zero with the next carrier. The new carrier's tool has different forms, a different workflow, and no memory of how the previous program operated. Any reimbursement documentation — Washington Stay-at-Work application records, Texas Bona Fide Offer of Employment correspondence, Oregon EAIP wage records — assembled inside the old tool is inaccessible when it is needed for a late-filed claim or a coverage dispute.
Multi-carrier books. Employers who self-insure one line, run a state-fund policy for another, or operate in multiple states with different carriers face a fragmentation problem that carrier-bundled tools have no architectural answer to. Each carrier's tool tracks only the claims on that policy. The employer has no unified view of open cases, no cross-carrier restriction-window calendar, and no consolidated audit trail.
Audit requests. When a carrier or a state agency asks for documentation of a modified-duty program — which happens in experience-rating reviews, premium audits, and state reimbursement applications — the employer needs to produce organized records quickly. Documentation assembled inside a carrier's portal may not export in a format that satisfies the request, and if the audit follows a carrier switch, it may not be accessible at all. The RTW audit trail and carrier audit preparation guide on this site covers what auditors typically request; the short version is that documentation gaps are costly.
What Carrier-Independent RTW Software Does Differently
A carrier-independent RTW system is software the employer purchases and operates directly — not bundled with any policy, not aligned to any carrier's claim-closure timeline, and not contingent on any particular insurance relationship.
Transitional Duty Manager is built in this category. The architecture starts from a different assumption: the employer's RTW program is an operational asset that should accumulate value, survive carrier changes, and serve the employer's documentation and compliance obligations — not the carrier's workflow.
The practical differences fall into four areas.
Employer data ownership. Case files, transitional job descriptions, restriction logs, communication records, and reimbursement documentation belong to the employer and are accessible regardless of which carrier is currently on the risk. When a carrier switches, the program continues without interruption.
Carrier-agnostic workflow. The system tracks cases across whatever combination of carriers, state funds, or self-insured retentions the employer operates. A manufacturing operation with a commercial policy in Ohio, a state-fund policy in Washington, and a self-insured program in Texas runs one workflow, not three disconnected ones.
Reimbursement documentation assembly. State wage-reimbursement programs — Washington's Stay-at-Work, Oregon's EAIP, Texas's employer modification reimbursement — have specific documentation requirements that carrier-bundled tools are not designed around. Washington's SAW program, for example, requires a written, physician-approved transitional job description submitted to the attending provider as early as possible, with wage records organized by approved days worked within approved hours; light-duty days worked outside approved hours or outside the approved job description are ineligible. (WA L&I Complete Stay at Work Guide, 2024.) An employer who cannot produce that documentation at the one-year filing deadline — because records are locked inside a carrier's portal after a policy switch — forfeits the reimbursement opportunity. For injuries on or after January 1, 2025, that opportunity is up to $25,000 per claim for the Stay-at-Work component alone. (AGC of Washington, 2025.)
Audit trail integrity. The return-to-work case management guide covers the full documentation requirements in depth. The short version: an audit trail that a court, a carrier, or a state agency will credit needs to be timestamped, complete, and producible on demand. Documentation assembled in a carrier portal and unavailable after a policy change does not meet that standard.
A Direct Comparison
The table below lays out the structural differences across the two models. Pricing for all software categories in this comparison is qualitative; exact figures vary by carrier, policy, and product.
| Dimension | Carrier-Bundled RTW Tool | Carrier-Independent System |
|---|---|---|
| Cost | Included with the policy; no separate line item | Separate subscription or purchase |
| Data portability | Non-portable; data stays in carrier's system | Employer-owned; accessible regardless of carrier |
| Carrier alignment | Aligned to carrier's claim-closure workflow | Neutral; serves employer's program continuity |
| Multi-carrier / multi-state | Single carrier only | Operates across any carrier or state combination |
| Reimbursement doc assembly | Not purpose-built for state wage-reimbursement programs | Designed around SAW, EAIP, BFOE, and similar documentation requirements |
| Audit trail | Accessible only during active policy; format may not meet auditor requirements | Maintained by employer; exportable on demand |
| Program continuity at renewal | Resets at carrier change | Accumulates over time |
| Form currency | Carrier maintains; aligned to carrier's jurisdiction | Employer responsible; system provides framework |
This is not a claim that carrier-bundled tools are without value. For a small employer on a stable, long-term carrier relationship with straightforward claim volume, a bundled tool may be sufficient. The question is whether "sufficient for now" is the right standard when the tool's limitations become visible exactly when you are under the most pressure — during a carrier switch, an audit, or a multi-state expansion.
The EMR and Frequency Dimension
One factor that makes RTW program continuity a financial concern, not just an operational one, is the experience modification rate.
EMR uses a three-year experience window, excluding the current year. (Higginbotham, 2026.) An elevated EMR persists for roughly three years after the claims that caused it. At an EMR of 1.3, a $10,000 base premium becomes $13,000. (Berry Insurance, 2024.) Frequency compounds this: five $10,000 claims raise EMR more than one $50,000 claim. (PolicyBenchmark, 2026.)
A documented, consistent RTW program reduces lost-time claim duration and, where applicable, converts indemnity claims to medical-only. That matters because NCCI experience rating reduces medical-only primary loss value by 70% — only 30% of the medical-only loss value is applied to the EMR calculation. (National Workers Comp Authority, 2025.) Medical-only claims account for 77.9% of claim counts but only 6.0% of total loss dollars. (NCCI, 2023.) An RTW program that consistently keeps injured workers in modified duty converts potential indemnity exposure into the category that EMR penalizes least.
The problem is that "consistent" is the operative word. A program that resets every time you switch carriers — relearning forms, rebuilding job descriptions, losing restriction history — is not a consistent program. It is a series of first-year programs.
What to Look For in a Carrier-Independent System
If you are evaluating a move away from a carrier-bundled RTW tool, the RTW software buyer's guide covers the full evaluation framework. The specific questions to ask about any carrier-independent system:
Who owns the data? The contract should be unambiguous that the employer retains all case records, job descriptions, and communication logs — and can export them in a usable format.
Does the system track by approved days and approved hours? For Washington SAW eligibility, this is not optional. A day worked outside approved hours is an ineligible day, and that distinction needs to be documented in the system, not reconstructed from payroll records later.
Does it support multi-carrier, multi-state workflows? If you operate in more than one state or carry more than one policy, a tool that tracks only a single carrier's claims creates the same fragmentation problem as the bundled tools, at an additional cost.
What does the audit trail look like? Ask for an example export. It should be timestamped, organized by case, and include documented offers, physician approvals, and restriction records.
Does the pricing scale with your actual use? Enterprise RMIS platforms built for Fortune 1000 self-insureds carry pricing and implementation timelines calibrated for that market. A 200-employee manufacturer does not need the same tool — or the same cost structure.
The comparison of RTW software versus spreadsheets is also relevant here: the spreadsheet baseline is what most employers are actually replacing, and understanding its failure modes clarifies what the system needs to do.
Making the Decision
Carrier-bundled RTW tools serve a real purpose. They lower the barrier to basic RTW documentation for employers who might otherwise use nothing at all. The forms are often current, the cost is zero, and for a stable single-carrier relationship with low claim volume, the tradeoffs are manageable.
The employer who should look carefully at a carrier-independent system is one who:
- Has switched carriers in the last five years, or anticipates doing so
- Operates in multiple states or carries more than one policy
- Has five or more open or recent claims and needs a consolidated view
- Has a state wage-reimbursement program available (Washington SAW, Oregon EAIP, Texas workplace modification reimbursement) and wants to protect that documentation
- Has been through a carrier audit or premium audit and experienced documentation gaps
- Wants to build institutional RTW knowledge that compounds over time rather than resetting at renewal
If that description fits your operation, the starting point is understanding what a purpose-built system looks like at a scale and price point built for employers — not for large self-insureds with dedicated risk-management departments.
Start a free trial of Transitional Duty Manager at app.transitionalduty.com/signup to see how carrier-independent case tracking works in practice. If you want a structured starting point for the program itself, the RTW Program Kit — Complete includes the core documentation templates, job description frameworks, and workflow guides to build a program you own from day one.
See pricing for current plan details.
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
