About
Recordkeeping software for the people who keep the log
300log turns the OSHA 300, 301 and 300A into one guided workspace, so safety, HR and operations teams record cases correctly and file on time.
Built around 29 CFR 1904
- 7 days
- to record a new case on the 300 and 301§ 1904.29(b)(3)
- Feb 1–Apr 30
- the 300A summary stays posted§ 1904.32(b)(6)
- Mar 2
- electronic submission to OSHA's ITA§ 1904.41(c)
- 5 years
- to keep the 300, 300A and 301§ 1904.33(a)
Who it's for
The person who owns the log
Often a safety manager, sometimes HR or an operations lead, rarely someone with recordkeeping as their only job.
Safety managers with several sites
Every establishment keeps its own log, 300A and filing status, side by side in one workspace.
HR and operations leads
Recordkeeping is one job among many. Guided steps and plain language keep each case short.
Employers that file with OSHA's ITA
Covered establishments get the 300A, and case data where required, in OSHA's upload format or filed automatically with their own token.
Not built forTraining records, inspections or chemical inventories. 300log does OSHA injury and illness recordkeeping, and does it carefully.
Principles
Accurate, honest, private
- 01
Accurate to the rule
Classification, totals and file formats follow 29 CFR 1904 and OSHA's own ITA specifications. Checks run where a mistake would otherwise hide, and they cite the section they come from.
- 02
Honest about what happened
Statuses say exactly what happened: a file generated, a filing authorized, a submission OSHA accepted. Nothing reads as filed unless OSHA confirmed it or you recorded your own upload.
- 03
Private by default
Your records are stored in your 300log account, and only your account and the people you invite to your workspace can open them. They go anywhere else only when you authorize an ITA filing or scan a report, and employee names never go to OSHA.
How it works
Where your records go
Everything starts in your workspace, saved to your account. Two roads lead to OSHA: the file you upload yourself, or a filing you authorize.
01 · Record
Log cases, finish each 301 and review the 300A, on any device you sign in on.
02 · Export
Generate PDFs to post and keep, and CSVs in OSHA's upload format.
03 · File
Authorize a filing and 300log submits it with your token right away, retrying if the ITA is down. Or upload the CSV at the ITA yourself.
Independence
Not affiliated with OSHA
300log is independent software. It is not affiliated with or endorsed by OSHA or the U.S. Department of Labor. Automatic filing uses OSHA's public ITA API with your own token, the way any employer or vendor can.
OSHA's Injury Tracking Application(osha.gov, opens in a new tab)Editorial policy
How our guides are made
Our guides explain OSHA injury and illness recordkeeping for the people who do it. They are published under the 300log Editorial Team byline.
Researched from primary sources
Every guide starts from the regulation itself, 29 CFR Part 1904, and from OSHA's own material: recordkeeping FAQs, Injury Tracking Application documentation and letters of interpretation. Injury-rate benchmarks come from the Bureau of Labor Statistics. Each guide lists the sources it relies on.
Reviewed, then kept current
Guides are checked against those sources before they are published and revisited when something they depend on changes: OSHA's annual penalty adjustments, a new ITA filing season, or a new release of BLS injury data.
Guidance, not legal advice
Our guides and free tools explain the rules in general terms. They are not legal advice and do not replace OSHA's own guidance or a qualified professional looking at your situation.
Found an error? Tell us
Send the guide's link and what looks wrong through our contact page. We check every report against the source and correct the guide when we got it wrong.
Contact us
Start with your own records
See your log, summary and filing in one place
- Records saved to your account
- Starts free, no card