OSHA 300 Log: Complete Guide to Recordkeeping and Compliance

The OSHA 300 Log is a federally mandated recordkeeping form that tracks work-related injuries and illnesses at a worksite. Officially called the Log of Work-Related Injuries and Illnesses, it is one component of a three-form system that OSHA requires most employers with 11 or more employees to maintain throughout the calendar year. The information captured in the 300 Log feeds OSHA's national injury and illness statistics, helps employers identify hazard patterns, and is a primary target during OSHA compliance inspections.

Understanding the 300 Log is not just a compliance checkbox — it is a window into your workplace's safety performance. When filled out accurately and reviewed regularly, the log reveals trends that informal incident tracking misses entirely. Which department has the most restricted-duty cases? Which job task generates the most lost-time incidents? Which shift produces the most sprains and strains? The 300 Log answers these questions with hard data, giving safety managers and supervisors the evidence base they need to prioritize interventions and allocate prevention resources effectively.

Employers who mismanage their 300 Log face penalties that escalate quickly. A single serious violation for failing to record a recordable case can cost up to $16,131 per violation as of 2024, and willful or repeat violations can reach $161,323 per violation. Beyond the financial exposure, an incomplete or inaccurate log can trigger broader OSHA inspections of your entire safety program. Getting the 300 Log right from the start protects both your workforce and your business. Employers pursuing their OSHA certification will find that recordkeeping mastery is consistently tested across all credential levels.

The 300 Log requirement exists because voluntary injury reporting produces systematically biased data. When left to their own discretion, employers under financial or competitive pressure often under-report incidents, making the national injury picture rosier than reality. Mandatory recordkeeping with enforcement teeth counteracts this tendency, producing data accurate enough to drive OSHA's regulatory priorities and research agenda. For employers, the discipline of accurate recordkeeping also counteracts the organizational tendency to normalize hazards over time — when incidents are formally counted and reviewed, they cannot quietly disappear from organizational memory the way undocumented near-misses do.

For new safety managers stepping into an established organization, auditing the existing 300 Log should be one of the first tasks on the agenda. Pull the last five years of logs and Forms 301, cross-reference them against workers' compensation records and medical leave data, and look for gaps. Cases that appear in comp records but not the 300 Log almost always indicate under-recording. This baseline audit both identifies compliance exposure and provides the historical trend data needed to set meaningful year-over-year improvement targets for the safety program going forward.

The 300 Log system consists of three separate forms, each serving a distinct purpose. Form 300 is the running log itself — updated throughout the year as incidents occur. Form 301 (the Injury and Illness Incident Report) is the detailed record for each individual case, capturing the narrative of what happened, the body part affected, the nature of the injury, and the object or substance that caused it.

Form 300-A is the annual summary — a one-page compilation of totals from the full-year log that must be certified by a company executive and posted at the worksite from February 1 through April 30 of the following year.

The threshold for keeping a 300 Log is 11 or more employees at any point during the calendar year, not just during the incident. Part-time, seasonal, and temporary workers all count toward the employee threshold if they work at your establishment. However, OSHA exempts certain low-hazard industries — including most retail, finance, insurance, real estate, and services sectors — from routine recordkeeping requirements.

Even exempt employers must maintain records if OSHA or the Bureau of Labor Statistics specifically notifies them to do so. Checking OSHA's current exemption list annually is advisable since the classification of industries can change with regulatory updates.

Work-relatedness is the critical determination that drives every entry in the 300 Log. An injury or illness is work-related if an event or exposure in the work environment caused or contributed to the condition, or significantly aggravated a pre-existing condition. The work environment includes not just the physical workplace but also any other location where employees work or travel as a condition of their employment.

For employees who work from home, the home office counts as the work environment during hours when they are working — though OSHA applies more limited criteria to home-based work to avoid intruding on employee privacy. Professionals pursuing an OSHA 30-hour course study work-relatedness determinations in depth as part of the recordkeeping module.

Multi-establishment employers face an additional complexity: each separate physical location must maintain its own Form 300. If your company has a headquarters in one city and a warehouse in another, the warehouse keeps its own log covering only the employees who work there. Corporate HR cannot maintain a single combined log and satisfy this requirement.

For employers with employees who travel between multiple sites, the injury is recorded at the site to which the employee is regularly assigned, not necessarily the site where the incident occurred. Mobile workers with no fixed site should have their records maintained at the site from which they are supervised, or at the home establishment if no single supervisory site exists.

First aid is the most common gray area in 300 Log recordkeeping. OSHA provides a specific list of first-aid treatments that do not trigger recording: using nonprescription medications at nonprescription strength, administering tetanus immunizations, cleaning and bandaging wounds, using nonprescription eye patches, hot or cold therapy, drilling a nail for relief of subungual hematoma, removing splinters with tweezers, using finger guards, massages, and drinking fluids to treat heat stress.

If treatment stays within this list, no entry is required. The moment treatment steps outside these boundaries — a prescription medication, a follow-up visit for wound management, or physical therapy — the case becomes recordable.

Privacy cases require special handling under OSHA recordkeeping rules. Eight categories of injuries and illnesses qualify as privacy cases: sexual assaults, mental illness, HIV infection, hepatitis, tuberculosis, needlestick injuries involving blood-borne pathogens, cases with intimate body parts or reproductive systems involved, and cases where the employee independently requests privacy.

For privacy cases, OSHA prohibits employers from entering the injured employee's name on the Form 300 — instead, write "privacy case" in the name column. A separate, confidential list of names and case numbers must be maintained so that OSHA inspectors can verify the entries if needed during an inspection. Form 301 for privacy cases must be kept confidential as well and should not be disclosed to anyone not authorized by OSHA's regulations.

