Managing Multiple Concurrent RTW Cases Without Losing Track

When the Third Case Opens, the System Breaks

It is a Tuesday morning. You have two light-duty workers already placed — one on a modified assembly role, one doing sedentary paperwork while a shoulder heals. The attending provider has just faxed an Activity Prescription Form for a third worker. At the same time, you get a voicemail from the carrier asking for an updated job description on the second case, and a reminder pops up that the first worker's transitional period is approaching its documented end date.

None of those three things is unusual. Together, on a Tuesday, with your regular duties running in parallel, they are the exact moment most RTW programs stop functioning as programs and start functioning as improvised memory exercises.

Managing concurrent return to work cases is not primarily a time-management problem. It is an information-architecture problem. The question is not whether you are working hard enough — it is whether the system surfaces the right fact about the right case at the right moment, without requiring you to hold the entire caseload in your head.

This article lays out a practical framework for triaging, tracking, and advancing multiple open cases simultaneously, so that a busy coordinator or HR manager can keep every case moving without missing a deadline, a reimbursement window, or a restriction change.

---

The Four Fields That Matter Across Every Open Case

Before any triage logic can work, every open case needs to carry the same minimum data fields — consistently, in the same format, updated at the same cadence. Coordinators who manage concurrent caseloads without a shared schema end up with one case in a folder, one in email, and one on a sticky note. That is when things fall through.

For each open case, maintain:

1. Restriction expiry date (or "open until further notice" flag). The attending physician's documented restrictions have a date range. When that date arrives and no updated report has been received, the case is in an uncontrolled state — neither clearly active nor clearly closed. Flag every case with an explicit next-provider-contact date before the restriction period ends.

2. Transitional duty end date (program-maximum or employer-policy maximum). Most employer RTW policies cap transitional duty at a defined period — 30, 60, or 90 days is common — after which the worker either returns to full duty, moves to a permanent accommodation process, or the claim disposition changes. That date is a hard deadline, not a soft target.

3. Reimbursement application status. If the claim is in a state with a wage-reimbursement program — Washington Stay-at-Work, Oregon EAIP, Ohio BWC Transitional Work, or the Texas workplace-modification benefit — there is a filing deadline and a documentation checklist. For Washington specifically, the reimbursement application must be submitted within one year after the light-duty work is performed; days worked outside an approved job description or outside approved hours are ineligible for reimbursement. (WA L&I, 2025) That eligibility is reconstructed from daily records after the fact, so the field you need to track is not just "SAW eligible: yes/no" — it is "SAW-eligible days logged this pay period: N" and "application submitted: yes/no."

4. Last documented contact date (carrier, provider, and worker). Cases stall when contact lapses. A case with no carrier contact in 30 days and no updated restriction document is a case that is quietly heading toward litigation or a missed closure opportunity. The field forces the question: when did something actually happen on this case, and what is the next scheduled touchpoint?

If every open case carries those four fields in a readable format, you have the minimum viable picture. If any of those fields is blank or out of date, that case is your most urgent case — regardless of how the worker is doing day to day.

---

Triage Logic: How to Prioritize When Everything Feels Urgent

With three, five, or eight cases open, not all of them require the same attention today. A triage framework lets you allocate the first hour of your morning to the cases that will cause irreversible harm if ignored, and batch the routine-status cases into a defined window later.

Sort your open cases each morning by the following hierarchy:

Tier 1 — Deadline within 5 business days. Any case where a restriction expiry, transitional duty end date, or reimbursement filing deadline falls within the next five business days. These cases require a specific action today: a provider contact to obtain an updated restriction document, a supervisor notification, a reimbursement application assembly, or a case-status conversation with the carrier. Do not let a Tier 1 case sit in a queue.

Tier 2 — Documentation gap. Any case where the last documented contact (provider, carrier, or worker) is more than 14 days ago, or where a required document (signed job description, updated restriction, acknowledged offer letter) has not been received. Documentation gaps are not emergencies yet, but they become emergencies on a predictable schedule. Tier 2 cases get a contact or follow-up action this week.

Tier 3 — Active and current. Cases where all four core fields are populated, all deadlines are more than five business days out, and the last documented contact is within 14 days. These cases need a status review this week but do not require immediate action. Batch them into a defined review block — Friday afternoon works well — rather than letting them interrupt Tier 1 and Tier 2 work.

Tier 4 — Pending closure. Cases where the worker has returned to full duty or the claim has been resolved but the file has not been formally closed and archived. These cases carry administrative risk: an open file with no active restrictions can create confusion if a new injury occurs or a carrier audit arrives. Close them on a defined schedule — within five business days of the worker's return to full duty — and archive the complete documentation set.

For a deeper look at how restriction expiry and maximum-duration flags function within a case file, see Tracking Restriction Expiry and Maximum Duration Flags.

---

The Information Hand-Off Problem: Supervisors and Carriers

One of the most common failure modes in concurrent caseload management is not a missed internal deadline — it is a communication breakdown between the RTW coordinator and the people who interact with the worker daily.

Supervisors are responsible for keeping the worker within the approved restrictions during each shift. But supervisors are not case managers. If a supervisor is tracking three or four light-duty workers across a shift, they are working from memory or from a whiteboard unless the coordinator has put the essential restriction summary in front of them in writing — specific to that worker, specific to that shift, with a named contact for questions.

The restriction summary a supervisor receives should contain exactly two things: what this worker can and cannot do, and who to call if something changes. It should not contain a diagnosis, a claim number, or any medical information beyond the functional restrictions. Under ADA confidentiality requirements, supervisors and managers receive restrictions and accommodations only — not the diagnosis. (EEOC via Gordon Feinblatt, 2024) That boundary is not just a legal requirement; it is also a practical one. A supervisor who knows the diagnosis but not the restrictions is holding the wrong information.

On the carrier side, the hand-off problem looks different. Carriers are tracking their own claim-closure metrics, and their interest in keeping a transitional duty placement active may not align with the employer's interest in a genuine recovery arc. The coordinator's job is to document the employer's RTW process completely and independently — not to rely on the carrier's claim file as the record of what happened. That means every offer letter, every signed job description, every restriction update, and every day-count for reimbursement purposes lives in the employer's own file, not only in the carrier system.

---

When Spreadsheets Stop Working

A single well-structured spreadsheet can manage one or two open cases reasonably well. It starts to fail at three or more concurrent cases, and it fails completely when cases overlap in their active periods, when the coordinator is out and a backup has to step in, or when a carrier or attorney requests a complete audit trail on short notice.

The specific failure modes are predictable:

• Date formulas break silently. A spreadsheet that calculates days remaining from a manually entered date gives a wrong answer the moment someone types the date in a different format — and there is no alert.
• There is no version history. When a restriction changes or a duty description is updated, the old version disappears. In a reimbursement audit or a dispute, the prior approved description may be material.
• Concurrent editing is not safe. A coordinator and an HR assistant editing the same workbook simultaneously create data conflicts that are not always visible until a number is wrong.
• There is no automatic escalation. A spreadsheet does not send a notification when a deadline is three days out. The coordinator has to remember to look.

For a direct comparison of what a purpose-built tracking tool addresses relative to a spreadsheet setup, see RTW Software vs. Spreadsheets.

If you are managing concurrent return to work cases today with a spreadsheet and need a structured starting point before transitioning to software, the Transitional Duty Case Tracking Workbook provides a field-complete template built around the four core tracking fields and the triage logic described above.

---

Building Sustainable Capacity: Cadence Over Heroics

The coordinators who manage five or six concurrent cases without crisis are not doing so through superior memory or longer hours. They are doing it through a defined weekly cadence that separates different types of case work into different time blocks.

A sustainable cadence for a coordinator managing multiple concurrent return to work cases typically looks like this:

Day	Block	Activity
Monday	Morning (45 min)	Full caseload triage: assign each case to Tier 1–4
Monday–Wednesday	As needed	Tier 1 actions: provider contacts, deadline-driven document assembly
Tuesday–Thursday	Defined 30-min block	Tier 2 follow-ups: carrier contacts, outstanding document requests
Friday	Afternoon (30 min)	Tier 3 status review; Tier 4 closures; next-week deadline preview

The cadence works because it reduces the cognitive load of deciding what to do next. When a new case opens mid-week, the coordinator places it in the triage matrix on the following Monday — or immediately if it is Tier 1 — rather than allowing it to interrupt the entire workflow.

For operations managing cases across multiple facilities or locations, the cadence and information-architecture questions become more complex. Multi-Site RTW Portfolio Management covers how to extend this framework across a distributed operation.

---

What a Well-Run Concurrent Caseload Looks Like

A coordinator with four open cases and a working system can answer the following questions in under two minutes, without opening a single email:

• Which case has a deadline in the next five business days?
• Which case is missing a required document?
• For each case in a reimbursement-eligible state, how many approved days have been logged this period?
• When was the last documented contact with the carrier on each case?

If those questions take longer than two minutes to answer — or require checking multiple systems, email threads, or folders — the information architecture is the problem, not the caseload volume.

The full framework for building and maintaining a case management system from intake through closure is covered in the Return-to-Work Case Management Guide.

When you are ready to move from a manual tracking setup to a system that surfaces triage flags, tracks restriction windows, and maintains the audit trail automatically, start a free trial of Transitional Duty Manager and run your next case in the platform.