Compliance frameworks and completeness scoring

What this row shows

Every compliance framework you're expected to run against, HazCom, the OSHA program suite (lockout/tagout, confined space, fall protection, heat illness, emergency action, PPE hazard assessment, respiratory protection, hearing conservation, bloodborne pathogens), fleet DOT safety, EPA RRP, has a written set of required elements: a written program, training records, an SDS library, a hazard assessment, whatever that specific framework calls for. The Compliance frameworks row turns each one into a single completeness number: how many of its required elements you actually have evidence for, scored from what has flowed in so far.

This is not a certification and not a legal opinion. It's IQ reading the evidence you've forwarded or uploaded, the training and policy records already on file, and telling you exactly which element is missing so you know what to go get. You decide what to file, forward, or draft next.

Where to find it

Open Compliance from the sidebar (/compliance). The Compliance frameworks row sits below Explore, above Most recent. Each framework appears as its own tile in the row, one tile per framework the catalog has seeded for your operation.

Reading a framework tile

Each tile is built from one framework's control set, scored against your evidence. What you see on the tile:

• Label: the framework's name, e.g. "HazCom," "OSHA Lockout/Tagout," "EPA RRP."
• Value: the framework's completeness score, 0 to 100 percent. This is a weighted average across every control in the framework, not a simple pass/fail count, controls the framework marks as more important carry more weight in the number.
• Sub-line: "All N elements in place" once every control clears the readiness bar, or "X of N elements in place · next: [section]" while gaps remain. The "next" name is the first element still short, named by its section (for example "Written program" or "Training"), so you know exactly what to chase without opening the tile.
• Gauge (the ring/bar under the number): colored red below 50%, amber from 50% up to 80%, green at 80% and above. The same three-way split colors the tile's accent: green, amber, or copper.
• Peer comparison: when you've opted into peer benchmarking and enough of the network has contributed for the comparison to be released, you'll see a line like "+6.2 vs Peer" or "vs Industry" next to the score. Until that comparison is available for a given framework, it's compared against broader industry data or omitted entirely. Framework-level peer comparisons are an early cut of this: today the same completeness comparison is shown across every framework tile, and it sharpens to a framework-specific peer line as more of the network reports in.

An element only counts as "in place" once its evidence clears roughly four-fifths completeness. Below that it's "partial" (counted toward the score but not toward "elements in place"), and with no evidence at all it's "missing."

Opening a framework: the detail view

Click any framework tile and a panel opens with the framework's name as its title. At the top:

"X of N elements in place · Y% inspection-ready. Forward or upload what you have and IQ scores each element. This is a completeness check, not a certification."

Below that, every control in the framework is listed as its own row: a status dot, the control's plain-language description, and its section name paired with its status, In place, Partial (N%), or Missing. The dot is green once a control clears the readiness bar, amber while it has partial evidence, and gray when nothing has landed yet.

From here you have two actions:

• Draft a starter program with IQ. This button appears only when the framework's written-program element is still short. It generates a starter written program for that framework and saves it to your policy library. Once drafted, the panel shows "Starter program drafted: [title]" with the note: "Saved to your policy library. It is a starting point, not legal advice. Review it with a qualified safety professional, then download it for your records." A Download PDF link produces the branded document.
• Upload evidence. Opens the same capture flow used across Verinode to forward or drop a document, an SDS binder, a training certificate, an audit report, whatever closes the gap on this framework.

At the bottom of every panel, a Download compliance binder (all policies, PDF) link exports your entire written-program library as one branded PDF, described as "Your whole posture in one branded PDF for an audit."

Where the score comes from

Every control on a framework draws its evidence from one of three places, and the ledger entry wins whenever more than one source has something to say:

1. Your evidence ledger. Anything IQ has scored from a document you forwarded or uploaded, an audit you ran, or evidence a drafter produced. Each ledger entry carries its own completeness (0 to 100%) and, where relevant, an expiration date.
2. An active HazCom training certification. If a team member holds an active or soon-to-expire HazCom training certification on file, HazCom's training element is automatically marked in place. You don't have to separately upload proof once the certification exists in your team records.
3. An active, framework-specific safety policy. For frameworks with a policy category specific enough to be unambiguous, HazCom, lockout/tagout, confined space, fall protection, heat illness, emergency action, PPE hazard assessment, and fleet DOT safety, an active written safety policy filed under the matching category automatically satisfies that framework's written-program element. Frameworks whose policy category is too broad to be framework-specific (respiratory protection, hearing conservation, bloodborne pathogens) don't get this shortcut; a generic policy shouldn't silently stand in for three different programs, so those rely on your evidence ledger or the drafter instead.

Evidence isn't permanent. If a piece of evidence carries an explicit expiration date, it stops counting once that date passes. If it doesn't carry one, IQ applies a default one-year validity window from when it was assessed before treating it as stale. The same applies to the policy shortcut above: an active policy past its own review date stops counting toward the written-program element until it's reviewed again. This is what makes the scoring continuous rather than a one-time checkbox, evidence decays, and the score reflects that.

Empty state

If the framework catalog hasn't been seeded for your operation yet, the row reads:

"Framework readiness (HazCom, OSHA recordkeeping, EPA RRP) will appear here. Forward or upload your written programs, SDS library, and training records and IQ scores each element for you."

This isn't a broken row, it means Verinode hasn't loaded a framework catalog for your operation yet. Forwarding your first written program or training record is what starts populating the tiles.

How this differs from your Shield Score

The framework row scores a single named framework's own control set. The Shield Score shown at the top of Compliance is a broader composite across training, insurance, carrier programs, regulatory exposure, and safety together, it isn't a framework itself. Think of frameworks as the individual audits you'd hand a regulator or a carrier's program manager, and the Shield Score as your overall compliance health across all of it.

Best-practice example

Say your HazCom tile reads 55%, amber, with the sub-line "2 of 4 elements in place · next: SDS library." Click it. The panel shows Written Program in place (a safety policy in the hazmat category is active and current), Training in place (a hazcom certification is on file), but SDS Library and Labeling both sitting at Missing. Rather than guessing what's required, forward your current SDS binder through the capture flow, IQ scores each sheet against the SDS Library element as it lands, and the tile's completeness climbs as coverage fills in. If the written program had instead been the gap, "Draft a starter program with IQ" would produce a starting document to review with a safety professional rather than starting from a blank page.

Data sources

Related reading

• Understanding your margin
• Benchmarks overview
• Reading a benchmark
• The decision workspace