How Safety reads a record: the stance engine

What the stance engine is

Click any row on the All Safety tab, on the Exposure tab, or on a decision inside Findings, and you land on the same kind of screen: a single record's detail card. At the top of that card sits a colored pill next to the record's kind label. That pill is the output of the safety stance engine, a small piece of logic that reads one record (an incident, a safety policy, or an insurance certificate of insurance) plus what Verinode knows about your team and your peer network, and picks one of five words to describe where that record stands right now.

Verinode does not grade your safety program or decide what you should do about a given record. The stance engine reads the dates, statuses, and numbers already on file, compares them against fixed regulatory and carrier-driven thresholds (and, where a peer figure exists, against the network), and writes three short lines under the pill: what to do, what you gain by doing it, and what happens if you don't. You decide whether and when to act.

This article covers the record-level detail card only, the one you land on after clicking through from a list. For the rollup views that sit above it, see The Safety home: hero KPIs and the Explore tiles, Standing tab: where you stand vs OSHA and peers, Exposure tab: capacity at risk this week, and All Safety tab: the unified records list.

Where to find it

Open Safety from the sidebar, at iq.verinode.ai/safety. From any of the five tabs (Findings, All Safety, Standing, Exposure, Benchmarks), clicking a row that represents an incident, a safety policy, or an insurance policy opens that record's detail card as an overlay on top of the page.

The pill: five stances

Every record shows one of five words in the eyebrow pill, next to the record's kind label (Incident, Policy, or Insurance):

• Healthy (Deere Green): nothing expired, nothing overdue, and, where a peer comparison exists, you're comfortable against it. Nothing needs attention right now.
• Drift (Hard Hat Yellow): you're approaching a threshold, a certificate is inside its renewal window, a policy review is coming due, a renewal quote should be starting. Nothing is broken yet, but it will be if it's left alone.
• Exposed (Ember Red): you're past a threshold that carries real but not immediate consequence, an expired document with no active-service impact, a policy review that's overdue, a renewal that's genuinely tight. This is usually closeable inside the week.
• Breaching (a deeper red): you're past a threshold that blocks work or exposes you today, an expired certificate of insurance, a workers' comp policy with an Experience Modification Rate (EMR) at or above 1.25, an incident whose corrective action is overdue. This is the "fix now, not this week" tier.
• Watching (muted gray): Verinode doesn't yet have enough on the record to stake a posture, no expiry date logged, a first-aid event nobody has triaged yet. This is an honest placeholder, not a failure to compute something: log the missing detail and the engine will pick a real stance.

The pill's color is the fastest signal on the page. It always sits beside the record's kind, so you know at a glance both what you're looking at and how urgent it is.

The three lines under the pill: action, gain, and cost of inaction

