By Rovaryn Digital · 11 min read
When One More Case Breaks the Tab
Picture this: it is a Thursday afternoon and your second open light-duty case in three weeks just landed. The injured worker from last month is still on a four-hour restriction, her attending provider approved a revised job description last Tuesday, and you have not yet logged the exact date. Now a second claim — a lower-back strain from the loading dock — arrives with a work capacity form and a seven-day window before the carrier asks whether you have a transitional assignment ready. Both cases need to be tracked. Both have approval documents that have to be filed and retrievable. Both have reimbursement deadlines that do not move.
You open the spreadsheet. There is one tab, sorted by date of injury. Last month's case is six rows deep, with notes crammed into a single cell. There is no column for approved hours. There is no reminder for the reimbursement filing deadline. The physician sign-off date is somewhere in an email chain.
This is not a failure of effort or diligence. It is a structural problem: a general-purpose tool being asked to do case-management work it was never built to carry. This article explains where spreadsheets and email genuinely hold up for return-to-work tracking, exactly where they break, and what changes when a purpose-built RTW tracking tool takes their place.
What Spreadsheets Do Well — and Where They Actually Hold
Honesty first: a spreadsheet is a legitimate starting point for an employer running one or two light-duty cases per year with a single, experienced coordinator who built the file and knows where everything lives.
In that narrow context, a well-designed workbook can capture date of injury, restriction type, transitional assignment title, the attending provider's sign-off date, and estimated return-to-full-duty. It can hold the basic arithmetic for a reimbursement estimate. It costs nothing beyond software the employer already owns.
If your operation has fewer than five workers' comp claims per year, one coordinator with no planned turnover, and no state-program reimbursement tracking to manage, the spreadsheet may be functionally adequate — not optimal, but not broken. The Transitional Duty Case Tracking Workbook exists precisely for this tier: a structured, pre-formatted workbook that brings discipline to the manual process without requiring a software subscription.
The problem is not the spreadsheet per se. The problem is what happens when case volume, coordinator continuity, documentation standards, or reimbursement complexity cross recognizable thresholds.
The Four Thresholds Where the Manual Process Breaks
1. Concurrent Cases: Three or More Open at the Same Time
A single open case in a spreadsheet is manageable. Two is workable if the coordinator is disciplined. Three or more concurrent cases is where the structural limits become visible and consequential.
Each open case has its own restriction window — specific approved tasks, approved hours per day, and an expiration date on the written job description. If the provider approved four hours but the worker clocks six on a given day, that day is ineligible for reimbursement under programs such as Washington's Stay-at-Work program, where a day worked outside approved hours does not count toward the reimbursement cap regardless of how many other days qualify (WA L&I, 2025). Catching that in a spreadsheet requires the coordinator to manually cross-reference timesheet data against the approved-hours column — every day, across every open case.
At three concurrent cases, the coordinator is maintaining three separate tracking threads, often across multiple tabs or files, with no automated flag when an approved-hours ceiling is approached or when a filing deadline is 30 days out. At five concurrent cases — common in a mid-size manufacturing or warehousing operation with a 2.3–2.5 injury rate per 100 FTE (BLS, 2026) — the cognitive load and the probability of a tracking error compound significantly.
A missed day-count is not a minor bookkeeping error. Under Washington's Stay-at-Work program, reimbursement caps rose substantially under House Bill 2127, with the maximum now reaching up to $75,000 per claim when both the Stay-at-Work and Preferred Worker programs apply (AGC of Washington, 2025). A miscounted day or a missed filing window — reimbursement applications must be submitted within one year after the light-duty work is completed (WA L&I, 2025) — forfeits money the employer earned by running a proper transitional program.
2. Coordinator Turnover and Institutional Knowledge Loss
RTW coordinators, HR managers, and safety officers change jobs. When the person who built and maintained the spreadsheet leaves, what transfers with them?
In most operations: the file. What does not transfer is the mental model — which email thread has the signed job description, what the abbreviation in column F means, why a particular case has a flag in the notes cell, and when the next reimbursement application is due. A successor coordinator opening an inherited spreadsheet for the first time is, in practice, starting over.
This is not a hypothetical risk. Research from the Workers' Compensation Research Institute found that the probability of a worker not returning to work rises substantially at smaller employers — 21% of injured workers at 1–50 employee firms did not return, compared with 10% at firms with 251–1,000 employees and 7% at firms with 1,000 or more (WCRI, 2018). Program continuity — the ability to sustain a functioning RTW process through coordinator transitions — is one mechanism that separates employers with strong RTW outcomes from those without. A spreadsheet does not preserve program continuity; it preserves whatever one person happened to write down.
3. Carrier Audits and Documentation Requests
When a carrier or TPA requests documentation for an open or closed claim — to verify that a transitional assignment was properly authorized, that restrictions were communicated correctly, or that a benefit suspension was supported by a valid written offer — the employer has to produce a coherent record. The standard is not "we tracked it" but "here is the document, dated and retrievable."
Under a manual process, that documentation typically lives across three places: the spreadsheet (summary fields), an email inbox (the actual signed forms), and a shared drive or physical file (the provider-approved job description). Reconstructing a complete, chronological case record from those three sources under time pressure — while current cases are still active — is a real operational burden, and gaps in the reconstructed record are common. See how audit-ready documentation works in practice for a detailed walkthrough of what carriers typically request and how case records need to be structured to respond efficiently.
The documentation standard for a written Bona Fide Offer of Employment in Texas, for example, requires that the offer meet every requirement of 28 TAC §129.6 in writing; a mailed offer is deemed received five days after mailing, and a carrier may begin reducing indemnity benefits on the earlier of the worker's rejection or the seventh day after that deemed receipt if it is refused or unacknowledged (28 TAC §129.6(g), 2024). If the employer cannot produce the dated written offer and the evidence of delivery, the benefit-coordination mechanism is not available — regardless of whether the employer actually made the offer.
4. Multi-State or Multi-Program Complexity
An employer operating in two or more states, or enrolled in more than one state reimbursement program simultaneously, is managing materially different rule sets. Oregon's EAIP repays 50% of early return-to-work gross wages for up to 66 work days within a 24-month period, with a combined cap of $5,000 on worksite modifications and an administrative fee of $120 per program (OR WCD, 2025). Washington's Stay-at-Work program uses a 50% of base wages formula with a maximum reimbursement of $25,000 per claim over up to 120 days worked for injuries on or after January 1, 2025 (WA L&I, 2025). Ohio's Transitional Work Grants run $3,700–$8,200 depending on employer size, with a Transitional Work Bonus (now being phased out — confirm current status with OH BWC) for operating a documented transitional work program (OH BWC).
Each program has different eligibility windows, different document requirements, different application timing rules, and different definitions of what constitutes a qualifying day of work. A spreadsheet built to track one program has to be rebuilt — or at minimum heavily modified — to track another. Errors in which rule set applies to which claim are likely, and the cost of an error is a forfeited reimbursement or a disqualified day count.
What Purpose-Built RTW Tracking Changes
The shift from a spreadsheet to a purpose-built RTW tracking tool is not primarily about convenience. It is about making the process defensible and portable — defensible to a carrier auditor, a treating provider, or an EEOC inquiry, and portable across coordinator transitions, carrier renewals, and state lines.
A purpose-built tool maintains case state over time. Each case has its own record: restriction window, approved hours, transitional job description status, filing deadlines, and document history — not distributed across a file, an inbox, and a drive, but consolidated in one retrievable location. When a coordinator opens a case that a predecessor managed, they see the same record that was there when the case opened.
Carrier independence matters here in a way that is worth stating plainly. Carrier-bundled RTW tools — those provided free with a commercial workers' comp policy — hold program data and document history on the carrier's infrastructure. When the policy renews with a different carrier, or when an employer shops the account, the case history does not transfer. The employer's RTW program effectively resets. For a more detailed comparison of carrier-bundled tools against independent options, see carrier-bundled RTW tools vs. independent alternatives. An independent, employer-owned tool means the program belongs to the employer — the case history, the approved job descriptions, the reimbursement records — regardless of which carrier writes the policy at the next renewal.
State agency toolkits and Excel provide current forms but no workflow, no case tracking, no duty-matching support, no reimbursement assembly, and no audit trail. They are the right choice for an employer who processes one or two claims per year and has the coordinator continuity to maintain a manual system reliably. For operations beyond that threshold, they require the employer to build the infrastructure the toolkit does not include — and to rebuild it every time something changes.
A Practical Framework for Deciding
Rather than treating this as a binary choice, consider the thresholds where the manual process introduces real risk:
| Condition | Spreadsheet holds | Upgrade warranted |
|---|---|---|
| Open concurrent cases | 1–2 | 3 or more |
| Claims per year | Fewer than 5 | 5 or more |
| Coordinator turnover risk | Low / single person, no transition planned | Moderate to high |
| State reimbursement programs tracked | None or one | Two or more |
| Carrier audit documentation needed | Rarely requested | Documented history required |
| Multi-carrier or renewal-year portability | Single carrier, stable | Shopping account or changing carriers |
If your operation sits entirely in the left column, a well-structured workbook — the Transitional Duty Case Tracking Workbook is built for exactly this tier — combined with disciplined email filing is a defensible starting point. If you are in the right column on two or more rows, the manual process is carrying risk that compounds with each additional case.
For a structured overview of what to evaluate when moving to dedicated software, the RTW software buyer's guide covers the feature categories, integration questions, and vendor questions worth working through before a purchase decision. For the foundational case-management framework that any tool should support, see the return-to-work case management guide.
The Reimbursement Math Makes the Business Case
The financial case for structured documentation is not abstract. Consider a Washington employer with a qualifying claim under Stay-at-Work. The program reimburses 50% of base wages for up to 120 days worked, with a maximum of $25,000 per claim for injuries on or after January 1, 2025 (AGC of Washington, 2025). A partial day counts as one reimbursable day, but a day worked outside the provider-approved hours or outside the approved job description is entirely ineligible — that day does not count (WA L&I, 2025).
An employer tracking approved hours manually, across three concurrent cases, in a spreadsheet with no automated flag for hours ceilings, is at real risk of logging ineligible days as reimbursable — or, more commonly, of undercounting eligible days because the documentation is incomplete. Either error costs money.
The reimbursement application must be submitted within one year after the light-duty work is done (WA L&I, 2025). A missed deadline means a forfeited reimbursement, regardless of how many qualifying days the employer actually delivered. The documentation system — whether a structured workbook or a purpose-built platform — is not overhead. It is the mechanism that captures the reimbursement the employer earned.
Try the Tool the Process Runs On
If your RTW tracking is at or near the thresholds described above, Transitional Duty Manager is built for the employer-side case management work that spreadsheets cannot reliably carry: concurrent case tracking, document history, restriction-window management, and reimbursement-ready records — portable across carriers, coordinators, and states.
Start a free trial and run a current case through the platform before committing. See pricing for plan options sized for operations from single-location employers to multi-site accounts.
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
