Safety Incidents row
Safety Incidents is a row on the Safety page in Verinode HQ. It lists every franchisee currently carrying an open safety-incident investigation, an OSHA-recordable event logged in the trailing 36 m…
On this page
What the Safety Incidents row shows
Safety Incidents is a row on the Safety page in Verinode HQ. It lists every franchisee currently carrying an open safety-incident investigation, an OSHA-recordable event logged in the trailing 36 months, or both, and it puts the worst-standing franchisee first. This is a named, per-franchisee list, not a network-wide pattern read: if one franchisee has an open incident and nobody else does, that franchisee still shows up here on its own.
Verinode does not run a safety program for your network and does not open, investigate, or close an incident on a franchisee's behalf. It reads the open-incident count and the OSHA-recordable count that each franchisee's own IQ account has already recorded, from the same team-summary feed that drives the rest of the Safety and Workforce pages, and rolls those counts up into this one row so leadership can see where open safety risk is sitting across the network right now.
Note
There are two "Safety Incidents" surfaces in HQ and they answer different questions. This article covers the row on the Safety page (hq.verinode.ai/safety), which names specific franchisees and their own open-incident and OSHA-recordable counts. The Compliance page (hq.verinode.ai/brand-compliance) has a separate Safety Incidents row that only surfaces once the same incident type has repeated across a meaningful share of the network, and it never names which franchisee is behind it. See Compliance overview for that surface. The two rows can both be non-empty at once and are not the same list.
Where to find it
Open Safety from the HQ sidebar, at hq.verinode.ai/safety. Safety Incidents is the fifth row on the page, directly under Safety Cert Coverage Gaps and above PPE Requirements. The full page, top to bottom, is: the Network Safety hero, Compliance Frameworks, Network Follow-Through (when your network has enough closed corrective actions to measure), Safety Cert Coverage Gaps, Safety Incidents, PPE Requirements, and Mandatory OSHA Requirements.
Reading a tile
Each franchisee in the row is its own tile, shown at double width with the platform's high-intensity "action" treatment, the same visual weight used everywhere on the platform for something that calls for a decision rather than a passive read. A safety glyph (a hard hat icon) marks the tile so it reads as a safety item at a glance, distinct from a cert-coverage or compliance-framework tile in a neighboring row. Every tile in this row carries the same Ember Red accent, since everything that qualifies to appear here is, by definition, open risk.
Each tile shows:
- A count label, top left. If the franchisee has any open incidents, this reads the open-incident count, for example "2 open." If it has no open incidents but does have OSHA-recordable events in the window, it reads that count instead, for example "1 OSHA."
- The franchisee's name, as the headline.
- A detail line underneath, built from whichever of the two figures apply:
- Both open incidents and OSHA-recordable events: both counts together, for example "2 open · 1 OSHA 36mo." - Open incidents only: "N open incident" (or "N open incidents" for more than one). - OSHA-recordable events only, no open incidents: "N OSHA-recordable rolling."
Clicking a tile opens that franchisee's own detail record. Up to six franchisees show in the row at a time; if more than six qualify, the six with the most combined open risk lead the row.
What counts as an "open incident" and an "OSHA-recordable event"
- Open incidents is a count of safety-incident investigations that franchisee's IQ account has logged as still open, meaning not yet closed out. It is a live, right-now number: as a franchisee closes an investigation, its count drops, and once it hits zero that franchisee no longer contributes an open-incident figure to this row.
- OSHA-recordable event follows OSHA's own recordability standard: an injury or illness serious enough to require entry on an OSHA Form 300, generally meaning it involved medical treatment beyond first aid, days away from work, restricted duty or job transfer, or a fatality. The count on this row looks back over a rolling 36-month window, always the trailing three years from today, not a calendar-year or fiscal-year window. That window recalculates continuously, so a franchisee's OSHA-recordable count here will not reset on January 1; an event only drops out of the count once it ages past 36 months old.
A franchisee can appear in this row from either figure alone, or from both together. A franchisee with zero open incidents and zero OSHA-recordable events in the trailing 36 months does not appear in the row at all.
Ranking: how severity is decided
The row is sorted by combined open risk, franchisees with the highest sum of open-incident count plus OSHA-recordable count leading the row, down to the lowest qualifying combination. There is no separate manual severity label on this row (unlike, for example, Cert Coverage Gaps, which bands franchisees into Good, Partial, and Missing); the sort order itself is the severity read. A franchisee sitting at the top of the row, with a large combined number, is carrying more open safety risk right now than one further down with a smaller combined number.
The privacy boundary
Safety Incidents shows a per-franchisee aggregate: an open-incident count and an OSHA-recordable count, nothing more. It never shows:
- The content of an incident report, an OSHA 300 log entry, or any injury or claim detail. That documentation stays inside the franchisee's own IQ account. HQ sees the count, not the file.
- A franchisee's real identity, in a network configured as independent franchisees. Names on this row follow the same identity gate used across HQ: anonymized to a stable label by default, shown in the clear only when your network is configured as a single legal entity operating multiple locations, because in that configuration it is one business looking at its own locations rather than a franchisor looking across independently owned businesses.
- Any per-job, per-claim, or per-employee detail behind the counts. Franchisees own and maintain their own safety records; HQ sees the roll-up standing on this row, never the underlying documentation.
Empty state
When no franchisee in the network currently has an open incident or an OSHA-recordable event in the trailing 36 months, the row collapses to a single line:
No open incidents or OSHA-recordable events in the last 36 months across the network.
Read this as good news, not a data gap. The Network Safety hero at the top of the page gives you the same read at a glance: its Open incidents figure (labeled "Active investigations") reads zero and its tone turns green, and its OSHA 36mo figure (labeled "OSHA-recordable rolling") reads zero and turns green as well. Those two hero figures are the network-wide sum of exactly the same counts that populate this row; when both are zero, the row underneath them is guaranteed to be empty too.
How to use it
- 1Open Safety from the HQ sidebar and check the Network Safety hero first. If Open incidents and OSHA 36mo both read zero, the Safety Incidents row will be empty and there is nothing to act on here today.
- 2If either hero figure is above zero, scroll to the Safety Incidents row. It is already sorted worst first, so the top tile is your highest-combined-risk franchisee.
- 3Click the top tile to open that franchisee's detail record and see its safety standing in full.
- 4Work down the row in order. A franchisee showing "open" incidents is the more time-sensitive case: that investigation is still active. A franchisee showing only an "OSHA" count is a trailing, already-recorded event, still worth a conversation but not unfolding in real time.
- 5Decide on a response through your own channels, a direct call to the franchisee, a documented review, or a broader bulletin if the same pattern is showing up elsewhere in the network (check Compliance overview for that cross-network read). Verinode surfaces the standing; it does not contact the franchisee or file anything on your behalf.
Related reading
- Safety: network safety posture at a glance, the full Safety page this row lives on, including the hero panel, Compliance Frameworks, Network Follow-Through, and Safety Cert Coverage Gaps.
- Compliance overview, the separate Compliance page and its own Safety Incidents row, the cross-network pattern-detection surface that never names a franchisee.
- Safety Risk (Workforce), the Workforce page's own safety row, which adds an OSHA-rate-per-100-FTE comparison against the network median on top of the same open-incident and OSHA-recordable counts.
- Compliance Frameworks row, the sibling row on the Safety page covering HazCom and OSHA recordkeeping completeness rather than incidents.
- HQ overview, where Safety fits into the rest of the HQ sidebar.
Data sources
- 1.Per-franchisee open-incident and OSHA-recordable counts. the network data.
- 2.Franchisee identity, gated by network entity model. Verinode HQ.