Why OSHA ITA Rejects a CSV File
Review common ITA CSV problems and distinguish local file checks from checks you must make in your OSHA account.
Free downloads / no signup
A checklist for the file. A tracker for the team.
Use these alongside the current OSHA templates. They are planning aids, not files to upload to ITA. Keep employee and case data out of the tracker.
File checks, privacy review and submission steps, with official source links.
Download the checklistTrack preparation, processing and confirmations. Dropdowns show your next unfinished step.
Download the trackerReviewed September 24, 2026. Expected 2027 filing dates are provisional; confirm OSHA’s current guidance before filing.
Why this happens
File preflight can catch formatting and consistency problems, but cannot confirm your ITA account state or guarantee acceptance. Review the local findings and the portal checks below before submission.
What you must verify yourself
These are workflow and human-review steps, not automatic RuleTally checks.
- Confirm the exact establishment name against the 300A submission in your ITA account.
- Confirm the corresponding 300A submission has processed before submitting combined 300/301 case data.
- Read the ITA processing result. RuleTally does not connect to your OSHA account or verify submission status.
How to fix it
- 01
Open the file in RuleTally; it is parsed in your browser and not uploaded to us.
- 02
Work through each finding by row and field, correcting the source export rather than the copy.
- 03
Clear blocking errors and review every remaining warning before exporting.
- 04
Test the corrected file in OSHA’s ITA Preview Environment before submitting for real.
Check the whole file locally.
RuleTally shows the row, field, expected format, and official source without uploading the employee file.
Open local preflight