Reference · built on requestOperator by FibricSafety, security & compliance

OSHA Recordkeeping

Turns closed incident tickets and absence records into proposed OSHA 300 log rows, 301 drafts, and the annual 300A summary.

Request accessPricing ↗

About

OSHA Recordkeeping is an operator for the injury and illness records that 29 CFR 1904 asks an employer to keep. It reads incident tickets as they close in your work management system and the time-off requests your HR system records afterward. For each case it applies the recording criteria in 1904.7, counts calendar days away and days restricted the way the rule counts them, and proposes a row for the OSHA 300 log and a draft 301 report.

At year end it proposes the 300A summary with the column totals, average employee count, and hours worked filled in. A person reviews every row. Nothing is entered in the log, posted, or sent to OSHA without an approval, and the executive certification stays a human signature.

This is a reference listing. It documents what Fibric would read from OSHA Recordkeeping and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Closed incident tickets in ServiceNow, Jira Service Management, or Freshservice, with the injured person, date, location, treatment, and outcome fields you map
  • Time-off requests in BambooHR, Workday, or ADP Workforce Now that begin after an incident, with their type, status, and dates
  • Restricted duty and job transfer records where your HR system holds them, for the days-restricted count
  • The 300 log you keep as an equivalent form in Microsoft Excel, Google Sheets, or on SharePoint, and the cases already on it
  • Headcount and hours worked for the year, from the HR or payroll export you name, for the 300A summary
  • Each establishment's size and industry code, which decide whether the electronic submission applies to it

Proposed actions

  • Target capability: propose one OSHA 300 log row per case that meets a 1904.7 criterion, with the classification and day counts, for your approval
  • Target capability: propose a draft 301 incident report from the ticket fields, for a person to complete within the seven-day window
  • Target capability: propose an updated day count when a related absence extends, capped at 180 calendar days as the rule allows
  • Target capability: propose the 300A summary at year end, with column totals, average employee count, and total hours worked, for the executive to certify
  • Target capability: propose a privacy-case entry, naming the case number only and adding the name to your separate confidential list

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Get the log row in before day seven

    A ticket closes in ServiceNow with treatment beyond first aid. The operator proposes the 300 row and a 301 draft the same day, and appends the row to your Excel log once you approve it.

    With ServiceNow, Microsoft Excel

  • Count days away the way the rule counts them

    A BambooHR time-off request starts the day after a recorded injury. The operator counts calendar days, weekends included, and proposes the updated day count on the existing row each time the request extends.

    With BambooHR, Google Sheets

  • Close the year with a 300A you can certify

    In January the operator totals the log, pulls average headcount and hours worked from Workday, and proposes the 300A. The executive reviews and signs. A CSV is prepared for a person to upload to the ITA.

    With Workday, Microsoft SharePoint

  • Keep privacy cases out of the posted log

    A Jira Service Management ticket matches a privacy concern case. The operator proposes the row with "privacy case" in the name column and a separate entry on your confidential list.

    With Jira Service Management, Google Sheets

Requirements

  • One work and ticket management connector holding your incident records, such as ServiceNow, Jira Service Management, or Freshservice
  • One HR connector with time-off read access, such as BambooHR, Workday, or ADP Workforce Now
  • One files connector holding the 300 log you keep as an equivalent form: Microsoft Excel, Google Sheets, or SharePoint
  • A field map from your ticket form to the 300 and 301 columns, and the list of establishments with their industry codes
Authentication
It reads tickets and absences through the credentials of your work management and HR connectors and writes rows through your spreadsheet connector. It carries no credentials of its own and never signs in to OSHA's Injury Tracking Application.

Limits

  • It applies the recording criteria as written. Whether a case is work-related is a judgment a person makes and records.
  • Absences it cannot tie to an incident are not counted. A time-off type mixing sick leave and injury leave needs a person to sort it.
  • It prepares the 300A. The company executive still certifies it, and a person still posts it from February 1 to April 30.
  • It does not submit to the Injury Tracking Application. It prepares the CSV a person uploads before March 2.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request OSHA Recordkeeping ↗

Questions and answers

What does a reviewer approve?
Every 300 row, every 301 draft, every day-count update, and the 300A. The reviewer sees the ticket, the absence it was tied to, the criterion the operator applied, and the row as it would appear. Approve, edit, or reject. Work-relatedness and the executive certification are decisions the operator never makes.
What record is kept, and for how long?
The log rows themselves, in the equivalent form you keep, plus a receipt for each: the ticket and absence it came from, the criterion applied, who approved it, and how to strike it. Struck rows stay visible, which matches how the rule asks you to line out a changed entry. Retention is the five years the rule sets.
Does it ever submit anything to OSHA?
No. It prepares the 300A figures and a CSV for the Injury Tracking Application's upload. A person signs in to the ITA and uploads it before March 2. Reporting a death within 8 hours or a hospitalization within 24 hours is a call a person makes, not something the operator does.
Ask about OSHA Recordkeeping

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy