Compliance Frameworks row: network completeness roll-up

What the Compliance Frameworks row shows

Restoration franchisees are subject to more than one OSHA program at a time, and each program is its own paperwork trail: a Hazard Communication (HazCom) program with safety data sheets and a written plan, an OSHA recordkeeping program with the 300 log and annual summary, and whatever other framework your network tracks. A franchisee can be excellent on one and behind on another. The Compliance Frameworks row is where Verinode HQ rolls that up by framework, across your whole network, so you can see which specific program is thin network-wide, not just which franchisee is behind.

Each tile in the row is one framework. Verinode reads how complete each franchisee's program is for that framework from the nightly aggregate refresh, averages it across every franchisee actually tracking that framework, and shows you the network average alongside how many franchisees are ready, partial, or at risk. Verinode does not run your HazCom program or fill out anyone's 300 log. It reads the completeness data your franchisees already have on file and reports the network picture back to you.

Two distinct read modes live in this same row, and which one a given tile is in depends entirely on whether that specific framework has an HQ standard set:

• No standard set (the default): each tile reads against the raw network average, with a green/amber/red split.
• Standard set: that tile switches to grading every tracked franchisee against the target percentage you defined, and the at-risk count becomes "how many are below the standard" instead of "how many are red."

This switch happens per framework, not for the whole row at once. It is entirely possible for HazCom to be graded against an 80% standard while OSHA recordkeeping is still showing the plain network average, because a standard exists for one and not the other. The rest of this article covers both modes and the one-click way to set a network-wide default.

Where to find it

Open Safety from the HQ sidebar, at hq.verinode.ai/safety. Safety sits inside the requirements-and-standing cluster alongside Compliance and Certifications, but it is its own page: a network safety hero, this Compliance Frameworks row, a Network Follow-Through tile (once your network has enough closed corrective actions to measure), Safety Cert Coverage Gaps, Safety Incidents, PPE Requirements, and Mandatory OSHA Requirements.

Compliance Frameworks is the second row on the page, directly under the safety hero panel (network safety-cert coverage, open incidents, and OSHA-recordable count over the trailing 36 months) and above Network Follow-Through.

Reading a framework tile before a standard is set

Until you set a standard for a given framework, its tile reads against the plain network average. You will see:

• Label, "{N} tracked", the number of franchisees actually reporting completeness data for this framework. This is not necessarily your full roster, only the members who have a reported program for that specific framework.
• Headline, the framework's name (for example "HazCom" or "OSHA recordkeeping").
• Sub-line, "{avg}% network avg · {green} ready / {amber} partial / {red} at risk", the average completeness percentage across every tracked franchisee, followed by how many of them fall into each of the three status tiers.
• Meta line, "{N} at risk" when the red count is above zero, or "On track" when it is not.
• Dot preview, one dot per tracked franchisee, with the at-risk ones highlighted. It is the same at-a-glance coverage-grid visual used elsewhere on the platform: a full row of dots reads as fully on track, a cluster of highlighted dots tells you at a glance how much of the tracked group is behind.
• Accent color, green when the network average is 80% or higher, amber (Hard Hat Yellow) from 50% up to 80%, and Ember Red below 50%.

Clicking a tile in this mode opens the franchisee detail view for the network's worst-performing member on that specific framework, the same Location Directory drill-in used across HQ. It is the fastest way to go from "this framework is thin network-wide" to "here is the specific franchisee dragging it down."

Reading a framework tile once a standard is set

Once you (or the one-click adoption described below) set a target completeness percentage for a framework, that tile's tone changes entirely: it stops reporting against the raw average and starts reporting against your bar.

• Label, "Standard {N}%", the target completeness percentage you set for this framework.
• Sub-line, "{meets} of {tracked} meet the {target}% standard · {avg}% network avg", so you can see both how many franchisees are clearing your bar and what the network is actually averaging.
• Meta line, "{N} at risk" for franchisees below the standard, or "On track" if none are.
• Dot preview and accent color now key off the standard rather than the raw average: green when nobody is below standard, amber when half or fewer of the tracked franchisees are below it, and Ember Red when more than half are.

