Take Action: process decisions and one-click adopt

What the Take Action row shows

Every restoration crew already has a way it runs a water loss, a fire job, a mold remediation. Most of that knowledge lives in someone's head, not on paper, which means it cannot be checked against a carrier's expectations, taught to a new hire, or compared to how the fastest operators in your peer group run the same job. The Take Action row on the Processes page is where Verinode turns that gap into specific, doable moves: write the SOP you have not written yet, confirm the pattern the system already noticed your crew doing, or adopt a ready-made starting point in one click.

Verinode does not write your SOPs for you and does not decide which one to tackle first. It reads the SOPs you upload, the patterns it notices in how jobs actually run, and the standards your peers are scored against, then lays out what is missing and what would close the gap fastest. You decide what to act on.

Where to find it

Open Processes from the sidebar at iq.verinode.ai/processes. The page opens with a hero band (SOPs written, your total count, with a pill showing the percent of your service lines that have a documented SOP), then a stack of rows: Take Action, Explore, How your work flows, and Most recent. This article covers the Take Action row, the first row under the hero and the first thing you see after the headline number.

The hero's subtext keys off the same numbers the row below works from: if you have zero SOPs, it reads "Upload your SOPs to get started." If you have at least one SOP but some service lines still have none, it reads "N of your service lines have no SOP yet" (singular or plural matched to the count). Once every active service line has a documented SOP, it reads "Every service line has an SOP."

The four launch tiles that lead the row

Reading left to right, up to four tiles appear before any actual decisions: an activation tile, an unlock tile, and two feature-launch tiles. Each one is there to get you moving even before Verinode has anything specific to recommend, and each retires on its own once you have used it, so a section with an established SOP library shows a much shorter row than a brand-new one.

1. Agent activation: "Start here"

The first tile is an album-cover style card labeled Start here with the headline Talk to IQ. Its thesis line reads: "I map how you actually run the business, and surface where the way you work is leaking margin or causing rework."

Clicking it opens the AI Agent Panel on the right with a seed message written for Processes, and the input ready for your reply. With no process data yet, IQ opens with something close to: "I'm IQ. I map how you actually run, from intake to final invoice, and surface where what you do (or don't do) is leaking margin or causing rework. Right now I have no SOPs, no workflow descriptions, nothing to compare against. The fastest way in: describe one workflow to me in plain words ('this is how we handle a water loss'), or upload an SOP doc. The moment one lands I'll match it against the way other operators run the same process and flag the gaps that cost the most. What's the workflow you'd most want me to look at first: intake, scoping, supplements, or billing?"

The tile retires the moment you engage with it, clicking it, or having any prior conversation history anchored to the Processes page from an earlier session dismisses it for good.

2. Unlock the section

Next (when it appears) is a copper-bordered tile that tells you exactly what to upload to switch the section on. Processes lists a single input: your written SOPs, satisfied by any uploaded process document. With cold state (no SOPs at all), the tile reads Make Processes Work with the headline "Upload Your Data To Switch It On," and the promise underneath: "Upload your SOPs and we'll flag where your team isn't following your own steps." The button reads Add Data and opens the same capture panel as the header's Add Data button.

Because Processes only lists one input, there is no middle "partial" state for this tile the way richer sections show, once that first SOP lands, the tile has nothing left to ask for and retires. (It does not track individual missing pieces the way, say, a multi-input section would show a running "N of M sources in" count.)

3. Launch the SOPs deck

The next tile is a bold, dark card with a pulsing Live dot, titled SOPs with the subtitle Write down how your team works best. Clicking it opens the SOPs deck as an overlay on top of whatever you were looking at, navigation and IQ still in place. It has three tabs:

• Overview states the value plainly: "Capture how a job type runs, once," with the reasoning underneath, "Every crew runs it the same way. We flag the wasteful steps for you." Before you have written anything, it shows a worked example playbook, captioned "Example playbook. We score yours for waste and benchmark it." Once you have SOPs, the empty-state promise names what fills in: each SOP with its waste score, and how yours compares to peer playbooks.
• Library lists every SOP you have written, with a count badge in the tab. Each row shows the SOP's title, its category, and its LEAN waste score out of 100 when one has been computed (for example, "Water · 82/100"). Clicking a row takes you back to the Processes page.
• Write an SOP is the entry point: "Build a playbook from a chat, an uploaded doc, or a job estimate. The builder turns it into clear steps, scores it for waste, and shares it with the crew." The button reads Open the SOP builder.

This is the same deck the header's + Add Process button and the deck's own primary action (Write an SOP) both point at, one builder, three ways in: chat, upload, or estimate.

4. Launch the QA Audits deck

The fourth tile is the same dark card treatment, titled QA Audits with the subtitle Score a job, crew, or process. Its tabs:

