By Rovaryn Digital · 11 min read
Why an Audit Finds Holes Before You Do
Picture this: a lost-time claim is 40 days old. Your carrier's managed-care auditor sends a written request for the return-to-work file. They want the original modified-duty offer letter, the physician's written approval of the job description, a day-by-day log of hours worked under restriction, and a signed acknowledgment from the employee — or, if the employee refused, a contemporaneous record of the refusal.
You open the claim folder. There is an email thread, a handwritten note from your supervisor, and a copy of a job description that was revised twice with no version control. The offer letter is there, but it is undated. The physician's signature is on a fax cover sheet that no longer shows the transmission timestamp. You have no day log.
That gap — between what you remember happening and what you can prove happened — is where a workers' compensation carrier audit becomes a liability problem. It can delay a reimbursement application, undermine a benefit-suspension action after a refusal, or expose you to dispute on indemnity charges you believed were defensible.
This article maps the exact documents a carrier auditor examines in a return-to-work review, explains what makes each one defensible, and shows how an immutable audit trail lets you answer every request without reconstructing a record from memory.
What a Carrier Auditor Is Actually Looking For
Carrier audits of return-to-work activity are not random. Auditors work from a checklist driven by two questions: Did the employer comply with the procedural requirements that condition the carrier's ability to manage indemnity exposure? And do the records prove it?
The specific triggers vary — a contested refusal, a state reimbursement application, an experience-modification-rate review, or a routine large-loss audit — but the document requests converge on the same four categories every time.
1. The modified-duty offer. The auditor wants proof that a formal, written offer of transitional work was extended, that it specified the duties and hours within the physician's restrictions, and that it was communicated to the employee in a traceable way. Verbal offers, after-the-fact reconstructions, and undated documents carry no weight. In Texas, for example, a Bona Fide Offer of Employment under 28 TAC §129.6 must satisfy every statutory requirement in writing before the carrier can move to reduce or suspend benefits — a carrier auditor in that state will check the offer letter against the rule's criteria line by line. (TDI-DWC RTW Guide, 2023)
2. The physician's written approval. The offer means nothing without evidence that the attending provider approved the specific job description in writing before the employee performed the work. An approval note that postdates the start of transitional duty is a documentation failure, not a clinical one. Washington's Stay-at-Work program makes this explicit: the attending provider must approve the transitional job description in writing, and a light-duty day worked outside the approved job description or approved hours is ineligible for reimbursement. (WA L&I Complete Stay at Work Guide, 2024)
3. The day log. For any claim involving a reimbursement program or an indemnity calculation that depends on days worked, the auditor needs a contemporaneous record of each day the employee worked transitional duty — the date, hours, and whether the work fell within the approved description and schedule. In Washington, a partial day counts as one reimbursable day, but a day where the employee worked more hours than approved is disqualified entirely. (WA L&I Complete Stay at Work Guide, 2024) Without a day-by-day log, you cannot reconstruct which days count and which do not.
4. The refusal or acknowledgment record. If the employee performed the transitional duty, you need a signed acknowledgment or attendance record. If the employee refused a valid written offer, you need a contemporaneous record of the refusal — date, method of communication, employee statement if any, and your response. In Texas, a mailed BFOE is deemed received five days after mailing, and the carrier may reduce indemnity benefits on the earlier of the worker's rejection or the seventh day after that deemed receipt. (28 TAC §129.6(g), 2024) Without the refusal record, that reduction is indefensible.
The Anatomy of a Defensible RTW Document
An auditor distinguishes between a document that exists and a document that is defensible. The difference is metadata: the signals that tell a reviewer when a record was created, by whom, and whether it has been altered.
A defensible document has four properties.
Contemporaneous. The record was created at or immediately after the event it documents — the offer was dated the day it was extended, the physician approval was received before Day 1 of transitional duty, the day log entry was made at the end of each shift. Auditors are experienced at identifying records that were assembled after a dispute arose; gaps in date patterns, formatting inconsistencies across entries, and timestamps that contradict a narrative all register immediately.
Specific. Vague language fails. "Light duty as available" is not a job description. "Restrictions noted" is not a physician approval. "Employee was told" is not a refusal record. Every document should name the claim, the employee, the specific duties, the specific hours, the physician, and the specific dates. When a reimbursement application or benefit action goes to review, specificity is what allows a reviewer to match a document to an event.
Unaltered. A document that shows signs of revision without a version history — a crossed-out date, a different font in one paragraph, a digital file with a modified-date that postdates the event — raises questions that are difficult to answer. An immutable audit log that records who touched a record and when is the clearest evidence of document integrity.
Carrier- and state-linked. If the employer has changed carriers since the claim opened, the new carrier may audit under different standards than the prior one, and the prior carrier's records may not transfer automatically. A program that stores documentation independently of the carrier, tied to the claim and the worker rather than to the policy, survives a renewal or mid-claim carrier change without a gap in the record.
Building the Audit Trail Before the Audit Arrives
The point of an audit trail is that it exists continuously, not that it is assembled in response to a request. The employers who survive carrier audits without disruption are the ones whose documentation practices during the claim period are indistinguishable from their documentation practices during an audit.
That means the following steps happen in real time, not retrospectively.
Lock the offer letter before delivery. The modified-duty offer letter is drafted, reviewed against the physician's current restriction note, dated, and stored in a fixed format before it is delivered to the employee. If the letter is delivered by mail, the mailing is logged with the date and method. If it is delivered in person, the delivery is logged and ideally acknowledged in writing. See the modified duty offer letter guide for the specific elements that make an offer defensible.
Store the physician approval with the job description it approves. When the provider's written approval comes back — by fax, mail, or through a generated form — it is filed immediately alongside the exact version of the job description it approves. If the job description changes because restrictions change, the process starts again: new description, new approval, new filing. A job description revision without a corresponding physician approval creates an eligibility gap.
Run a daily log from Day 1. The day log is a simple record: date, scheduled hours, hours actually worked, and whether the work was within the approved scope. It does not need to be elaborate. It needs to exist, to be current, and to be stored where it cannot be modified retroactively without a visible record of the change. For reimbursement programs with strict eligibility rules — Washington's Stay-at-Work program, Oregon's EAIP — the day log is the primary evidence the administering agency uses to determine which days are reimbursable. Oregon's EAIP, for example, repays 50% of early return-to-work gross wages for up to 66 work days within a consecutive 24-month period; the day log is how you prove how many days qualify. (OR WCD, 2025)
Document refusals within 24 hours. If an employee refuses or fails to acknowledge a valid written offer, that fact is documented the same day — not at the end of the week, not when the claim handler follows up. The contemporaneous refusal record is what supports a subsequent benefit action. The guide to documenting light-duty refusal covers the required elements state by state.
Capture restriction changes as they happen. Restrictions are not static. When the treating physician modifies them — expanding hours, adding duties, shortening the transitional period — the updated restriction note is filed immediately and the day log is annotated to show which period corresponds to which restriction set. An auditor reviewing a six-month claim will expect to see the restriction history, not a single note applied to the whole period.
What Breaks Down in Practice — and Why
The most common documentation failures in workers' comp carrier audit documentation are not the result of negligence. They are the result of a documentation system that was not designed for concurrent claims, carrier changes, or multi-month timelines.
Spreadsheets collapse at scale. A single claim tracked in a shared spreadsheet is manageable. Three claims open simultaneously, with different physicians, different restriction windows, and different state programs, produce version-control problems, missed entries, and no audit log of who changed what. The comparison of RTW software and spreadsheets covers this in detail, but the audit consequence is straightforward: a spreadsheet cannot demonstrate that a record was not altered after the fact.
Carrier-bundled tools don't survive a renewal. Some employers document their RTW activity in tools provided by the carrier. When the policy renews with a different carrier, that documentation may not transfer. The incoming carrier audits from a blank file. The employer is left reconstructing records from email threads and memory — exactly the scenario this article opened with.
Verbal approvals are not approvals. A phone call from the case nurse confirming the physician is "fine with the offer" is not a written physician approval. It is a note in someone's call log, at best. If the physician later disputes the approval or the claim goes to hearing, the verbal confirmation is not evidence. The standard is written, and the written document must be filed contemporaneously.
Offer letters survive; delivery records don't. Employers often retain the offer letter but have no record of how or when it was delivered. The offer that was never demonstrably received is treated, for audit purposes, as the offer that was never sent.
The Role of an Immutable Audit Log in Workers' Comp Carrier Audit Documentation
An immutable audit log is a system-level record that captures every action taken on a claim file — document created, document accessed, document modified, user, timestamp — in a format that cannot be retroactively altered without the alteration itself appearing in the log. It is the technical implementation of contemporaneousness.
For RTW documentation, the practical effect is significant. When a carrier auditor or a state agency reviewer asks whether a particular record existed before a dispute arose, the audit log answers the question directly. The offer letter was created on this date, by this user, before the employee's refusal. The physician approval was filed on this date, which precedes Day 1 of transitional duty. The day log entry for each day was made within 24 hours of the shift.
This is not a capability that spreadsheets or generic document storage provides. It requires a purpose-built case management tool that ties every document action to a claim record and a timestamp that cannot be edited.
The full return-to-work case management guide explains how case management structure supports audit readiness across the life of a claim. The experience modification rate guide covers how a documented, defensible RTW program connects to the EMR calculation — because the audit trail that defends a claim today also supports the frequency-and-severity picture that determines next year's premium. With a 3-year experience window driving the EMR calculation (Higginbotham, 2026), a single poorly documented claim that converts from medical-only to lost-time status can affect the employer's cost for years.
Getting Audit-Ready Without Starting from Scratch
If the current documentation system is a folder of PDFs and a spreadsheet, the path to audit readiness is not a full rebuild — it is identifying the four document categories above and establishing a contemporaneous filing habit for each one, starting with the next claim that opens.
A practical starting point is a structured case tracking workbook that provides a consistent template for each document type — offer, physician approval, day log, refusal — with version control and a clear file structure. The Transitional Duty Case Tracking Workbook is designed specifically for this: a template-based system that imposes structure on each document category and makes the audit trail visible at a glance.
For operations handling five or more concurrent claims, or claims that span multiple states or carrier renewals, a software-based audit trail eliminates the structural limitations of a workbook. Start a free trial of Transitional Duty Manager to see how the platform maintains an immutable log across every claim, every document action, and every state program — independent of which carrier is on the policy at the time of the audit.
The documentation either exists in a defensible format, or it does not. The audit is when you find out which.
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
