By Rovaryn Digital · 10 min read
Why a Transitional Duty Case Needs a Formal Closing Step
Picture this: an injured assembler spent eleven weeks on light duty, returned to her full job in March, and everybody moved on. Six months later, an audit request lands on your desk. The carrier wants a dated, signed full-duty release and the last light-duty timesheet. You open the case file and find a phone note that says "back full duty" — no release, no closure date, no sign-off from anyone.
That gap is not unusual. Transitional duty programs are built around the opening end of a case — the restriction letter, the job description, the offer letter — and the closure step is treated as a formality that happens whenever someone remembers. The result is a file that technically never closed, restrictions that remain "active" on paper long after the worker is back at full capacity, and a documentation trail that cannot support a benefit-suspension decision, a reimbursement application, or a carrier inquiry without significant reconstruction.
This article explains what a proper return to full duty case closure looks like, how to handle the other realistic disposition paths when a case does not end with a clean full-duty release, and what records need to be in the file before you mark anything closed. By the end, you will have a step-by-step process you can apply to the next case that reaches its endpoint — whatever that endpoint turns out to be.
The Four Realistic Disposition Paths
Not every transitional duty case ends with the worker back at her original job at full capacity. Before you can document a closure correctly, you need to name the actual outcome. There are four paths that cover nearly every case.
Path 1 — Full duty release, return to original position. The treating physician issues a written release lifting all restrictions. The worker resumes her pre-injury job without modification. This is the most common and cleanest path.
Path 2 — Maximum medical improvement (MMI) with permanent restrictions, reassignment. The physician determines the worker has reached MMI and the remaining restrictions are permanent. The employer offers and fills a different position that accommodates those restrictions within ADA interactive-process requirements. The transitional duty case closes; the accommodation is documented separately under ADA.
Path 3 — MMI with permanent restrictions, no suitable position available. The employer conducts a documented good-faith search, concludes no position can be reasonably accommodated, and — after completing the ADA interactive process — the employment relationship ends or the worker is placed on an unpaid leave status. The transitional duty case closes; the separation documents belong in the ADA file, not the RTW file.
Path 4 — Voluntary resignation, termination for cause, or claim closure without medical discharge. The worker leaves for reasons unrelated to the injury, or the workers' comp claim closes administratively before the restriction period ends. The transitional duty case closes on that date with the specific reason recorded.
Naming the path before you start the closure paperwork determines which documents you need and which regulatory obligations attach.
What Goes in the Closure File
Regardless of which path applies, every closed transitional duty case should contain the same core documentation set. Think of it as the file a carrier auditor, a state agency reviewer, or your own legal counsel would need to reconstruct the case without calling anyone.
1. The medical endpoint document. For Path 1, this is the full-duty release — a written, dated, signed statement from the attending provider lifting restrictions. A verbal release relayed by the worker is not sufficient; call the clinic and request the written note, or use a medical status update form your program provides for the provider to complete. For Paths 2 and 3, this is the MMI determination with the permanent restriction list. For Path 4, it is the last restriction letter on file, with a notation that the employment relationship ended before medical discharge.
2. The last approved light-duty timesheet. For any case where a state reimbursement program applied — Washington Stay-at-Work, Oregon EAIP, or similar — the timesheet is not optional. Document every approved day worked, with the hours matching the approved job description. Confirm the last date of light-duty work before closure. This date anchors your reimbursement application window and, where applicable, affects whether the final partial days count.
3. The return-to-full-duty acknowledgment (Path 1). A short document — one page is sufficient — signed by the worker and a supervisor or HR representative, confirming the date restrictions were lifted, the date the worker returned to the original job classification, and that no further accommodation is needed at this time. This is distinct from the medical release; it is the employer-side record that the transition actually happened.
4. The case closure summary. A dated record, authored by the RTW coordinator, identifying the case by claim number or internal ID, stating the disposition path, listing the final restriction status, noting any open items (pending reimbursement application, ADA file transfer, FMLA exhaustion date), and recording who was notified — typically the supervisor, HR, the carrier or TPA, and the payroll contact.
5. Notification to the carrier or TPA. Do not assume the carrier knows the worker is back at full duty or that the transitional assignment ended. A written notification — email is fine, so long as it is retained — prevents the carrier from continuing to track an open transitional assignment that no longer exists, and it starts the clock on any reimbursement program deadline the carrier helps administer.
Documenting a Return to Full Duty: Step by Step
The following sequence applies to Path 1 closures. Adapt as needed for the other paths.
Receive the written full-duty release. Confirm it is dated, signed by the attending provider, and specifies that all restrictions are lifted. If it says "may return to work" without specifying full duty or restriction status, call the provider's office and request clarification in writing before closing the case.
Calculate the last reimbursable day. If a state wage-reimbursement program is in play, identify the last calendar date on which approved light-duty work was performed. Confirm the hours match the approved job description. Flag any day where hours worked exceeded or fell short of the approved schedule — those days may not be reimbursable.
Prepare the return-to-full-duty acknowledgment. Complete the form with the claim number, the worker's name, the medical release date, the return date to the original classification, the job title, and the name of the supervisor who confirmed the return.
Have the acknowledgment signed. Obtain signatures from the worker and the supervisor or an authorized HR representative. File the signed original in the case file; give the worker a copy.
Notify the carrier or TPA in writing. State the medical release date, the date the worker returned to the original position, and whether a reimbursement application is forthcoming.
Update your case management record. Set the case status to closed, record the disposition path and the closure date, and note any pending items with their responsible party and due date.
Transfer any ADA or FMLA records as needed. If FMLA leave ran concurrently with transitional duty, confirm the FMLA exhaustion date and close that tracking separately. See the guidance on coordinating FMLA and workers' comp for the interaction between these two processes.
File the reimbursement application before the deadline. Reimbursement program deadlines are strict and vary by state. Do not leave this step to the carrier; the application is the employer's obligation. Confirm the current deadline with the administering agency before submitting.
The ADA Boundary at MMI
Paths 2 and 3 require a brief note on scope, because the RTW coordinator's role changes at the point of MMI with permanent restrictions.
Up through the transitional duty period, the RTW coordinator is managing a time-limited accommodation — a temporary assignment with documented restrictions, reviewed periodically as the worker heals. That is RTW program territory.
At MMI, permanent restrictions trigger ADA interactive-process obligations that belong in a separate HR or legal process. The RTW file should document that MMI was declared, that restrictions are permanent, and that the case is being closed and transferred to the ADA process. It should not document the ADA analysis itself, the specific interactive-process exchanges, or the accommodation decision — those belong in the ADA file, which carries its own confidentiality requirements under 29 CFR 1630.14(c)(1).
One practical point: supervisors and managers in the ADA process are entitled to know the worker's restrictions and what accommodations are in place. They are not entitled to know the underlying diagnosis. That boundary — restrictions yes, diagnosis no — applies equally during transitional duty and carries through to any permanent accommodation. Confirm the specifics of your ADA obligations with employment counsel; this is a description of the mechanism, not legal advice.
Common Errors That Complicate Case Closure
Leaving restrictions technically active. If your case management system or spreadsheet still shows active restrictions after the worker returned to full duty, that record conflicts with the medical release and creates confusion for anyone who queries the file later. Update the restriction status on the closure date.
Missing or undated release documentation. A full-duty release with no date — or one that was received weeks after the return actually happened — creates a gap between what the medical record says and what actually occurred. Date-stamp incoming medical documents when you receive them, and note the receipt date separately from the document date if they differ.
Closing the case before notifying the carrier. The carrier may be tracking indemnity benefits, managing a reimbursement application, or coordinating a reserve adjustment. Notify before closing, not after.
Confusing claim closure with case closure. The workers' comp claim may close — administratively or by agreement — while the worker is still on transitional duty. The RTW case closes on the date the transitional assignment ends or the worker returns to full duty, which may be a different date. Track them separately.
Failing to capture the FMLA endpoint. If FMLA ran concurrently, the exhaustion date matters for benefit continuation obligations. Do not fold it into the RTW closure without noting it explicitly. The FMLA and workers' comp coordination guide covers this interaction in detail.
Building the Habit Across Multiple Concurrent Cases
A single case with a clean full-duty release is manageable in a spreadsheet. Three or four cases at different stages — one approaching MMI, one pending a reimbursement application, one where the worker resigned mid-assignment — quickly exceed what informal tracking handles well. Restriction expiry flags and maximum-duration alerts help you see which cases are approaching a decision point before they pass it. See the guidance on restriction expiry and maximum duration flags for how to set up that visibility.
The case closure step should be built into the program's standard workflow, not treated as an afterthought. A program that opens cases consistently and closes them inconsistently produces an audit trail with a systematic gap at exactly the point the auditor will look first.
For a complete view of how case closure fits into the full RTW workflow — from first report through return — see the return-to-work case management guide.
Templates for Each Disposition Path
Each disposition path above requires a slightly different document set. The Return-to-Full-Duty & Case Closure Pack at /store/return-to-full-duty-case-closure-pack includes editable templates for the full-duty acknowledgment, the case closure summary, the carrier notification letter, and the MMI-to-ADA transfer memo — formatted to work alongside the rest of your RTW program file. Download the pack and adapt the templates to your organization's claim numbering and notification chain before the next case reaches its endpoint.
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
