Audits: the overview

The short version

"Audits" is not one screen in Verinode. It is one word that covers two related but different things:

1. Tracked audit events, the carrier program audits, TPA reviews, and regulatory inspections that happen to your business from the outside, scheduled, in progress, or completed, with a score and findings when they wrap. These live inside Compliance.
2. Self-audits, the checklists and rubrics you run on yourself, on a closed claim, a job, a crew, before anyone from a carrier or regulator ever shows up. These live inside Forms, on their own Audits tab.

If you type or click /audits, Verinode sends you to the first of these: /compliance?tab=audits, the Compliance section with its Audits tab already open. That redirect exists because Audits used to be its own page and got folded into Compliance as part of a broader rollout. The rest of this article walks through both faces, what each number and empty state means, and how the two connect.

Face 1: tracked audit events, inside Compliance

Where to find it

Open Compliance from the Compliance section in the sidebar (alongside Certifications and Safety), at /compliance. The page opens on the Compliance home. Audits show up in three places on that home before you ever open the Audits tab itself:

• The Compliance Posture hero at the top, which folds an audit signal into its subtext when nothing more urgent is happening, for example "Carrier Program audit in 12 days."
• Two hero side-stats: Critical Open (open critical exposures) and Audits Due, which sums audits scheduled in the next 30 days plus any overdue ones. Its sub-line reads "N Overdue" when something has slipped past its scheduled date, "In Next 30 Days" when something is coming up but nothing is overdue, or "No Audits Scheduled" when the calendar is clear.
• The Explore row, which carries a dedicated audit tile (described below).
• The Most recent row, a horizontal strip of tiles mixing exposures, audits, and regulations, sorted with critical items first and soonest due-dates next.

The Audits tile in Explore

In the Explore row, the audit tile's label and value change with what is actually happening:

• If any audits are overdue, the tile is labeled Audits Overdue and its value is the overdue count, with the sub-line reading "N audit(s) past scheduled date."
• Otherwise, if there is a next scheduled audit, the tile is labeled Next Audit and its value is the day count until it (e.g. "12d"), or "Nd past" if it slipped through without the overdue count catching it. The sub-line names the audit, for example "Carrier Program audit."
• If nothing is scheduled at all, the tile just reads Audits with the count of audits due in the next 30 days as its value, and a sub-line falling back to "N total on file."

The tile carries a small distribution strip underneath (overdue vs. due-within-30-days vs. everything else on file), so you can see at a glance how the load breaks down before opening the full list. Clicking the tile opens the Audits tab of the Compliance card slider.

What counts as a tracked audit event

Every row here is a real audit event: a carrier program audit, a TPA review, a state or federal regulatory inspection, anything scheduled against you or already run. Each one carries:

• An audit kind (e.g. "Carrier Program," "OSHA"), title-cased from however it was captured.
• An auditor name, when known.
• A scope note, when one was captured.
• A scheduled date, and a completed date once it has happened.
• A result score (0 to 100%) once it is scored.
• A status: Scheduled, In progress, Completed, or Canceled.

Verinode turns that into a plain-language status label depending on where the audit sits:

• Still ahead and more than 60 days out: no urgency badge, just the days-out count.
• Within 60 days: "Nd out."
• Within 14 days: same "Nd out," but the record is flagged as a warning.
• Past its scheduled date and not completed: "Overdue Nd," flagged critical.
• Completed with a score: "Completed (N%)." A score under 75% is flagged as a warning even though the audit itself is done, since a weak result usually means work still to do.
• Canceled: "Canceled."

Opening the Audits tab

Click the Audits tile, or "Audits Due" / "Audits Overdue," and the Compliance card slider opens on its Audits tab (one of five: Findings, Exposures, Audits, Regulations, Benchmarks). Each row shows the audit's title, its status label in the right-hand column (colored red for critical, amber for warning, muted otherwise), and a subtitle line showing the scope or, if there is none, the same status text. Tap a row to open its full detail card.

Empty state. If you have no audit events on file at all, the tab reads: "No audits on file. Upload an audit notice via Add Data to schedule one." Use the Add Data button in the page header to forward or upload the notice; Verinode extracts the kind, auditor, and scheduled date and creates the tracked event for you.

Audit detail card

Opening an audit shows:

• Status, Scheduled date (with a days-out or days-overdue delta while it is still pending), the Auditor name (or, once completed, the Score in its place), and the audit Kind.
• An overview section repeating the kind, auditor, scope, scheduled and completed dates, and any result score or notes captured on the record.
• A Findings section, when the audit produced any, one row per finding with its severity (critical, major, or a neutral tier), a recommendation where one exists, and a remediation due date, marked closed once you have resolved it.

From there the card carries the same Findings, Benchmarks, and Decisions experience every compliance record shares, so an audit finding can turn into a decision on your feed the same way an exposure or a regulation change does.

The peer number: Audit pass rate

