Reference · built on requestOperator by FibricSafety, security & compliance

Near-Miss Triage

Classifies near-miss reports by hazard type, location and severity. Proposes an owner and a corrective-action ticket for each.

Request accessPricing ↗

About

Near-miss reports arrive as a form row, a message in a channel, a work request, or a photo with a line of text. They sit until the safety meeting. Near-Miss Triage reads each new report from the places you collect them, an Airtable base, a Google Sheet, a Slack channel, a MaintainX work request, and proposes a classification: hazard type, the location and asset it concerns, and a severity on the scale you define.

From the location and hazard type it proposes an owner and a corrective-action work order or ticket, written with the report's own words and photo. The owner accepts or changes the classification. Reports that describe an injury are routed to the safety lead first.

This is a reference listing. It documents what Fibric would read from Near-Miss Triage 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

  • New report rows in Airtable or Google Sheets, read through the Airtable list records endpoint or the Sheets values API, with photos where attached
  • Messages in a reporting channel in Slack or Microsoft Teams, including replies that add detail
  • Work requests submitted through a MaintainX work request portal, or UpKeep work orders tagged as safety
  • Locations and assets from your CMMS, so a report can be pinned to a place and a piece of equipment
  • Open corrective-action work orders, so a hazard already being fixed is linked rather than duplicated

Proposed actions

  • Target capability: propose a classification per report, hazard type, location, asset and severity, written back to the report row once the owner confirms it
  • Target capability: propose a corrective-action work order in MaintainX or UpKeep, or an issue in Jira, with the report text and photo attached
  • Target capability: propose an owner from the location or hazard type mapping you maintain, with a Slack or Teams notice to that person
  • Target capability: propose routing a report that describes an injury to the safety lead before any classification is applied
  • Target capability: propose a monthly summary by hazard type and location, with open and closed corrective actions

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

What you can build

  • Turn a Slack photo into a work order

    A forklift near-miss posted in the safety channel becomes a proposed classification and a MaintainX work order for the aisle, with the photo attached and the warehouse lead as owner.

    With Slack, MaintainX

  • Triage the form responses every morning

    New rows in the Airtable near-miss base are classified overnight. Each morning the safety coordinator sees the proposed hazard types, severities and owners, confirms them in one pass, and the corrective actions open in Jira.

    With Airtable, Jira

  • Link a repeat hazard to the open fix

    A second Google Sheets report about the same loading dock step matches an open UpKeep work order. The operator proposes attaching the report to it rather than opening another.

    With UpKeep, Google Sheets

Requirements

  • At least one intake source: an Airtable base, a Google Sheet, a Slack or Teams channel, or a MaintainX work request portal
  • A CMMS or ticket connector for corrective actions, such as MaintainX, UpKeep, or Jira
  • A location and asset list, from the CMMS or a sheet you maintain
  • Your hazard type list, severity scale, and the owner mapping by location or hazard type
Authentication
Near-Miss Triage has no account on any system. Reports, locations and work orders are read and proposed through the connectors you connect. A classification is written to the report only after the owner confirms it.

Limits

  • Severity is proposed from the report's words against your scale. A person confirms it. The operator does not inspect the site.
  • A report with no location named, and no photo that places it, is classified by hazard type only and left for a person to place.
  • Regulatory recordkeeping, such as an injury and illness log, is not produced here. An injury report is routed to a person.
  • Duplicate detection is by location, hazard type and time window. Two reports of one hazard from different angles may still both be proposed.

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 Near-Miss Triage ↗

Questions and answers

Who confirms the hazard type and severity?
The owner the operator proposes, or the safety coordinator if you set a single reviewer. They see the report, the photo, and the proposed classification, and change any field before it is written back.
What if a report describes an injury, not a near miss?
It is routed to the safety lead before anything else happens. No classification or work order is proposed until that person has seen it, because an injury may carry reporting duties the operator does not handle.
What does the record show a year later?
Each report with its confirmed classification, the work order or issue it produced, the owner, who confirmed it and when, and the status of the corrective action. The monthly summaries are kept with it.
Ask about Near-Miss Triage

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