Explore metrics and confirming patterns Verinode spotted

What the Explore row is

The Explore row sits directly under the Take Action row on your Processes home. It always opens with four metric tiles that read your process coverage back to you: My SOPs, To Confirm, Standards, and Lines Without An SOP. When Verinode has patterns waiting on you, one more tile appears after each of those four, one per pattern, where you actually Confirm, Edit, or Dismiss what the nightly clusterer inferred from your own jobs.

Nothing on this row compares you to other operators. Every number here is you against your own service mix and your own job history. Peer comparisons live one tab over, in Benchmarks, covered in the Benchmarks tab.

Where to find it

Open Processes from the sidebar, under Operations, or go directly to /processes. The Explore row is the second row on the page, right under the hero panel and the Take Action row. See the Processes overview for the full page layout and acting on decisions for the Take Action row above it.

The four metric tiles

Each tile opens a filtered view of the process card slider when you click it. None of them require any setup to appear, they read straight from your SOP library, your service-line profile, your pending observations, and Verinode's standards catalog.

My SOPs

Shows how many SOPs you have written and activated, the same count as the hero panel's headline. The line under the number reads "Written By You" once you have at least one, or "Upload One To Start" while your library is empty.

Below the number, when you have at least one service line on file, a grid of dots shows one dot per active service line, with the ones that already have a documented SOP lit. It is the same coverage ratio the hero's percentage pill shows, just drawn as a grid instead of a badge.

Click the tile and it opens the All Processes tab of the process card slider, filtered to My SOPs. From there you see every SOP you have, each opening into its own detail card with its steps, its LEAN waste score if one has been computed, and its work type. See the All Processes tab and the SOP detail card.

To Confirm

Shows the count of pending observed patterns still waiting on you, the same number as the hero's "To Confirm" secondary figure. The line underneath reads "Tap To Confirm" when there is a backlog, or "Nothing Waiting" when the queue is clear. When there is a backlog, a grid of dots below the number fills one dot per pending observation, in an amber watch tone, so the size of the queue reads at a glance.

Click the tile and it opens the All Processes tab filtered to Pending Confirmations, the label this record kind carries there. That list shows every individual observation still on file, confirmed or not, each with its inferred step and a quoted snippet where one exists.

Standards

If Verinode has your state on file, this tile's label swaps to "<Your State> + Federal". Without a state on file, it reads plainly "Standards." The number counts reference standards in Verinode's shared research library that are tagged specifically to your state, pulled from IICRC, LEAN, OSHA, EPA, and state-level sources. The line underneath, "IICRC · LEAN · OSHA · EPA · State," names every framework the library spans, not just the state-specific slice this particular tile counts, so don't be surprised if the catalog you land on is broader than the number on the tile.

Click the tile and it opens the By Standard tab, where you can browse the complete catalog grouped by framework, All, IICRC, LEAN, OSHA, EPA, and State, each with its own count. See the By Standard tab.

Lines Without An SOP

Your service-line coverage gap: how many of the service lines in your operator profile have no active SOP attached yet. The tile's accent flips with the state of the gap, red (Ember) while lines are missing coverage, green once none are. The line underneath reads "Write One To Close It" while the gap is open, or "All Covered" once it closes.

Below the number, a gauge shows your documented-coverage percentage as a filled arc against two zones, red below 60%, amber from 60% up to 90%, green at 90% and above. That is the same percentage the hero's pill shows, drawn as a gauge instead of a badge. The gauge only renders when you have at least one service line configured; with none on file, there is nothing to divide, so it is simply omitted rather than showing a misleading 0% or 100%. In that same edge case the tile's own number still reads 0 with "All Covered," since a gap of zero is technically true even before you have any service lines to measure against, that is a real zero, not a documented one.

Click the tile and it opens the Coverage tab: the full service-line matrix, showing which lines have an SOP, which have relevant certifications or carrier program alignment on file, and which have neither. See the Coverage tab.

The pending-cluster confirmation tiles

After the four metric tiles, one tile appears for every pattern Verinode's nightly clusterer has ready for your review, up to eight at a time, oldest first. Clearing the longest-standing pattern first works down the backlog instead of only reacting to whatever was captured most recently. When there is nothing waiting, the row simply ends after the four metric tiles, there is no placeholder card for an empty queue.

What a pattern is

As your jobs move through Verinode, agent specialists quietly log small observations about how work actually happens, a step that keeps recurring before drying starts, a sign-off pattern on mold jobs, a habit around scope changes. A single observation does not mean much on its own. Once the same category, work type, inferred step, and pattern kind have been captured across enough separate jobs to agree with each other, the clusterer groups them into one "pattern to confirm," a claim about how your operation actually runs, backed by real evidence pulled straight from your own work. That is the tile you see here.