• Overview: "Score a job, crew, or process in minutes," reasoning underneath, "Catch what slips before the carrier does. A rubric, a score, a shareable PDF." A worked example shows an 88% audit score, "Above your 85% pass bar," broken into Workmanship (9/10), Documentation (8/10), and Safety on site (7/10), each shown as a percent bar. Before you have run one, the empty state promises: audits in progress ready to resume, and completed audits with their scores.
• In progress lists any audit you started but have not closed, with a count badge. Each row names the job or crew being audited and a Resume link.
• Run an audit is the start panel where you pick a rubric and begin scoring.

The deck's primary action, Run a QA audit, jumps straight to that start panel.

Surfaced process decisions

Everything after those four tiles is either a real decision or the row's empty-state message. Most process decisions render as the same Recommended tile every section on the platform uses:

• Label: always reads Recommended.
• Headline: when the decision carries a dollar figure, the headline is that number ($5.0k, $2.2M, or a plain dollar figure under $1,000), with the period ("/mo" or the relevant period label) in smaller type beside it. Without a dollar figure, the headline is the decision's metric name written out in full, never a raw lowercase key.
• Sub-line: whenever the headline is a bare dollar figure, a line underneath names what the number is about, so a figure never floats without a subject.
• Action visual: a small logo or initial for the entity the decision concerns, its name, and a row of four lifecycle dots, Flagged, Planned, Acting, Resolved, the filled-in dot showing how far along the decision is. Below the dots, when Verinode has enough history, a trend arrow and label read Improving, Declining, or Stable.

Clicking one of these tiles opens the decision as a glass overlay on top of the page, where you see the full reasoning and recommended plan, and can act, snooze, or dismiss it. See the decision workspace for how that surface works across every section.

The one exception: Adopt now

One kind of process decision does not use that shared tile. When Verinode notices you offer a service line, water, fire, mold, reconstruction, or contents, with no documented SOP behind it at all, it surfaces an Adoption Gap tile instead: a bespoke card built for a single, one-click move.

This tile shows:

• A small eyebrow row: Adoption Gap on the left, One-click fix in copper on the right.
• The decision's title as the headline, and underneath, a short line naming the consequence of leaving the gap open.
• Two buttons at the bottom: Adopt now and Details.

Details takes you to the decision's full page, the same reasoning-and-plan view every decision opens into. Adopt now is the shortcut: click it and Verinode copies the recommended standard's steps, framework, and category straight into a new draft SOP under your account, no builder session, no blank page. While it runs, the button reads "Adopting…"; once it lands, a confirmation toast reads "Draft SOP created. Refine the steps and activate when ready," and the page refreshes so the new draft appears in your library, status Draft, titled after the source standard (for example, "IICRC S500 (draft)"), with the source standard's steps already scored for LEAN waste in the background.

That draft is a real starting point, not a placeholder: it carries the citation back to the benchmark it was adopted from, so the SOP's detail view can show where it came from, and it is scored the same way any SOP you write from scratch is. You still decide when to refine the steps and flip it from Draft to Active, Verinode has just removed the blank-page problem.

Empty state

When there are no open process decisions and no adoption gaps to surface, the row does not show a blank space. Instead it reads: "Nothing needs a decision right now. When a job runs slower than your SOP or your peers, it shows up here."

This is the only empty-state message the Take Action row on Processes uses, no multi-stage "still learning" or "all clear" variants, just the plain statement that nothing is currently flagged and what would trigger something to appear.

Best-practice example

Say you open Processes for the first time. The hero reads "0 SOPs written, Upload your SOPs to get started." In Take Action, the activation tile and the unlock tile are both still visible (you have not written anything and have not talked to IQ yet), followed by the SOPs and QA Audits launch tiles. Because you selected water and mold as service lines during onboarding but have documented neither, two Adoption Gap tiles sit in the row: one titled toward a water-loss standard, one toward a mold-remediation standard, each with a one-line consequence underneath and an Adopt now button. You click Adopt now on the water tile. A moment later a toast confirms the draft landed, and a new SOP titled after the source standard appears in your library as a Draft. You open it, read through the steps the standard shipped with, tighten the language to match how your crew actually talks about the job, and flip it to Active when you are ready. The mold gap is still sitting there for next time, one click away from the same shortcut.

Data sources

Related articles

• The decision workspace, how decision overlays, plans, and resolution work across every section
• Acting on decisions, what happens after you act, snooze, or dismiss
• Connecting your data, setting up forwarding and uploads so process data flows in automatically
• Forwarding documents, what document types Verinode recognizes and how to send them in
• Benchmarks overview and reading a benchmark, for the peer standards behind the adopted-standard tiles
• Understanding your margin, how a documented process ties back to what you keep on a job