The Compliance detail slider, five tabs

What the Compliance slider is

Compliance is where Verinode reads your insurance, your audits, your carrier-program requirements, and the regulations that apply to your state and service mix, and tells you where you actually stand. The Compliance detail slider is the drill-in overlay that holds all of that: five swipeable cards, one per tab, each a real record list you can open into. Verinode does not file paperwork or make a compliance call for you. It reads what's flowed in from your policies, your audit history, and the regulatory catalog, and lays the posture out so you can decide what to close first.

Where to find it

Open Compliance from the sidebar at iq.verinode.ai/compliance. The page itself is flat: a Shield Score band at the top, a Take Action row, and an Explore row of tiles beneath it. None of those tiles are the slider, they're the entry points into it. Tap any of the following and the slider opens on the matching tab:

• Shield Score and Specialist Activity tiles open Findings
• Cross-Domain Stacks tile opens Findings
• Open Exposures tile opens Exposures
• Next Audit (or Audits Overdue, or plain Audits, depending on your posture) opens Audits
• Regulations and Regulatory Autofeed tiles open Regulations
• The Shield Score's benchmark link opens Benchmarks

A row in the "Most recent" list, or a Take Action recommendation, opens the slider straight into that specific record's detail instead of the tab overview.

Once it's open, the five tab-cards sit side by side on one horizontal canvas:

1. 1Switch tabs by dragging the canvas left or right, swiping on a touch screen, using the floating left/right arrows that appear at the edges of the screen, or clicking a dot in the small navigator pinned to the bottom of the overlay.
2. 2Open a record by tapping any row in a tab's list. The header cross-fades into a breadcrumb (tab name, then the record's title, then a position count like "3/12"), and the same floating arrows now step between records instead of tabs.
3. 3Step back with the breadcrumb's tab-name link, or close entirely with the X in the top right. Escape does the same: one press steps out of a drilled record, a second press closes the overlay. Clicking the dimmed backdrop also closes it.

The header also carries the same Add Data control you see on the page itself, so you can forward or upload a document without leaving the slider. See connecting your data and forwarding documents for how that pipeline works.

Findings

What it is. Findings is your compliance decision queue: the cross-domain stacks Verinode's nightly compliance-synthesizer has assembled, plus the individual decisions tagged to compliance.

Cross-domain stacks. A stack is what happens when several compliance signals point at one root cause across domains (an insurance gap, a scheduled audit, and a regulation adoption all traced back to the same underlying issue, for example). When one or more are open, the tab leads with a header reading the count of stacks this sweep, then a card per stack:

• An eyebrow reading Cross-Domain Stack, and, when Verinode can size it, a monthly cost-of-inaction figure next to it.
• A count of linked signals in the top right corner.
• A bold headline and a plain-language synthesis paragraph explaining what's connected.
• An italic Root cause line, when one has been identified.
• An Action sequence: a numbered list of steps, each tagged with a horizon chip (30d, 60d, or 90d) and a specialist chip naming who handles it (Insurance, Regulatory, Cert Renewal, OSHA, Contract, and similar routing labels), followed by the action itself in plain language.
• A footer with four controls: Act (opens the full decision workspace for that stack, see the decision workspace), Not now (parks it and hides the card without discarding the underlying signal), Ignore (dismisses it), and Acknowledge with note (logs a note while marking it handled).

The decision grid. Below any stacks, the tab shows an eyebrow counting how many decisions are open ("N decisions to review"), then a grid of finding tiles, the same tile style used on every section's Findings tab. Tapping a tile drills into that decision's own card, with the floating arrows now paging between the loaded set of your most recent compliance-tagged decisions. Close returns you to the grid.

Empty state. When there are no open cross-domain stacks, that block simply doesn't render, no placeholder text. When there are also no open compliance decisions, the tab reads:

"No decisions for compliance right now. As your agent finds patterns, they'll appear here."

Exposures

What it is. An exposure isn't something you entered, it's a gap Verinode computes between the coverage or status you currently hold and what an active carrier program, contract clause, or license actually requires. Typical exposure kinds: an insurance sub-limit sitting below a program's required floor, a required policy that isn't on file at all, an eligibility gate tied to a commercial or EMR program, or a coverage type that's missing outright.

The list. Each row shows the exposure's title in bold, with a second line naming the source or sources requiring it ("Required by [program name]") when that's known; if it isn't, the second line repeats the status word instead. The right side carries a status chip in one of three states:

• Breaching (red), the most severe: active program work is running without coverage that's actually required.
• Exposed (amber): coverage sits below a required threshold, not yet actively breaching.
• Drift (neutral): a soft gap worth tightening before it hardens into something worse.

Opening a record. The detail card's stat row shows Severity, Current (the state you're actually in), Required (the state the program or contract needs), and Required by (who's requiring it, or a count of sources when there's more than one). Below that, an Exposure Overview panel repeats the exposure's kind in plain words, its description, current and required state, the requiring source(s), and, when Verinode has one, a suggested remediation action.

Empty state.

"No exposures detected, coverage matches active program requirements."

Audits

What it is. Audits tracks every audit event on file, scheduled, in progress, or completed, whether it's a carrier program review, a state licensing audit, an OSHA inspection, or anything else your operation goes through.

The list. Each row's title reads as the audit kind in title case (for example, General Liability) followed by "audit," with the auditor's name appended when it's known. The second line shows the audit's scope when one is set, or repeats the status word when it isn't. The right side carries a status label:

• Scheduled, the default, before a date or once one's set more than 60 days out.
• "Nd out" in neutral gray once the date is more than 14 days away but inside 60.
• "Nd out" in amber once you're inside a 14-day prep window.
• "Overdue Nd" in red once the scheduled date has passed with no result logged.
• "Completed", or "Completed (X%)" when a result score was recorded, amber if that score is under 75%, neutral at 75% or above.
• "Canceled" for canceled audits.

Opening a record. The stat row shows Status, Scheduled (with a delta chip reading how many days overdue or out, for anything not yet completed), a third stat that's either the completed Score (colored green at 90% or above, neutral in the mid-70s to high-80s, red under 75%) or the Auditor name while the audit is still upcoming, and the audit Kind in title case. The Audit Overview panel repeats kind, auditor, scope, scheduled and completed dates, the result score, and any notes. When the audit has structured findings attached, a separate Findings panel lists each one: its description, a severity chip (Critical, Major, or a muted default for anything milder), a recommendation line when present, and a due date with a closed date once it's been remediated.

Empty state.

"No audits on file. Upload an audit notice via Add Data to schedule one."

Regulations

What it is. Regulations joins Verinode's regulatory catalog, filtered to the rules that actually apply to your state and service mix, against your own adoption status for each one. Many of these arrive automatically: a weekly regulatory-scan feed watches for new state and federal rules and adds them for you.

The list. Each row's title is the regulation's own title, with a second line combining its publishing source, its jurisdiction (federal, state, or local), and the state code when one applies. Rows pulled in by the automatic feed carry a small badge: newly landed ones read NEW · Autofeed in copper, and once they've aged past that window the badge simplifies to a plain Autofeed chip, so you can still tell where the row came from. Regulations added any other way show no badge at all.

On the right, the status reads as a countdown, "Nd to effective," turning amber once you're inside 30 days of the rule taking effect. Once it's live, the status becomes one of: Compliant, Exempt, In progress (amber), or "Effective, adopt" in red, meaning the rule is already in force and adoption hasn't started.

Opening a record. The stat row shows Status, Effective (the date, with a delta chip reading days in effect or days out), Jurisdiction with the state appended when relevant, and Source. The Regulation Overview panel repeats source, jurisdiction, category, effective date, a plain-language summary, the action required, your operator status, and a link out to the regulator's own source page when one was published.

Empty state.

"No applicable regulations in the catalog for your state + service mix."

Benchmarks

What it is. Benchmarks is the one tab that isn't a record list, it's a flat comparison panel for two portfolio-level metrics: Compliance shield score (the blend of training, insurance, carrier standing, regulatory adoption, and safety data that produces the Shield Score you see on the Compliance home page) and Audit pass rate.

The layout. Each metric gets its own block with three columns:

• Peer, your peer cohort's value for that metric, rounded to a whole percent, or a dash when it isn't available yet. Underneath, once a value shows, a small cohort figure indicates roughly how many peer operators are behind that comparison.
• Research, the published research benchmark for the same metric, with the publisher's name beneath it when known.
• Scope, the comparison group the peer figure is drawn from (national or state), or a dash if that hasn't resolved.

A footnote clarifies the logic: a peer-relative number only appears once enough similarly sized peer operators have contributed data to compare safely; until then, the tab shows the published research benchmark instead. This is the same anonymization floor every peer comparison on Verinode respects, see how benchmarks work and reading a benchmark for the general mechanism, and benchmarks overview for how this fits the rest of the platform. Verinode never sells your data to carriers, and every peer figure you see here is aggregated across contributing operators, never traceable back to any one of them.

Data sources