Safety: network safety posture at a glance
Safety is the OSHA reference and safety-posture surface inside the Compliance band of HQ. It answers a narrower, sharper question than the Compliance page's broad brand-health composite: specifical…
On this page
What the Safety section shows
Safety is the OSHA reference and safety-posture surface inside the Compliance band of HQ. It answers a narrower, sharper question than the Compliance page's broad brand-health composite: specifically, is the network carrying the safety certifications OSHA expects a restoration crew to hold, and where are the open incidents and OSHA-recordable events sitting right now. Where the Compliance page (/help/hq-compliance) blends certification currency, safety, and reputation into one composite score, Safety goes one level deeper on the safety dimension alone: which memberships are missing safety certs, which are carrying open incidents, and what the reference catalog of mandatory and PPE-related OSHA requirements actually says.
Verinode does not run a safety program for a membership and does not file, close, or dismiss an incident. It reads OSHA reference data (a static catalog of requirements, standards, and citations, not something Verinode edits) alongside the safety-certification and incident figures your memberships' own IQ accounts already generate, rolls those figures up to the network level, and lays out where the coverage gaps and open risk sit. Every number on this page is an aggregate or a rollup. Safety never opens a membership's actual incident report, its OSHA 300 log, or any other private business record. Memberships own their safety data; HQ sees network-level posture and per-membership cert and incident counts, never the underlying documents behind them.
Where to find it
Open Safety from the HQ sidebar. It sits in the Compliance band alongside Programs, Compliance, and Certifications, and it is its own full page at hq.verinode.ai/safety (not a tab inside another card slider). The Compliance band groups these four together because they are all "what does the network commit to, and how is it doing against that" surfaces: Programs holds SOPs and training mandates, Compliance is the blended brand-health composite (cert currency + safety + reputation), Certifications is the full credential-by-membership matrix, and Safety is where OSHA reference material and safety-specific posture live on their own.
Note
Safety is not the same page as the Safety Incidents row on the Compliance home (/help/hq-safety-incidents). That row is a cross-network early-warning surface: it only surfaces an incident type once it has repeated across enough of the membership base to read as a pattern, and it never tells you which single membership is behind it. This page, by contrast, names which memberships are short on safety certs or are carrying open incidents right now, at the level of aggregate counts per membership, not job- or report-level detail. The two surfaces answer different questions and both hold the same privacy boundary: no membership's underlying incident report or job file is ever exposed.
The page loads by reading your group's OSHA requirement catalog (a fixed reference set, no per-membership query needed) alongside two rollups from the network layer: each membership's active safety-certification counts and each membership's open-incident and OSHA-recordable counts. Both rollups are computed once per membership per certification or incident type and unioned together, so a membership shows up here as soon as it has either kind of data, even if it hasn't reported the other kind yet. Membership names on this page are handled the same way they are everywhere else in HQ: in a franchise or association network, a membership's name is anonymized to a short, stable label unless your group has been configured as a single legal entity operating multiple locations, in which case real location names show through because they are, legally, the same business. Either way, the underlying safety-cert and incident figures are never traceable back to a specific job, claim, or employee.
The Network Safety hero
At the top of the page sits a single dominant number under the eyebrow "Network safety": the count of memberships that hold safety certifications, shown as a big animated count-up. Beside it, a pill reads "of N memberships" (N being your total membership count), tinted green when cert compliance is 80% or higher, neutral gray between 50% and 80%, and red under 50%.
Under the headline, a line of context reads, for example, "18 active safety certs across the network · 12 OSHA standards tracked," summarizing the total number of active safety certifications logged across every membership and the number of OSHA standards in the reference catalog behind the rest of the page.
Three secondary figures sit beside the headline:
- Cert compliance, a percentage, labeled "Franchisees with safety certs." This is the same ratio driving the headline pill: memberships holding at least some safety certification, divided by total memberships tracked. It reads green at 80%+, neutral between 50% and 80%, and red under 50%, the same banding as the pill.
- Open incidents, a count, labeled "Active investigations": the total number of open safety incidents summed across every membership in the network right now. It reads green at zero, neutral at three or fewer, and red above that.
- OSHA 36mo, a count, labeled "OSHA-recordable rolling": the total number of OSHA-recordable events logged across the network in the trailing 36 months. It reads red (in this tile's own scheme, "maintain" tone) whenever the count is above zero, and green only at zero.
The safety certifications behind these counts are the specific set OSHA and general jobsite safety practice call for on a restoration crew: OSHA 10, OSHA 30, OSHA 510, First Aid/CPR, Confined Space, Fall Protection, and HAZWOPER. A membership counts toward "compliant" the moment it holds at least one of these current; the Safety Cert Coverage Gaps row below breaks that same set down further into good, partial, and missing.
Empty state. Until any membership has registered a safety certification, the hero's context line reads: "Safety certification data will appear as franchisees register their OSHA / first-aid / confined-space certifications." The pill reads "No data yet" instead of an "of N franchisees" count in that state.
Compliance Frameworks
Below the hero sits a row of tiles, one per compliance framework your network tracks (for example HazCom or OSHA recordkeeping programs), reading network-wide completeness for each. Two states exist for this row, depending on whether HQ has set a required standard yet:
- Before a standard is set, each tile shows how many memberships are tracked for that framework, the network average completeness percentage, and a breakdown of how many memberships are "ready," "partial," or "at risk" (Verinode's own green/amber/red read for that framework, independent of any HQ-set target). A dashed "Set network standard" tile leads the row in this state, offering a one-click way to require 80% framework completeness across the network; clicking "Adopt 80% standard" turns that target on immediately, and every membership is then graded against it going forward. You can tighten the target per framework later.
- Once a standard is set, each tile instead reads "N of M meet the X% standard · Y% network avg," and the "at risk" count reflects memberships below your chosen target rather than Verinode's own ready/partial/risk read.
Clicking a framework tile opens the membership carrying the worst standing for that framework (the framework's own detail view), so you can see who to follow up with first.
Empty state. Before any membership has built out a compliance framework, this row reads: "Framework completeness (HazCom, OSHA recordkeeping) appears across the network as franchisees build and forward their programs."
Network Follow-Through
This row surfaces one metric tile, "Incident Follow-Through," the median number of days the network takes to close a corrective action once a safety incident is logged, measured from the incident occurring to its corrective action being marked closed. It is mined from the same lifecycle-date process-mining engine that powers Network Flow (/help/hq-network-flow), specifically the "safety" process's stage transitions, and it rolls those per-membership medians up to one network figure.
Where an external industry comparison exists for this transition, the tile carries a delta line underneath the day count: "On Pace With Industry" in neutral gray when the network's median and the industry median are within half a day of each other, or "Xd vs Industry" in green (network faster) or red (network slower) when they differ by more than that.
Empty state. This tile does not render at all until enough memberships have reported enough safety-incident lifecycle dates for the network median to be statistically meaningful. Until then, the row is empty and no placeholder tile appears.
Safety Cert Coverage Gaps
This row lists memberships that are behind on the safety-certification baseline, up to eight at a time, sorted so the memberships with the fewest active certs lead the row. The baseline is the same seven-certification set from the hero (OSHA 10/30/510, First Aid/CPR, Confined Space, Fall Protection, HAZWOPER); Verinode treats three or more active certs from that set as full coverage.
Each tile shows:
- A coverage band: Good (three or more active certs, green), Partial (one or two, yellow), or Missing (zero, red). This is the tile's top-left label and also sets its accent color.
- The membership's name as the headline.
- A cert count line: either "N active cert(s)" or, for a membership with none on file, "No active safety certifications."
- A dot preview, a small visual reading the shortfall against the 3-cert baseline, colored red for a Missing membership and amber for a Partial one.
Only memberships that are Partial or Missing appear in this row at all; a membership at Good coverage never shows up here. Clicking a tile opens that membership's detail record.
Empty state. When every membership carries at least three active safety certifications, the row reads: "Every franchisee has at least 3 active safety certifications. Network is at baseline coverage."
Safety Incidents
This row lists memberships carrying open safety risk right now, up to six at a time, sorted with the highest combined open-incident-and-OSHA-recordable count leading the row. Each tile is rendered 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.
Each tile shows:
- A count label in the top-left: the number of open incidents if the membership has any (e.g., "2 open"), or the OSHA-recordable count if it has none open (e.g., "1 OSHA").
- The membership's name as the headline.
- A detail line: when a membership has both open incidents and OSHA-recordable events, it reads both together ("2 open · 1 OSHA 36mo"); otherwise it reads whichever one applies ("2 open incidents" or "1 OSHA-recordable rolling").
Clicking a tile opens that membership's detail record. A membership only appears in this row while it is carrying at least one open incident or at least one OSHA-recordable event in the trailing 36 months; once both drop to zero, it drops off the row.
Empty state. When no membership carries an open incident or an OSHA-recordable event, the row reads: "No open incidents or OSHA-recordable events in the last 36 months across the network."
PPE Requirements and Mandatory OSHA Requirements
The two rows at the bottom of the page are static reference material, not per-membership data. They exist so that a leadership team scanning Safety can see the actual OSHA standards behind the page's numbers without leaving HQ.
- PPE Requirements lists OSHA standards specifically about personal protective equipment: anything in the catalog whose requirement name mentions PPE, protective equipment, respiratory protection, or hearing protection. Up to eight show as tiles.
- Mandatory OSHA Requirements lists every requirement in the catalog tagged with mandatory severity (as opposed to recommended or best-practice). Up to twelve show as tiles.
Each tile in both rows shows the requirement's plain-language name as the headline, the issuing authority (for example OSHA) as the sub-line, and the citation (for example "29 CFR 1910.134") in the trailing corner. Clicking a tile with a 29 CFR 1910 or 1926 citation opens the canonical OSHA.gov page for that standard in a new tab. Citations that follow a state-statute or agency-code format instead of the federal 29 CFR pattern don't have a single canonical URL to link to, so clicking those tiles does nothing; that is deliberate rather than a broken link, since a wrong guess at a state citation's URL would be worse than no link at all.
Empty states. If the reference catalog has no PPE-tagged standards, PPE Requirements reads: "No PPE-specific OSHA standards in the reference catalog yet." If it has no mandatory-severity standards, Mandatory OSHA Requirements reads: "No mandatory requirements in the reference catalog."
The privacy boundary on this page
Every figure on Safety is either a network-wide rollup or a per-membership aggregate count (a number of active certs, a number of open incidents, a number of OSHA-recordable events). Safety never shows:
- The content of an incident report, an OSHA 300 log, or any injury or claim detail. A membership's underlying safety documentation stays in that membership's own IQ account.
- A membership's real identity, in a franchise or association network configured as independent operators. Membership names on this page are anonymized the same way they are across the rest of HQ, unless your group is configured as a single legal entity operating multiple locations.
- How narrow a cohort has to be before a figure would be considered identifiable. Where this page rolls figures up across the network (for example the Network Follow-Through median), it simply doesn't render the tile until there is enough underlying data for the figure to be meaningful; it does not publish the sample size behind that decision.
How to use it
- 1Start at the Network Safety hero. Read the cert-compliance pill and the two secondary figures (open incidents, OSHA 36mo) as your fast scan: green across all three means the network's safety posture is in good shape today.
- 2If a compliance framework standard is not yet set, consider adopting the one-click 80% standard on the Compliance Frameworks row so every membership going forward is graded on the same bar.
- 3Check Safety Cert Coverage Gaps for any membership marked Missing. A membership with zero active safety certs is the most urgent gap on the page, since it means none of the baseline OSHA-10 / first-aid / confined-space certifications are on file.
- 4Check Safety Incidents for any membership carrying open incidents or recent OSHA-recordable events, and decide whether that membership needs a direct conversation, a bulletin, or a documented review.
- 5Use PPE Requirements and Mandatory OSHA Requirements as reference when drafting a network-wide safety bulletin or updating a training program in Programs, so the language matches the actual OSHA citation.
Related reading
- Compliance overview, the blended brand-health composite (cert currency + safety + reputation) that Safety's incident and cert figures feed into.
- Safety Incidents across the network, the cross-network pattern-detection row on the Compliance page, distinct from this page's per-membership incident list.
- Cert Coverage, the certification-by-type currency read across all certification categories, not just the safety-specific baseline covered here.
- Network Flow, the full process-mining surface the Incident Follow-Through tile is mined from.
- Programs, where SOPs and training mandates live if a cert gap or incident pattern needs a codified fix.
Data sources
- 1.OSHA safety and PPE requirement catalog. Verinode intelligence layer, sourced from OSHA 29 CFR and state agency standards.
- 2.Per-membership safety-certification and incident rollups. the network data and the network data.
- 3.Safety process stage medians (Incident Follow-Through). Verinode network intelligence layer, process-mining aggregate refresh.