Processes with a client and how each carrier pays you

What "process" means on a client

Every client relationship runs on a process, whether or not it is written down: the categories of work you actually do with that client (water, fire, mold, reconstruction, contents), and the sequence of dates each job moves through to get paid. Verinode reads both from your own job records and surfaces them in two places on the Clients section:

• The Processes tab inside a client's detail card, one row per category of work you run with that specific client, matched against the Standard Operating Procedure (SOP) you have on file for it.
• The How Carriers Pay You panel at the bottom of the Clients home page, one row per carrier, showing how long that carrier takes to pay once billed and how long it takes your crew to mobilize once a job is assigned.

Both read from the jobs you already have on file. Verinode does not create a process for you and does not decide which category needs an SOP first, it groups what is already happening and points at the gaps.

Where to find it

Open Clients from the sidebar at iq.verinode.ai/clients. From there:

• Click any client tile to open its detail card, then select the Processes tab (alongside Overview, Jobs, Scorecards, Intelligence, and the other tabs on that card). The tab's badge shows a count, the number of categories in play plus the number of linked SOPs found.
• Scroll to the bottom of the Clients home page itself, past the row stack, for How Carriers Pay You. It renders once, for the whole client list, not per client.

The per-client Processes tab

What it is. For each category of work you have run with this client, Verinode counts the jobs, works out an average cycle time, and checks whether you have a matching SOP in your Process hub. A client relationship with real volume and no matching SOP is exactly where process intelligence earns its keep, so that combination gets a prompt to fix it.

How categories are decided. Verinode reads each job's category and normalizes it into one of five SOP categories: Water, Fire, Mold, Reconstruction, or Contents. A job whose category does not map cleanly to one of those (or has none recorded) lands in General. This is the same category vocabulary your SOPs are written against, so a job and an SOP can be matched directly.

What each row shows.

• Category name (Water, Fire, Mold, Reconstruction, Contents, or General), as the row title.
• Job count and average cycle time, as the subtitle, for example "6 jobs · 14d avg cycle." The cycle-time figure is the average number of days from Assigned to Completed, counted only across jobs that have finished (an active job in progress does not get a cycle time yet, since it has not reached Completed). If none of the category's jobs have both dates on file, only the job count shows.
• One of three states on the right side of the row, depending on volume and whether an SOP is matched:

- SOP on file. The category has a matching SOP. The subtitle appends the SOP's title (for example "6 jobs · 14d avg cycle · Water Mitigation Standard"), a small "SOP on file" tag sits on the right, and the whole row is clickable: it closes the client card and opens /process?highlight=<sop id>, landing you directly on that SOP inside the Process hub. - Create SOP. The category has enough jobs to be a real pattern (three or more) but no SOP matches it yet. A Create SOP button appears on the row. Clicking it closes the client card and opens /process?action=create&category=<category>, dropping you into the Process hub's SOP editor with the category pre-filled. - Watching. The category has fewer than three jobs and no SOP. The row shows a muted "Watching · N more jobs" note, counting down how many more jobs it would take to cross the volume that triggers a Create SOP prompt. This keeps Verinode from asking you to formalize a process off one or two jobs.

Sort order. Categories are ordered by job count, busiest first, so the category you run most with this client is always the top row.

Empty state. If this client has no jobs on file yet, the tab reads exactly:

"Process signals populate once jobs with [client name] are on file. Verinode groups them by category and matches against your SOPs."

Related SOPs, below the category rows

Underneath the category list, for Carrier and TPA clients only (not Private Pay or Commercial), Verinode adds a second block: every SOP that links to this specific carrier or TPA, independent of category. Verinode links an SOP to a client automatically when the link is documented from a job, detected from an uploaded document, or set manually in the SOP editor, no manual tagging is required for it to show up here.

While it loads, the block reads "Resolving linked SOPs…"

Once loaded, it opens with a count line, "N SOPs on file," then one row per linked SOP:

