
By Rovaryn Digital · 10 min read
When the Money Was Already Yours
The wage reimbursement check that never arrives usually has nothing to do with ineligibility. The worker was injured. The employer offered a transitional position. The attending provider gave written approval. The injured worker showed up and did the work. Every underlying condition for reimbursement was satisfied — and then the employer filed late, submitted an unapproved job description, or logged hours instead of days, and the recoverable dollars disappeared.
That scenario repeats itself constantly across Washington's Stay-at-Work (SAW) program, Oregon's Employer-at-Injury Program (EAIP), Ohio's Transitional Work program, and Texas's Bona Fide Offer of Employment (BFOE) framework. The programs are funded and available. The employers who use transitional duty are already doing the hard operational work of accommodating a restricted worker. The reimbursement is the financial recognition of that effort — and forfeiting it is almost always a documentation or timing problem, not an eligibility problem.
This article catalogs the specific mistakes that cause employers to lose return to work reimbursement they were otherwise entitled to collect, and the practices that prevent each one. After reading it, you will be able to audit your own RTW process against each failure mode before you file — not after a denial arrives.
Mistake 1: Submitting the Job Description After the Work Has Already Started
Every state reimbursement program that pays wage costs requires the attending provider to approve the transitional job description before — or at the very beginning of — the light-duty assignment. In Washington's SAW program, the attending provider must approve the transitional job description in writing before reimbursable days accumulate. (WA L&I Complete Stay at Work Guide, 2024)
What happens operationally: the employer calls the injured worker back on Monday. The job description gets faxed to the clinic on Thursday. The provider signs it Friday. Days one through four are now unverifiable as provider-approved light-duty days.
The practical fix is to treat provider sign-off as a prerequisite, not a parallel task. The job description goes to the provider before the worker's first scheduled return date. Nothing starts the clock until the signed document is back in hand.
Mistake 2: Logging Hours Worked Instead of Days Worked
Washington's SAW program reimburses on a day basis, not an hourly basis. A partial day counts as one reimbursable day. (WA L&I Complete Stay at Work Guide, 2024) That means a worker who completes three hours of a four-hour approved shift still generates a reimbursable day — as long as those hours fall within the approved job description and approved schedule.
The disqualifying corollary is equally precise: a light-duty day worked outside the approved hours is ineligible. If the provider approved a four-hour shift and the worker logs six hours, that day is disqualified entirely — not trimmed proportionally. (ERNwest, 2025)
Many employers track RTW in the same timekeeping system they use for regular payroll, which records clock-in and clock-out times. That system will not flag a six-hour day against a four-hour approval. The mismatch only surfaces when the claim is audited or denied.
The minimum documentation standard for any day you intend to claim:
- The approved job description, signed by the attending provider, specifying the authorized hours and duties.
- A daily log confirming the worker's actual hours and tasks — kept separately from regular payroll records.
- A reconciliation step — at least weekly — confirming that logged hours do not exceed approved hours on any individual day.
See the Approved Dates Only Tracking guide for a structured daily-log format built around this requirement.
Mistake 3: Missing the One-Year Filing Window
Washington's SAW program requires the reimbursement application to be submitted within one year after the light-duty work is completed. (WA L&I, 2025) There is no exception for good-faith delay, administrative backlog, or staff turnover. If the window closes, the reimbursement is permanently forfeited — regardless of how well the underlying work was documented.
With the expanded SAW caps effective for injuries on or after January 1, 2025 — reimbursement of 50% of base wages, up to 120 days worked, to a maximum of $25,000 per claim (AGC of Washington, 2025) — the cost of a missed deadline has grown substantially. An employer who documented 90 approved light-duty days at $25/hour base wages for an eight-hour approved shift, then missed the filing window, forfeited a calculable reimbursement opportunity. The money was earned operationally. It is lost administratively.
The fix is a calendar event, not a memory. When a transitional assignment closes, record the last approved date worked and set a deadline reminder at nine months — giving you a three-month buffer to assemble the packet and correct any errors before the one-year window expires. The WA SAW Reimbursement Packet Checklist lists every document L&I requires in the application.
Mistake 4: Counting Days Worked After Claim Closure
Washington's SAW program does not reimburse for wage costs incurred after the workers' compensation claim is closed. (WA L&I Complete Stay at Work Guide, 2024) If a claim closes and the worker continues in a modified-duty position, any wage costs after the closure date are ineligible — even if the job description was provider-approved and the hours were compliant.
This mistake is easy to make when the transitional assignment outlasts the claim. The employer's HR or payroll team may not track claim status independently of the RTW schedule. Days accumulate. The employer assumes the full assignment period is reimbursable. It is not.
The practical control: include claim status as a tracked field alongside the daily work log. When L&I (or the relevant state agency) closes the claim, that date becomes the hard stop for SAW-eligible days. Any days worked after that date should be reclassified in your records before the application is assembled.
Mistake 5: Submitting Unapproved or Generic Job Descriptions
The attending provider is approving a specific, documented set of duties and physical parameters — not a job title. "Light duty" or "modified office work" is not an approvable job description. The provider needs to see the actual tasks, the physical demands (lift limits, posture requirements, duration on feet), and the authorized hours.
A generic description creates two problems. First, the provider cannot meaningfully assess whether the assignment respects the worker's medical restrictions. Second, the reimbursing agency has no baseline against which to evaluate whether the days worked were within the approved scope. Both problems become denial grounds.
The job description submitted for SAW reimbursement should specify:
- Job title and work location
- List of specific tasks, each with relevant physical demands
- Maximum lifting, carrying, pushing, and pulling limits
- Posture and positioning requirements (seated vs. standing, overhead reach)
- Authorized hours per day and days per week
- Start date and anticipated end date (or claim-closure contingency)
When that description matches the daily log — task by task, hour by hour — the application packet can be assembled cleanly. When it does not, the discrepancies become the auditor's first question.
Mistake 6: Failing to Submit the Job Description to the Provider Early
Separate from the approval timing problem, there is a sequencing problem: employers often wait until the worker is ready to return before sending the job description to the provider. That delay compresses everything. The provider may need time to review and revise. The worker's first return date gets pushed. Approved days are fewer.
Washington L&I's guidance is direct: submit the light-duty job description to the provider as early as possible. (WA L&I Complete Stay at Work Guide, 2024) "As early as possible" in practice means at or near the time of injury — not when the worker's restrictions stabilize. The employer can draft a conditional job description based on expected restrictions, send it to the provider with a note that it is contingent on the treatment plan, and revise once restrictions are confirmed. That approach keeps the provider in the loop early and often shortens the gap between injury and first reimbursable day.
Mistake 7: Incomplete or Misrouted Texas BFOE Documentation
In Texas, the Bona Fide Offer of Employment (BFOE) is a written document that must meet every requirement of 28 TAC §129.6. An offer that is verbal, incomplete, or delivered through an informal channel does not qualify as a BFOE under the rule, regardless of what the employer intended. (TDI-DWC RTW Guide, 2023)
The consequences of a non-compliant offer run in both directions. A properly documented, compliant BFOE that the injured worker refuses or fails to acknowledge allows the carrier to reduce or suspend indemnity benefits on the earlier of the worker's rejection or the seventh day after deemed receipt, a mailed offer being deemed received five days after mailing. (28 TAC §129.6(g), 2024) An improperly documented offer forfeits that leverage and may expose the employer to dispute over whether a valid offer was made at all.
The documentation minimum for a Texas BFOE:
- Written form, delivered per the rule's delivery method requirements
- Specific duties and physical demands consistent with the treating physician's restrictions
- Wage and hours information
- Start date and duration
- Proof of delivery (certified mail or documented in-person presentation)
Confirm the current form requirements and delivery rules with TDI-DWC or qualified Texas workers' compensation counsel before issuing an offer. Rules can change, and a technical defect in the offer can void its legal effect.
The Pattern Behind the Mistakes
Laid out together, these mistakes share a structure. They are not errors of malice or negligence toward the injured worker. They are errors of sequence and record-keeping — things that happened in the right order operationally but were not documented in a way that survived audit.
| Mistake | What was lost | The recoverable point |
|---|---|---|
| Job description submitted after return-to-work start | Days before provider sign-off | Submit before day one |
| Hours exceed approved shift | Entire disqualified day | Reconcile daily against approved schedule |
| Missed one-year filing window | Entire claim's reimbursement | Set deadline at claim close + calendar |
| Days counted after claim closure | Post-closure days | Track claim status alongside work log |
| Generic job description | Application reviewability | Specify tasks and physical parameters |
| Late provider outreach | Fewer approved days, slower start | Send description at time of injury |
| Texas BFOE documentation defects | Carrier leverage on refused offer | Use compliant written form per 28 TAC §129.6 |
The common thread is that reimbursement programs require the employer to reconstruct a sequence of events — provider approval, compliant work, timely filing — from contemporaneous documentation. If the documentation was not kept in real time, the reconstruction is either impossible or unpersuasive to the reviewing agency.
What Systematic Documentation Prevents
An RTW process that generates reimbursable outcomes looks like this: the job description is drafted before the worker returns, submitted to the provider immediately, and revised in writing whenever restrictions change. Each day worked is logged against the approved description and approved hours. Claim status is checked at regular intervals and the log stops at closure. The filing deadline is calendared at the start of the assignment, not at the end.
That process is not complicated. It is consistent. The difference between an employer who routinely recovers reimbursement and one who routinely forfeits it is almost never the quality of the transitional duty program — it is the quality of the contemporaneous record.
The Transitional Duty Case Tracking Workbook provides a structured daily-log format, a provider-approval tracking sheet, and a pre-filing checklist built around the documentation requirements described here. For employers managing multiple concurrent claims, the Washington Stay-at-Work Reimbursement Guide and the State Reimbursement Programs Hub cover program-specific parameters in detail.
If your organization is ready to move from a spreadsheet-based process to a purpose-built case-tracking workflow, you can start a free trial of Transitional Duty Manager to see how case documentation, approved-day tracking, and filing-deadline alerts work together in practice.
The reimbursement programs are funded. The money is available. The only variable is whether your documentation is good enough to support the application.
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

