Tracking carrier and program audits

What this covers

An audit, in Verinode's compliance model, is any formal review of your operation: a carrier program review (the kind carriers call a PSP, ASP, or DRP audit depending on the program), an OSHA jobsite inspection, a state licensing audit, or an internal LEAN or ISO review. Every one of those lands in the same place: the Compliance page, under the Audits tab, as a record of what is scheduled, what is in progress, what has been completed, and what is overdue.

Verinode does not schedule or file your audits. It reads the audit notices, carrier correspondence, and audit reports you upload or forward, and turns them into a countdown, a status, and, once results are in, a findings list you can work from. You decide what to do with an overdue or upcoming audit; Verinode's job is to make sure it never gets buried in an inbox.

Where to find it

Open Compliance from the sidebar, under the Compliance section (alongside Certifications and Safety), at iq.verinode.ai/compliance. If you land on an old /audits link, it redirects straight to Compliance with the Audits tab already open.

Audits show up in three places on that page:

• The Compliance Posture hero panel at the top, where an Audits Due figure sits beside your Shield Score.
• The Explore row, in a tile that reads Next Audit or Audits Overdue depending on where you stand.
• The Most recent row at the bottom, where any audit due soon or newly logged appears as its own tile.

Clicking any of these opens the same place: the Audits tab inside the Compliance detail deck, a violet-accented tab alongside Findings, Exposures, Regulations, and Benchmarks. From there, clicking an individual audit opens its full detail page.

The Compliance Posture hero

What it is. The panel at the top of the Compliance page leads with your Shield Score, a 0 to 100 read on your overall compliance posture built from training, insurance, carrier, regulatory, and safety signals together. It carries a pill next to it (for example, "78 Shield Score") tinted green when the score is strong, amber when it needs attention, and copper red when it needs action now.

Below the score, a line of context adjusts to whatever is most pressing:

• If nothing has flowed in yet, it prompts you to add data so exposures, audits, and regulations can start populating.
• If you have a critical exposure open (a coverage gap, for example), that takes priority in the message.
• Otherwise, if an audit is coming up, it names it directly, for example "Carrier Program audit in 12 days."
• If none of the above apply, it falls back to how many regulations are tracked for your jurisdiction.

Audits Due. Beside the score, a secondary stat reads Audits Due, the sum of audits scheduled in the next 30 days plus any that are already overdue. Its subtext tells you which situation you are in: a count of overdue audits if any exist, "In Next 30 Days" if none are overdue but something is coming, or "No Audits Scheduled" if the audit calendar is clear.

The Next Audit / Audits Overdue tile

This is the tile in the Explore row that answers "when is my next audit, and am I already late on one." Its label and value change depending on your situation:

• If any audit is overdue, the tile's label switches to Audits Overdue, the value is the count of audits past their scheduled date, and the subtext reads how many audits are past their scheduled date. The tile turns copper.
• If nothing is overdue but an audit is scheduled, the label reads Next Audit, and the value is a day count, for example "9d" if it is nine days out. The subtext names the audit if Verinode has enough to identify it, or otherwise notes it is scheduled in the next 30 days. The tile turns amber inside 14 days, teal further out.
• If no audit has a date on file at all, the label reads Audits, the value falls back to the count scheduled in the next 30 days, and the tile turns green.

Underneath the number, a small distribution bar breaks your audits into three buckets: overdue, due in the next 30 days, and everything else on file, so you can see the shape of your audit calendar at a glance, not just the next date.

Clicking this tile opens the Audits tab in the detail deck, the same place the Most recent tile and the hero's Audits Due figure lead to.

Carrier program audits (PSP, ASP, DRP)

Not every audit in the list is the same kind. Verinode tracks several, and the kind is what tells you whether you are looking at a carrier relationship or a regulator relationship:

• Carrier program audits (referred to elsewhere as PSP, ASP, or DRP audits depending on the carrier, for example State Farm's Preferred Service Program, Travelers' Approved Service Program, or Allstate's Direct Repair Program) review whether your operation still meets that carrier's network requirements: documentation, insurance, response times, and quality standards.
• OSHA audits review jobsite safety against federal recordkeeping and inspection standards.
• State audits cover your state contractor licensing.
• Internal audits (including LEAN and ISO reviews) are your own quality-management cycles.
• Financial audits cover your books.

Each audit record carries a Kind field and, where known, an Auditor name (for example, a specific carrier's compliance department or a state licensing board) and a Scope (for example, "Annual program review" for a carrier audit, or the specific federal standard for an OSHA inspection).

Carrier program audits are also the reason two specialist agents exist in the compliance roster: one focused on carrier program requirements and prep, and one that runs a mock audit against your current documentation, incident log, policy library, and certification stack to surface the findings a real auditor would raise today, before the real one arrives. The Specialist Activity tile in the Explore row shows how many of the compliance specialists on standby have actually engaged with your data in the last 30 days.

Scheduled, in-flight, and completed status

Every audit record moves through one of four states, and each one reads differently across the platform:

• Scheduled, a date is on the calendar and nothing else has happened yet. This is the default state for a newly logged audit.
• In progress, the audit is actively underway.
• Completed, the audit has concluded, and, once a score is in, the record shows a result percentage.
• Canceled, the audit was called off.

On the Audits tab list and on the Most recent tile, the status reads a little differently depending on timing, so you get the countdown along with the state:

• A scheduled audit due soon shows the day count instead of the word "Scheduled," for example "9d out."
• A scheduled audit whose date has passed with no result shows "Overdue," with the number of days past due.
• A completed audit shows "Completed" or, once scored, "Completed (92%)."
• A canceled audit shows "Canceled."

On the full audit detail page, the Status field always shows the plain state (Scheduled, In progress, Completed, or Canceled), and a separate Scheduled field carries the date itself with a day-count badge next to it (for example "12d overdue" or "9d out") whenever the audit has not yet completed. A fourth field does double duty: before the audit runs, it shows the Auditor; once the audit is complete, it swaps to the Score, colored green at 90% or above, neutral in the mid-70s to high-80s, and red below that.

Opening the Audits tab

Click the Audits tile, the Most recent tile, or the Audits Due figure and the Compliance detail deck opens to the Audits tab. It lists every audit on file, most severe and soonest-due first, each row showing the audit's title, its status line, and a status badge colored red for critical (overdue), amber for a warning (due inside 14 days, or a completed score under 75%), or neutral gray otherwise.

If nothing is on file, the tab reads: "No audits on file. Upload an audit notice via Add Data to schedule one."

Click any row to open the audit's own detail page.

Reading a single audit's detail page

Open any audit and the top of the page carries an eyebrow reading "Audit" next to a stance pill: Hedged, Drift, Exposed, Breaching, or Watching. This is the same five-word posture vocabulary Verinode uses across compliance, safety, and certifications, and for audits it reads roughly like this:

• Hedged, passed with a strong score, or scheduled far enough out (more than 60 days) that nothing needs attention yet.
• Drift, passed but with open findings still to close, or inside the 60-day prep window with time to work through it calmly.
• Exposed, scored below a comfortable passing mark, or inside 14 days of the audit date with prep still incomplete.
• Breaching, the scheduled date has passed with no result logged.
• Watching, no date has been logged yet, so there is nothing to count down to.

Below the pill, the page names a specific next step (for example, "Start the readiness walkthrough against the template" during the healthy prep window, or "Escalate: audit window missed, notify auditor and schedule" once overdue), followed by the four hero stats (Status, Scheduled, Auditor or Score, Kind) described above.

Audit Overview. The details section repeats the Kind, Auditor, and Scope, then the Scheduled and (once it exists) Completed date, the Result percentage, and any Notes logged against the audit.

Findings. When an audit has come back with specific findings attached, they list below the overview: each finding's description, a severity tag (critical, major, or a lighter tag for anything else), a recommendation where one exists, and, if remediation has a due date, that date alongside a closed date once you have resolved it.

Open Tips. A separate tab (only shown when tips exist, with a count badge) surfaces short, specific pointers tied to this audit, each with a headline, the reasoning behind it, and a suggested action.

Findings (linked decisions). A second tab, also count-badged and hidden when empty, shows any Verinode decision generated from this audit, with its dollar cost of inaction when one applies. See acting on decisions for how to work a decision once you open it, and the feed for where these first surface as they are generated.

1. 1Open Compliance from the sidebar, or click the Audits Due or Next Audit / Audits Overdue figure from wherever you saw it (the home page hero, an Explore tile, or a Most recent tile).
2. 2On the Audits tab, scan for anything red (overdue) or amber (due inside 14 days) first.
3. 3Open the audit and read its stance pill and next-step line, then check the Audit Overview for the auditor, scope, and any notes already logged.
4. 4If the audit is a carrier program review and it is inside the prep window, run the audit-prep specialist against your current documentation before the real auditor arrives.
5. 5If findings already exist from a completed audit, work through them from the Findings section, prioritizing anything tagged critical.

Peer comparison

The Benchmarks tab of the same Compliance deck carries an Audit pass rate figure alongside your Shield Score, shown against a peer figure when Verinode has a large enough same-size cohort to report one reliably, and against a broader research figure otherwise. See how benchmarks work and reading a benchmark for how Verinode builds and gates these comparisons, and benchmarks overview for how audit pass rate sits alongside every other metric Verinode tracks for you. As with every benchmark on the platform, your audit history is never sold to carriers; it only ever comes back to you as an anonymized comparison.

Getting audits into Verinode

Audits arrive the same way most compliance data does: you upload the audit notice or report through Add Data, or you set up auto-forward so future audit notices land automatically. See forwarding documents and connecting your data for the mechanics of both paths. If your compliance record set is empty entirely, the Take Action row on the Compliance page prompts you toward the fastest three moves, one of which is exactly this: forward an audit-notice or regulator email so future notices land here without you having to think about it again.

Best-practice example

Say the Explore row shows Audits Overdue: 1, with a subtext reading one audit past its scheduled date. Opening the Audits tab, the row is tagged critical. Its detail page shows a Breaching stance, a Carrier Program kind, and a next step to escalate: notify the auditor and reschedule. Rather than letting it sit, you reschedule with the carrier that day, and Verinode's countdown resets to a fresh scheduled date, with the healthy 60-day prep window now open. From there, the audit-prep specialist runs a mock pass against your current documentation so any findings surface before the real auditor's visit, not during it.

Data sources