Inside the Benchmarks tab of the same slider, Audit pass rate sits alongside Compliance shield score and Framework completeness. It shows your value next to a peer or industry reference figure once enough contributing operators exist to support a comparison; until then it reads as unavailable rather than showing a number built on too thin a sample. See how benchmarks work for why that floor exists and reading a benchmark for how to read the comparison itself.

Face 2: self-audits, inside Forms

Where to find it

Open Forms from the My Data section in the sidebar (alongside Vault and Connect), at /forms. Forms has three tabs across the top: Surveys, Audits, and Reviews. Switch to Audits. This is a genuinely separate list from the Compliance Audits tab: nothing you run here writes a pii.audit_events row, and nothing scheduled in Compliance shows up here. A self-audit is a form you fill out yourself, on your own schedule, about your own work.

What a self-audit is

A self-audit is a structured checklist or scoring rubric you run against a job, a crew, or a closed claim, before an outside party does. Verinode ships two ready-made templates on the Audits tab:

• Internal Mock Audit Run Sheet (about 25 minutes): a walk-through dry run of a carrier audit. You pick a recently closed claim and work through pre-audit setup, documentation compliance, procedural compliance, customer communication, billing integrity, and action items, then sign off as the Project Manager. It targets a 90% pass rate. The idea is to find what a real carrier auditor would flag, on your own terms, with time to fix it.
• Job Quality Audit (about 12 minutes): a QA rubric you run against a job, crew, or process, distinct from the carrier-prep run sheet above. It scores workmanship, documentation, safety on site, and customer experience, then closes with action items and a Project Manager sign-off. It targets an 85% pass rate.

(A third template, 1-on-1 Performance Review, uses the same underlying self-audit form shape but lives on the Reviews tab instead, since it scores a person, not a job or a claim.)

Running one

1. 1Open Forms from the sidebar and switch to the Audits tab.
2. 2Click + Add Audit in the page header.
3. 3Pick a template: Internal Mock Audit Run Sheet or Job Quality Audit.
4. 4Work through the sections in order, checkboxes, ratings, and short text answers, section by section (setup, documentation, procedure, and so on through action items).
5. 5Sign off at the end. Signature is required; this is what makes the finished form a real record, not a draft.

Every question you check off or rate rolls into the template's scoring rule, either a percentage of checkboxes passed or an average of the rating questions, compared against that template's target pass rate. The two open-ended "action items" questions near the end (top items to fix, who needs a coaching note) are where the audit turns into something your team can act on immediately, before you even close the form.

What the Audits tab shows

The Audits tab reuses the same hero-plus-Explore-plus-recent layout as the rest of Forms, with its labels swapped to audit vocabulary instead of survey vocabulary:

• Active tile: audits currently open (in draft or in progress), with its sub-line reading "N% Pass Rate" once you have runs to measure, or "Run Your First Audit" when the tab is empty.
• Audit Runs tile (the Responses tile's audit-tab label): the count of completed run-throughs, with an average score once more than one exists, or "No Runs Yet" before your first one.
• Templates tile: the count of pre-built audit sheets available (Internal Mock Audit Run Sheet and Job Quality Audit), labeled "Pre-Built Audit Sheets."
• Closed tile: audits you have finished, labeled "Historical Audits" once you have any, or "Completed Audits Land Here" before you do.

Below that, an Upcoming row lists any audits you have set to repeat on a schedule (a quarterly Job Quality Audit on a given crew, for instance), and a Most recent row lists individually run audits with their type label, pass percentage, and how long ago they ran.

Empty state. With nothing run yet, the Most recent row reads: "Recently asked surveys appear here as you send them. Use a template from the Templates tile or click "+ Add Survey" to ask your first question." (This copy is shared with the Surveys tab; on Audits, read "send them" as "run them" and "+ Add Survey" as "+ Add Audit.")

How the two faces connect

They are deliberately separate lists, but they point at the same goal: fewer surprises when a real carrier auditor or regulator shows up.

• A tracked audit event in Compliance is something happening to you, on a schedule you often do not fully control, with a result you find out after the fact.
• A self-audit in Forms is something you run on yourself, whenever you want, specifically to catch what a tracked audit would flag, before it does.

The natural sequence: when Compliance shows a Next Audit counting down, run an Internal Mock Audit Run Sheet against a comparable recent claim first. Its findings and action items give your team something concrete to fix before the real thing lands as a tracked event with its own score.

Related reading

• How benchmarks work: how the Audit pass rate comparison figure is built and gated.
• Reading a benchmark: how to read any peer or industry comparison in Verinode, including the one on the Audits benchmark tab.
• Forwarding documents: how Add Data turns an emailed or uploaded audit notice into a tracked Compliance audit event.
• Connecting your data: the broader Connect setup that feeds Compliance and every other section.
• The decision workspace: what happens when an audit finding turns into a decision on your feed.
• The feed: where compliance decisions, including audit-driven ones, surface day to day.