• Title, the SOP's name.
• Underneath, a meta line: the SOP's category (Water, Fire, Mold, Reconstruction, Contents, or General), followed by its status when the SOP is not active (for example "· Draft"), followed by how the link was made when it was not a manual or direct link: "· Detected from a document" or "· Detected from job execution." A manually linked or directly linked SOP shows no extra tag, since that is the default.
• An Open button that closes the client card and takes you to /process?highlight=<sop id>, the same destination as clicking a matched category row above.

If this client has no linked SOPs at all, the block simply does not render, only the category rows above it show. For Private Pay and Commercial clients, this block never appears, since carrier and TPA relationships are what SOPs are typically written against.

How Carriers Pay You, on the Clients home page

What it is. This panel answers a narrower, sharper question than the per-category cycle times above: for each carrier, how long does it take to get paid once you bill them, and how long does it take your crew to actually start once a job is assigned. It reuses the same milestone-mining engine that powers the Process hub's job-lifecycle view (Assigned, Estimate submitted, Carrier approved, Started, Completed, Billed, Paid), sliced here per carrier instead of across your whole book.

What you see. A heading, "How Carriers Pay You," with a count on the right ("N carriers"), and underneath it: "Your own jobs, split by carrier: how long each one takes to pay once billed, and how long it takes your crew to mobilize once assigned." Below that, one row per carrier:

• Leading logo and carrier name.
• Subtitle, the number of jobs this carrier's numbers are built from.
• Value, on the right: up to two figures, separated by a dot: "12d to pay" (the median days from Billed to Paid) and "3d to start" (the median days from Assigned to Started). Either figure can be missing if that particular transition does not have enough dated jobs behind it yet, in which case only the figure that is available shows.

Sort order. Slowest payer first, the carrier with the longest Billed to Paid median sits at the top. Carriers where that figure is not yet available (only an Assigned to Started read exists) sort to the bottom, after every carrier with a real pay-speed number.

Where the numbers come from. This reads directly from your own jobs table: the Assigned, Started, Completed, Billed, and Paid dates on each job, matched to the carrier attached to it. Archived carriers are excluded. Because this is your own CRM data, not a peer or anonymized read, no cohort anonymization applies to it, this is not a benchmark against other operators, it is your book, sliced by carrier. For how your pay speed compares to peers, see How benchmarks work.

Gating. A carrier only earns a row once it has enough dated jobs on the books for the median to mean something, a single job does not produce a reliable "days to pay" figure. Carriers below that bar simply do not appear yet, there is no placeholder row for them. If no carrier in your book clears that bar, the entire panel is omitted, no heading and no empty-state message, since a panel with nothing real to show is worse than no panel.

How the two views relate

The per-client Processes tab and the home-level carrier lens measure different things and should not be read as the same number:

| | Per-client Processes tab | How Carriers Pay You | |---|---|---| | Scope | One client at a time | Every carrier at once | | Grouped by | Category of work (Water, Fire, etc.) | Carrier | | Measures | Assigned to Completed (average) | Billed to Paid, Assigned to Started (medians) | | Purpose | Spot which categories need an SOP | Spot which carriers are slow to pay or slow to mobilize |

Use the Processes tab when you are deciding whether a specific client relationship needs a documented process. Use How Carriers Pay You when you are deciding which carrier relationship is costing you the most in cash-flow terms, then cross-reference Cash flow and runway for what a slow carrier does to your AR aging.

Best-practice example

Open a carrier client and its Processes tab shows Water at "9 jobs · 11d avg cycle" with a Create SOP button, Fire at "2 jobs" watching, and Reconstruction with an SOP on file already. Write the Water SOP first, since it is the category with real volume and no documented process. Then check How Carriers Pay You on the Clients home page: if this same carrier sits near the top of that list with a high days-to-pay figure, the conversation is not just process, it is collections. Both signals point at the same relationship from two different angles, and neither one replaces the other.

Related articles

• Clients and carriers
• The decision workspace
• Cash flow and runway
• How benchmarks work
• Forwarding documents
• Connecting your data

Data sources