OSHA's ITA makes establishment data a continuing control
OSHA says covered establishments that missed March 2 must still submit 2025 injury data. The operating challenge is identity, scope, privacy, and correction control.
Editorial figure by Safety Operations Standard. Source context: Occupational Safety and Health Administration.
A missed deadline does not close the workflow
OSHA's electronic-submission page says covered establishments that failed to meet the March 2, 2026 deadline for calendar-year 2025 injury and illness data are still required to submit. The agency states that the Injury Tracking Application will accept the data through December 31. That makes late identification and remediation part of the operating control. A calendar reminder is useful, but it does not prove that every covered establishment was identified or that its accepted submission matches the authoritative logs.
Organizations should maintain a status for each establishment: coverage determination, required forms, source-log readiness, internal review, submission attempt, acceptance response, correction, and closure. A firm-level 'submitted' flag can hide a missing location or an unresolved rejection. Buyers should ask whether the system reconciles the expected establishment population to accepted ITA transactions and shows exceptions without overwriting the original attempt.
Coverage begins with establishment identity
OSHA applies the electronic-reporting criteria at the establishment level, not to the firm as a single unit. Size, industry, and other applicability facts may differ by location. Certain covered establishments submit Form 300A summary data, while a subset with 100 or more employees in designated high-hazard industries also submits case information from Forms 300 and 301. A corporate headcount alone cannot support those determinations.
The practical data model needs stable establishment identities, addresses, industry codes, employment counts, operating dates, and relationships to legal and organizational structures. Those records also change. A facility opening, consolidation, code correction, or acquisition can alter the submission population. The system should preserve who made the applicability determination, which source facts were used, the effective period, and how a change affected current or prior reporting.
Submission format does not remove data responsibility
OSHA supports manual entry, CSV upload, and an application programming interface. Those are transport choices, not different accountability standards. Bulk and API methods can reduce repetitive work, but they also make mapping and population errors repeatable at scale. Teams should validate identifiers, required values, date and code formats, case counts, duplicate handling, and the returned acceptance or error response before treating a batch as complete.
A representative test should include an invalid establishment identifier, a partial batch, a corrected case, and a retry after an error. The audit trail should connect the submitted payload to its source record and retain the agency response. If a connector transforms fields, the transformation rules and version should be visible. Documented API connectivity establishes a capability; it does not establish that every submitted record is accurate or accepted.
Privacy controls belong in the data path
OSHA's guidance and personal-information job aid distinguish the data requested for electronic submission from personally identifying details that should not be sent in Form 300 and 301 fields. That boundary needs to exist before export. A redaction step after a file has entered an integration queue may leave sensitive information in logs, staging tables, or error messages even if it never reaches the final agency payload.
Buyers should trace a privacy-sensitive case through collection, review, transformation, submission, rejection, correction, retention, and access. The platform should limit fields by purpose, apply permissions, record disclosures, and support correction without spreading obsolete values. OSHA's page establishes current submission instructions; it does not certify software or determine an establishment's obligations. Applicability and recordkeeping decisions remain with accountable personnel using the governing requirements.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Safety Operations Standard will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.