How to Build a Transitional Duty Program From Scratch

Why Most Transitional Duty Programs Fail Before the Third Claim

Picture this: a line supervisor forwards a fax from the treating clinic — light duty approved, four-hour days, no overhead lifting, effective Monday. The HR manager writes the restrictions on a sticky note, assigns the worker to "something light," and marks the claim as active. Three weeks later the carrier calls for documentation. Nobody can locate a signed job description. The approved hours were never tracked. The day the worker stayed an extra two hours to help unload a truck? That day is gone, and so is any reimbursement eligibility tied to it.

This scenario is not unusual. A transitional duty program exists in almost every organization that has survived a lost-time claim — but the program is often a set of informal habits rather than a documented system. Informal habits do not survive coordinator turnover. They do not satisfy a carrier audit request. They do not generate the records needed to recover wage-reimbursement dollars from state programs.

The difference between a program that holds and one that collapses under pressure is the build order. Stand up the right components in the right sequence, and each claim that runs through the system strengthens it. Rush to the task-matching step without a policy or a documentation framework, and every claim creates a new improvised variant of the program.

This guide walks through how to build a transitional duty program from scratch — the six structural components, in the sequence that makes each one usable before the next one depends on it.

---

Step 1 — Write the Policy First, Before You Touch Tasks or Forms

The written policy is the foundation everything else rests on. Before you designate a transitional duty coordinator, before you build a task bank, before you order new forms, you need a document that answers three questions in plain language:

1. What is the program's purpose and scope? Define "transitional duty" explicitly: it is temporary, modified work assigned within the injured worker's medical restrictions, with the goal of maintaining employment continuity and supporting recovery. State which locations, worker classifications, and claim types the program covers.

2. What are the duration limits? Most programs cap transitional assignments at 90 to 120 days. The cap should appear in the policy. A cap without a written policy is an informal practice; an informal practice creates inconsistency exposure when two workers in similar circumstances receive different treatment.

3. What happens at the end of the transitional period? The policy must describe the exit paths: return to full duty, extended accommodation under a separate ADA process, or separation — and specify which of those decisions belongs to whom.

A written policy also defines participation expectations for supervisors and the injured worker. That clarity matters the moment a supervisor says "we don't have anything for them" and a coordinator needs to push back with authority.

For a policy template you can adapt to your operation, see the RTW program policy template.

---

Step 2 — Build the Task Bank Before Any Claim Opens

A task bank is a pre-approved, written list of specific modified-duty assignments, organized by the physical demands they require. Building it before a claim opens is not optional — it is the single most time-sensitive structural decision in program design.

Here is why the sequence matters: when a claim opens, you typically have 24 to 72 hours to offer transitional work before the worker is placed by the carrier into the medical-management track. If you build the task bank during that window, you will produce a list shaped by desperation and the one supervisor who happened to pick up the phone. That list will not reflect actual work available across your facility, and it will not hold up if the treating provider reviews it.

A well-constructed task bank has four characteristics:

• Each task is written as a job description, not a job title. "Light assembly" is not a task description. "Visual inspection of finished components at a stationary workbench, seated or standing, no lifting above five pounds, no repetitive wrist rotation" is a task description a physician can evaluate.
• Each task specifies its physical demand level — sedentary, light, medium — using consistent definitions across the bank. Sedentary: lifting limited to ten pounds occasionally, mostly sitting. Light: lifting up to twenty pounds occasionally, frequent lifting or carrying up to ten pounds.
• Each task includes a realistic capacity. How many workers can be absorbed in this assignment at the same time? A task that can only accommodate one person should not appear on the bank as if it scales.
• Each task is reviewed and pre-approved by management before any claim opens. Pre-approval means a supervisor has confirmed the work is available, that the output serves a genuine operational need, and that the physical demands described are accurate.

The task bank is also the document you submit to the treating provider for written approval of a specific transitional assignment. Under Washington's Stay-at-Work program, the attending provider must approve the transitional job description in writing before those days become reimbursable — there is no retroactive approval mechanism. (WA L&I Complete Stay at Work Guide, 2024) Building the bank in advance means you can submit a task description to the provider the same day the claim opens rather than drafting one from scratch under time pressure.

For a detailed walkthrough of task-bank construction, including physical-demand classification and task-description templates, see how to build a transitional duty task bank.

---

Step 3 — Assign Roles and Put Them in Writing

A transitional duty program is a coordination problem. The claim involves the employer, the treating provider, the carrier or TPA, and the injured worker — and they rarely communicate in real time. Someone at the employer has to own each handoff.

