SafetyLeads combines public OSHA enforcement records, employer-reported injury and illness data, severe injury reports and related establishment context for search and account research. The source agency remains authoritative; a SafetyLeads signal is a dated, processed record—not a promise that a condition is current or that an account intends to buy.
An inspection or citation describes agency enforcement activity. An ITA 300A summary describes an employer's annual reported totals. A Severe Injury Report describes a reportable event. These records should not be blended into one undifferentiated “risk” claim.
Inspections, citations and penalties
Records of agency enforcement activity tied to an inspection or establishment. A citation is not the same thing as an injury report or a current hazard assessment.
Use with care: Check the inspection, citation status, issue date and establishment before describing it.
Employer-reported annual summary data
Annual establishment-level counts and hours used to describe recordable injuries and illnesses and calculate measures such as TRIR or DART when the required fields are available.
Use with care: A 300A summary is not an individual case narrative and does not itself identify a citation or cause.
Employer severe-injury reports
Reports made to OSHA for qualifying severe events, including inpatient hospitalizations, amputations and losses of an eye under the applicable reporting rule.
Use with care: A report signals that an event was reported; it is not, by itself, an OSHA finding of fault, a citation or proof of current risk.
Employer-reported case-level information
Case-detail records can add incident outcome, days away, job-transfer and other coded fields where OSHA has published the record.
Use with care: Availability and detail vary by filing and year. Treat coded fields as source data, not a complete investigation narrative.
Source records are downloaded or read from configured government data endpoints and stored with dataset metadata.
Names, addresses, dates and coded fields are normalized so records can be searched consistently across views.
Records are associated with employer and establishment records when identifiers or matching fields support that association.
Search results and profiles expose source context, dates and available evidence so users can verify before outreach.
Some measures are derived from source fields. For example, TRIR and DART displays use employer-reported counts and hours where those fields are present. Derived measures are estimates of the reported data, not independent audits.
OSHA and other agencies publish, revise and sometimes remove records on their own schedules. SafetyLeads processes data through ingestion jobs and caches; the OSHA scheduler uses a configured cadence with a seven-day default in the application, while deployment settings can differ. The alert worker can process newly available records separately, but no real-time coverage or delivery time is promised.
Always check the event date, source date and record status. A missing record may reflect publication timing, matching or coverage rather than the absence of an event.
Where a source provides a stable establishment identifier, SafetyLeads can use it to join records. Where it does not, normalized employer names and location fields help create a consistent association. Cross-source EPA facility matching uses candidate similarity across name, address, ZIP, city and compatible industry fields, with candidates separated into approved, review and lower-confidence states.
A shared identifier supports a stronger join when the source supplies one.
Name and location normalization helps find the same establishment despite formatting differences.
Similarity scores can produce candidates; a score does not prove the legal entity or site is the same.
These links are provided so researchers can check definitions, reporting rules and underlying records rather than treating a summary as the source.
OSHA's data landing page and catalog for workplace safety and enforcement datasets.
OSHA's explanation of employer-submitted injury and illness information, including the ITA data program.
OSHA's public reports for severe injury events reported under its reporting requirements.
OSHA's establishment and inspection search, useful for checking an underlying enforcement record.
The official reporting rule that defines when fatalities, inpatient hospitalizations, amputations and eye losses must be reported.
BLS's overview of the Survey of Occupational Injuries and Illnesses and related national statistics.
ITA 300A is an employer-reported annual summary of injury and illness information. An OSHA citation is an enforcement record associated with an inspection. They come from different processes and should not be treated as interchangeable.
No. A Severe Injury Report is a report of a qualifying event under OSHA's reporting requirement. The report alone does not establish fault, a citation or an inspection outcome.
Publication and ingestion have lag, and a record may not yet be associated with an establishment. Check the source agency, event date and latest ingestion context; absence from a profile is not proof that no record exists.
When the employer-reported fields needed for the calculation are present, SafetyLeads derives rates from reported case counts and hours. Those values are estimates of the filing and should be interpreted with the filing year and establishment scope.
No. Matches and scores support sales research. They are not legal, regulatory, medical, insurance or employment advice, and consequential decisions require independent verification and appropriate review.
Identify the accounts that matter, understand the signals behind them, and execute a more precise go-to-market strategy.
Get started