Process findings and Take Action decisions

What this page shows

Processes is where Verinode reads how your work actually flows, not how your SOP says it should. It compares your written procedures against the patterns it observes in your job history, against the standards for your trade and state, and against the pace of operators like you, then turns the gaps it finds into decisions you can act on. This article covers the Take Action row on the Processes home and the Findings tab inside the Processes card slider: the two places open process decisions surface, plus the four kinds of tiles that seed that row before a single decision exists.

Two companion articles cover the rest of Processes: how the mining metrics further down the page work, and how the pending-pattern queue and standards library behave. This article is scoped to decisions and the tiles that lead into them.

Where to find it

Open Processes from the sidebar. The route is /processes.

The page opens on a hero panel ("SOPs written," with your count of written SOPs and a pill showing the percentage of your service lines with an SOP), and directly under it sits the Take Action row, the first thing after the headline, on every page in Verinode. Below that is an Explore row of four metric tiles, then How your work flows (the mining metrics), then Most recent, a roster of your latest SOPs, confirmed patterns, and standards.

Clicking any open decision, or the Findings tab of the Processes card slider, opens the same decision detail: the full Act / Not now / Why workspace lives at /decisions/[id].

The Take Action row

The Take Action row always opens with up to four seed tiles, in this fixed order, before any decision tiles:

1. An agent activation tile
2. An unlock-section tile
3. A Write an SOP launch tile
4. A QA Audits launch tile

Then, after those four: one tile per open process decision, or an empty-state message if there are none.

1. The agent activation tile

The first tile in the row, styled as a copper album-cover graphic with the Processes glyph watermarked into it and an "Ask IQ" chip. Clicking it opens the AI Co-COO panel on the right with a Processes-specific opening message already queued and the reply box ready, so your first question and your first IU spend happen in the same click.

This tile is self-retiring. Once you have any conversation history anchored to Processes, from any device or session, it disappears permanently and does not come back.

2. The unlock-section tile

A copper-tinted tile that reads your current data state for Processes and tells you exactly what's missing, by name.

• Cold (you have nothing yet): headline reads "Upload Your Data To Switch It On," with the specific exports Processes needs, each one labeled by the source tool it comes from.
• Partial (some sources in, some missing): headline reads "N Of M Sources In. Add The Rest.," listing which inputs are present and which are still missing.
• Complete: the tile disappears.

Every row lists the exact export or upload Processes is waiting on, not a generic "connect your data" nudge. This tile only shows the gap; the actual upload runs through the Add Process button in the page header or the send-data control, which opens the same capture flow either way.

3. Write an SOP

A dark, animated launch tile: eyebrow "SOPs," subtitle "Write down how your team works best," a pulsing "Live" dot, and a Generate button. Clicking it opens the SOP generator deck in an overlay on top of the page, nav and IQ panel still in place. Inside, it previews a sample playbook scored for wasted steps and shows how yours will compare to peer playbooks once you have written one, then lets you draft a real SOP from scratch.

4. QA Audits

The fourth seed tile: eyebrow "QA Audits," subtitle "Score a job, crew, or process," with a Preview button (its archetype runs a scored audit rather than a generator, so the call-to-action reads differently from the SOP tile). Clicking it opens the QA audit deck, which walks you through scoring a job, a crew, or a process against a rubric (workmanship, documentation, safety on site, and similar dimensions) and saves the result as a scored record.

Decision tiles

After the four seed tiles, every open process decision renders as its own tile. Most decisions use the same shared decision-tile design every other section on Verinode uses (jobs, vendors, clients, team, equipment, safety, compliance, recruiting, certifications, reputation, margin), so Processes reads as one system with the rest of the platform:

• Eyebrow: always "Recommended." Every decision Verinode surfaces is one it thinks is worth acting on; there is no separate "just FYI" tier.
• Headline: a dollar figure when the decision carries a quantified impact (for example, "$1.2k/mo," using the /mo or /yr suffix that matches how the impact was measured), or a plain-language title when it doesn't.
• Sub-line: under a dollar headline, a short topic sentence naming what the figure is about, for example "Your dry time is slipping against peers," so the number is never floating without context.
• Center column: the entity the decision concerns (a vendor, a process, or your own book, shown as "Portfolio" when nothing more specific applies), a row of lifecycle dots, and, when Verinode knows which way the underlying metric is moving, a trajectory line: an up arrow and "Improving," a down arrow and "Declining," or a right arrow and "Stable."
• Lifecycle dots: Flagged, Planned, Acting, Resolved. The current stage lights up depending on whether you've acted on the decision yet, whether an action plan exists, how many of its steps are complete, and whether the underlying issue has resolved.

Clicking a decision tile opens the full decision workspace in an overlay: the complete case, the proof behind it, and the Act, Not now, and Why buttons. See the decision workspace for how that overlay behaves once it opens, and acting on decisions for what happens after you click Act.

The Adoption Gap tile: one-click "Adopt now"

