Building a Return-to-Work Workflow for Injured Healthcare Employees

A nursing assistant strains her low back repositioning a patient on a Tuesday. By Friday, her treating provider says she can work but shouldn't lift more than 15 pounds for three weeks. What happens next — whether she sits at home collecting comp or comes back on modified duty — is decided by your return to work workflow. And whether that decision is recorded correctly on your OSHA 300 Log is decided by whether the people running that workflow understand the recordkeeping rules underneath it.

Let's clear up one thing first, because it trips people up: there is no federal law requiring you to run a return-to-work (RTW) or transitional-duty program. OSHA regulates the recordkeeping side of injured-worker outcomes under 29 CFR Part 1904 — how you count and classify a case. RTW itself is a best practice driven by workers' comp economics. But the two are tightly coupled: the moment you bring someone back on light duty, you've changed how that case is classified and counted on a regulated federal form. Done well, the workflow lowers your cost and keeps your log accurate at the same time.

What steps make up a return-to-work workflow?

Think of it as six stages, each with a documentation obligation.

1. Injury report and medical evaluation. The employee reports the injury; you provide first aid or arrange a medical eval. This is where the clock starts.

2. Recordability determination and logging. Decide whether the case is OSHA-recordable, and if it is, get it onto the 300 Log and complete an OSHA 301 Incident Report (or an equivalent) within seven calendar days of learning about it (1904.29(b)(3); the 301 requirement is 1904.29(b)(2)). Don't wait for the case to "settle down" before you log it — the seven-day window runs regardless of whether you know the final outcome.

3. Get the work-status and restrictions. Obtain a written work-status note from the treating physician or other licensed health care professional (PLHCP). This should spell out specific functional limits — weight, reach, standing time, no direct patient handling, whatever applies — not just "light duty," which is uselessly vague.

4. Match restrictions to a transitional assignment. This is the stage that determines whether the rest of the workflow matters. Can you build a real job that fits the restrictions? Chart audits, triage phone lines, supply-room organization, patient-education callbacks, screening desk. The assignment has to be genuine work within the limits, not busywork parked in a break room.

5. Track restricted/transfer days and update as status changes. Restrictions get renewed, tightened, or lifted. Every change updates the case classification and the day count. This is the stage most programs handle worst — the note comes in, it's initialed, and it never makes it back to the 300 Log.

6. Full-duty clearance and closeout. The PLHCP releases the employee to full duty, you end the restricted-day count, and you close the case. Keep the paper.

One retention note that catches people at audit time: you must keep the 300 Log, the 300A annual summary, the privacy case list, and the 301 reports for five years after the calendar year they cover — and you must go back and update a stored 300 Log if a case's classification changes (1904.33). A case that moves from days-away to restricted duty in March affects a log you may have thought was finished.

How do I track work restrictions and light duty?

This is where RTW becomes OSHA recordkeeping, so it's worth getting the mechanics exactly right.

What counts as restricted work. Under 1904.7(b)(4)(i), restricted work exists when, because of a work-related injury or illness, you keep the employee from performing one or more routine job functions or from working a full workday — or a PLHCP recommends they not. "Routine functions" are the ones the employee performs at least once a week (1904.7(b)(4)(ii)). So if a floor nurse who lifts patients daily is told not to lift, that's restricted work. If she's told not to do something she only does once a month, it isn't.

Light duty is restricted work — not a days-away case. This distinction drives the whole classification. When you provide modified duty that fits the restrictions, you convert what would have been a days-away-from-work case into a restricted-work case. Still recordable, but a different and generally less-severe classification. If instead she'd stayed home, those same days pile up in the days-away column.

On the 300 Log itself, restricted-work and job-transfer cases share the same checkbox — check the job transfer/restriction column — and you enter the number of restricted or transferred days in the restricted-workdays column. Days away go in Column K; days on job transfer or restriction go in Column L (eCFR 1904.7). If someone works part of a day on modified duty, count it as a full day of restriction — except the day of injury itself (1904.7(b)(4)(v)). And if part of the day is spent in a different job, the case involves a job transfer (1904.7(b)(4)(ix)).

You can cap the count at 180 days. You aren't required to keep counting past 180 calendar days away from work, and restricted/transfer days are counted the same way (1904.7(b)(3)(vii) and (b)(4)(xi)). Enter 180 and stop.

