By Rovaryn Digital · 10 min read
When the Calendar Wins
A warehouse coordinator receives an Activity Prescription Form on a Monday morning. She logs the restrictions — no lifting over 15 pounds, no repetitive bending — assigns the injured worker to a light receiving task, and moves on to the next item in her queue. Six weeks later, the carrier's field case manager calls: the re-evaluation appointment was never scheduled, the restriction window lapsed two weeks ago with no documented review, and the worker is still on light duty without a current provider sign-off.
No single person failed. The restriction expiry date lived on a paper form in a manila folder, and nobody had a system reminding them to look at it.
This is how transitional-duty assignments drift from short-term medical accommodations into indefinite arrangements that expose the employer to ADA-accommodation questions, carrier friction, and audit findings. Restriction expiry tracking — combined with a max-duration flag that forces a human review at a defined ceiling — is the operational mechanism that prevents that drift. This article explains how to set that system up, what the 90-day flag means in practice, and why the flag triggers a review rather than an automatic termination.
Why Restriction Dates Are Not Self-Enforcing
An Activity Prescription Form, a work-status note, or a treating provider's restriction letter is a point-in-time document. It describes what the worker can do as of the date the provider signed it. It is almost never a standing order that remains accurate indefinitely.
Restrictions change in both directions. A worker recovering from a rotator cuff strain may have lifting limits reduced from 10 pounds to 30 pounds at the six-week mark, opening more transitional tasks. A worker with a cumulative soft-tissue injury may have a restriction tightened — or extended — when the provider sees a plateau in recovery. Either change should produce a new document, and that new document needs to reach the RTW coordinator before it affects the assignment.
The problem is that provider appointments do not appear on the coordinator's calendar by default. Without a structured alert, the coordinator's awareness of the restriction window depends entirely on the worker remembering to share updated paperwork — a system that research into RTW outcomes suggests breaks down precisely when cases are complex or relationships are strained.
Research from the Workers' Compensation Research Institute (WCRI, 2018) found that roughly 50% of injured workers return to work within 30 days, and approximately 75% return by three months. That data point matters for setting a 90-day ceiling: the large majority of cases that will resolve with standard RTW do so before the flag fires. The cases still open at 90 days are, by definition, the complex or prolonged ones — exactly the cases that need the most deliberate review, not passive continuation.
Anatomy of a Restriction Expiry Alert System
A functional alert system has four components. They can be implemented in purpose-built RTW case management software or, with discipline, in a shared calendar and a structured spreadsheet — though managing multiple concurrent cases in a spreadsheet breaks down quickly.
1. Restriction window entry at intake
When a new restriction document arrives, the coordinator records three dates:
- Document date — the date the provider signed the form, not the date it was received.
- Restriction effective date — the date from which the restrictions apply (often the same as the document date, but sometimes explicitly stated as a future date post-surgery or post-procedure).
- Next review or expiry date — either the explicit date the provider listed ("re-evaluate in six weeks") or the coordinator's calculated date based on the stated duration ("lifting restriction for 45 days from injury date").
If the provider gave no explicit duration or re-evaluation date, record the document date and set an alert for 30 days out as a default prompt to request an updated status from the provider. Do not assume an open-ended restriction is permanent or that it will self-close.
2. Tiered alert schedule
A single alert on the expiry date is insufficient — by the time it fires, there may be no time to schedule a provider appointment, brief the supervisor, or prepare revised duty paperwork before the window closes.
A tiered schedule works better:
| Alert | Timing | Action prompted |
|---|---|---|
| Early reminder | 14 days before restriction expiry | Coordinate with worker to confirm provider appointment is scheduled |
| Pre-expiry notice | 5 days before restriction expiry | Confirm updated documentation is received or request it in writing |
| Expiry-day flag | Day of restriction expiry | Document current status; do not continue assignment without a renewed restriction document or a full-duty release |
| 90-day max-duration flag | Day 90 of the transitional assignment | Mandatory supervisory and HR review; see §4 below |
The 14-day and 5-day alerts are soft prompts — they appear in the coordinator's queue and generate a logged entry, but they do not automatically change the assignment. The expiry-day flag is a harder stop: the case record should show a documented decision, not silence.
3. Document receipt confirmation
An alert that fires without a corresponding document is just noise. Each alert should trigger not only a calendar reminder but a documentation step: either a new restriction form is attached to the case file, or a note is logged explaining why it has not yet arrived and what the follow-up action is. This creates the audit trail that carriers and legal counsel will ask for if the case becomes disputed.
The audit trail value here is significant. WCRI data (2018) shows that workers at employers with 1 to 50 employees do not return to work at a rate of 21% — roughly double the rate at employers with 250 to 1,000 employees. Smaller operations are more exposed precisely because their case-management infrastructure is thinner. A documented alert system is one of the lowest-cost ways to close that gap. For guidance on building the broader record, see RTW audit trail and carrier audit preparation.
4. Medical record confidentiality
Every restriction document that arrives is a medical record. Under ADA requirements, medical information must be kept on separate forms, in a separate medical file, accessible only to personnel with a legitimate need (29 CFR 1630.14(c)(1); JAN, 2025). Supervisors and managers are entitled to know the restrictions and accommodations — not the underlying diagnosis (EEOC via Gordon Feinblatt, 2024). The alert system should surface restriction information to the supervisor, not the full medical document. This applies to electronic records as well as paper (EEOC Informal Discussion Letter, 2011).
The 90-Day Max-Duration Flag: What It Is and What It Is Not
The 90-day flag is a case-management signal, not a legal deadline or a program-termination trigger. It means: this transitional assignment has been running for 90 days; a deliberate human review is required before it continues.
There is no universal federal or OSHA mandate that transitional duty must end at 90 days. Some state programs use specific windows — Oregon's Early Return to Work program, for example, covers wages for up to 66 work days within a 24-month period (OR WCD, 2025) — but the 90-day flag in a case management system is an operational ceiling chosen to prevent indefinite continuation, not a legal rule.
What the flag actually does:
- Fires a required review task assigned to the RTW coordinator and the supervisor. The task cannot be dismissed without a logged outcome.
- Prompts documentation of the current restriction status — is there a current provider document on file, or is the assignment running on an expired restriction?
- Requires a recorded decision from HR or management: continue with documented medical support, escalate to an ADA interactive-process review, or initiate case closure per your RTW program's criteria.
- Does not terminate the assignment automatically. Auto-termination based solely on a calendar trigger — without a physician's release, without HR review, and without documented rationale — creates legal exposure. The flag forces the review; the review produces the decision.
The distinction matters because some cases legitimately run longer than 90 days. A worker recovering from a surgically repaired fracture, for instance, may be on appropriately documented light duty at day 95, with a current provider restriction in the file and a documented prognosis. The flag in that case is not a problem — it is confirmation that the coordinator looked at the file and recorded a sound basis for continuation.
What the flag surfaces as a concern is the case where the assignment is running on an expired restriction from week three, no updated documentation has been requested, and nobody has talked to the supervisor about whether the transitional task still fits the worker's current functional capacity. That case needs intervention regardless of how many days have elapsed.
For a structured look at what case closure should look like when full-duty release does arrive, see case closure and return to full duty.
Handling the 90-Day Review in Practice
When the flag fires, the coordinator should run through a short documented checklist:
- Is a current restriction document on file? If not, the first action is requesting one from the treating provider — in writing, with a copy to the file.
- Does the transitional task still match the current restrictions? If the worker's restrictions have changed and the task was not updated, document the mismatch and correct it before continuing.
- Has the supervisor confirmed the worker is performing within restrictions? Get a dated written confirmation; a verbal conversation has no audit value.
- Is the worker aware of the review? The review is not disciplinary; communicating it clearly — in writing — prevents misunderstanding. If the worker has declined modified duty at any point during the case, that refusal should already be documented; see documenting light-duty refusal.
- What is the documented forward plan? The review should produce one of three logged outcomes: (a) continue with a defined next review date, (b) escalate to an ADA interactive-process review with HR and counsel, or (c) initiate closure per program criteria.
Log all five steps with dates and actor names. A review that happened but was not documented did not happen for audit purposes.
Keeping the System Running Across Multiple Cases
When one case is active, a paper-based or calendar-based system can hold together. At three or more concurrent cases — a common threshold in light manufacturing or mid-size healthcare operations — the manual system begins to produce gaps. Alerts for case B get missed because the coordinator is managing the week-six document chase for case A. The 90-day flag for case C fires during a staffing shortage and gets pushed.
Purpose-built RTW case management software maintains the alert schedule independently of the coordinator's capacity in a given week. Each case carries its own restriction window, its own alert timeline, and its own logged decision record. The coordinator sees a prioritized queue rather than a mental map of paper folders.
If your operation is managing cases in a spreadsheet today, the Transitional Duty Case Tracking Workbook provides a structured template — restriction dates, alert columns, and a review log — that imposes the same discipline without requiring an immediate software change.
For operations ready to move to a system that tracks restriction windows, fires tiered alerts, and logs review decisions across every open case, start a free trial of Transitional Duty Manager. The 90-day flag and restriction-expiry alerts are built into the case workflow by default — the coordinator does not have to build or maintain the schedule manually.
Summary
Restriction expiry tracking is not administrative overhead — it is the mechanism that keeps a transitional-duty assignment from becoming an undocumented, open-ended arrangement. A tiered alert schedule (14-day, 5-day, expiry-day) surfaces the right action at the right time. The 90-day max-duration flag forces a deliberate human review at the ceiling, producing a documented decision — not an automatic termination. Both tools protect the employer's audit position, keep the assignment aligned with current medical reality, and give the coordinator a defensible record at every stage of the case.
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
