Framework panel, starter-program drafter, and binder

What this covers

The Compliance frameworks row on the Compliance page (see Compliance section overview for the row itself) scores your written-program readiness against named regulatory frameworks: OSHA Hazard Communication (HazCom), lockout/tagout, confined space, fall protection, respiratory protection, hearing conservation, heat illness, emergency action, PPE hazard assessment, fleet and driver safety, OSHA recordkeeping, EPA Lead-Safe (RRP), insurance and COI completeness, carrier program audit readiness, IICRC firm standing, and sell-side diligence readiness, plus whatever else Verinode's frameworks catalog adds over time. This article is about what happens when you click into one of those tiles: the framework detail panel that opens, the button that has IQ draft a starter written program for you, the evidence-upload path, and the compliance binder PDF you can hand to an auditor.

The framework panel, drafter, and binder are web (IQ) features today. On mobile, tapping a framework tile opens a chat with IQ instead of this detail panel.

Where to find it

Open Compliance from the sidebar at iq.verinode.ai/compliance, scroll to the Compliance frameworks row, and click any framework's tile. That dispatches an in-page event that opens a modal titled with the framework's full name (for example "OSHA Hazard Communication (HazCom) Program"). Nothing separate to navigate to: it is the same page, same data, just a focused view on one framework.

If the row itself is empty, you have not forwarded or uploaded anything a framework can score yet. It 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."

The framework detail modal

The header line

At the top of the modal, one line of context: "N of M elements in place · X% inspection-ready. Forward or upload what you have and IQ scores each element. This is a completeness check, not a certification." The N and M are the count of elements at or above 80% complete versus the framework's total element count; the percentage is the weighted composite score, the same number shown on the tile you clicked.

The control list

Below the header, one row per required element (what the code calls a "control"), each with:

• A status dot: solid green when that element is at least 80% complete, amber when it has partial evidence (anywhere above 0% but under 80%), and a muted gray when there is no evidence on file at all.
• The element's label, in plain language, for example "A written Hazard Communication program is in place that names a program administrator and covers chemical inventory, Safety Data Sheet access, container labeling, and employee training."
• A subtitle pairing the element's section (its grouping, like "Written program," "Chemical inventory," "Safety Data Sheets," "Labeling," or "Training" for HazCom) with a plain status word: In place, Partial (N%), or Missing.

Elements are not weighted equally toward the top score (a framework's written program usually counts for more than, say, its device-storage requirement), but every row in this list displays its own completeness on its own terms, regardless of weight, so you can see exactly which single element is dragging the score down.

Drafting a starter written program with IQ

When a framework's core written-program element is the one showing as Missing or Partial, the modal shows a Draft a starter program with IQ button. Today that button appears for these frameworks specifically: HazCom, OSHA Lockout/Tagout, OSHA Permit-Required Confined Space, OSHA Fall Protection, OSHA Respiratory Protection, OSHA Hearing Conservation, and the Fleet and Driver Safety Program. For the rest of the catalog (OSHA recordkeeping, EPA Lead-Safe, insurance and COI completeness, carrier program audit readiness, IICRC firm standing, sell-side diligence readiness, heat illness prevention, the emergency action plan, and the PPE hazard assessment), this specific button is not wired up yet; the way to close those gaps today is forwarding or uploading the real document, described below.

1. 1Click Draft a starter program with IQ. The button label changes to "Drafting…" and disables while IQ writes.
2. 2IQ looks up the framework's required elements from the catalog and reads your operator profile (company name, state, and service mix) so the draft is not generic. It writes a plain-language program covering every element on the list, aimed at 500 to 800 words, with a named program-administrator role (never a specific person), a review schedule, and an acknowledgment section, opening with the same not-legal-advice disclaimer every draft carries.
3. 3The draft is saved as a new record in your policy library, filed under the safety-policy category tied to this framework (hazmat for HazCom, lockout/tagout, confined space, fall protection, and driving for fleet safety), marked active, with today as its effective date and a review date one year out.
4. 4Because that category is exactly the one this framework's written-program element reads from, the score updates immediately: the element flips from Missing or Partial to In place without any separate approval step.
5. 5The modal replaces the drafting buttons with a confirmation: "Starter program drafted: [title]," a line reminding you it is a starting point and not legal advice, to review it with a qualified safety professional, then download it for your records, and a Download PDF button.

For the three frameworks that fall back to a generic policy category instead of a dedicated one (OSHA Respiratory Protection, OSHA Hearing Conservation, and OSHA Bloodborne Pathogens), the drafter still writes and saves the program the same way, but a single "general" policy is deliberately not allowed to silently satisfy more than one program at once. That is intentional: a generic safety policy standing in for three different OSHA programs would be worth less to you at audit time than it looks.

If drafting fails, the modal shows the reason inline in red instead of the confirmation: an empty result from the model, a failed save, an unrecognized framework, or "Not authenticated" if your session lapsed. Nothing is saved when a draft fails; the buttons remain so you can try again.

The drafted document also shows up as a normal policy record in your Safety section (kind: policy), listed by category alongside anything you upload directly, and it can be re-downloaded any time from there using the same branded PDF export.

Uploading your own evidence

Whether or not the drafter button is available for a given framework, the modal always offers Upload evidence. Clicking it closes the framework panel and opens the same Add Data capture flow you would reach from the Compliance page header, so if you already have a written program, an SDS library, training rosters, audit reports, or a carrier COI sitting in your inbox or on your computer, you can forward or drop it in directly rather than starting from IQ's draft. See forwarding documents and connecting your data for the mechanics of getting documents in.

Behind the scenes, anything you forward or upload that plausibly touches a compliance program (its document type, or keywords like "hazard communication," "safety data sheet," "lockout," "bloodborne," "confined space," "fall protection," or "OSHA" in its text) gets read by IQ against every framework's element list at once, conservatively: it only credits an element when the document genuinely addresses it, and it is instructed to score low or skip an element entirely when it is not sure. That scoring never downgrades an element that already had stronger evidence on file, so a weaker follow-up document cannot accidentally undo a stronger one. This is what makes the framework list update as your real paperwork lands, without you filling in a single form.

The compliance binder PDF

At the bottom of every framework's modal, a second link sits below the drafter and upload buttons: Download compliance binder (all policies, PDF), subtitled "Your whole posture in one branded PDF for an audit." It is the same link no matter which framework's tile you opened the modal from, because the binder is not scoped to one framework, it is your whole posture.

Clicking it generates a fresh PDF on the spot (nothing is cached, so it always reflects your data as of that click) with:

• A cover page titled "Compliance Binder," your company name if you have one on file, and a "Framework readiness" section listing every framework in the catalog with its name, its score as a percentage, and how many elements are in place out of its total. If the framework catalog cannot load, this section reads "No compliance frameworks tracked yet." instead. The cover closes with the same completeness disclaimer as everywhere else: "This binder is a completeness record for inspection-readiness, not a certification of compliance. Review with a qualified safety professional."
• One full page per policy, pulled from every active safety-policy record you have across nine categories (General, PPE, Lockout/Tagout, Confined Space, Fall Protection, Heat Illness, Driving, Emergency Action, and Hazmat), sorted by category. Each policy's page prints its title, its effective and review dates when set, and its complete written content, with headers, bullet lists, and italics carried over from the source document.
• A page number and the same short disclaimer in the footer of every page.

The binder carries your company's own branding (logo and name) the same way every other branded PDF on the platform does. Only active policies are included; a policy you have marked inactive will not appear, and it will not count in the cover page's per-framework counts either since those numbers come from the live scoring engine, not from what happens to be in the PDF.

This is a different export from the single Download PDF button you see right after drafting a program: that one exports one policy at a time (handy right after you draft or upload something specific), while the binder exports everything you have, all at once, as the one document to hand an auditor.

What each empty state means

• Frameworks row is empty: no framework has any evidence at all yet. Nothing to click into. Forward or upload a written program, SDS library entry, or training record to get the first tile scored.
• A control shows Missing: no evidence on file for that specific element, or evidence that aged out past its roughly one-year validity window and was never refreshed.
• Drafter button absent for a framework: either that framework's core element is already at least Partial complete (so there is nothing to draft), or the framework's written-program control does not currently expose the one-click drafter, in which case forwarding or uploading the real document is the path.
• "No compliance frameworks tracked yet." on the binder cover: the framework catalog failed to load for that PDF generation; the policy pages that follow are unaffected.

Data sources

Related

• Compliance section overview
• Forwarding documents
• Connecting your data
• The decision workspace