The Ving Blog

How To Fill Out Your OSHA 300 Log Correctly In 2026

Written by Karen Gerberry, Ving Success Manager | 1/26/26 11:00 AM

 

Filling out the OSHA 300 Log doesn’t have to feel overwhelming — but getting it wrong can lead to citations, fines, and stressful OSHA inspections.

In 2026, OSHA continues to place a strong emphasis on recordkeeping accuracy, electronic submissions, and consistency across job sites. This guide breaks down exactly how to fill out your OSHA 300 Log correctly, using plain language, clear examples, and practical tips safety managers can actually use.

Whether you’re managing one location or multiple job sites, this walkthrough will help you stay compliant and confident.

 

What Is the OSHA 300 Log (In Simple Terms)?

The OSHA 300 Log is a running list of work-related injuries and illnesses that meet recordable criteria set by the Occupational Safety and Health Administration.

You’re not logging every scrape or sore muscle. You’re documenting incidents that meet OSHA’s definition of a recordable case.

Think of the OSHA 300 Log as:

  • A year-long injury and illness tracker
  • A required compliance document
  • A tool to spot safety trends and problem areas

You update it throughout the year, then summarize it at year-end using OSHA Form 300A.

 

Step 1: Confirm the Incident Is Recordable

Before you write anything on the OSHA 300 Log, ask one key question:

Does this incident meet OSHA’s recordable criteria?

An injury or illness is recordable if it is:

  • Work-related
  • A new case
  • And results in any of the following:
    • Days away from work
    • Restricted work or job transfer
    • Medical treatment beyond first aid
    • Loss of consciousness
    • A significant injury or illness diagnosed by a healthcare professional

If the answer is yes, it goes on the log.

If the incident only required basic first aid (bandage, ice, cleaning a wound), it usually does not belong on the OSHA 300 Log.

 

Step 2: Fill Out Each Column on the OSHA 300 Log

Each recordable incident gets one line on the log. Here’s how to complete each section correctly.

 

Column A: Case Number

Assign a unique number to each case.

Tip: Start with “1” at the beginning of each calendar year and number cases in order.

 

Column B: Employee’s Name

Enter the employee’s full name.

Privacy cases:
For sensitive injuries or illnesses, write “Privacy Case” instead of the employee’s name and keep details confidential.

 

 

Column C: Job Title

Use the employee’s regular job title, not the task they were performing.

Example:
✔ “Maintenance Technician”
✘ “Fixing conveyor belt”

 

Column D: Date of Injury or Onset

Record the date the injury occurred or the illness first appeared.

 

Column E: Where the Event Occurred

Be specific but simple.

Examples:

  • Warehouse – aisle 4
  • Job site – north stairwell
  • Maintenance shop

 

Column F: Description of Injury or Illness

Briefly explain:

  • What happened
  • What part of the body was affected

Good example:
“Employee slipped on wet floor and sprained right ankle.”

Avoid vague descriptions like “hurt leg” or “accident.”

 

Step 3: Check the Correct Outcome Box

You must check only one outcome category — the most serious one.

Options include:

  • Death
  • Days away from work
  • Job transfer or restriction
  • Other recordable cases

Example:
If an employee was on restricted duty and later missed work, record the case as days away from work.

 

Step 4: Count Days Away or Restricted

If time away or restricted duty applies:

  • Count calendar days, not workdays
  • Start counting the day after the injury
  • Stop when the employee returns to normal duties
  • Cap counting at 180 days

Update the log if the number of days changes.

 

Step 5: Classify the Injury or Illness Type

Check the category that best matches the medical diagnosis:

  • Injury
  • Skin disorder
  • Respiratory condition
  • Poisoning
  • Hearing loss
  • Other illness

Choose based on the diagnosis, not personal judgment.

 

Step 6: Complete the OSHA 301 Incident Report

Every OSHA 300 Log entry must have a corresponding OSHA 301 Incident Report (or approved equivalent).

Many safety managers complete the 301 first and then use it to accurately fill out the OSHA 300 Log.

 

 

Step 7: Keep the Log Updated All Year

The OSHA 300 Log is a living document, not a one-time task.

You must:

  • Record incidents within 7 days
  • Update cases if severity changes
  • Keep records for 5 years
  • Maintain separate logs for each establishment if required

 

Common OSHA 300 Log Mistakes to Avoid

OSHA frequently cites employers for:

  • Recording first-aid-only cases
  • Not updating days away or restrictions
  • Vague injury descriptions
  • Incorrect injury classification
  • Mishandling privacy cases
  • Mixing multiple locations on one log

Accuracy and consistency matter — especially with increased electronic reporting.

Take OSHA 300 Recordkeeping Off Your Plate with Ving

If you’re still managing your OSHA 300 Log on paper or spreadsheets, you’re not alone — but in 2026, there’s a much easier way.

Ving’s OSHA 300 Log template allows you to take your paper charting online, making injury tracking, updates, and year-end filing far more manageable.

With Ving, safety managers can:

  • Digitally log OSHA 300 entries as incidents occur
  • Update days away or restrictions without rewriting forms
  • Keep records organized and audit-ready all year
  • Simplify annual summaries and OSHA reporting
  • Store training records and third-party certificates in one place

Ving cannot issue OSHA 10 or 30 cards, but it does support nearly every OSHA-required training topic that can be delivered online, and allows you to log third-party certifications alongside your recordkeeping documentation.

Instead of juggling paper logs, spreadsheets, and reminders, Ving helps you manage training, recordkeeping, and compliance in one system — built for real safety teams and real job sites.

If you’re ready to move your OSHA 300 Log out of the filing cabinet and into a system that actually works, Ving makes it simple.