Stance, Open Tips and Findings on a process

What this shell is

Processes holds three different kinds of record: an SOP you have written (My SOPs), a pattern Verinode noticed in how your team actually works and is waiting on you to confirm (Pending Confirmations), and an outside reference procedure your work gets measured against (Standards, drawn from IICRC, LEAN, OSHA, EPA, and state rules). The three kinds hold very different content, but they all open into the same detail card. That shared card, its stance pill, its recommendation, its synthesis paragraph, and its Open Tips and Findings tabs, is what this article covers. The content that changes between the three kinds (LEAN scores, adherence, step editors, adoption flows) has its own articles, linked at the bottom.

Verinode does not decide what to do with any of these records. It reads your SOPs, the patterns it observed, and the standards that apply to you, then names what it sees, what you would gain by acting, and what it costs you to wait. You make the call on every one.

Where to find it

Open Processes from the sidebar (Operations section), at /processes. Click any tile, an SOP, a pending confirmation, or a standard, and its detail card opens. The top of that card is identical in structure across all three kinds; only the numbers and the kind-specific body underneath change.

The hero: kind, stance, and the headline action

At the top of every process detail card sits an eyebrow line with two things side by side: the kind label (My SOPs, Pending Confirmations, or Standards) and a stance pill.

The stance pill: HEALTHY, DRIFT, EXPOSED

The pill reads one of three words, each with its own color:

• HEALTHY (Deere Green). Nothing needs your attention right now.
• DRIFT (Hard Hat Yellow). Something needs a look, but nothing is actively at risk.
• EXPOSED (Ember Red). An open signal, a carrier requirement, or a real gap is putting this record on the line right now.

The same three words and colors are used everywhere else on the platform that carries a stance (Safety, Compliance, and so on), so once you have read a stance pill anywhere in Verinode, you already know what it means here. What trips each stance is specific to the kind of record:

• An SOP goes EXPOSED when an open process signal is flagged against it and its LEAN score is either missing or under 60. It goes DRIFT when the LEAN analysis has not run yet, when the score is under 60 on its own, or when the SOP has not been updated in more than a year. It is HEALTHY once it is analyzed, scored 60 or above, and reviewed within the last year, with nothing flagged against it.
• A pending confirmation goes HEALTHY the moment you confirm, edit, or dismiss it, there is nothing left to act on either way. While it is still pending, it goes EXPOSED if an open process signal is waiting on your decision, DRIFT once it has sat unconfirmed for more than two weeks, and otherwise sits in a soft DRIFT state that simply invites a quick confirm.
• A standard goes EXPOSED when a carrier program requires an SOP in this category and you do not have one documented yet. It goes DRIFT when you have no SOP in the category but nothing external requires one. It is HEALTHY once you already have a documented SOP here, at which point the recommendation shifts to diffing your SOP against the standard rather than starting one.

The subtitle under the record's title, directly below the hero title, is a single plain-language sentence naming the specific action behind that stance, not a generic nudge. That same sentence reappears word for word as the headline of the recommendation card described below.

The four hero stats

Beside the title, four numbers summarize the record. Which four you see depends on the kind:

My SOPs

| Stat | What it means | |---|---| | LEAN Score | The SOP's current LEAN score out of 100, or "Pending" while the first analysis is still running. When this category has a target standard on file, a delta line shows how the score compares (for example, "Target 85"). | | Steps | How many steps are documented in the SOP. | | Jobs Using | How many jobs in this SOP's category currently reference it. Colored to match the stance pill. | | Updated | The date the SOP was last edited. |

Pending Confirmations

| Stat | What it means | |---|---| | Status | Pending, Confirmed, Dismissed, or Edited. Confirmed and Edited show green; Pending shows neutral; Dismissed shows plain. | | Confidence | How confident the detector was when it captured this observation, as a percentage. 80% or higher shows green. | | Cluster | How many observations, including this one, were grouped together as the same underlying pattern. When there are others, a note reads "similar pending." | | Captured | The date the observation was first logged. |

Standards

| Stat | What it means | |---|---| | Framework | The source framework (IICRC, LEAN, OSHA, EPA, or a state code), in uppercase. | | Target Score | The score a documented SOP needs to hit to be considered aligned with this standard. | | Required Steps | How many of the standard's steps are locked in by a specific citation. | | Programs | How many carrier programs require an SOP in this category at or above this standard. Colored to match the stance pill, with a "require this" note when the count is above zero. |