The minimum role structure for a program that runs more than two or three concurrent cases is:

Role	Core Responsibilities
RTW Coordinator	Opens the case file; requests restrictions; submits the transitional job description to the provider; tracks approved days, hours, and restrictions; triggers reimbursement filings; manages case closure
Direct Supervisor	Confirms task availability on the floor; monitors that the worker stays within approved hours and duties; reports any restriction changes to the coordinator immediately
HR or Risk Manager	Maintains ADA-compliant medical record separation; handles the ADA interactive process if the injury triggers a longer accommodation need; manages any benefit continuation questions

The ADA dimension is not incidental. Medical information — including restriction letters from treating providers — must be maintained on separate forms, in a separate medical record, accessible only to personnel with a legitimate business need. (29 CFR 1630.14(c)(1); JAN, 2025) Supervisors receive the worker's restrictions and accommodations, not the underlying diagnosis. (EEOC via Gordon Feinblatt, 2024) Your role structure should make this separation automatic rather than dependent on someone remembering the rule during a busy week.

For a full treatment of how to document RTW roles in a format that survives turnover, see RTW roles and responsibilities.

---

Step 4 — Set Up the Documentation Framework Before the First Case

Documentation is the audit trail. In the context of a transitional duty program, it serves four distinct functions:

1. Reimbursement eligibility. State wage-reimbursement programs are documentation-gated. Washington's Stay-at-Work program, for example, requires that the attending provider approve the transitional job description in writing, and that the reimbursement application be submitted within one year after the light-duty work is done. (WA L&I, 2025) A day worked outside the approved job description or approved hours is ineligible — for instance, if the provider approved four hours and the worker was on-site for six, that day does not qualify. (ERNwest, 2025) You cannot reconstruct this documentation retroactively with sufficient reliability to satisfy the program.

2. Carrier audit defense. When a carrier audits a claim, they look for a signed offer of transitional duty, a written job description with physical demand levels, a record of who approved the assignment, and daily or weekly attendance records that match the restriction windows. If those documents are not in a centralized case file, the audit becomes a search project — and the absence of records creates ambiguity about whether the program was administered consistently.

3. EMR protection. A claim that is managed as a medical-only claim — rather than a lost-time claim — receives materially different treatment in experience-rating calculations. Under NCCI experience rating, medical-only primary loss value is reduced by 70%, meaning only 30% is applied toward the experience modification calculation. (National Workers Comp Authority, 2025) Transitional duty is the mechanism for keeping a claim medical-only by maintaining wage continuity. The documentation that proves a transitional assignment was offered, accepted, and worked is the same documentation that supports a medical-only classification.

4. Consistency protection. Written records of how each case was managed let you demonstrate that similarly situated workers received the same program — which is relevant under both EEOC standards and general employment-practice liability.

The minimum document set for each case:

• Written offer of transitional duty (dated, signed by the employer)
• Transitional job description submitted to the treating provider (physical demands, hours, duration)
• Provider's written approval of the job description
• Daily or weekly attendance/hours log for the transitional period
• Record of any restriction changes and corresponding assignment modifications
• Case closure documentation

For a detailed guide to writing the job description component, see how to write a light-duty job description.

---

Step 5 — Map the Reimbursement Workflow by State

If your operation spans multiple states — or if you are starting in a single state with a wage-reimbursement program — the reimbursement workflow needs to be mapped before claims open, not discovered during one.

State wage-reimbursement programs vary materially in their parameters, deadlines, and eligible expenses. The table below summarizes the current parameters for the four states with the most operationally significant programs. Confirm current figures, form versions, and effective dates directly with each administering agency before filing.

State	Program	Wage Reimbursement	Duration	Cap	Key Deadline
Washington	Stay-at-Work (SAW)	50% of base wages	Up to 120 days worked	$25,000 per claim (injuries on/after Jan 1, 2025)	Application within 1 year after light-duty work is done
Oregon	EAIP	50% of early RTW gross wages	Up to 66 work days within 24 consecutive months	$5,000 combined cap on worksite modification + tools/equipment; $120 administrative fee	Confirm with OR WCD
Ohio	Transitional Work Grant	100% of approved development costs	Re-apply every 5 years	$3,700–$8,200 by employee count (effective July 1, 2023)	Confirm with OH BWC
Texas	Workplace modification assistance	Up to $5,000 for DWC-preauthorized modifications	One-time per qualifying employer	Employers with 2–50 employees carrying WC coverage	Confirm with TDI-DWC

