OSHA 300 Log Days Away vs Restricted Work: Classification and Day Count Rules
Imagine a warehouse worker slips on a wet floor Friday afternoon, twisting an ankle badly enough to hobble but not collapse. Come Monday, can they clock in for light duties, or must you mark this as days away on your OSHA 300 Log? The line between these classifications can mean the difference between accurate recordkeeping and an OSHA citation during an audit.
On the OSHA 300 Log, days away from work signals a more serious outcome than restricted work or job transfer. Check only one outcome box in columns G through J. If the employee cannot work at all after the injury day, classify as days away. If they can work but cannot perform a routine job function or full shift—with no days away—classify as job transfer or restriction. When both occur, prioritize days away in the checkbox, then log day counts in both relevant columns.
Why Classification Matters in OSHA 300 Log Days Away vs Restricted Work
Getting OSHA 300 log days away vs restricted work right isn't just bureaucratic busywork. These distinctions drive your injury trends analysis, help pinpoint safety gaps, and ensure compliance with 29 CFR 1904.7. Misclassify a case, and your log distorts reality—perhaps understating severity or inflating minor incidents. For small-business owners and safety coordinators juggling HR duties, clarity here prevents headaches at year-end when prepping the 300A summary.
OSHA mandates checking the single most serious outcome. Days away trumps restricted work every time. Picture a case evolving: an employee out for a week, then back on light duty. You check 'days away,' count those initial calendar days in column H, and add restriction days in column I. Never erase what happened; record it fully.
Classifying Days Away from Work: The Rules
Days away applies when an injury or illness keeps the employee from any work after the incident day. Per 1904.7(b)(3), enter calendar days away in column H. Skip the injury day itself—start counting the next calendar day, including weekends and holidays if the restriction holds.
Key Triggers and Physician Recommendations
- If a physician recommends staying home but the employee shows up anyway, record the recommended days away.
- Conversely, if they recommend return-to-work but the employee stays out, stop counting on the advised date.
- Count days the employee couldn't work, even scheduled time off like vacations, if the condition prevented it.
Consider a Friday injury. Employee returns Monday. For the weekend: record only if a health professional says they shouldn't have worked or needed restrictions then. Same logic for holidays or plant shutdowns.
Employee Departure and Estimates
If the worker leaves for unrelated reasons—retirement, layoff—stop counting. Injury-related exit? Estimate remaining days. For long absences, update the log as facts emerge.
Restricted Work and Job Transfers: When and How to Record
Restricted work or job transfer kicks in without days away, per 1904.7(b)(4). Check column I and tally calendar days. This covers scenarios where you or a physician limit routine functions—tasks done at least weekly—or the full workday.
Defining Routine Functions and Partial Shifts
- Partial shifts post-injury? Record as restriction days, excluding the incident day.
- Vague 'light duty'? Probe: Can they do all routine tasks and full shift? Yes to both means no recording. No to either? Record it. Can't clarify? Default to restricted.
- Physician recommends limits, but employee pushes through? Still record.
- Job switch, even part-day? That's a transfer, same column.
- Permanent modified role eliminating restrictions? Stop counting after at least one day, once permanent.
Producing less output while hitting all routines and hours? Not restricted. Focus on functions and time, not productivity dips.
Do not record restrictions only on the injury day. A recommendation must impact routine work or shift length.
Day Count Mechanics: Shared Rules for OSHA 300 Log Days Away vs Restricted Work
Both categories use calendar days, not workdays. Skip day zero, cap at 180 total days across away and restrictions combined (1904.7(b)(3)(vii) and (b)(4)(xii)). Hit 180? Enter it and halt tracking.
- Incident: Day 0, no count.
- Next day out/restricted: Day 1.
- Weekends/holidays: Include if unable.
- Estimate long-term, revise later.
- Cap: 180 calendar days maximum.
For year-end cases, log in the incident year only. Estimate for 300A totals if ongoing; update log post-summary. Learn more on OSHA 300A posting requirements.
Decision Tree: Classifying Your Case Correctly
Step-by-Step Guide
- Death? Column G.
- Days away at all? Column H, count them; add restrictions to I if later.
- No days away, but restrictions/transfers? Column I.
- Neither? Other recordable, column J.
- Both away and restricted? H primary, counts in both.
Example: Worker sprains wrist, out three days (count 3 in H), then two weeks restricted (count 14 in I). Check H. Total tracked: up to 180 combined.
For full entry basics, see our step-by-step OSHA 300 Log instructions. Small businesses, review recordkeeping requirements.
Pitfalls to Dodge in OSHA Recordkeeping
- Workday vs calendar confusion: Always calendar.
- Ignoring physician notes: Record recommendations as if followed.
- Double-counting boxes: One outcome only.
- Year-end double-logging: Incident year once.
- Under 180 cap temptation: Use it, but accurately.
State Plan states? Verify local rules. This guidance educates on federal standards; consult pros for specifics. FORM 300 LOGBOOK is independent software, not OSHA-affiliated.
Streamline with the Right Tools
Tracking these nuances manually invites errors, especially at year-end. Use the FORM 300 LOGBOOK recordkeeping workspace to keep day counts, classifications, and 301 details together—so 300A totals aren't a scramble. Download a free OSHA 300 Log template to start.
Mastering OSHA 300 log days away vs restricted work builds safer workplaces and smoother compliance. Your log isn't just paper—it's your safety story, told right.