Directly under the record's title, the subtitle is the stance engine's action line, a single sentence naming exactly what to do (or confirming there's nothing to do). Below the hero, the agent-insight panel expands on that action with two more lines, always present together, whatever the stance:

• Gain, what you get by acting now. For example, on an insurance certificate 10 days from expiring: "Smooth 14-day renewal keeps operations continuous; scrambling inside 7 days is when operators pay for premium expediting."
• Cost of inaction, what happens if you don't. For the same record: "Brokers bid best with 14+ days notice, get ahead of it."

These three lines (action, gain, cost of inaction) render on every record regardless of stance, including Healthy ones. A Healthy incident still tells you what closing it is worth ("Review for learning value") and what leaving it unreviewed costs ("the next person on the job learns the lesson the hard way"). Verinode's fractional-COO framing never goes quiet just because nothing is currently wrong, it always has a next move in mind, even if that move is "keep doing what you're doing."

How each record kind picks its stance

The stance engine runs a different threshold ladder per record kind. All three currently-live kinds share one instinct: absolute regulatory and carrier facts (an expiry date, an EMR, an OSHA recordability flag) always outrank a peer comparison. Peer data adds context on top, it never overrides a hard deadline.

Incidents

An incident's stance depends on its status, its severity, and whether its corrective action is on time.

• A closed incident with a documented closure date is always Healthy. The action line asks you to review it for learning value; the cost-of-inaction line notes that an undiscussed closed incident means "the next person on the job learns the lesson the hard way."
• A fatality, or any incident whose corrective action is overdue, is Breaching. A fatality triggers mandatory OSHA reporting and the action line says so directly ("OSHA notification + investigation in progress"). An overdue corrective action reads "Close the corrective action today," because open corrective actions past due are the single biggest driver of OSHA citation escalation.
• An OSHA-recordable incident that's still open is Exposed. If Verinode can compare your incident rate against a peer figure and you're running meaningfully above it, the cost-of-inaction line quotes the specific gap (for example, "You're 0.8 points above the peer rate, each open recordable widens the gap"); otherwise it falls back to a plain statement about EMR compounding.
• A lost-time incident that's still open is also Exposed, framed around the fact that an employee out is capacity you're already paying for.
• Any other open incident (typically a first-aid event) sits at Drift: add a root cause and a corrective action before it has a chance to repeat as something worse.
• An incident with none of the above flags reads Watching, "No action needed right now," with a nudge to review it alongside the rest of the month's first-aid events for a pattern.

Safety policies

A policy's stance depends on its status and how far its review date is from today.

• An archived policy is Watching: retained for audit history, no active exposure.
• A draft policy is Drift: it doesn't count toward compliance yet, so you're "exposed on paper only" until it's finalized and activated.
• A policy with no review date on file is Drift: without a review cycle, most program audits fail it automatically.
• A review date more than 90 days overdue is Exposed: this is the point most carrier and OSHA audits actually flag.
• A review date overdue but inside 90 days is Drift: schedule the review and refresh the language before it crosses that line.
• A review date due within 60 days is Drift: this is when most operators draft and circulate the update.
• Anything further out, or already reviewed and current, is Healthy.

Notice that policies never reach Breaching. An overdue policy review is a paperwork gap, not something that blocks work or triggers same-day exposure the way an expired certificate of insurance does, so the ladder tops out at Exposed.

Insurance (certificates of insurance)

Insurance carries the widest ladder, because it mixes a hard carrier-priced number (EMR) with a straightforward expiration date.

• A workers' compensation policy with an EMR of 1.25 or higher is Breaching, regardless of how far out the policy is from renewal. EMR is a three-year rolling average, so the action line focuses on the loss run behind it: "Request loss run + targeted incident-prevention plan," because an EMR at this level disqualifies you from most commercial and larger-carrier programs, and every renewal at this rate locks in another year of the same rate.
• A policy with no expiration date on file is Watching: log the date so the 60/30/14-day renewal calendar can start working.
• An expired policy is Breaching: carrier programs typically auto-suspend within one to three business days of a lapsed certificate of insurance, so the action line is urgent and specific, "Contact broker today + send updated COI to carrier programs."
• A policy expiring within 14 days is Exposed: brokers bid best with 14 or more days of notice, so this is the point to confirm the renewal and line up COI distribution.
• A policy expiring within 60 days with no auto-renew is Drift: this is the annual negotiation window, the 60-day lead time is what lets the broker shop competing quotes.
• A workers' comp policy with an EMR above 1.00 but under 1.25 is also Drift, even outside any renewal window: every 0.1 off your EMR compounds into three years of premium, so this is flagged as a standing opportunity, not just a renewal-season one.
• Anything else, active, inside its renewal window, no EMR concern, is Healthy.

Reading the pill in context: the hero stats

Underneath the title, four stat tiles sit beside the pill, and which four you see depends on the record's kind. These are read-only facts, not part of the stance decision, they're the evidence the stance was built from:

• Incident: Severity, whether it's OSHA-Recordable, the Corrective Action status (with a day count or "No due date"), and when it was Logged.
• Policy: the Review date (with its own color coding), the document Version, how many team members have Acknowledged it out of the total team size, and its Status.
• Insurance: the Expires date, Coverage limit, annual Premium, and, for workers' comp specifically, the EMR value in place of a deductible figure.

A record's peer-comparison strip, when one appears below the hero, draws on four metrics resolved for the Safety section as a whole: your incident rate per 100,000 hours against the peer figure, your training compliance percentage, days since your last recordable, and your policy review currency percentage. Not every metric will show a peer line every time, Verinode only shows one when the network has a comparable cohort for that metric; when it doesn't, your own number still shows in full. Verinode never surfaces how many operators sit behind a given peer figure, only whether there's enough to compare against safely. See How benchmarks work and Reading a benchmark for how these comparisons are built generally.

The rest of the card

Below the hero and the agent-insight panel, a sticky row of tabs carries the rest of the record:

• Details always shows. What it contains depends on kind: an incident's Details tab breaks out What Happened (description, location, people involved, a linked job if one exists) and Root Cause & Preventive Change (your 5-Why root cause and corrective action, with an honest placeholder line, "No root cause recorded yet, the fastest way to prevent a repeat is a 5-Why pass. The incident-reporter agent can walk through it," when neither has been logged yet), plus a Pattern Context block naming how many OSHA recordables you've had in the last 90 days when that count is above zero. A policy's Details tab shows its Overview (category, version, effective and review dates), an Acknowledgments block once your team has more than zero members ("X of Y team members have acknowledged," with up to eight names and dates listed), and Version History when earlier versions exist. An insurance record's Details tab shows Coverage Overview (carrier, policy number, EMR with a plain-language note on which tier you're in, effective and expiration dates, auto-renew status) and, when other active policies exist, an Other Active Policies list.
• Open Tips only appears when there's at least one open tip tied to this specific record, with a badge showing the count. Each tip shows a headline, an optional rationale line, and, when there is one, a specific action line prefixed with an arrow.
• Findings only appears when a decision links back to this record, again with a count badge. Each entry shows the decision's title and, when Verinode can size it, the dollar figure it's costing you per month.

A Quick Survey button sits in the hero's action slot on every record. It opens a short, one-question survey you can answer about the record, part of how your own experience feeds back into Verinode's peer intelligence layer; that contribution is anonymized before it ever reaches the benchmark cohort, and it is never sold to carriers.

Empty states

There's no single "no data" screen for this card, because you only ever reach it by clicking an existing record. The honest empty states you'll see live inside the tabs described above: "No root cause recorded yet" on an incident with nothing logged, "No corrective action documented" until one is assigned, Open Tips and Findings tabs that simply don't render when nothing qualifies rather than showing an empty shell, and the "Watching" stance itself, reserved for records missing the one field (an expiry date, most often) the engine needs to compute anything more specific.

Best-practice example

Say you click into a workers' comp certificate of insurance from the Exposure tab. The pill reads Drift, because the policy is 45 days from expiring with no auto-renew, and its EMR sits at 1.08. The subtitle reads "Kick off renewal quoting with the broker." The agent-insight panel explains the gain, a 60-day lead time lets the broker shop competing quotes with room to negotiate, and the cost of inaction, waiting past 30 days means competing with every other operator chasing the same seats. The hero stats confirm the numbers: Expires in 45 days, Coverage at whatever your limit is, Premium for the year, and EMR at 1.08, colored amber. Since EMR above 1.00 is itself a standing Drift condition, even once the renewal window closes this record won't fall back to Healthy until the EMR itself comes down, which the Details tab and the loss-run conversation on Standing are built to help you work toward.

Data sources

Related articles

• The Safety home: hero KPIs and the Explore tiles
• Take Action: safety decisions and activation
• All Safety tab: the unified records list
• Standing tab: where you stand vs OSHA and peers
• Exposure tab: capacity at risk this week
• The certification detail card and stance engine
• How benchmarks work
• Reading a benchmark