The first time you log into the OSHA Injury Tracking Application, it's not obvious what happens next: which fields need typing in, whether a file upload is even worth setting up, and what "submitted" actually looks like when it's done. The Injury Tracking Application, or ITA, is OSHA's system for electronically submitting recordkeeping data, and every covered establishment has to use it every year. This guide walks through the process in order — account, establishment, data, review, submit, confirmation — the way we'd explain it to someone doing it for the first time this year, with a worked example and the mistakes that trip people up.
What is the OSHA Injury Tracking Application?
The ITA is the online portal OSHA built to collect Form 300A summary data — and, for some establishments, Form 300 and 301 data too — electronically instead of on paper. It sits under 29 CFR Part 1904, the recordkeeping regulation, and it exists because Congress and OSHA wanted establishment-level injury and illness data collected in one consistent format rather than scattered across paper filings. Once submitted, that data becomes part of the dataset OSHA has said it intends to make available, in keeping with the rule's stated aim of improving transparency around workplace safety outcomes.
Not every employer submits the same scope of data. Establishments with 250 or more employees, and those in certain higher-hazard industries at lower headcounts, generally have to submit more than the 300A summary — check OSHA's current establishment-size and industry thresholds before you decide what your establishment owes, because the exact cutoffs are set out there, not in this guide. Smaller, lower-hazard establishments typically submit only the 300A totals. If you haven't worked out whether your establishment is even covered, our 300A posting requirements guide and the ITA deadline explainer both cover who's in scope before you get anywhere near the ITA itself.
When is the OSHA ITA submission deadline?
The deadline is generally 2 March each year, covering data for the prior calendar year. So the submission due 2 March 2027 covers everything on your 2026 log. That date doesn't move around much year to year, but OSHA has adjusted it before, so it's worth checking osha.gov/injuryreporting each cycle rather than assuming last year's date still applies. Treat 2 March as a hard stop, not a target — the safer plan is to have your log finalised and reviewed well before it, which we'll come back to in the pitfalls section below.
Before you touch the ITA: is your log actually finished?
This is the step people skip, and it's the one that matters most. The ITA submission is meant to reflect a completed year's log — not a document you're still editing. Before you open an ITA account, your 300 Log (where required) and your 300A summary should be finalised: every recordable case entered, every case classified correctly as days-away, restricted/transfer, or other recordable, and the summary totals checked against the log line by line.
If you're still unsure whether a specific case belongs on the log, don't submit around the uncertainty — resolve it first. Run the case through the free recordability check, which applies the three-part test under 1904.7: work-relatedness, new case, and recording criteria. Where the rule genuinely leaves the answer to judgement, the tool returns "needs review" instead of guessing, because a guess baked into a federal submission is worse than an honest flag. If you want more on how work-relatedness gets decided in edge cases, see our piece on OSHA work-relatedness exceptions.
The submission process, step by step
Once the log is finalised, the ITA process itself is mechanical. Here's the sequence from start to confirmed submission.
| Step | What happens | What to check |
|---|---|---|
| 1. Create or access your ITA account | Set up an ITA login (or sign back into an existing one) for the establishment's employer | Use the same account each year where possible, so establishment history stays linked |
| 2. Add or select the establishment | Identify the specific establishment (location) the data belongs to | Match the establishment's name, address, and NAICS code exactly to prior filings |
| 3. Choose manual entry or file upload | Enter 300A (and 300/301, where required) data directly into web forms, or upload a structured file for larger record counts | Manual entry suits a handful of cases; a file upload suits establishments with many rows |
| 4. Enter or upload the data | Type in totals and case details, or upload your CSV-style file matching the ITA's required schema | Every figure should trace back to your finalised 300 Log and 300A — no live edits during submission |
| 5. Review the totals | The ITA displays what you've entered or uploaded before you commit it | Compare against your own 300A printout, not just what's on screen |
| 6. Submit | Formally submit the establishment's data for the year | Submission timestamp and establishment details should match your records |
| 7. Confirm | Save or record the confirmation the ITA provides once submission completes | Keep this alongside your finalised 300 Log and 300A as your compliance record |
Table: the seven steps from opening an ITA account to a confirmed OSHA ITA submission.
Can I upload a file instead of typing data in manually?
Yes. For establishments with more than a handful of recordable cases, typing each one into a web form is slow and invites transcription errors — a date typo, a mismatched case number, a total that doesn't add up to the individual rows. The ITA accepts a structured file, generally a CSV matching its published schema, so you can prepare the data once in your own system and upload it as a single file rather than re-keying every case. This is where having your 300 Log data already in a clean, structured format pays off: if your log lives in a spreadsheet or a recordkeeping tool, the export step should be close to instant, not a manual re-entry exercise.
What data does the OSHA ITA actually require?
At minimum, every covered establishment submits its 300A summary: total deaths, days-away cases, restricted/transfer cases, other recordable cases, the underlying day counts, average employment, and total hours worked for the year. Establishments that meet the higher-hazard or larger-size thresholds also submit the case-level detail from the 300 Log — and in some cases the 301 incident report data — covering each individual recordable case, not just the totals. Whichever scope applies to you, the data needs to match, line for line, what's already recorded on your finalised log. The ITA isn't a place to reconstruct your recordkeeping from memory; it's a place to transmit what you've already got right.
A worked example: a construction firm's first electronic submission
Picture a mid-sized commercial framing contractor — sixty field employees, one office location, NAICS code in a sector that OSHA classifies as higher-hazard construction. That means they owe more than the 300A: they submit 300 and 301 detail too.
Their safety coordinator spends the last week of January closing out the log: eleven recordable cases for the year, two with days away, the rest restricted-duty or other recordable. She reconciles each entry against the 301 incident reports on file, fixes one case where the days-away count didn't match the return-to-work date in payroll, and finalises the 300A totals. With the log locked, she exports the finalised data as a CSV formatted to the ITA's schema rather than typing eleven cases into web forms by hand — matching field names, date formats, and case classifications to what the ITA expects. She opens the ITA, selects the single establishment (their office, since that's where OSHA logs are kept for this employer's operations), uploads the file, and gets a screen showing the parsed totals: eleven cases, two days-away, matching her own printed 300A. She checks it against her paper copy, submits, and saves the confirmation record to the same folder as the year's finalised log and 301s. Start to finish, once the log itself was actually done, the ITA part took under twenty minutes.
That's the order that works: finalise first, format the data, then let the upload do the re-keying you'd otherwise do by hand.
One EHS manager we spoke with put it this way: "the log always takes longer than the submission — if you're spending real time inside the ITA itself, it usually means the data wasn't ready when you sat down."
Common pitfalls — where teams get this wrong
Submitting before the log is finalised. The ITA takes whatever you give it. If a case is still under review, or a days-away count hasn't been confirmed with payroll, submitting anyway locks in a number you may need to correct later. Finish the log first.
Mismatched establishment details. If your company operates multiple locations, each establishment needs its own accurate name, address, and NAICS code in the ITA, matching what's on file elsewhere. A submission logged against the wrong establishment, or a NAICS code that's drifted from what payroll or your insurer has on record, creates a mismatch that's harder to fix after the fact than to get right up front.
Leaving it to 1 March. The deadline is generally 2 March, but that's not when you should start. Waiting until the last day means any file formatting issue, login problem, or last-minute data discrepancy has no slack to absorb it. Treat the deadline as the outer limit, not the plan.
Submitting the wrong scope of data for your establishment. A smaller, lower-hazard establishment that only owes 300A totals doesn't need to submit case-level detail — and a larger or higher-hazard establishment that only submits the 300A when it should also submit 300 and 301 detail is under-reporting. Check your specific establishment against OSHA's current thresholds rather than assuming last year's scope still applies, since headcounts and industry classifications change.
Re-keying data that already exists. Typing case-level detail into web forms when you already have a clean, structured 300 Log invites transcription errors that don't exist in your source data. If your record count justifies a file upload, use one — it's not just faster, it's more accurate than manual re-entry.
Where Job13 fits
Job13 doesn't submit data to OSHA on your behalf — the ITA submission itself is still something you do, through OSHA's system, using your own account. What Job13 does is get you to that point with clean data: log recordable cases through the recordability check, keep a running 300 Log and 300A, and on a Pro account, export that data as a CSV file formatted for the ITA's electronic submission requirements — generated straight from your saved log, not rebuilt from scratch every January. If your establishment's data lives somewhere else and you'd rather pull it through an API, our API and MCP docs cover automating the export directly. See pricing for what's included on the Pro tier.
Before you open the ITA this year, get your log finalised and your export ready — check Job13's pricing to see how the Pro tier's ITA CSV export fits into that, or read the API docs if you're automating the pull.
Frequently asked questions
Does every employer have to submit data through the OSHA ITA?
Not every employer, but most covered establishments do. Coverage depends on employee count and industry classification — check OSHA's current thresholds for your establishment, since size and industry both affect whether you submit only the 300A or the 300A plus case-level 300 and 301 data.
What file format does the OSHA Injury Tracking Application accept?
Manual entry is available through the ITA's own web forms. For establishments with many records, the ITA accepts a structured file, generally a CSV matching its published schema, which you can prepare from your own recordkeeping system and upload in one step rather than typing each case in individually.
Can I fix a mistake after I've submitted to the ITA?
The ITA is built around annual data tied to a finalised log, so submitting before your figures are confirmed is the mistake to avoid rather than one to plan around fixing afterwards. If you do find an error post-submission, OSHA's own guidance at osha.gov/injuryreporting is the place to check current correction procedures, since this guide can't confirm specifics that change year to year.
Do I need to submit 300 and 301 data, or just the 300A summary?
That depends on your establishment's size and industry. Smaller, lower-hazard establishments generally submit only the 300A summary. Establishments at or above OSHA's current size threshold, or in certain higher-hazard industries, generally submit 300 and 301 case-level detail as well. Confirm your establishment's specific scope against OSHA's current thresholds rather than assuming.
Is Job13's ITA export the same as submitting to OSHA?
No. Job13's Pro tier generates a CSV file formatted for the ITA's electronic submission requirements, built from your saved 300 Log and 300A data — but you still upload that file, or enter the data, through OSHA's own Injury Tracking Application yourself. Job13 gets your data ready; the actual submission happens on OSHA's system, under your ITA account.
