OSHA 300A Summary Extractor

Extract the establishment, reporting year, hours worked, total case counts, incidence rates, and executive certification from an OSHA 300A summary PDF.

The full guide: TRIR and DART rates from an OSHA 300A summary

How should we start?

Build with Talonic

Need to scale? Create an API key, then run this from your own code or an agent.

Create an API key

Free account required

Start with a document

Upload a file or pick a sample, and see the fields come back.

No signup · nothing stored

Questions about OSHA 300A Summary Extractor.

What does the OSHA 300A summary extractor read?

The form number and date, the reporting year, the employer (establishment) name, EIN, and address, the total employees and total hours worked during the year, the establishment description and NAICS code, and the reporting location if the organization runs multiple sites.

How is the OSHA 300A summary different from the OSHA 300 log?

The 300A is the annual summary posted from February 1 to April 30: it reports establishment-level totals — total cases, hours worked, days away, and incidence rates for the year — and is signed and certified by a company executive. The OSHA 300 is the case-by-case log with one row per recordable injury or illness. This tool reads the summary totals; for the per-case log use the OSHA 300 log extractor.

Which annual total fields come out?

The total injuries and illnesses, the lost workday cases, the days away from work, the job transfer or restricted duty days, the other recordable cases, and the total deaths each come back as fields, alongside the calculated injury rate and lost workday rate per 100 full-time-equivalent employees.

Does it capture who certified the summary?

Yes. The certifier name and title (typically the owner, CEO, or a senior officer), the certification date, and whether the establishment claims a recordkeeping exemption (boolean) each come back as fields, so the executive attestation required on the 300A is captured.

What are the file limits and privacy terms?

PDF only, up to 10MB and 100 pages. The summary reports aggregate counts rather than named individuals. It is processed via the Talonic API for extraction only, is not retained for training, and is not shared.

Doing this to one file, or to ten thousand?

The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.

See PDF to Markdown if you run this for data and platform teams, or the extraction API if you are building it in.