Audits, scheduling, results, and findings

Audits are one of three record kinds inside Compliance, alongside Exposures and Regulations. An audit is any formal review of your operation, a carrier program audit (PSP, ASP, DRP), an insurance a…

8 min read·Updated July 13, 2026
On this page

What this covers

Audits are one of three record kinds inside Compliance, alongside Exposures and Regulations. An audit is any formal review of your operation, a carrier program audit (PSP, ASP, DRP), an insurance audit, an internal review, or an OSHA-style inspection, that has a scheduled or completed date and, once it runs, a result. Verinode reads audit events off documents you send in (an audit notice you forward, a scheduled-audit email, a completed audit report) and turns them into a record it tracks for you: when it is due, whether it is overdue, what it scored, and what it found.

This article covers the Next Audit tile on the Compliance home page, the Audits tab in the compliance card slider, and the audit detail card you land on when you open one, including how the countdown and overdue detection work, what the result score means, and how per-audit findings surface.

Verinode does not schedule audits for you and does not decide whether you pass one. It reads what carriers, auditors, and your own records tell it, tracks the dates, and surfaces the gap between where you stand and what is coming due, so you can act on it before it becomes a problem.

Where to find it

Open Compliance from the sidebar (/compliance). Compliance is one of Verinode's activation-gated sections: if you have not turned it on yet, you will land on an activation screen instead of the page described here.

On the Compliance home page:

  • The hero band at the top shows your Shield Score and, underneath it, an Audits Due stat, the count of audits scheduled in the next 30 days plus any that are overdue.
  • The Explore row includes a Next Audit tile (or Audits Overdue, see below), one of seven tiles in that row alongside Shield Score, Cross-Domain Stacks, Open Exposures, Regulations, Regulatory Autofeed, and Specialist Activity.
  • The Most recent row at the bottom of the page lists your latest compliance records across all three kinds, audits show up there too, sorted with the most urgent first.

Clicking the Next Audit tile, or an audit tile in Most recent, opens the compliance card slider directly on the Audits tab. The slider has five tabs across the top: Findings, Exposures, Audits, Regulations, Benchmarks. You can also land on the Audits tab directly by opening any audit record from elsewhere in the app.

Note

Compliance intelligence (audit result detail, findings, benchmarks) is gated to Premier membership. On Contributor and Executive tiers the section still renders in full layout, records are counted, but the scarce intelligence underneath is blurred with an upgrade prompt. If you are on a lower tier and see fewer of the numbers below, that is the paywall, not missing data.

The Next Audit tile

This tile answers one question: what is the next audit on your calendar, and how far out is it.

How the countdown is built. Verinode scans every audit event whose status is Scheduled or In progress and that has a scheduled date, and picks the one closest to today, whether that audit is still ahead of you or already past its date. If you have both an upcoming audit and an overdue one, the tile favors whichever is numerically closer to today.

What the tile shows normally. The label reads Next Audit, the value is the day count (for example "12d"), and the sub-line names the audit, using its kind and, when known, the auditor, for example "Carrier Program audit" or a similar kind label followed by the auditor's name. If nothing is scheduled at all, the tile falls back to a plain count of audits on file, "N total on file."

When an audit is overdue. The moment the nearest scheduled or in-progress audit's date has passed, the tile switches identity: the label becomes Audits Overdue, the value becomes the count of overdue audits (not days), and the sub-line reads "N audit(s) past scheduled date." The tile's accent also switches to the alert color. This is Verinode's overdue detection: it is not a separate flag you set, it is computed every time the page loads by comparing each scheduled or in-progress audit's date against right now.

Distribution preview. Underneath the number, the tile draws a small distribution graphic built from three buckets: audits overdue, audits due in the next 30 days, and everything else on file. An empty bucket simply does not appear in the graphic.

Clicking the tile opens the Audits tab in the compliance slider.

Tip

The hero band's Audits Due stat (in the top-of-page summary) is a superset of what the Next Audit tile shows: it adds together audits due in the next 30 days and audits already overdue into one number, so you can see the total workload at a glance before drilling into which specific audit is closest.

The Audits tab

Open the Audits tab from the Next Audit tile, from Most recent, or by clicking the Audits pill inside the slider (its accent is violet). It lists every audit event on file for your operation as a set of cards.