Verinode does not decide this is one of your SOPs. It surfaces the pattern it noticed and asks you to say whether it is right. Nothing from a pattern feeds the Business Analyst's process reads as evidence until you have acted on it.

What each tile shows

• "Pattern to confirm" in the top-left corner, a fixed label.
• "N× captured" in the top-right, in copper, the number of separate observations the clusterer grouped together to build this pattern.
• The inferred step, in bold: the behavior Verinode believes it found, in its own words (for example, "Photograph moisture readings before setting equipment"). If nothing specific was inferred, the tile falls back to the evidence snippet instead, and if there is neither, it reads "Unnamed pattern."
• A quoted evidence snippet underneath, in italics, when one exists: the actual wording pulled from your jobs, so you are never confirming a black box. If no usable snippet was kept, this line is skipped entirely.
• A category and work type line at the bottom (for example, "Water Mitigation · Residential"), so you know which part of your business the pattern describes.

The three ways to respond

1. 1Confirm. Click Confirm if the pattern is accurate as written. The button reads "Confirming…" while it saves, then the tile toasts "Pattern confirmed." Every observation that fed this pattern flips to confirmed and becomes usable evidence for the Business Analyst.
2. 2Edit, then confirm. Click Edit if the pattern is close but not quite right. The tile swaps to a text box pre-filled with the inferred step so you can refine the wording. When ready, click Save & confirm (disabled until you type something); the tile toasts "Confirmed with your edit." Your phrasing becomes the record of what actually happens. Verinode's original inference stays on file underneath so future clustering can still recognize the same underlying behavior. Cancel discards your edit and returns to the read-only view without saving anything.
3. 3Dismiss. Click Dismiss if the pattern is not real or does not matter. The tile toasts "Pattern dismissed." The observations behind it are not deleted, they are unlinked from this cluster and returned to a pending, unclustered state. If the same behavior shows up again across future jobs, the clusterer can group a fresh pattern from it later.

If a save does not go through, the tile toasts "Couldn't confirm, try again" or "Couldn't dismiss, try again" and leaves the pattern exactly where it was so nothing is lost.

Where the clustering happens

A clusterer runs nightly over every observation still sitting unclustered and pending. It groups observations that agree on category, work type, inferred step, and pattern kind (case and spacing differences are normalized so near-identical phrasing does not fracture one real pattern into two), and only turns a group into a reviewable tile once enough separate jobs have backed the same behavior, a single coincidence never earns a tile. If a matching pattern from an earlier run is still open, a new agreeing observation grows that same cluster's count and refreshes its evidence and headline rather than creating a duplicate tile.

Patterns you never act on do not sit in your queue indefinitely. One that has gone unconfirmed for a long stretch, roughly three months without any new supporting evidence, is automatically retired so it stops competing for your attention. Nothing is deleted when that happens, the underlying observations stay on file; the pattern simply stops asking for a decision unless a fresh wave of the same behavior brings it back.

Empty states

• No pending patterns at all. The Explore row shows only its four metric tiles, nothing more. The To Confirm tile itself reads "0" with "Nothing Waiting" underneath, and its dot preview is empty.
• No SOPs yet. The hero and the My SOPs tile both read "Upload One To Start" (or "Upload your SOPs to get started" on the hero), and the dot-grid preview shows a full row of unlit dots if you have service lines configured.
• Every service line covered. The coverage gap is zero, the hero reads "Every service line has an SOP," and Lines Without An SOP reads "All Covered" in green.
• No service lines configured at all. The coverage percentage has nothing to divide, so the gauge preview on Lines Without An SOP is omitted entirely rather than rendering a false 0% or 100%. The tile's own count still reads 0.
• A confirm, edit, or dismiss action fails. The tile shows an error toast and stays exactly as it was, nothing in the queue is lost or changed.

None of these are broken screens. Each one means the underlying data, your service mix, your SOP library, and the observations your team's activity has generated, has not caught up yet, and the row tells you exactly what is missing rather than guessing.

Best-practice example

Say the Explore row shows a tile reading "Pattern to confirm, 4× captured, Photograph moisture readings before setting equipment, Water Mitigation." Four separate jobs backed the same behavior. If that genuinely is your team's habit, click Confirm, it becomes a real, evidence-backed part of how you run water jobs and feeds directly into how the Business Analyst reads your process going forward. If the wording is close but your crew actually photographs readings after setting equipment, click Edit, correct the order, and Save & confirm, your phrasing becomes the record. If it was a one-off habit on a single crew that is not how you actually want the job run, Dismiss it. Nothing is lost, and if the behavior turns into a genuine pattern later, it can resurface as a fresh tile.

Related reading

• The Processes section
• Acting on decisions
• The Coverage tab
• The By Standard tab
• The All Processes tab
• How your work flows
• How Verinode's benchmarks work
• The decision workspace
• Connecting your data
• Forwarding documents