How your work flows: reading the process-mining row

What this row is

"How your work flows" is Verinode's process-mining read on your own book. Every job, supplement, recruiting file, incident, purchase, lead, and review you run already carries dates on it: assigned, started, completed, billed, paid, submitted, responded, hired, occurred, closed. Nobody sits down and mines those dates by hand. Verinode does, turning them into stage-by-stage timing so you can see exactly which step is eating the calendar instead of guessing.

Verinode does not run your operations or decide what to fix. It reads the dates already sitting in your data, does the arithmetic honestly (real sample sizes, no invented medians, out-of-order dates excluded rather than averaged in), and shows you where the time goes. You decide what to act on.

Where to find it

The Help Center files this topic under Excellence, but you will not find a page in the sidebar with that name. Open Processes instead, under the Operations group in the left sidebar, at iq.verinode.ai/processes. Visiting /excellence directly takes you to the same workspace. It is a one-line redirect left in place so an old link still lands you somewhere real.

Processes is a Premier membership feature. Below Premier, the page still renders in full layout, but the SOP library, this row, and peer benchmarks sit blurred behind an upgrade prompt. If the section itself hasn't been switched on for your account yet, you'll see a short activation screen first, with a note that nothing runs until you say so.

Once the page is live, the rows stack top to bottom: the hero band (SOPs written, coverage), Take Action (decisions waiting on you), Explore (four KPI tiles plus any patterns awaiting confirmation), How your work flows, which this article covers, and Most recent (your latest SOPs, patterns, and standards).

Why the row hides until you have job history

The row's title always sits on the page. What fills the space under it depends entirely on whether any of your registered processes has cleared its own data floor. Until at least one has, the whole row collapses to a single line instead of tiles:

"Add your job history and we'll show how long each step takes, and where jobs slow down."

That is not a broken screen. It means none of your dated processes have enough in-order history yet to trust a number. As job dates, supplement dates, recruiting dates, and the rest flow in, tiles appear one process at a time, in whatever order the underlying data clears its floor.

The roster: one tile per process

Once at least one process qualifies, the row renders as a roster: one tile per process you actually run, never a jumble of raw stage names sitting side by side. Verinode currently mines, in this order when each has data:

• Jobs. Your core lifecycle: Assigned, Started, Completed, Billed, Paid.
• Exterior. The same lifecycle, sliced to just your exterior and roofing jobs, so a roofing-heavy book sees its own timing instead of a blend with water and fire work.
• Supplements. Submitted to Responded, the carrier's turnaround on a supplement package.
• Recruiting. Received, Interviewed, Hired, your applicant pipeline.
• Safety. Occurred to Action Closed, how long an incident stays open before its corrective action closes.
• Purchasing cycle. Ordered to Invoiced, your procurement cycle on material invoices. Received and Paid dates are captured when a supplier prints them, but only Ordered and Invoiced are dated reliably enough to time today.
• Lead response. Received, First response, Converted, how fast a new lead gets worked and whether it becomes a job.
• Review response. Posted to Responded, how quickly you reply to a customer review.
• Drying. A different shape from the rest, covered on its own below.

A process you don't run never shows up. A business that doesn't recruit never sees a Recruiting tile; one that has never logged a drying job never sees Drying. Nothing is hidden on purpose, it simply hasn't produced a number yet.

Reading a tile

Every tile shows:

• A label. Jobs, Exterior, Supplements, Recruiting, and Safety carry their short process name. Purchasing, Leads, and Reviews render under their fuller descriptor names instead: "Purchasing cycle," "Lead response," "Review response."
• A day count as the headline value, the median time that stage takes across your own qualifying cases.
• A sub-line. When a process has more than one stage transition clearing the floor, the tile shows its slowest one: "Slowest: Started to Completed." When a process has only one possible transition (Supplements, Safety, Reviews, Purchasing all mine a single stage-to-stage gap), the sub-line just names it plainly, with no "Slowest" label, because there is nothing else on that process to be slowest against.
• A small chart. A marker bar shows your median against the peer median where a comparison exists; the process tiles that fall back on Drying's own count of logs instead show dots or segments rather than a bar.
• A color. For every ordinary process tile, copper-red means you're running slower on that stage than operators like you, green means faster, and steel blue means there's no peer group to compare against yet. The color only turns red because you're actually behind peers, never just because a stage happens to be that process's own internal slowest.
• A peer delta, formatted as, for example, "+2d vs Peer" or "-1d vs Peer," once enough comparable operators are contributing the same stage for a read to exist. Until then the tile carries your own number alone, never a manufactured comparison.

