By Rovaryn Digital · 10 min read
The Scenario That Ends in Dispute
It is a Tuesday at 10:14 a.m. You have a signed provider release limiting the injured worker to no lifting over ten pounds and no ladder work. You have a transitional assembly role that fits every restriction. You called the worker, described the position, and gave the return date. The worker said no.
On Friday, the carrier calls. The adjuster wants to know whether a valid modified-duty offer was made and refused. You say yes. The adjuster asks for the record. You find a note in a shared drive that says, "Called Mike — he said he's not coming in." There is no timestamp, no witness, no job description attached, no detail about what Mike said or why.
That record will not hold up. The carrier may continue paying indemnity benefits. Your experience modifier stays elevated. And if the matter escalates to a dispute or a hearing, your credibility is the only evidence you have — and it is weak.
Documenting light duty refusal is not a formality. It is the record that determines whether the offer legally existed at all. This article walks through exactly what that record must contain, how to structure it in the moment, and how to store it so it is retrievable when you need it most.
Why the Record Determines Whether the Offer "Counts"
A modified-duty offer that cannot be documented is, for practical and legal purposes, an offer that was never made.
Workers' compensation systems in every state share a common logic: indemnity benefits compensate for lost wages when the worker cannot earn. When the employer makes a genuine offer of work within the worker's medical restrictions and the worker refuses without a valid reason, the basis for continued lost-wage benefits weakens materially. But the burden of proving that a valid offer was made — and refused — falls on the employer.
In Texas, the standard is codified explicitly. Under 28 TAC §129.6, a Bona Fide Offer of Employment must be in writing and meet every requirement of the rule; refusal of a valid written offer allows the carrier to reduce or suspend benefits, with a mailed offer deemed received five days after mailing and the reduction permitted on the earlier of the worker's rejection or the seventh day after that deemed receipt (TDI-DWC RTW Guide, 2023; 28 TAC §129.6(g), 2024). The documentation requirements for the offer itself are detailed — and the refusal documentation is the other half of that same file.
Other states operate under similar logic, even where the rules are less prescriptive. Confirm your state's specific procedural requirements and timelines with your state workers' compensation authority or qualified counsel before acting.
The underlying principle holds everywhere: a carrier, a judge, or an auditor evaluating the record will look for evidence that the offer was real, that the worker knew about it, and that the refusal was voluntary and documented contemporaneously. A retroactive note cannot provide that.
For a complete guide to structuring the underlying offer, see How to Write a Modified-Duty Offer Letter.
The Five Elements Every Refusal Record Must Contain
When documenting a light duty refusal, the record needs to answer five questions a reasonable adjuster or hearing officer will ask.
1. What was offered, specifically?
The refusal record must reference — or attach — the exact job description that was presented to the worker. "Light duty" is not sufficient. The record should identify the position title, the physical demands (lift limit, duration of standing, any restricted activities), the location, the hours, and the start date. If the offer was made verbally, the record should note that the written job description was the document the coordinator read from or described.
The job description must fall within the restrictions the treating provider approved in writing. If there is any gap between what was offered and what the provider authorized, the offer's validity is in question before the refusal even matters. For detail on matching duties to restrictions, see the Return-to-Work Case Management Guide.
2. How and when was the offer communicated?
Record the method — in person, by phone, by certified mail, by email — and the precise date and time. Where the offer was delivered by phone, note the number called and the call duration if your system captures it. Where it was delivered in writing, attach the delivery confirmation: certified mail receipt, read receipt, or a signed acknowledgment.
A timestamp from a phone log or an email header is harder to dispute than a note written after the fact. Build the habit of logging the communication the moment it occurs, not at the end of the day.
3. Who witnessed the communication?
Have a second person present for every verbal offer of modified duty, or for any conversation where refusal is anticipated. The witness does not need to say anything. Their role is to confirm, in their own contemporaneous note, that the offer was made as described and that the response they heard matched what the coordinator recorded.
Two consistent, independent records of the same event are significantly more credible than one.
4. What did the worker say, verbatim or as close as possible?
Record the worker's actual words, not a characterization of them. "Employee stated he would not return until his doctor released him to full duty" is far more useful than "employee refused." The specific language tells the adjuster and the carrier whether the refusal was unconditional, whether the worker raised a medical objection (which may require follow-up with the provider), whether they gave a personal reason, or whether they simply did not respond.
If the worker raised a medical objection — "my back is still hurting" or "the doctor told me not to" — that is not necessarily a voluntary refusal. It may indicate the treating provider's written approval of the job description was not communicated to the worker, or that restrictions have changed and a new authorization is needed. Note the objection exactly and follow up with the provider before treating the situation as a clean refusal. Watch expiring or changed restrictions closely — the restriction expiry and maximum-duration flags guide explains how to track those windows.
5. What happened immediately after?
Document every action taken within 24 hours of the refusal: the carrier was notified by phone at a specific time; the carrier adjuster's name and the message left or response received; a follow-up written offer was sent by certified mail; or the coordinator escalated to HR. This follow-up chain shows that the employer acted in good faith and did not simply accept the refusal and close the loop.
Notify the carrier the same day. They need the information to make decisions about benefit continuation, and a delay on your part can compromise their options.
Structuring the Written Record
The refusal record is a contemporaneous internal document, not a legal brief. Keep it brief, specific, and signed. A usable format includes:
| Field | What to enter |
|---|---|
| Claim / case number | The carrier-assigned claim ID |
| Worker name | As it appears on the claim |
| Date and time of offer | Exact, to the minute |
| Method of communication | Phone / in person / certified mail / email |
| Offer document attached | Yes — job description version and date |
| Provider authorization attached | Yes — provider name and date signed |
| Witness name and title | Who was present or on the call |
| Worker's response (verbatim) | Exact language used |
| Reason given by worker | Medical objection / personal / none stated |
| Follow-up action taken | Carrier notified at [time]; certified letter sent [date] |
| Coordinator signature | Name, title, date signed |
This table becomes the core of the refusal record. Attach it to the offer letter, the provider's written job-description authorization, and any delivery confirmation. That package is what you send to the carrier and what you produce at audit.
For an audit-ready file structure and the records a carrier will typically request, see RTW Audit Trail: What Carriers Actually Look For.
Common Errors That Undermine an Otherwise Valid Refusal Record
Documenting at end of day rather than in the moment. Memory is imprecise. A record written four hours after a phone call cannot establish the exact time of that call or reproduce the worker's words reliably. Log the record while the conversation is still open, or within minutes of ending it.
Treating a non-response as a refusal without completing the process. If the worker does not respond to a written offer by the specified date, that is not automatically a refusal under most state rules. The employer typically must make a documented, reasonable attempt to reach the worker before the non-response can carry the same weight. Check your state's requirements; do not assume silence equals refusal.
Omitting the job description from the refusal file. The refusal is only meaningful relative to the specific offer. A refusal record without the attached, provider-approved job description is incomplete. An adjuster cannot evaluate the offer's validity without seeing what was offered.
Recording the reason in general terms. "Employee was uncooperative" tells an adjuster nothing. It signals that the coordinator characterized the interaction rather than observing it. Specific language — even language that reflects poorly on the worker — is more credible and more defensible than a summary.
Failing to notify the carrier promptly. Delayed notification limits the carrier's ability to act on the information. In states where benefit-suspension mechanisms are available, the clock often starts from when the carrier receives notice of the refusal, not when the refusal occurred.
Storage and Retrieval
The refusal record, the offer letter, the provider authorization, and all delivery confirmations belong in the claim file — not in a general HR folder, not in email only, and not in a shared drive without version control.
Medical information, including restriction documentation from the treating provider, must be maintained on separate forms in a separate medical file, accessible only to those with a legitimate business need (29 CFR 1630.14(c)(1); JAN, 2025). The supervisor who needs to know the worker cannot lift over ten pounds does not need access to the diagnosis. Keep the medical file separate from the administrative refusal record, and keep both separate from the general personnel file.
Electronic records carry the same ADA confidentiality obligations as paper records (EEOC Informal Discussion Letter, 2011). If your RTW documentation lives in a software system, confirm that access controls reflect the medical-administrative separation.
Retrievability matters as much as completeness. If the carrier calls at 3:45 p.m. and needs the refusal record, you need to be able to produce it in minutes, not hours. A case management system that ties offer letters, refusal logs, provider authorizations, and carrier communications to a single claim record makes that possible in a way that a folder of individual files does not.
Build the Record Before You Need It
The best time to build a refusal documentation habit is before a worker refuses. That means having a structured offer letter that meets your state's requirements, a provider-authorization step built into every duty-matching process, a second person identified before you make any modified-duty offer by phone, and a refusal log template that your coordinators can complete in the room or on the call.
Download the Modified Duty Offer Letter Templates from the Transitional Duty Manager store — they are formatted to support the documentation chain described here, and they pair with the refusal log structure above so the complete file stays coherent.
When you have the offer structure right, the refusal record follows naturally. When you do not, the refusal is where the gaps become visible — and costly.
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