Verinode's recommendation: action, gain, and cost of inaction

Right under the hero, on every process detail card, sits a recommendation card. This is the fractional-COO triad: what to do, what you gain by doing it, and what it costs you to leave it alone. Every stance carries all three, there is no state where Verinode just says "monitoring" and leaves it there.

The card's small colored badge and eyebrow track the stance: Recommended (red) when the stance is EXPOSED, Watching (yellow) when it is DRIFT, and On track (green) when it is HEALTHY. Its headline is the same action sentence you saw under the hero title. Below the headline, two lines of evidence:

• A plain-text line naming what you gain by acting: the payoff of closing the gap, in operator language, not a generic benefit statement.
• An italicized, muted line naming the cost of not acting: what continuing to leave this alone actually costs you, framed in terms of carrier defensibility, margin, or the risk of the knowledge staying in one person's head.

Verinode's read on this: the synthesis paragraph

At the top of the Details tab, above the kind-specific content, sits a short paragraph labeled IQ's read on this. It is generated fresh for this record and weaves together the stance, the recommended action, the gain, and the cost of inaction into a single second-person read, along with a mention of how many open tips and linked findings exist for this record when there are any. It reads as one continuous thought, the same fractional-COO voice used across the platform: Verinode names what it sees and what it would do next, and leaves the decision with you.

While it is generating, the paragraph's space shows three skeleton lines so the page does not jump when the text lands. The result is cached for a week and only regenerates when something about the record's stance, action, gain, or cost actually changes. If the generation fails for any reason, the section simply does not render, nothing broken shows on screen.

Open Tips tab

The Open Tips tab holds open process-domain signals tied specifically to this record, the same Act, or leave it kind of tip you see on Safety, Equipment, and Clients records. Each tip shows:

• A bold headline naming what was detected.
• A rationale line underneath, in muted text, explaining why it was flagged, when one is on file.
• An action line, prefixed with an arrow, naming the specific recommended move, when one is on file.

This tab is not shown at all when there are no open tips for this record, it does not appear as an empty tab, it simply is not in the tab list. When it does appear, its tab label carries a numeric badge showing how many tips are open.

Findings tab

The Findings tab holds active decisions from your Feed that link back to this specific record: a low-margin pattern tied to this SOP, a compliance gap tied to a standard, and so on. Each finding shows a bold action title and, underneath in muted text, its cost-of-inaction summary when one is on file. For how these decisions get created, prioritized, and worked, see the decision workspace and acting on decisions.

Like Open Tips, this tab is hidden entirely when there is nothing linked, and carries a numeric badge on its tab label when there is.

Reading a process card, start to finish

1. 1Open Processes from the sidebar and click any tile, an SOP, a pending confirmation, or a standard.
2. 2Read the stance pill and the action sentence under the title. That single sentence is the specific thing Verinode wants you to do next.
3. 3Read the recommendation card right below the hero: the gain line tells you what closing the gap buys you, the italicized line tells you what waiting costs.
4. 4Scroll to IQ's read on this for the full paragraph tying the stance, action, gain, and cost together in one read.
5. 5If Open Tips or Findings appears in the tab bar, check the count badge and open it, that is specific, detected evidence tied to this exact record.
6. 6Work the kind-specific body under Details (LEAN score and steps for an SOP, the confirm-or-dismiss controls for a pending confirmation, the adopt-as-draft button for a standard). See the sibling articles below for what lives there.

What differs by kind

The stance pill, the recommendation card, the synthesis paragraph, and the Open Tips and Findings tabs are identical across all three kinds. Everything under the Details tab's kind-specific body is not:

• My SOPs carries the LEAN score, adherence, credentials, carrier links, entity links, framework scores, waste signals, and the step editor. See The SOP detail card.
• Pending Confirmations carries the inferred step, its evidence sources, similar pending observations in the same cluster, and, once you confirm enough of them, a path to draft an SOP update. See Confirming patterns Verinode spots.
• Standards carries the standard's framework, jurisdiction, and required steps, an Adopt as draft SOP button, and, when a carrier program requires it, the list of programs behind that requirement. See By Standard.

Related reading

• The Processes section
• Your Processes home: coverage headline and KPI tiles
• The SOP detail card
• Confirming patterns Verinode spots
• By Standard: the IICRC, LEAN, OSHA, EPA and state library
• The decision workspace
• Acting on decisions
• The Feed
• How benchmarks work
• Benchmarks overview

Data sources