Reading an exposure detail

What this page is

This is the detail view you land on when you click a single exposure. An exposure is a coverage gap that Verinode computes by comparing what you currently hold (a policy, an EMR, an endorsement) against what a carrier program, a policy floor, or a service line requires. It is not a record anyone typed in and it is not something you edit here: Verinode recalculates every exposure from your insurance policies, your active carrier-program memberships, and your service mix each time the page loads. This article covers what is on the detail page itself. For how exposures get computed in the first place and the three kinds Verinode currently derives, read Risk & Exposures: where it lives now first.

Verinode surfaces the gap and a suggested remediation. It does not bind a policy, file an endorsement, or negotiate your EMR paydown. That work, and the decision to do it, stays with you.

Where to find it

There is no standalone Risk section in the sidebar. Open Compliance and click into the Exposures tab (iq.verinode.ai/compliance?tab=exposures), then click any row in the exposures list. A saved /risk link redirects straight there.

The hero band

At the top of the detail page, the eyebrow reads Exposure next to a colored stance pill: BREACHING, EXPOSED, or DRIFT. Verinode uses a single five-state stance vocabulary (Hedged, Drift, Exposed, Breaching, Watching) across every compliance record so exposures, audits, and regulations read the same way; an exposure never lands in Hedged or Watching because a coverage gap is either present or it doesn't exist as a row at all.

• Breaching (red): a critical-severity exposure, for example an active carrier program with a required policy type missing entirely.
• Exposed (amber): a warning-severity exposure, coverage that exists but sits below a program's required threshold.
• Drift (muted): an informational-severity exposure, most often the endorsement-confirmation heuristic where Verinode is asking a question rather than asserting a gap.

Below the eyebrow, the title is the exposure's plain-language name (for example "Missing workers comp" or "EMR 1.31, commercial gate breached"), and the subtitle is Verinode's recommended next step for it, the same text that appears in the Remediation field further down.

To the right, four stats run in a 2x2 grid:

• Severity: the plain severity word, critical, warning, or info, colored to match the stance (red for critical, muted for the rest).
• Current: what you have on file right now, for example "Not on file" or an EMR value like "1.31." Shows a dash when nothing is on record.
• Required: the state you need to reach, for example "Active policy" or "<1.25 (commercial); <1.0 (preferred)." Always shown in the "needs attention" color, since by definition an open exposure hasn't reached this state yet.
• Required by: the source driving the requirement. If exactly one program or service line is behind it, its name is shown (for example "Liberty Mutual Preferred"). If more than one source drives the same gap, this reads as a count, for example "2 sources," rather than listing every name. Shows a dash when the exposure isn't tied to a named source (the EMR gate, for instance, is a general market-standard gate rather than one program's rule).

A Quick Survey button sits in the hero actions. It opens a one-question survey you can send to a teammate, asking them to weigh in on this item; it has nothing to do with resolving the exposure itself, it's the same quick-survey tool available from every entity detail page across the platform, for gathering a colleague's read before you act.

Exposure Overview (the Details tab)

This is the section named in the page itself, and it's where every field about the gap is spelled out in full:

• Kind: the underlying exposure type in plain words, shown with underscores replaced by spaces, for example "missing required policy," "emr commercial gate," or "coverage type missing." Verinode currently derives three kinds:

- Missing required policy: you're enrolled in a carrier program that requires an active policy type, most often general liability or workers' comp, that you don't currently hold as active. - EMR commercial gate: your workers' comp Experience Modification Rate has crossed the threshold most commercial carrier programs use to disqualify a contractor, read off your most recently expiring active workers' comp policy. - Coverage type missing: you run a service line, currently mold or biohazard work, that typically needs a specific endorsement on your general liability policy, and Verinode hasn't been able to confirm that endorsement from the policy data it has. This one is a heuristic prompt to check, not a confirmed gap, since Verinode hasn't parsed your certificate of insurance for endorsement language yet.

• Description: a full sentence naming exactly which policy, program, or service line triggered the flag. For example, for a missing policy: "Liberty Mutual Preferred requires an active workers comp policy. No active policy of this type is on file." For an EMR gate: "Workers' comp EMR 1.31 is above the 1.25 commercial-program gate. Most large-carrier programs disqualify at or above this threshold until EMR trends back down over 2-3 policy years."
• Current: what you actually have on file, spelled out the same way as the hero stat (for example "Not on file," "1.31," or "Endorsement not confirmed").
• Required: the state you need to reach (for example "Active policy," "<1.25 (commercial); <1.0 (preferred)," or an endorsement description like "pollution endorsement on general liability").
• Required by: only shown when at least one source is behind the requirement. Lists every program or service line by name, comma-separated, rather than the condensed count you see in the hero. For the EMR gate, this reads "commercial carrier programs" since that's a market-standard threshold, not one program's rule. For the coverage-endorsement heuristic, this lists the service line itself (for example "mold"), since the requirement traces to running that work rather than to a named carrier program.
• Remediation: only shown when Verinode has a concrete suggestion on file. This is the exact next step, not something Verinode does for you. Real examples: "Contact broker to bind a workers comp policy and upload the COI," "Request a loss run + work with the insurance-advisor on the 12-month pull-down plan," or "Confirm with broker that general liability includes a pollution endorsement. Upload the declaration page if available."

Open Tips tab

This tab only appears when Verinode has open, unresolved tips connected to this exposure, and its label carries a count badge when it does. Each tip shows a headline, an optional rationale explaining why Verinode flagged it, and an optional suggested action prefixed with an arrow. If there are no open tips for this exposure, the tab is hidden entirely rather than shown empty.

Findings tab

This tab surfaces any Decisions in your Feed that are linked back to this same exposure, again with a count badge and hidden entirely when there are none. Each linked item shows its action title and, when Verinode has priced it, a monthly cost-of-inaction figure underneath (for example "$1.2k/mo cost of inaction"). Clicking through takes you to that decision in the decision workspace; see The decision workspace and Acting on decisions for how to work a linked item once you're there.

Peer benchmarks

Below the tabs, a peer-compare panel shows how your compliance posture compares to other operators, using two metrics that apply to the exposure regardless of its specific kind:

• Compliance shield score: the same 0-100 posture score shown on the Compliance home, built from your audit pass history, regulation compliance, and exposure resolution together. Higher is better.
• Audit pass rate: the share of your completed audits that passed. Higher is better.

A scope switcher lets you compare against National peers or narrow to State peers in the same jurisdiction. Both metrics are blurred until you've contributed enough of your own data for a fair comparison, consistent with how every peer benchmark on the platform works, since Verinode never sells your data to carriers and only unlocks comparisons once a comparison is statistically meaningful. If there isn't enough peer data on file yet for either metric, that metric's row doesn't render.

Empty states

• If an exposure has no linked source (no program tied to it), the "Required by" hero stat and the Details "Required by" field both show a dash rather than blank space.
• If Verinode has no remediation suggestion recorded for the exposure, the Remediation field is omitted from the Details section entirely rather than shown with a dash.
• If there are no open tips, the Open Tips tab does not appear in the tab bar.
• If there are no linked decisions, the Findings tab does not appear in the tab bar.
• You cannot reach an exposure detail page with nothing to show: since exposures are derived, not stored, there's no such thing as an exposure detail page with a missing record. If the underlying gap closes (you bind the policy, your EMR trends back down, the endorsement gets confirmed), the exposure stops being generated and its row, along with its detail page, simply disappears from the Exposures tab on the next load.

Related reading

• Risk & Exposures: where it lives now
• The decision workspace
• Acting on decisions
• How benchmarks work
• Forwarding documents