Sources: WA L&I / AGC of Washington, 2025; OR WCD, 2024–2025; OH BWC, 2023; TDI-DWC RTW Guide, 2023.

A few operational notes that affect the workflow design:

Washington: A partial day of transitional work counts as one reimbursable day — but only if the worker stays within the approved hours. A day worked outside approved hours is ineligible. (WA L&I Complete Stay at Work Guide, 2024) The reimbursement application is a separate filing from the claim itself; many employers miss the one-year filing window because nobody owned that deadline. In Washington, SAW and Preferred Worker Program (PWP) combined create a total reimbursement opportunity of up to $75,000 per claim for injuries on or after January 1, 2025. (AGC of Washington, 2025)

Texas: The written Bona Fide Offer of Employment (BFOE) under 28 TAC §129.6 must meet every requirement of the rule. A valid written BFOE that the injured worker refuses or fails to acknowledge allows the carrier to reduce or suspend indemnity benefits — but only if the offer was written and documented correctly. (TDI-DWC RTW Guide, 2023) Once the offer is mailed, the worker is deemed to have received it five days later, and the carrier may treat the offered wages as post-injury earnings - reducing indemnity benefits - on the earlier of the worker's rejection or the seventh day after that deemed receipt. (28 TAC §129.6, 2024)

Oregon: The $120 EAIP administrative fee is a one-time program fee, not per-claim. (OR WCD, 2025)

Ohio: The prior per-lifetime limit on transitional work grants was removed; employers may now reapply every five years. Ohio's Transitional Work Bonus (a premium discount for employers with an established transitional work program) is being phased out; confirm current status with OH BWC. The Transitional Work Grant is the durable incentive. (OH BWC)

Map which of your states has an active reimbursement program. For each, identify: who files the application, which forms are required, who tracks the filing deadline, and where the documentation is stored. Build that workflow into your case-management process before the first claim in that state opens.

---

Step 6 — Run a Closed Case Through the Program as a Drill

Before the program goes live, take one closed claim from the past 12 months and run it backward through the framework you just built.

• Could you produce a signed offer letter dated within 24–72 hours of claim opening?
• Could you produce a written job description with physical demands that match the provider's restrictions?
• Could you produce the provider's written approval of that job description?
• Could you produce a daily attendance log for the transitional period, with hours that match the approved schedule?
• If you are in Washington, could you have filed the reimbursement application within the one-year window?

Most operations find two or three documentation gaps on the first pass. That is useful. Finding those gaps on a closed claim costs nothing. Finding them during a carrier audit costs credibility; finding them after a reimbursement filing deadline costs real money.

The drill also stress-tests your role assignments. If the answer to "who would have done this?" is "whoever was available," the roles are not sufficiently defined.

---

How to Build a Transitional Duty Program: The Build Order at a Glance

Building in the wrong sequence is the most common source of rework. Here is the correct dependency chain:

1. Written policy — defines scope, duration limits, exit paths, and participation requirements
2. Task bank — pre-approved, physically characterized assignments ready before any claim opens
3. Role assignments — named and documented; includes ADA medical-record separation by design
4. Documentation framework — minimum document set for each case; storage and access protocols
5. Reimbursement workflow — state-specific filing deadlines, responsible party, and form set
6. Drill on a closed case — validates the framework before it runs live

Each component is simple in isolation. The value is in having all six in place before the next claim opens — not assembled during one.

---

Keeping the Program Alive Between Claims

The most overlooked maintenance requirement for a transitional duty program is the task bank. Physical demands change as operations change. Tasks that were available last year may not be available now. Tasks created for a specific department may no longer exist after a layout change.

Build a task-bank review into your annual safety program audit. Walk the floor with the list and confirm that each task is still operationally real and that the physical-demand characterizations are still accurate. Update job descriptions when operations change, not when a claim opens.

The role-assignment document needs the same treatment. Coordinator turnover is common. If the program is documented only in one person's head, the next coordinator starts from scratch — which is how informal programs re-emerge after formal ones are built.

---

Starting Point: The RTW Program Kit

If you are building from scratch and need a starting set of policy templates, job description formats, and case documentation forms — pre-organized in the build-order sequence described here — the RTW Program Kit — Complete contains the core documents in editable format. Download the kit, work through the six steps above, and adapt each document to your operation before the next claim opens.

For a broader treatment of how cases are managed once the program is running, see the return-to-work case management guide.