Check your ITA 300A CSV before you upload
Open the 300A CSV you made and see every problem OSHA's documentation would reject — EIN, ZIP leading zeros, NAICS, size, hours per employee — with fixes.
Errors are cheaper to fix before the upload
ITA processes CSV uploads in a queue and reports errors afterwards. Open your file above and Safetally reads it against OSHA's documentation: required columns, the “ein” header in OSHA's template (the documentation calls it ein_number), EINs and ZIPs that lost their leading zero in Excel, NAICS codes that aren't six digits, size classes, totals that don't add up (cases G–J against injury types M1–M6), and hours divided by average employees at 8,760 or more (rejected) or 500 or less (flagged).
Fix the figures in the form and, with Pro, download a corrected file.
What Safetally checks
- The log: every case has a date, a description, exactly one outcome (death, days away, job transfer/restriction, other recordable) and one injury/illness type; day counts match the outcome; the 180-day cap applied if you turn it on (1904.7(b)(3)(vii)).
- The 300A: totals G–M are added from the log, not typed, and checked against any totals you give; annual average employees and hours worked are present and plausible.
- Privacy: cases that look like privacy concern cases (intimate body parts, sexual assault, mental illness, HIV/hepatitis/TB, contaminated sharps) are flagged so you can withhold the name.
- ITA readiness: EIN with 9 digits, ZIP with its leading zero, a 6-digit NAICS code, the size class, establishment type, and every field OSHA's CSV documentation marks as required.
How it works
- Open your injury log (CSV or Excel) — or try the sample, or start a zero-injury year.
- Fill in each establishment once: address, EIN, NAICS, peak and average employees, hours worked, and who certifies.
- Fix what it flags, then print the 300A to post by February 1, the 300 log and the 301s — or with Pro download the ITA CSVs for March 2.
FAQ
What are the OSHA 300, 300A and 301?
The three injury and illness recordkeeping forms in 29 CFR Part 1904. The 300 is the log of recordable cases, the 301 is the incident report for each case, and the 300A is the yearly summary a company executive certifies and posts from February 1 to April 30. Some establishments must also submit the 300A — and some, 300 and 301 case data — to OSHA's Injury Tracking Application by March 2.
Is my data uploaded?
No. Your log is read by JavaScript in your browser tab and never sent to us or anyone else. Injury cases aren't stored; close the tab and they're gone. With Pro you can save establishment details (not cases) in this browser for next year.
Which files can I use?
CSV, tab-separated or Excel: one row per case with the employee, job title, date, location, description, outcome and day counts. Establishment details can be in a second sheet or file. A 300A CSV made for ITA can be opened and checked too. Download the templates to see the layout; your own column names usually work.
What's free?
Every check for any number of cases and establishments, the TRIR and DART rates, the printed 300A summary, and the 300 log and 301 reports with up to 3 cases and a small footer. Pro prints every case without the footer and adds the ITA 300A CSV, the ITA case data CSV, an Excel workbook and saved establishments.
Will OSHA accept these forms?
29 CFR 1904.29 allows OSHA's forms or equivalent forms with the same information, as readable and completed using the same instructions. Safetally's 300A uses OSHA's wording, and the ITA files follow OSHA's published CSV formats. You review, certify and submit them yourself; Safetally is not affiliated with OSHA.
Does it decide whether a case is recordable?
No. You decide recordability under 29 CFR 1904.4–1904.7. Safetally checks that what you recorded is complete and consistent, totals it and lays it out on the forms.