How to Upload OSHA 300A Electronically Through the ITA

In OSHA's Injury Tracking Application, confirm each establishment, then enter 300A data by web form, CSV upload, or API, and submit it. Emailing or mailing forms to OSHA does not count as submission.

Uploading is simple when the establishment list is clean and painful when it is not.

Gather these first, and keep them with the record afterward:

• The coverage decision for each establishment: peak headcount, NAICS code, and which appendix applies
• The EIN used by each establishment
• The submitted file or payload and the ITA confirmation
• Notes on any corrections made after submission

Covered establishments submit injury data to OSHA's Injury Tracking Application (ITA) by March 2 each year for the previous calendar year; for 2026 data that is March 2, 2027 (29 CFR 1904.41). Three groups must submit: establishments with 250 or more employees that must keep records (300A data); establishments with 20 to 249 employees in an industry listed in Appendix A to Subpart E (300A data); and establishments with 100 or more employees in an industry listed in Appendix B (300A data plus 300 and 301 case data). Headcount means every individual employed at any time in the prior year, including part-time, seasonal, and temporary workers, and every submission includes the establishment's EIN.

1. Confirm coverage for each establishment.
2. Prepare the file or form data.
3. Upload and resolve validation errors.
4. Submit and keep the confirmation.

Tip: Use the ITA web form, CSV upload, or API, depending on volume and systems.

Teams sometimes email forms or keep PDFs assuming that counts as submission.

Most ITA problems are establishment data problems: an old NAICS code, a parent-company EIN, or a headcount measured at the wrong level. The fix is to decide coverage per establishment in the fall, clean the EIN, NAICS, and address data then, and leave only validation and submission for February.

Operations leaders rarely make the recordkeeping call, but they control the schedules, postings, and site managers that make the deadlines work.

• Large employers need repeatable controls because one bad row can delay the whole batch.
• For 300 and 301 case data, OSHA excludes employee names and addresses and health care provider details from the submission (1904.41(b)(9)).

A single-site employer with one covered establishment logs in to the ITA, confirms the establishment profile carried over from last year, types the 300A totals into the web form, and submits. A 30-site employer uploads one CSV instead. Both save the confirmation page.

The ITA submission is built from the certified 300A (and, for Appendix B establishments, the 300 and 301), so every correction to the log has to be reconciled with what was submitted.

300log validates EIN and NAICS formats, produces ITA-ready CSV files for the 300A and for case data, and can authorize auto-filing of 300A data once you connect an ITA API token.

For a quick answer without an account, use the free ITA coverage checker.

• High-Hazard Industries and OSHA Electronic Reporting: What 20 to 249 Employee Establishments Need to Know
• OSHA 300 and 301 Electronic Reporting for 100+ Employee Establishments
• EIN in OSHA ITA Submissions: Why the Field Matters
• OSHA 300 Log Requirements for 2026: A Practical Recordkeeping Guide