By Rovaryn Digital · 10 min read
The Problem Is Not the Sites — It Is the Silence Between Them
A regional safety manager at a 400-employee distribution operation told a story that most multi-location coordinators will recognize: a lumbar sprain claim opened in the Ohio facility in February. By March, the Colorado site had a shoulder claim. By April, the Tennessee location had two more. Each site manager was doing their best — one in a spreadsheet, one in their email inbox, one in a paper binder. Nobody at the corporate level had a consolidated count of open cases, which states were involved, or whether any of the four claims had a modified-duty job description on file with the treating provider.
When the TPA called in April asking for current restrictions on the Ohio claimant, the safety manager had to run down three phone calls to reconstruct a file that should have been one screen.
That is not an unusual story. It is the default state of multi site return to work management at employers who have grown faster than their systems. This article explains the specific failure modes that appear when RTW is managed site-by-site rather than as a portfolio, and what a coherent cross-location program actually requires in practice.
By the end, you will have a concrete framework for consolidating case oversight, handling state-specific documentation without letting it fragment your process, and monitoring program health before a TPA audit or carrier renewal makes the gaps visible.
Why Site-by-Site Management Fails at Scale
At a single-location employer with two or three open claims per year, a shared spreadsheet or even a disciplined email folder can hold the program together. Add a second or third site — with different supervisors, different injury patterns, and potentially different state workers' compensation rules — and the architecture breaks in predictable ways.
Visibility collapses. When each location owns its own files, the person responsible for program-level performance — a corporate safety director, HR VP, or risk coordinator — cannot see the portfolio without manually aggregating reports from each site. That aggregation is rarely done in real time, which means decisions are made on stale information.
Inconsistency compounds. A modified-duty job description built by a supervisor at one site may not transfer cleanly to a similar role at another site. Restriction language that one site documents well may be absent entirely from another site's files. The program looks different depending on which site a carrier auditor happens to examine.
State-form compliance fragments. A Washington state claim requires a specific light-duty job description submitted to the attending provider before the Stay-at-Work reimbursement clock starts. A Texas claim requires a written Bona Fide Offer of Employment (BFOE) that meets every element of 28 TAC §129.6 before a carrier can act on a refusal. An Oregon claim has its own Early Return-to-Work (ERTW) documentation sequence under the state's Employer-at-Injury Program (EAIP). If each site is managing its own paperwork without a shared framework, the likelihood that state-specific requirements are met consistently — across all sites, on every claim — is low.
Missed reimbursement accumulates quietly. Washington's Stay-at-Work program reimburses 50% of base wages for light-duty work, up to 120 days worked and a maximum of $25,000 per claim for injuries on or after January 1, 2025, according to AGC of Washington (2025). Oregon's EAIP reimburses 50% of early return-to-work gross wages for up to 66 work days (OR WCD, 2025). Both programs require documentation that is filed after the fact — meaning a site that did not track qualifying days precisely, or filed outside the reimbursement window, loses money that was legitimately earned. Multiply that across three or four states and a dozen claims per year, and the cumulative missed reimbursement is material.
What a Portfolio View Actually Means
"Portfolio view" is not a reporting feature. It is an operating discipline — a commitment to treating every open RTW case, regardless of which site opened it, as a unit in a managed program with shared standards.
In practice, a portfolio view answers four questions at any given moment without requiring anyone to call a site manager:
- How many cases are open, at which sites, and in which states?
- What is the current restriction status and duty assignment for each case?
- Which cases are approaching a critical date — a reimbursement filing window, a restriction-review appointment, an indemnity benefit trigger?
- Which cases are missing required documentation — a signed job description, a written offer letter, a provider approval?
The mechanism for answering those questions changes depending on your scale, but the questions themselves are the standard. A program that cannot answer them in real time is not being managed — it is being reacted to.
A useful step toward understanding what a consolidated case management workflow looks like in detail is the return-to-work case management guide, which covers the core documentation sequence from first report through full duty return.
Handling State-Specific Rules Without Letting Them Fragment Your Process
The practical tension in multi state workers' comp RTW is this: state rules are genuinely different and genuinely matter, but they cannot be allowed to create entirely separate programs at each site. The solution is a two-layer approach.
Layer one: the universal process skeleton. Every claim, regardless of state, follows the same structural sequence — first report of injury, initial restriction review, transitional duty assessment, job description documentation, offer or assignment, periodic restriction review, return-to-full-duty or case closure. The documentation standards, the approval chain, and the audit trail are the same everywhere.
Layer two: state-specific parameters loaded into the skeleton. Washington claims carry SAW reimbursement tracking; Texas claims carry BFOE documentation requirements; Oregon claims carry EAIP enrollment steps. These parameters are additions to the standard skeleton — not replacements for it — and they are keyed to the state associated with each claim, not to the physical site location (which may differ from the state of injury for traveling workers).
This architecture means a coordinator opening a new claim in Nevada, where your company has no prior experience, follows the same intake process they would follow in Ohio. The state-specific layer prompts the relevant additional steps rather than requiring the coordinator to independently know Nevada's rules.
For a current reference on which states operate wage-reimbursement, modification-grant, and preferred-worker programs — and what each one requires — the state RTW incentive programs overview and the State RTW Incentive Atlas & Parameter Workbook both provide program-by-program detail you can map directly into your intake process.
The Self-Insured and Multi-Carrier Complication
Multi-site employers are disproportionately likely to be self-insured, to carry policies through multiple carriers across different states, or to work with a TPA that handles claims across their book. Each of those arrangements introduces a coordination problem that site-by-site management makes worse.
With a carrier-bundled RTW tool, the documentation and case tracking exist inside the carrier's system — which means the program is non-portable. If a site changes carriers at renewal, the RTW history for that site goes dark. If two sites are with different carriers, the portfolio view does not exist at all because the data lives in two separate carrier platforms, neither of which has any obligation to share it with the other.
Self-insured employers face a different version of the same problem: the TPA handles claims administration, but the employer is responsible for the RTW program, and the TPA's system is optimized for claim closure — not for the employer's program continuity, documentation standards, or reimbursement recovery. The employer needs a system they own and control, regardless of which TPA or carrier touches a given claim.
If your organization uses a TPA or broker who manages RTW services across your locations, the TPA and broker RTW service differentiator article covers how to structure that relationship so program standards travel with the employer rather than being rebuilt with each service provider.
What Coherent Multi-Site RTW Documentation Looks Like in Practice
Across a portfolio of open cases, documentation coherence means:
Standardized transitional duty job descriptions. Each site has a library of approved light-duty task descriptions, written at the occupation level and reviewed by a clinical resource before use. When a restriction comes in, the coordinator is matching the restriction to an existing, approved description — not drafting a new document under time pressure.
State-specific offer letters generated from restriction data, not from memory. A Texas BFOE that does not meet every element of 28 TAC §129.6 does not protect the employer's ability to have benefits adjusted after a refusal. The offer letter for a Texas claim should be generated from the actual restriction data on file, in a format that has been reviewed against the rule, not typed fresh by a site manager who may not know the rule.
Day-count tracking for reimbursement programs. Washington's SAW program has specific eligibility rules: a light-duty day worked outside the approved job description or approved hours is ineligible for reimbursement, and a partial day still counts as one reimbursable day (WA L&I Complete Stay at Work Guide, 2024). Oregon's EAIP runs for up to 66 work days within a consecutive 24-month period (OR WCD, 2025). Neither of those counts keeps itself. If it is not tracked case-by-case, from the first qualifying day, the reimbursement calculation at filing time will be unreliable.
A single audit trail that does not depend on any one site's file cabinet. When a TPA, carrier, or state agency audits a claim, the documentation should be retrievable centrally — not by contacting the site manager who handled the intake eighteen months ago.
Evaluating Whether Your Current System Can Hold the Load
Before selecting a tool or restructuring a process, assess where the current system actually breaks. For most multi-site employers, the failure point is one of three things:
Aggregation failure: Corporate cannot see portfolio status without manually polling sites. If your current answer to "how many open cases do we have today?" is "let me check with the sites," aggregation is the primary gap.
Documentation inconsistency: Different sites produce materially different documentation for similar claims. If a carrier auditor would find meaningfully different files depending on which site they examined, documentation standards are the primary gap.
Reimbursement leakage: Claims in Washington, Oregon, or other wage-reimbursement states are not being tracked at the day level from intake, or applications are being filed late or with incomplete records. If you have had SAW or EAIP-eligible claims in the last two years and have not filed — or have filed and been partially denied — reimbursement tracking is the primary gap.
Most multi-site operations have more than one of these gaps. But naming the primary one helps sequence the fix. Aggregation gaps require either a shared platform or a disciplined reporting cadence. Documentation gaps require standardized templates and a review process. Reimbursement gaps require day-level tracking keyed to state-specific rules, starting at claim intake — not at application time.
The RTW software buyer's guide covers the evaluation criteria for tools at this stage, including what to ask about multi-site case access, state-form libraries, and reimbursement tracking.
Running Multi-Site RTW as One Program
Multi site return to work management works when it is designed as one program that operates in multiple locations — not as multiple site programs that occasionally compare notes. The structural requirements are not complicated, but they require deliberate choices: a universal process skeleton, state-specific parameters loaded into that skeleton, documentation standards that apply across every site, and a portfolio view that answers the four key questions in real time without a phone call.
Employers who get this right tend to do it in steps: standardize documentation first, then centralize case visibility, then layer in reimbursement tracking as the documentation becomes reliable enough to support filing. Each step makes the next one easier.
If you are at the stage where the gaps are visible but the architecture is not yet in place, Transitional Duty Manager is built specifically for this operating model — carrier-independent, multi-site, with state-specific form and reimbursement logic that travels with the claim rather than the carrier. Start a free trial and see the portfolio view against your actual case load. Pricing details are at /pricing.
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