Grading against a standard uses a tolerance band rather than a hard cliff at the target. A franchisee at or above the target percentage meets the standard outright. One that falls short but stays within 20% of the target (for example, an 80% standard with a franchisee at 66% or higher) is graded as near the standard rather than failed outright; only a franchisee more than 20% below target is graded as missing it. Both "near" and "missing" count toward the at-risk figure on the tile, since both represent a franchisee below the bar you set, just at different distances from it.

Clicking a graded tile behaves the same way as the ungraded version: it opens the detail view for the specific franchisee furthest below the standard on that framework.

Setting a network standard

Until at least one framework has a standard, a Set network standard tile leads the row, ahead of the framework tiles themselves. It reads:

SET NETWORK STANDARD Require 80% framework completeness across the network Each franchisee is graded against the standard; those below surface as at-risk. Tighten per framework later. Adopt 80% standard →

1. 1Click Adopt 80% standard →. The button reads Setting… while it runs.
2. 2Verinode looks at every framework where at least one franchisee already has some completeness reported (a framework nobody is engaged with at all is skipped, so members are not suddenly marked non-compliant against a program they may not even be subject to).
3. 3For each engaged framework that does not already carry a standard, Verinode sets an 80% target completeness requirement, marks it required, and tags it as a network default rather than a hand-typed value.
4. 4The page refreshes. Every framework that just picked up a standard switches into graded mode immediately; a franchisee below 80% (or more than 20% below, for the "missing" tier) now counts toward that framework's at-risk figure.
5. 5The Set network standard tile itself disappears once any framework has a standard, whether that came from this one-click action or was set individually. It will not reappear once at least one standard exists.

Only HQ admins can set a standard. Attempting this without admin access returns the error "Only group admins can set standards," and the button surfaces whatever the underlying error is if the save fails for any other reason.

Empty state

If your network has no completeness data reported for any framework yet, the entire Compliance Frameworks row is replaced with a single line:

Framework completeness (HazCom, OSHA recordkeeping) appears across the network as franchisees build and forward their programs.

There is nothing to click in this state, no set-standard tile and no framework tiles. As soon as at least one franchisee reports completeness data for at least one framework, the row populates and the set-standard tile appears (assuming no standard exists yet).

The privacy boundary

Compliance Frameworks holds the same line as the rest of Safety and Compliance: HQ sees the completeness percentage and status per franchisee per framework, computed by the nightly aggregate refresh, never the underlying program documents, safety data sheets, or 300 log entries themselves. Franchisees own and maintain their own compliance program; HQ sees the roll-up standing, not the paperwork behind it.

Franchisee names follow the same identity gate used across HQ. In the default independent-franchisee model, the name shown when you click into a worst-performing franchisee is an anonymized, stable label rather than the real business name. In a same-entity, single-owner multi-location network, the real location name shows, because it is one business looking at its own locations. Either way, the completeness percentages and status counts feeding this row are identical: the identity gate only changes whether a name is shown in the clear, never what HQ can see.

How to use it

1. 1Scan the row for any tile showing an Ember Red accent or an "N at risk" meta line above zero. That is your worst framework network-wide, whichever mode it is currently reading in.
2. 2If no framework has a standard yet, click Adopt 80% standard → to put a real bar under every framework your network is actually engaged with, in one action.
3. 3Click into a red or at-risk tile to open the specific franchisee furthest behind on that framework, and take it from there through your own compliance channel.
4. 4Revisit the row periodically as new franchisees start reporting completeness data. A framework with a small tracked count today can shift quickly as more of the network builds out that program.

Related reading

• Compliance overview: the brand-health page (certifications, cross-network safety-incident patterns, reputation) that sits alongside Safety in the sidebar.
• Standards conformance: the sibling grading system for stage-time process standards (days-per-stage on the Network page), built on the same met/near/missed logic as framework completeness.
• Safety Risk (Workforce): per-franchisee open incidents and OSHA-recordable rate per 100 FTE, benchmarked against the network median, on the Workforce page.
• HQ overview: where Safety fits into the rest of the HQ sidebar.
• Network Health: the broader signal surface that cross-network safety patterns feed into.

Data sources