Drying and Jobs (once its richer read kicks in) each break from this pattern in their own way, covered next.

The Jobs tile: discovered flow, or the fallback bottleneck

Jobs gets the richest treatment of any process here. Two different reads can sit behind the same tile, and Verinode always uses the better one available:

• Discovered flow, once Verinode has enough case-tied activity on your jobs, not just the five milestone dates, but the real sequence of steps your work traveled, including any that repeat. The tile reads the slowest gap in that discovered sequence, for example "Jobs · 6d · Slowest: Billed to Paid," and always renders steel blue with no peer-delta badge on the tile itself. The peer comparison for that gap, when one exists, lives inside the detail card instead.
• The milestone bottleneck, the same read every other process tile uses, until the richer discovered flow becomes available. In that state the Jobs tile behaves exactly like any other transition tile: it can turn green or copper-red against peers, and carries a peer-delta badge when a comparison exists.

Either way, clicking the tile opens the same detail card, described below.

The Drying tile

Drying isn't a stage-to-stage lifecycle like the others, so its tile is built differently and always renders teal, never colored by peer comparison (that read is a follow-up surface, not live yet). Once you have enough dried jobs on record, the tile shows your median days to dry, plus, when available, median equipment-days per job. The sub-line reads "Typical dry time." Below the sample floor, it instead shows the raw count of drying logs captured so far, with the sub-line "Drying logs so far," because a median built from only a couple of jobs would mislead.

Clicking a tile: the Flow tab

Click any tile in the row and it opens the Flow tab of the Processes card slider, drilled straight into that tile's own detail card. The slider carries six tabs across the top (Findings, Flow, All Processes, By Standard, Coverage, Benchmarks); Flow is where every process-mining metric lives, curated home tile or not.

The complete list groups every metric under a labeled heading with a small colored dot: Your jobs (every job-lifecycle stage, the routes your jobs actually took, and recent claim journeys), Pace and outcomes, Drying performance, and then one group per other process you run: Recruiting, Supplements, Safety, Exterior, Purchasing cycle, Lead response, Review response. Swiping from a drilled card pages you through the full list in that same order.

What the detail card shows depends on what kind of metric you tapped:

A stage bottleneck (Jobs' fallback read, Exterior, Supplements, Recruiting, Safety, Purchasing, Leads, Reviews). The card leads with the day count and a plain sentence: going from one stage to the next takes about that many days on a typical case, naming it as your slowest stage when it is one, and stating how many days faster or slower than operators like you when a comparison exists. Below that, "Where your time goes" breaks out every stage transition on that process side by side as bars, and "How you compare" shows your median next to the peer median plus the range most comparable operators fall in, when enough peer data exists. A closing note states how many of your own cases the number rests on, and that half clear the stage within the median while the slow ones stretch out well past it.

A job path. These live only in the Flow tab's "Your jobs" group, not on the curated home row. The card leads with what share of your completed jobs followed that exact route, for example "38% of completed jobs. This is how most of your jobs run," and, where enough of those jobs have a full cycle, how long that route typically takes start to paid. "The rest took other routes" bars out where the remaining jobs went. A closing note is explicit that different routes aren't mistakes: a deposit-first job or a same-day mobilization simply runs a different clock than the standard flow, scoped to roughly the last twelve months of completed work.

Pace and outcomes. Also Flow-tab-only. Some processes clear a stricter bar: enough jobs with both a stage duration and an outcome (margin or satisfaction) to say something about how pace relates to results. The card leads with the point spread between your fastest and slowest jobs on that stage, then breaks the two bands out as bars with their own sample counts. It states plainly that this is a pattern in your own book, not proof that one causes the other.

Drying performance. The overall card leads with your median days-to-dry and equipment-days, then breaks losses out by IICRC S500 water class (Class 1 through 4), since a Class 4 loss legitimately takes longer to dry than a Class 1. Below the sample floor it shows your log count and how many jobs have finished instead of a fake median. Tapping a single class shows just that class's typical dry time and the case count behind it.

Claim journey. Flow-tab-only. Tapping a recent job with at least two lifecycle dates on record shows which stage it has reached and how many of its five lifecycle stages it has moved through, with an Open job button that takes you straight to that job's own detail card.

Discovered job flow. When the richer read is available for Jobs, its card leads with the real sequence most of your jobs travel and names the single gap eating the most time, in plain language, worded around what's happening during that wait rather than the raw two-stage name (so it reads "the most time goes into getting paid," not "Billed to Paid"). "Where your time goes" breaks every gap in that discovered path into bars. "How you compare" appears when a peer read exists for the slowest gap. "Other routes jobs took" shows the next most common sequences your jobs actually followed. If a step tends to repeat before a job moves on, a note calls that out too, a step that comes back usually means a handoff is bouncing.

Data-quality guardrails behind every number

A few things happen before any duration reaches a tile or a detail card:

• Out-of-order dates never enter a median. If a job's Paid date lands before its Billed date in a way that isn't a recognized legitimate pattern, that pair is excluded from the stage's math rather than silently averaged in.
• Extreme outliers are capped, not deleted. A single date typo, a year-off entry that turns a 30-day wait into a 395-day one, is capped to a statistically reasonable ceiling before medians are calculated, once a stage has enough cases to define a sensible range. Your genuinely long reconstructions are never touched by this; only implausible entries are capped.
• Job paths are classified, not judged. A payment dated before the bill often means a deposit or advance and is labeled "Deposit-First." A missing start date often means same-day mobilization, labeled "Same-Day Start." Only orderings that genuinely cannot happen on the ground, a payment or completion dated before the job was even assigned, are flagged as impossible, and those feed a separate data-quality prompt elsewhere in Processes rather than quietly polluting your timing numbers.

What's still catching up

Below the grouped list, the Flow tab appends honest notes rather than leaving you to guess:

• If any of your registered processes hasn't cleared its floor yet, a line names them: "Your [process names] will appear here as that data flows in."
• If your account has peer comparisons unlocked but no cohort has formed yet for any of your qualifying transitions, a separate line says so: comparisons to operators like you switch on once enough operators are contributing the same data, not on a fixed schedule.

Neither note is an error. Both are Verinode being honest about where the data, yours or the network's, still needs to catch up.

How to use it

1. 1Scan the roster for the reddest (copper) tile: the process running slower than operators like you, or, with no peer read yet, the stage where your own book spends the most time.
2. 2Click it to open the Flow tab detail card and read the verdict line first. It names the exact gap in days and, when available, how you compare to operators like you.
3. 3Check "Where your time goes" to see whether the bottleneck is isolated or whether every stage in that process runs long.
4. 4When a peer comparison is showing, read the typical range most peers fall in alongside the median, not just the single number, before deciding the gap is worth acting on.
5. 5If a related decision already exists (a stage slower than your own SOP or your peers), it is waiting in the Take Action row above this one, not buried at the bottom of the page.

Best-practice example

Say your Jobs tile reads "6d · Slowest: Billed to Paid," colored copper, with a peer delta of "+2d vs Peer." Open it. The detail card confirms billing-to-payment is your slowest stage and that you're running behind operators like you, with most of them collecting in a noticeably tighter window. "Where your time goes" shows every other stage in your lifecycle is tight by comparison, so this is the gap actually worth working. From there you might check the Cash Flow view to see whether the same billing-to-payment gap shows up as aging receivables, or open the decision workspace if Verinode has already turned the pattern into something you can act on.

Related reading

• Excellence (Processes): the fractional-COO process coach, the full home page, row by row
• How your work flows: process mining on your jobs, the same row under the Processes section name, with deeper detail on every metric kind
• The decision workspace
• Acting on decisions
• The Feed
• Understanding your margin
• The Benchmarks section
• How Verinode's benchmarks work
• Reading a benchmark
• Clients and carriers
• Forwarding documents
• Connecting your data

Data sources