Counting days correctly is another area that trips up many employers. Days away from work are counted as calendar days — not business days or scheduled workdays. If an employee is injured on a Friday and cannot return until the following Wednesday, that is four calendar days away (Saturday, Sunday, Monday, Tuesday), even though only two of those are workdays. The day of injury itself is not counted.

Days on restricted work are similarly counted as calendar days. If the employee is still on restricted duty at the end of the 180th calendar day, record 180 days and stop counting. Related injuries are tracked on the same Form 301 entry if they stem from the same event, while separate incidents get separate log entries even for the same employee. OSHA recordable incidents have precise criteria that every safety coordinator should internalize.

Hearing loss cases deserve special attention under OSHA recordkeeping rules. A standard threshold shift (STS) — defined as a 10-decibel or greater average shift in hearing in either ear at 2000, 3000, and 4000 Hz, measured from the baseline audiogram — is recordable if the employer or physician determines it is work-related. OSHA requires employers to retest hearing within 30 days of a positive STS finding, and if the retest confirms the shift, the case must be recorded.

Age adjustment is permitted: employers may calculate age-corrected STS values using OSHA's correction tables, which reduces the number of cases that cross the threshold. Given that industrial noise exposure is one of the most prevalent workplace hazards, hearing loss entries are among the most common on 300 Logs for manufacturing and construction employers.

Employee access rights are a critical compliance dimension that employers sometimes overlook. Current employees, former employees, their personal representatives, and authorized employee representatives (typically union representatives) all have the right to access the 300 Log. Current and former employees can request access to cases that involve them personally.

The log must be provided by the end of the next business day after a request is made. OSHA inspectors can access the log immediately during an inspection without advance notice. For multi-establishment employers, each establishment must maintain its own 300 Log for the injuries and illnesses that occur at that location — you cannot maintain a single centralized log for all sites.

Late recording is better than no recording. OSHA requires that recordable cases be entered on the Form 300 within seven calendar days of receiving information that the case is recordable. If you determine a case is recordable weeks after it occurred — for example, after an employee's follow-up medical appointment reveals a work-related diagnosis — enter it immediately when you have that knowledge. Do not backdate the entry. OSHA understands that some recordability determinations require time; what they penalize is deliberate failure to record, not good-faith delayed recording with a documented rationale.

Correcting prior-year logs is both permitted and sometimes required. If you determine that a previously recorded case was not actually recordable, you may line it out but should not erase it — maintain a note explaining the determination. Conversely, if you discover a case that should have been recorded in a prior year was missed, record it now and note the original incident date.

OSHA's five-year retention requirement means prior-year corrections must be made to the retained logs. Employers participating in voluntary protection programs or undergoing OSHA consultation visits often use these opportunities to audit and correct their 300 Logs retroactively without penalty exposure. Completing your OSHA 10-hour card provides foundational recordkeeping training that supports accurate 300 Log maintenance.

Supervisors are often the weakest link in the 300 Log compliance chain. They may discourage incident reporting to protect their department's safety record, misclassify recordable cases as first aid to avoid the paperwork, or simply be unaware of the seven-day recording deadline. Training supervisors on what must be reported, how to report it, and why accurate reporting protects rather than penalizes them is a foundational element of any strong recordkeeping program.

Many employers build a non-retaliation policy explicitly into their injury reporting procedure — documented, posted, and covered in supervisor training — both because OSHA requires anti-retaliation protections and because employees who fear retaliation simply do not report incidents, leaving hazards unaddressed and the 300 Log inaccurate.

Linking your 300 Log program to your broader incident investigation process multiplies its value. Every recordable case should trigger a formal root cause analysis that examines not just what happened but why hazards were present and what systemic factors contributed. The 300 Log entry points back to the Form 301 narrative, which in turn connects to the investigation report and the corrective action log.

This closed-loop system ensures that every injury recorded becomes intelligence that prevents the next one. Safety committees typically review the 300 Log monthly, looking for trends in injury type, department, time of day, and tenure of injured workers.

Benchmarking against industry rates gives your 300 Log data strategic context. OSHA and the Bureau of Labor Statistics publish annual injury and illness rates by NAICS industry code, expressed as Total Recordable Incident Rates (TRIR) — injuries per 100 full-time equivalent employees per year. To calculate your TRIR, multiply total recordable cases by 200,000 (the hours in a 100-employee year) and divide by actual hours worked.

Comparing your TRIR to your industry average tells you whether your safety performance is above, at, or below the norm. Companies with TRIR values significantly below the industry average qualify for OSHA's Voluntary Protection Program (VPP) recognition, which provides public acknowledgment and exempts the site from routine programmed inspections.

Using the 300 Log as a proactive safety tool rather than a backward-looking compliance exercise is what separates excellent safety programs from merely compliant ones. When safety managers analyze the log quarterly — plotting incidents by department, time of day, job tenure, and injury type — patterns emerge that point directly to the training gaps, equipment deficiencies, or procedural failures driving the numbers.

A cluster of back injuries in the shipping department during the 4-to-midnight shift suggests ergonomic risk factors compounded by fatigue — actionable intelligence that translates into engineering controls, rotation schedules, and targeted training. A spike in laceration cases among employees with less than 90 days tenure points to onboarding training gaps. The 300 Log, treated seriously, becomes a continuously updated hazard map of your organization, guiding preventive action with empirical precision rather than intuition.

In short, the OSHA 300 Log is not paperwork to be minimized — it is safety intelligence to be maximized. Accurate records protect workers and organizations alike.