Patterns to confirm: how Verinode captures your process steps

What this is

While your team works, Verinode's specialists quietly notice things: a step that keeps coming up before drying starts, a sign-off habit on mold jobs, a recurring check before a scope change goes out. Each of those is logged as a single observation, evidence pulled from a document, a conversation, or an artifact you sent in. A single observation does not prove anything on its own. Once the same likely step has been captured across enough separate jobs that they agree with each other, Verinode groups them into one pattern and puts it in front of you as a card you can confirm, edit, or dismiss.

This article covers that whole path: how an observation gets captured, how Verinode groups matching ones into a pattern, what the confirm/edit/dismiss card looks like, and what you see when you open one individual observation's own detail record, its source, its confidence, and which specialist first noticed it.

Verinode never decides a pattern is one of your real SOP steps. It surfaces what it noticed, backed by evidence pulled straight from your own work, and asks you to say whether it is right. Nothing from a pattern becomes evidence for the Business Analyst's process reads until you have acted on it.

Where to find it

Patterns to confirm live inside Processes, the sidebar item under Operations, at /processes. (If a link takes you to /excellence first, it forwards straight to /processes, same page.) Processes is a Premier membership feature; Contributor and Executive memberships see the section's layout with the SOP library, process mining, and pattern queue blurred behind an upgrade prompt. See the Processes overview for the full page.

Two places show you patterns to confirm:

• The hero panel, at the very top of the page, has a To Confirm figure next to the headline SOP count.
• The Explore row, right under Take Action, ends with one card per pattern that has enough evidence behind it, after its four metric tiles.

To see every individual observation on file, not just the ones that have cleared into a reviewable pattern, open the full card view and go to All Processes, then filter to Pending Confirmations. Clicking any one of those rows opens its own detail card, covered later in this article.

How an observation gets captured

Verinode's specialists log an observation silently, while reading a document you sent in, while you describe how a job ran in chat, while an agent runs a scheduled check-in. Each observation records:

• A category and, where known, a work type (Residential, Commercial, or both).
• An inferred step, the behavior Verinode believes it found, written in its own words.
• A pattern type, when Verinode can tag what kind of behavior it is.
• Evidence: one or more source entries, each carrying the artifact type (an email, a voice note, a photo, an upload, an attachment), a snippet of the actual text or transcript, and a confidence score.
• A confidence score for the observation as a whole.

Every observation starts at status Pending. It stays there until it is confirmed, edited, or dismissed, either directly or by way of the pattern it gets grouped into.

The nightly clusterer

A clusterer runs nightly over every observation still sitting pending and ungrouped. It groups observations that agree on category, work type, inferred step, and pattern type (small differences in case and spacing are normalized so near-identical phrasing does not fracture one real pattern into two), and only turns a group into a reviewable card once enough separate jobs have backed the same behavior. A single one-off observation never earns a card on its own.

For each group that clears that bar, Verinode builds a card headlined by its highest-confidence snippet, carrying up to three supporting snippets as evidence. If a matching group from an earlier run is still open, a new agreeing observation grows that same card's count and refreshes its evidence rather than creating a duplicate.

The To Confirm figure

On the hero panel, next to the SOPs-written headline, a secondary figure reads To Confirm with the count of pending observations underneath it. It reads "Patterns Waiting On You" when the count is above zero, or "Nothing Waiting" when your queue is clear.

On the Explore row, a matching metric tile repeats the same count, labeled To Confirm, with "Tap To Confirm" underneath when there is a backlog or "Nothing Waiting" when there is not. When there is a backlog, a small grid of dots below the number fills one dot per pending observation in an amber tone, so the size of the queue reads at a glance without opening anything. Clicking the tile opens All Processes filtered to Pending Confirmations.

Both figures count every individual observation still pending, including ones that have not yet been grouped into a reviewable pattern card. That is a different number from the count on any single pattern card, which only reflects the observations that particular card grouped together.

The pattern-to-confirm card

Each qualifying group appears as its own card at the end of the Explore row, oldest first, so working the backlog in order clears the longest-standing pattern before the newest capture. When nothing is waiting, the row simply ends after its four metric tiles, there is no placeholder card for an empty queue.

Each card 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 grouped into this card.
• The inferred step in bold, the behavior Verinode believes it found (for example, "Photograph moisture readings before setting equipment"). If nothing specific was inferred, the card falls back to the evidence snippet, 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 own jobs, so you are never confirming a black box. If no usable snippet was kept, this line is skipped.
• A category and work type line at the bottom (for example, "Water Mitigation · Residential").

1. 1Confirm. Click Confirm if the pattern is accurate as written. The button reads "Confirming…" while it saves, then the card toasts "Pattern confirmed." Every observation that fed this card flips to status 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 card swaps to a text box pre-filled with the inferred step so you can refine the wording. Click Save & confirm (disabled until you type something) and the card 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.
3. 3Dismiss. Click Dismiss if the pattern is not real or does not matter. The card toasts "Pattern dismissed." The observations behind it are not deleted, they are unlinked and returned to a pending, unclustered state, so if the same behavior shows up again across future jobs, the clusterer can group a fresh card from it later.

If a save does not go through, the card toasts "Couldn't confirm, try again" or "Couldn't dismiss, try again" and leaves everything exactly as it was.

Inside one observation's detail card