Each card shows:

  • Title, built from the audit kind (Carrier Program, Insurance, Internal, and so on, each word capitalized) followed by the auditor's name when Verinode has it, for example "Carrier Program audit, [Auditor Name]."
  • Status label, one of:

- Overdue Nd, scheduled or in-progress, past its date - Nd out, scheduled or in-progress, still ahead (shown once the audit is inside 60 days of today; further out it still reads the day count) - Scheduled, scheduled with no computed distance yet - Completed or Completed (N%), once a result score is on file - Canceled, if the audit was called off

Empty state. If you have no audits on file yet, the tab reads: "No audits on file. Upload an audit notice via Add Data to schedule one." Use the Add Data control to forward or upload the notice; Verinode reads it and creates the audit event.

The audit detail card

Clicking any audit card opens its detail view. The top of the card (the hero) shows four stats that change meaning depending on whether the audit has happened yet:

  • Status, the humanized status: Scheduled, In progress, In review, Completed, or Canceled. This stat also carries the audit's overall stance color (see below).
  • Scheduled, the scheduled date, with a delta badge next to it while the audit is not yet completed: "Nd overdue" in red if the date has passed, or "Nd out" if it is still ahead.
  • Score (once completed) or Auditor (before completion). Once an audit is marked Completed, this stat switches to showing the result score as a percentage, colored green at 90% and above, amber from 75% up to 90%, and red below 75%. Before completion, it shows the auditor's name if known, or a dash.
  • Kind, the humanized audit kind (Carrier Program, Insurance, Internal, and so on).

Below the hero, the Audit Overview section lists every field Verinode has for the record:

  • Kind
  • Auditor, when known
  • Scope, a free-text description of what the audit covers, when provided
  • Scheduled, the date
  • Completed, the date, once the audit has closed
  • Result, the score as a percentage, once completed
  • Notes, any free-text notes attached to the audit event

Findings

If the audit has come back with specific findings, cited deficiencies or observations the auditor made, they appear in a Findings section beneath the overview. Each finding shows:

  • Its description (what was found)
  • A severity tag: critical, major, or a lower tier, styled in red, amber, or muted respectively
  • A recommendation, when the auditor or Verinode's synthesis gave one
  • A due date, when remediation has a deadline, and a closed date if it has already been resolved

This section only appears when the audit actually has findings attached. A clean audit, or one still awaiting its result, simply won't show it.

Open Tips and Findings (decisions) tabs

Two further tabs can appear on the detail card, each hidden when empty:

  • Open Tips, short IQ-generated pointers tied to this specific audit, each with a headline, the reasoning behind it, and a suggested next action.
  • Findings, a distinct tab from the audit's own findings list above, this one surfaces any Verinode decisions (the platform's unified recommendation type) linked to this audit record, each with its action title and, where there is a quantifiable cost of leaving it unaddressed, a dollar figure labeled "cost of inaction" per month.

Both tabs carry a badge showing their count and disappear entirely when there is nothing to show, so an audit with no open tips or linked decisions has a shorter tab bar.

Stance and the shield score

Every audit, like every exposure and regulation in Compliance, is scored into one of five stances: Hedged, Drift, Exposed, Breaching, or Watching. This is the same vocabulary used across Compliance and Safety, so an operator moving between the two reads the same posture language. The stance drives the color you see on the Status stat and the pill in the card header, an audit trending toward Breaching (badly overdue, or completed with a low score) reads in the alert color, while a Hedged audit (on schedule, or completed with a strong score) reads in the positive color.

The Shield Score shown at the top of the Compliance home page is a separate, broader number: it blends training, insurance, carrier-program, regulatory, and safety posture together into one 0 to 100 figure, of which your audit history (recent completed audits scoring 80% or higher counting as passes) is one input among several. A strong Shield Score reflects good standing across all of those domains, not audits alone.

Peer comparison

Where your membership tier includes it, the audit's benchmarks panel compares your audit pass rate against peers in your cohort. Verinode never sells or exposes your underlying operator data to carriers, and it never shows you which specific peer operators sit behind a benchmark, only the aggregate comparison. If your cohort has not yet cleared the minimum size Verinode requires to protect anonymity, the peer comparison simply does not display for that metric yet.

Was this helpful?