Watch the privacy cases. Healthcare generates a lot of them. For a contaminated needlestick or sharps injury — and for injuries to intimate body parts or the reproductive system, sexual-assault injuries, mental illnesses, and HIV/hepatitis/TB cases, among others — you may omit the name on the log and enter "privacy case," keeping the name on a separate confidential list (1904.29(b)(6) and (b)(7)). A bloodborne-exposure case that lands on restricted duty for follow-up testing is exactly this situation.

This is where work restrictions tracking matters most — restriction dates, day counts, classification changes, and privacy flags are precisely the fields that fall through the cracks on a spreadsheet. Whatever you use, whether it's a dedicated tracking system or a well-disciplined shared log, the goal is the same: the restriction note and the 300 Log should never disagree.

Who clears an employee to return?

Split it cleanly, because confusing the two roles is how programs get into trouble.

The clinician defines medical capacity. The treating physician or PLHCP sets and removes restrictions and issues the work-status note. OSHA explicitly ties restricted-work status to a PLHCP recommendation (1904.7(b)(4)(i)(B)). Full-duty clearance also comes from the clinician — though exactly which clinician (physician, NP, PA, occupational-health nurse) may sign it depends on your state's scope-of-practice law and your own policy. Capture that release on a standard RTW clearance form so the medical release, the effective date, and any remaining restrictions live in one place.

The employer defines the job. Occupational health or the RTW coordinator decides whether a transitional assignment exists that fits the restrictions, and builds it. HR keeps it inside the accommodation and comp framework. The clinician never assigns the job; the employer never overrides the medical limits. When someone asks "can she come back?" the honest answer is two answers: what can she safely do (clinician), and do we have work that fits (employer).

How does RTW reduce lost time and cost?

Start with the burden, because healthcare carries a heavy one. Musculoskeletal disorders — overwhelmingly from manual patient handling — dominate. OSHA reports that in 2017 nursing assistants had 18,090 days-away MSD cases at a rate of 166.3 per 10,000 workers, more than five times the all-worker average of 30.5, driven by overexertion from repeated lifting and repositioning (OSHA, Safe Patient Handling). NIOSH finds MSDs make up 52% of all days-away cases for nursing assistants (CDC/NIOSH). OSHA pegs the direct and indirect cost of back injuries alone in healthcare at roughly $20 billion a year, and notes as many as 20% of nurses who leave direct patient care cite the physical risk (OSHA). More broadly, healthcare and social assistance ran a total recordable case rate of 3.4 per 100 full-time workers in 2024, down from 3.6 in 2023 (BLS, Jan 2026), with "overexertion and bodily reaction" the leading event category for days-away, restricted, or transferred cases (BLS SOII Table 2).

The cost mechanism is simple. Every day an injured worker sits at home is a day of indemnity payments and a day of lost productivity, and the longer the gap runs, the harder return becomes. Bringing the person back on genuine modified duty keeps them productive, keeps them connected to the workplace and recovering, and — on the log — keeps the case out of the days-away column. Insurance carriers and comp consultants publish striking ROI figures for structured return to work programs, but those are industry sources, not government data, so weigh them accordingly. The government-verifiable case is the burden above plus the plain arithmetic: fewer days away, lower comp exposure, a more accurate 300 Log.

FAQ

Is a return-to-work program required by OSHA? No. No federal regulation mandates an RTW or transitional-duty program. OSHA regulates recordkeeping under Part 1904; RTW is a best practice driven by workers' comp economics that also improves the accuracy of your required records.

Does light duty still count as a recordable case? Yes — if the underlying injury is recordable, providing a light duty assignment makes it a restricted-work case, not a days-away case. You still record it, check the job transfer/restriction box, and count restricted days in Column L (eCFR 1904.7).

How long do I count restricted days? Until the employee is released to full duty, or until you hit the 180-calendar-day cap, whichever comes first (1904.7(b)(3)(vii) and (b)(4)(xi)).

Who decides whether someone returns to full duty? The treating physician or PLHCP clears the employee medically; the employer decides whether a job fitting any remaining restrictions exists. Keep those roles separate.

Map your own program to the six stages above, then check the weakest link — for most healthcare employers it's stage five, where a renewed or lifted restriction never makes it back to the log. Whatever tools you use, the aim is to keep restriction tracking and OSHA 300 classification in sync, because that's what protects both your people and your records.

This article is general information about occupational-health recordkeeping practice, not legal or medical advice. Confirm classification decisions against the current CFR text and your state's requirements.