Open All Processes, filter to Pending Confirmations, and click any row to open that single observation's own detail card, separate from the pattern card above it. This is where you see the full trail behind one specific observation: where it came from, how confident Verinode is, and what else it might roll up into.

The header. The eyebrow reads "Pending Confirmations" with a status pill beside it (Healthy once confirmed or edited, Drift while pending, Exposed if a related process issue is waiting on it). The title is the inferred step itself, or "Pending observation" if none was captured. Underneath, a subtitle line gives you the actual next step, and its wording changes with the observation's state:

• Already confirmed or edited: "Confirmed, promote into a documented SOP step."
• Already dismissed: "Dismissed, no further action."
• Pending, with an open process issue tied to it: "Confirm or dismiss, a process signal is waiting on this."
• Pending for more than two weeks: "Confirm or dismiss, pending [N]d."
• Freshly pending: "Quick confirm, [N]% confidence from [the specialist that captured it]," or "Quick confirm, captured by [that specialist]" when no confidence score was recorded.

The quick facts. A row of four figures sits under the header:

• Status: Pending, Confirmed, Edited, or Dismissed.
• Confidence: the observation's own confidence score as a percentage, or a dash if none was recorded.
• Cluster: how many other pending observations share this one's category, plus this one, with a "similar pending" note when there are any. This is a live count of nearby pending observations, not necessarily the exact group a completed pattern card was built from.
• Captured: the date this specific observation was logged.

Inferred Step. The full inferred-step text, the pattern type when Verinode tagged one, who or what first captured it ("Captured by," naming the specialist, for instance the detector that reads through job documents and conversations, or the coach that runs a scheduled monthly check-in), and the observation's status.

Source, or Sources (N). One row per piece of evidence behind this observation. Verinode explains it plainly above the list: each row is an artifact the detector saw on its way to this inferred step, and confirming rolls these up as evidence on the resulting SOP step. Each row shows:

• A label for what kind of artifact it was: Email, Voice note, Photo, Upload, or Attachment (an unrecognized type is humanized rather than shown as a raw code).
• How long ago it was captured, in relative time ("4h ago," "3d ago"), and a confidence percentage when one was recorded for that specific source.
• The quoted snippet itself, when one was kept.
• A short caption naming the artifact it came from, for example "from email" followed by a short id, or "from upload" followed by the file name, so you can trace the observation back to where it came from.

Similar Pending (N). Other observations still pending in the same category, newest first, up to eight, each showing its own inferred step, who captured it, when, and its confidence. Verinode notes why this section matters: confirming a few of these together is what trips the cluster and lets the SOP-drafter draft an update for you. This section only appears when there is at least one sibling observation to show.

Target SOP. When you already have an active SOP in the same category, it appears here as the promotion target, its title and how many steps it has already, with a note that it is "ready for an additional step." This section is omitted when you have no SOP yet in that category.

What confirming actually changes

Confirming or dismissing happens at the pattern-card level, and it cascades down to every individual observation the card grouped together:

• Confirm flips the card's status to Confirmed and every contributing observation's status to Confirmed in the same action.
• Confirm with an edit flips the card to Edited, stores your rewritten text separately from Verinode's original inference, and still cascades the contributing observations to Confirmed.
• Dismiss flips the card to Dismissed. The contributing observations are not deleted or marked dismissed themselves, they are unlinked and go back to being pending and unclustered, free to regroup into a fresh card later if the same behavior shows up again.

Only confirmed or edited patterns feed the Business Analyst as evidence. A dismissed one teaches Verinode nothing further about that particular grouping, but the door stays open if the underlying behavior turns out to be real after all.

Empty states

• No pending observations at all. The hero reads "Nothing Waiting," the Explore row's To Confirm tile reads "0" with "Nothing Waiting" and an empty dot preview, and the Explore row shows only its four metric tiles with no pattern cards after them.
• No supporting snippet kept for an observation. The evidence line is skipped rather than shown blank.
• No confidence score recorded. The figure reads a dash instead of a percentage.
• No sibling observations pending in the same category. The Similar Pending section is omitted entirely.
• No SOP yet in the observation's category. The Target SOP section is omitted.
• A confirm, edit, or dismiss action fails. The card shows an error toast and stays exactly as it was, nothing in the queue is lost.

None of these are broken screens. Each one means the underlying evidence, your job history, the documents and conversations Verinode reads from, has not caught up yet, or genuinely has nothing to show for that slot.

Best-practice example

Say a card on the Explore row reads "Pattern to confirm, 4× captured, Photograph moisture readings before setting equipment, Water Mitigation · Residential." Before deciding, open All Processes → Pending Confirmations and click into one of the contributing observations. Its Sources section shows two email attachments and a voice note, all landing within the same week, each with a confidence above 80%, and Similar Pending shows one more observation in the same category still forming. That is a well-supported card: back on the Explore row, click Confirm, and it becomes real, evidence-backed input for how the Business Analyst reads your water jobs going forward. If the wording were close but your crew actually photographs readings after setting equipment rather than before, Edit the card, correct the order, and Save & confirm, your phrasing becomes the record instead.

Related reading

• Explore metrics and confirming patterns Verinode spotted
• The Processes section
• Acting on decisions
• The decision workspace
• Connecting your data
• Forwarding documents

Data sources