One kind of process decision gets its own tile instead of the shared design: adoption-gap decisions, the ones Verinode raises when a written industry, LEAN, OSHA, EPA, or state standard exists for something you don't yet have an SOP for. This tile is smaller (a standalone card, not the double-wide decision tile) and carries its own inline action:

• Eyebrow: "Adoption Gap," with a copper "One-click fix" label on the right.
• Body: the decision's title and, below it, a short line on the consequence of leaving the gap open.
• Adopt now button: click it and Verinode copies the standard's steps straight into a new draft SOP in your library, no typing required. While the copy is running the button reads "Adopting…"; once it finishes you get a toast, "Draft SOP created. Refine the steps and activate when ready," and the page refreshes so the new draft shows up in Most recent and in the All Processes tab.
• Details button: opens the same decision workspace as any other tile, in case you want the full case before adopting.

If the adopt action fails for any reason, you get an error toast ("Couldn't adopt, try again.") instead of a silent failure.

1. 1Scan the Take Action row for a tile labeled "Adoption Gap."
2. 2Read the consequence line under the title to understand what the gap is costing you.
3. 3Click Adopt now. Verinode scaffolds a draft SOP from the matching standard's steps.
4. 4Watch for the confirmation toast, then open the All Processes tab (kind filter: My SOPs) to find the new draft.
5. 5Edit the draft's steps to match how your crews actually work, then activate it when you're satisfied.

You can reach the same one-click adopt from a second place: the By Standard tab of the Processes card slider carries an Adopt button on every standard row, so you don't have to wait for a decision to surface before adopting a standard you already know you want.

When the row is empty

If you have no open process decisions, the seed tiles still show (agent activation, unlock, Write an SOP, QA Audits, in whatever combination applies to your data state), and after them the row reads, verbatim:

"Nothing needs a decision right now. When a job runs slower than your SOP or your peers, it shows up here."

This is not a broken screen. It means Verinode is not currently seeing a gap between your written procedures, your job history, and the standards or peer pace it's checking against.

The Findings tab

The Processes card slider (opened from any process record, or from a decision tile's Details link) carries six tabs: Findings, Flow, All Processes, By Standard, Coverage, Benchmarks. Findings is the first tab and lists every open process decision in the same grid used across the platform's other sections, so you can browse the full set without scrolling the home page's Take Action row. Clicking a card here opens the same decision workspace overlay, and with several decisions open you can swipe between them without closing the panel.

The Flow tab, immediately to its right, is where every process-mining metric lives in full (grouped by Your jobs, Pace and outcomes, Drying performance, and each support process), not just the curated subset shown on the home page's "How your work flows" row. That tab, along with All Processes, By Standard, Coverage, and Benchmarks, is covered in the companion articles on process mining and the SOP library.

How decisions get here

A process decision starts as one of two things: a finding, a comparison Verinode's detectors ran across your SOPs, your observed job patterns, and the relevant standards or peer cohort, or a concrete action recommendation tied to a specific fix. When both exist for the same issue, Verinode merges them into one decision so you see the loss framing and the concrete next step together, not two separate cards.

Every decision carries a confidence label ("We're sure about this," "Strong signal," or "Early signal, more data helps"), an effort estimate ("Takes 5 minutes" through "Multi-step project"), and a realization window (how soon you'd expect to see results if you act). None of that appears on the home-row tile itself; it's part of the full workspace behind the click.

Decisions only appear in Take Action while they're still awaiting a call: pending, or snoozed after you park them. Once you act on one, it drops off this row and moves into your action-plan tracking inside the decision workspace; once it resolves, its outcome lives in your decision history, not back on this row. That's deliberate: Take Action is a to-do list, not a running log of everything Verinode has ever noticed.

Coverage and pending confirmations at a glance

Two numbers from the hero panel and Explore row are worth calling out because they drive which decisions you'll see:

• Lines Without An SOP: your active service lines minus the ones with a documented SOP. A nonzero gap here is exactly what feeds Adoption Gap decisions once a matching standard exists for that gap.
• To Confirm: patterns the nightly clusterer has spotted in your job history but hasn't turned into a written step yet. These live in the Explore row as their own confirm-or-dismiss tiles, separate from decisions, and are covered in the companion pending-confirmations article. Confirming a pattern is how an observed habit becomes a documented step your SOP can be measured against, which is often the raw material behind a future decision.

Best-practice example

Say your Take Action row shows an Adoption Gap tile for water-mitigation drying, alongside two ordinary decision tiles for recruiting and cost. Read the consequence line first: it names what's slipping and roughly how much it's costing. Click Adopt now on the Adoption Gap tile to get the standard's steps into a draft immediately, then use the Details link only if you want the full case before you commit. For the other two decisions, open each one to see the proof and the concrete action, and use Not now to park anything you're not ready to work this week rather than letting it clutter the row: parked decisions still count toward your lifecycle dots but stop demanding attention until you're ready.

Data sources

Related reading: The decision workspace, Acting on decisions, The Feed, Connecting your data, Forwarding documents, Understanding your margin.