Inside a process record: Details, Open Tips, and Findings

What this is

Processes holds three different kinds of record, side by side: an SOP you have written or adopted (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 underneath, but every one of them opens into the same shape of detail card: a stance pill, a recommended action with its gain and cost of inaction, a synthesis paragraph, and, when there is something to show, an Open Tips tab and a Findings tab.

This article is the full reference for that shared card, plus what changes underneath the Details tab for each of the three kinds. Verinode does not decide anything on your behalf here. It reads your SOPs, the patterns it observed, and the standards that apply to your state and trade, then names what it sees, what acting would gain you, and what waiting costs. You confirm, edit, adopt, or dismiss. The call stays yours.

Where to find it

The Help Center groups this page under Excellence. In the product, the sidebar item is Processes, under Operations, at /processes. Visiting /excellence forwards you to the same page; see Excellence (Processes): the fractional-COO process coach for the full story on that naming gap, plus the two independent gates (Premier membership tier, and whether the section has been switched on for your account) that can stand between you and the page.

Once you're past both gates, click any tile anywhere on Processes, a written SOP, a pattern waiting on you, or a standard reference, and its detail card opens. From inside the card you can swipe (on mobile) or use the on-screen arrows (on desktop) to page through every process record in the order Verinode loaded it, not just the narrower list you clicked in from.

The hero: kind, stance, and four numbers

At the top of every process detail card, an eyebrow line carries two things side by side: the record's kind label (My SOPs, Pending Confirmations, or Standards) and a stance pill. The title underneath is the record's name (the SOP's title, the inferred step's text, or the standard's source citation), and the subtitle is a single plain-language sentence naming the specific action Verinode recommends right now, never a generic nudge.

The stance pill: HEALTHY, DRIFT, EXPOSED

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

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

These are the same three words and colors used everywhere else on the platform that carries a stance, so a stance pill on Safety or Compliance reads the same way here. What actually trips each state is specific to the kind of record:

My SOPs. An SOP goes EXPOSED when an open process signal is flagged against it and its LEAN score is either missing or under 60 ("Tighten this SOP, a process signal is flagging gaps"). It goes DRIFT when the LEAN analysis hasn't run yet ("LEAN analysis pending, re-trigger if it stalled"), when the score has come back but sits under 60, or when the SOP hasn't been updated in more than a year ("Refresh, LEAN below 60" or "Refresh, not reviewed in 12+ months"). It's HEALTHY once it's analyzed, scored 60 or above, and reviewed within the last year, with nothing flagged against it ("Keep using it, re-review yearly to keep it tight").

Pending Confirmations. A pattern is HEALTHY the moment you confirm, edit, or dismiss it, there's nothing left to act on either way. While it's still pending, it goes EXPOSED if an open process signal is specifically waiting on your decision ("Confirm or dismiss, a process signal is waiting on this"). Past that, it goes DRIFT once it has sat unconfirmed more than two weeks ("Confirm or dismiss, pending Nd"), and otherwise sits in a lighter DRIFT state that simply invites a quick confirm, naming the detector's confidence and which specialist captured it.

Standards. A standard goes EXPOSED when a carrier program requires an SOP in this category and you don't have one documented yet ("Adopt this standard, N carrier program(s) require it"). It goes DRIFT when you have no SOP in the category and nothing external requires one yet ("Compare to your SOP, start a draft if you don't have one"). It's HEALTHY once you already have a documented SOP here, at which point the recommendation shifts from adopting to diffing your SOP against the standard's latest revision.

The four hero stats

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

| Kind | Stat 1 | Stat 2 | Stat 3 | Stat 4 | |---|---|---|---|---| | My SOPs | LEAN Score, the current score out of 100, or "Pending" while the first pass is still running. Shows a "Target N" delta when a target standard is on file. | Steps, the count of documented steps. | Jobs Using, how many of your jobs currently reference this exact SOP (not just jobs in its category). Colored to match the stance pill. | Updated, the date it was last edited. | | Pending Confirmations | Status, Pending, Confirmed, Dismissed, or Edited. | Confidence, the detector's read on this observation as a percentage. 80% or higher shows green. | Cluster, how many observations, this one included, were grouped as the same underlying pattern; a note reads "similar pending" when there are others. | Captured, the date the observation was first logged. | | Standards | 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 above zero. |

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

Right under the hero sits a recommendation card, the fractional-COO triad that appears on every record regardless of stance: what to do, what you gain by doing it, and what leaving it alone costs you. Every stance carries all three; there's no state where the card just says "monitoring" and stops there.

The card's badge and eyebrow track the stance: Recommended in Ember Red for EXPOSED, Watching in Hard Hat Yellow for DRIFT, On track in Deere Green for HEALTHY. Its headline is the same action sentence you saw under the hero title. Below it, two more lines:

• A plain-text line naming what you gain by acting, the payoff of closing the gap, in operator language.
• An italicized, muted line naming the cost of not acting, framed around carrier defensibility, margin, or the risk of knowledge staying in one person's head.

IQ'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's generated for this specific record and weaves the stance, the recommended action, the gain, the cost of inaction, and, when there are any, a mention of how many open tips and linked findings sit against this record, into one continuous second-person read.

While it generates, the space shows three skeleton lines so the page doesn't 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 doesn't render, nothing broken shows on screen.

The Details tab, by kind

Everything above this point, the hero, the stance, the recommendation, and the synthesis paragraph, is identical across all three record kinds. What sits underneath in the Details tab is not. Each kind has a genuinely different body.

If it's an SOP you wrote or adopted (My SOPs)

In order, the sections you can see on an SOP's Details tab:

1. Status. Appears only when relevant: a copper note naming the standard this SOP was adopted from and how many of its steps are locked in by citation, or, on a draft SOP, an amber Draft pill with the line "Activate this SOP to contribute to peer benchmarks and surface in job process matches." and an Activate this SOP button. Clicking it flips the status to active and shows a success toast: "SOP activated. It now contributes to peer benchmarks and links to jobs."
2. Adherence (90 days). Whether jobs in this SOP's category are actually being run the way it's written, read from your last 90 days of closed-out jobs. Shows a followed-over-total count and its percentage, a cohort-confidence pill (Early signal, Indicative, Observed, or Verified), a 13-week sparkline of weekly adherence, a variance line comparing actual time against the SOP's own time estimates ("ran on plan," "N% over plan," or "N% under plan"), and a short read on what the numbers mean. With no jobs closed out against this SOP yet, it reads "No execution data yet. When jobs in this category close out and link to this SOP, adherence + drift signal land here."
3. Credentials this SOP implies. Only for SOPs adopted from a standard that declares required or preferred certifications. Each credential shows how many of your active team members hold it against how many the standard calls for, tagged Required or Preferred, with a link out to Certifications.
4. LEAN Score. The 0 to 100 score with a progress bar, and, when the analysis carries a standard comparison, a line reading how many points above or below the target you sit.
5. Process Rating. A three-dimension rating: Effectiveness (an owner rating out of 5), Usability (a staff rating out of 5), and Compliance (the LEAN score folded into a 1 to 5 read). Any dimension without a rating on file shows "Not rated." Once at least one job has run against the SOP, an Outcome Correlation line reports how many jobs used it and compares the average margin (what you keep) on those jobs against jobs that didn't use it.
6. Link to Carrier or TPA. A single-select dropdown tying the SOP to one client. Once you change the selection, a Save link button appears; saving shows "Linked to [name]" or "Carrier link cleared" as a success toast, or a "Link failed, try again." error toast if it doesn't go through. When a link is set, any specific requirements that client has for this category (with an SLA timer and penalty, where on file) list underneath.
7. Link to Vendors, Team, or Equipment. Three separate chip pickers, one each for vendors, team members, and equipment, so IQ can reach for this SOP when you ask about a linked vendor, team member, or piece of equipment elsewhere on the platform.
8. Framework Scores. Only when the analysis carries per-framework results (IICRC, LEAN, OSHA), each with its own 0 to 100 score and bar.
9. Top Recommendations. Up to three ordered, concrete changes the analysis suggests, referencing actual steps.
10. Waste Signals. One entry per step the analysis flags for one of the LEAN waste types (Waiting, Transportation, Motion, Defects, Over-processing, Overproduction, Inventory, Skills), each naming the step, describing the issue, and suggesting a fix.
11. Process Steps. The step list itself, read-only by default with an Edit steps button. Editing flips every row into a form (type, description, role, equipment, estimated minutes) with + Add step and a per-row Remove control; Save steps and Cancel sit above the list while editing. Saving shows "Steps saved. LEAN re-scoring runs in the background." Steps a source standard locks in by citation carry a copper Required pill, and removing one prompts a confirmation naming the citation and the reason before it lets you continue. With no steps recorded, it reads "No steps recorded. Click Edit steps to add some."
12. Feedback. Community sentiment on this SOP, a free-text feedback box, a Quick Survey button, and, at the bottom, the record's Archive SOP (or Restore SOP, once archived) control. Archiving asks first: "Archive this SOP? It won't appear in your active list. You can restore it from archived view." Restoring confirms with "Restore this SOP? It will reappear in your active list."

If it's a pattern waiting on you (Pending Confirmations)

An observed pattern's Details tab is read-only. It shows you the evidence behind the pattern; confirming, editing, or dismissing it happens from the pattern-to-confirm card in the Explore row on the Processes home, not from inside this detail view. See Patterns to confirm: how Verinode captures your process steps for that flow.

What you see here:

1. Inferred Step. The behavior Verinode believes it found, in its own words, plus, when known, a Pattern Type, who captured it (Captured by), and the current Status.
2. Sources. One entry per artifact the detector saw on the way to this inferred step: the source type (an email, a voice note, a photo, an upload, an attachment), how long ago it was extracted, a confidence percentage where one exists, and, when there is one, a quoted snippet of the actual text or transcript. Confirming the pattern rolls these sources up as evidence on the resulting SOP step.
3. Similar Pending. Other observations grouped into the same cluster as this one, each with its own inferred text, who captured it, when, and its confidence. Confirming a few of these together is what moves a cluster toward a proposed SOP update.
4. Target SOP. Appears only when this pattern is a candidate for an existing SOP rather than a brand-new one, naming that SOP's title and how many steps it already documents.

If it's a standard reference (Standards)

A standard's Details tab is built around one decision: adopt it as the starting point for your own SOP, or not.

1. Adopt as your SOP. A short line naming how many steps you'd start with and which framework's citations come pre-attached, and an Adopt as draft SOP button. Clicking it scaffolds a draft SOP from the standard and shows "Draft SOP created. Open the All tab in Processes to edit it." (or "Couldn't adopt this standard, try again." if it fails). If you already have an SOP in this category, a note tells you adopting creates a separate draft you can compare against, it doesn't overwrite what you have.
2. Standard Overview. The framework, jurisdiction, source citation, version, description, and target score.
3. Your SOP. If you have a documented SOP in this category, its title, step count, and LEAN score, plus a note that diffing against this standard catches drift between what the framework requires and what your SOP says today. If you don't, it reads "You don't have a documented SOP in this category yet. Drafting one against this standard is the cleanest baseline for the rest of your work in this category."
4. Carrier Programs Requiring This. Only when at least one carrier program requires an SOP in this category at or above this standard's target score: each program's name, a confidence tier (Low, Medium, High), and the minimum target score it requires.
5. Required Steps. Only when the standard locks specific steps in by citation: each step's position, its citation, the matching step text where it lines up with the standard's own step list, and the rationale behind requiring it.

Open Tips tab

The Open Tips tab holds open process-domain signals tied specifically to this record, the same kind of tip you see on Safety, Equipment, and Clients records. Each tip shows a bold headline naming what was detected, a muted rationale line explaining why (when one is on file), and 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 doesn't appear as an empty tab, it simply isn't in the tab list. When it does appear, its label carries a numeric badge counting the open tips.

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. Clicking through opens the full Act / Not now / Why workspace at /decisions/[id]; see The decision workspace and Acting on decisions for how those get prioritized and worked.

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

Record-level actions, at a glance

| Kind | Actions available on this record's detail card | |---|---| | My SOPs | Activate (draft only), edit or add or remove steps, link to a carrier or TPA, link to vendors, team, or equipment, leave feedback or run a Quick Survey, archive or restore. | | Pending Confirmations | None inside this card. Confirm, edit, or dismiss from the pattern-to-confirm card on the Processes home. | | Standards | Adopt as a draft SOP. Everything else on this card is read-only reference material. |

Best-practice example

Say a Pending Confirmation shows up with 87% confidence, captured from a voice memo one of your techs left after a mold job: a step where the crew photographs the moisture meter reading before starting containment. Its stance reads DRIFT, pending nine days, no open signal on it yet. You open the record, read the Sources section, see the actual quoted line from the voice memo, and check Similar Pending: two more observations from other jobs back the same behavior. That's enough for you to trust it. You go back to the Processes home, confirm the pattern from its card, and it becomes evidence for a documented step the next time you touch the SOP for that category. Meanwhile, that same SOP's own detail card might show EXPOSED, LEAN score under 60 with an open process signal flagging it: read the recommendation card, work through the Waste Signals and Top Recommendations sections, tighten the flagged steps, save, and let LEAN re-score in the background.

Related reading

• Excellence (Processes): the fractional-COO process coach
• Your SOP library: writing, editing, and scoring SOPs
• Patterns to confirm: how Verinode captures your process steps
• Standards library: IICRC, LEAN, OSHA, EPA, and state rules
• Process findings and Take Action decisions
• The decision workspace
• Acting on decisions
• The Feed
• How Verinode's benchmarks work
• Understanding your margin