Flow metric detail: where your time goes, vs peers

What this card is

Every row on the Flow tab, and every tile in the "How your work flows" row on the Processes home page, opens into the same card: one detail view built to answer one question in plain English, then show the number underneath it. Verinode calls this the flow metric detail card. It never invents a verdict; it reads your own job, supplement, recruiting, safety, purchasing, lead, review, and drying dates, and turns the stage timing already sitting in them into a sentence you can act on.

The card renders identically whether you open it from the web slider's Flow tab or from a tile on the mobile Processes home. Same math, same layout, same wording, so a reading you saw on your phone matches what you see back at a desk. Nothing on this card is a recommendation Verinode is making on your behalf. It surfaces where the time goes and, once enough peers exist, how that compares. You decide what, if anything, to do about it.

Where to find it

Web. Open Processes from the sidebar (/processes), then the Flow tab, the second tab across the card slider (Findings, Flow, All Processes, By Standard, Coverage, Benchmarks). Every row in that list, grouped under headings like "Your jobs," "Pace and outcomes," "Drying performance," "Recruiting," "Supplements," and "Safety", opens this card when you click it. Swiping left or right inside the opened card pages through the full mining list in the same order the tab lists it, so you can move stage by stage without closing and reopening. See the Flow tab for how that list itself is organized.

Mobile. Open the Processes home and scroll to the How your work flows tile row: one tile per process Verinode can currently mine from your own data (Jobs, Exterior, Supplements, Recruiting, Safety, Drying, and any other registered process with enough history behind it). Tap a tile and this same card opens in the mobile detail deck. Mobile shows the curated, one-tile-per-process subset; the web Flow tab is the complete, ungrouped-by-tile list of every metric Verinode has mined, including every job-path variant and claim-journey spotlight the mobile roster doesn't have room for.

Processes is a Premier-tier feature. On Contributor or Executive the page renders in full layout but the mining reads stay blurred behind an upgrade prompt; see the Excellence overview for both gates (tier and section activation) that stand between you and a live card.

The shape every card shares

Every card, regardless of what it's measuring, opens with the same three pieces, stacked top to bottom:

1. An eyebrow. A small uppercase label in copper naming which of three families the card belongs to: How your work flows (stage timing, job routes, claim journeys, and the discovered job flow), Pace and outcomes (speed-versus-result findings), or Drying performance (days-to-dry figures).
2. The lead. A large number, when the metric has one clean headline figure, colored green when the reading favors you, red (Ember Red) when it doesn't, or a neutral tone when there's no direction to call. Underneath it, one sentence in plain language states the verdict: what's actually happening and, where a peer figure exists, how it stacks up.
3. The supporting sections, which vary by what kind of row you opened: a bar breakdown titled Where your time goes, a benchmark row titled How you compare, and a closing note giving the sample size and context behind the number.

Nothing on the card ever shows internal vocabulary. You will never see "window," "tercile," "p25," or "n=" spelled out as jargon; a stage transition reads as "Billed → Paid," a peer range reads as "most run 14 to 24 days," and a sample size reads as "Based on 22 jobs."

Where your time goes: the bar visual

Most cards carry a section titled Where your time goes, a stack of horizontal bars, one per stage (or per route, or per class), all drawn on the same scale so the longest bar really is the slowest stage, not an artifact of a different axis. Each bar shows:

• The stage's plain-language label on the left (for example, "billing the job" rather than the raw milestone key billed).
• A readout on the right: the median days for a stage-timing bar, a job or dollar count for a route bar, or a percentage for a share.
• The bar itself, filled to a length proportional to its value against the tallest bar in the set, so a 3-day stage visibly reads as short next to a 22-day stage.
• A color: green for a genuinely good reading, red (Ember Red) for the flagged bottleneck, copper for a neutral reading with no direction to call.
• Emphasis: the bar for the exact stage you opened is bolded and drawn at full opacity; every other bar in the set sits at half opacity for contrast, so your eye lands on the one you clicked first, then reads it against its siblings.

This is the same bar geometry and coloring the benchmark row below it uses, so a Flow card, a job detail card, and a client or vendor detail card all read as one visual language, not three different chart styles bolted together.

What each kind of card shows

The card body itself changes shape depending on which metric you opened. Every version below can appear from either the web Flow tab or the mobile "How your work flows" tiles.

Stage-to-stage timing

Opened from any "X → Y" row (Assigned → Started, Billed → Paid, Received → Interviewed, and so on, across every process Verinode mines). The lead number is the median days a typical case takes to clear that stage. The verdict sentence names the stage in plain language ("Going from billed to paid takes about 12 days on a typical job") and, if this is the slowest stage in its process, opens instead with "This is your slowest stage." When a peer figure exists, the sentence adds how many days faster or slower than "operators like you" you're running.

Below the lead, Where your time goes lists every stage of that same process that has cleared its own sample floor, so you see the stage you opened next to its siblings, not in isolation. When a peer read exists, How you compare shows the benchmark row (see below), plus a line naming the cohort and the middle range peers typically fall in ("most run 14 to 24 days"). The closing note states your own sample size in plain language and how far your slowest cases stretch past the median, calling out explicitly when the stage is your single highest-leverage place to speed up.

Job path

Opened from a "Job Path · [Route Name]" row (for example, "Job Path · Standard Flow" or "Job Path · Deposit-First"). The lead is the share of your completed jobs that took this exact route, with a verdict naming it either "This is how most of your jobs run" (the top route) or "One of the ways your jobs run" (any other route), plus the median cycle time from start to paid when there's enough sample behind that figure.

The rest took other routes bars out where your remaining completed jobs went, up to three other routes with their job counts. The 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, and states the trailing window (in months) the routes are drawn from.

Your job flow (discovered)

Opened from the single "Your job flow" tile, once Verinode has mapped enough of your job history to discover the real order events happened in, not a fixed template, but the actual sequence read from your milestone dates plus anything running alongside them (drying, supplements, on-site visits). The lead number is the time spent at your single slowest discovered handoff. The verdict names the path most of your jobs follow in plain phrases ("starting the job," "getting drying set up," "billing the job," "getting paid") and calls out where the most time goes.

Where your time goes bars out every leg of that main path, the slowest leg emphasized in red. When that slowest leg happens to line up with a stage that has a peer cohort, How you compare shows the same benchmark row a stage-timing card would. Other routes jobs took lists up to three alternate sequences your jobs actually followed, with their counts. If any step in the discovered path tends to repeat before a job moves on, a note calls it out directly: a step that comes back usually means a handoff is bouncing between two people rather than moving forward. The closing note states how many jobs the discovery is built from and reminds you this is the order work actually took, not a template you're being measured against.

Pace and outcomes

Opened from a "[Stage] · Margin" or "[Stage] · Satisfaction" row. This card connects how fast a stage moved to how the job turned out, on your own book of jobs. The lead is the point swing between your fastest and slowest jobs on that outcome (for example, "+6.2 points Margin"), colored green when moving faster is the better outcome, red when it isn't. The verdict sentence is the exact finding, in the same voice throughout the platform: "Jobs paid within 18 days of billing ran 4.2 pts higher margin than jobs that took 31+ days."

The bar section compares your fastest-band jobs against your slowest-band jobs on that same outcome, each bar labeled with its own day range and carrying its own sample size underneath. The closing note is explicit, every time: this is a pattern in your own book, not proof that one causes the other, and names whichever group (the slow ones, or the fast ones, depending on direction) is worth a closer look at what they share.

Drying performance, overall

Opened from the single "Drying Performance" tile. Once you've logged enough completed drying jobs to publish a median, the lead is your typical days-to-dry, with the verdict adding your typical equipment-days per job when that figure is available too. Before you clear that bar, the lead instead shows your total logged drying jobs, with the verdict stating how many have finished drying so far and that a typical dry-time appears once a few more wrap up.

By water damage class bars out the median dry time for each IICRC S500 water class (1 through 4) that has enough of your own logs behind it, with a note that higher classes are wetter losses and take longer, Class 4 being the most saturated. A closing note states how many jobs have finished drying, and how many are still open, when that applies.

Drying performance, by class

Opened from an individual "Class N Losses" tile. A single, simple card: that class's own median days-to-dry as the lead, a verdict repeating the same "higher classes take longer" context, and a closing note giving the job count behind that class's number.

Claim journey

Opened from a "Claim Journey · [Category]" spotlight, a small set of individual, still-moving jobs Verinode highlights. There's no bar section and no peer comparison here: the verdict names which of the five job lifecycle stages that specific job has reached and how many of the five it's moved through so far, followed by an Open job button that takes you straight to that job's own detail card to trace the full timeline stage by stage.

The peer comparison row: How you compare

Wherever a peer figure exists, the card shows it through the exact same benchmark row used across job, vendor, and client detail cards, so the whole platform reads as one surface rather than a Processes-specific chart style:

• Your own value, bold, on the left.
• The delta against the peer figure, colored and signed ("−3d vs Peer" in green, "+5d vs Peer" in red), directly beside it.
• A thin bar with your value filled in and a tick mark showing exactly where the peer median sits, so you can see at a glance whether you're close to the line or well past it.
• Underneath the bar, a plain line naming the cohort and the middle range peers typically fall in, for example "operators like you in [your state] · most run 14 to 24 days."

The cohort label itself adapts to how specific a comparison group Verinode can form for you. From most to least specific, it reads as "operators like you in [state]," "operators in [state]," "[solo/small/mid-size/large] operators nationally," or plainly "operators nationally" when no state or size slice applies. Verinode never names your exact peer group beyond that description, and never states how many operators sit behind the number.

The read gate

A peer comparison only ever appears once two things are both true: your account has peer reads unlocked (a paid membership, or a Contributor who has opted in and contributed the same kind of data), and enough other operators have contributed that exact same measurement to form a real cohort. Verinode holds every cohort to an anonymity floor before it publishes anything from it, and deliberately never surfaces that floor, or how many operators are actually behind a given number, on any screen. If your account is unlocked but a particular stage doesn't have a cohort yet, the card simply shows your own reading with no benchmark row attached, rather than a placeholder or a fake comparison. This is the same trust boundary behind every peer figure on the platform: see how Verinode's benchmarks work for the full mechanics, and reading a benchmark for how to read a peer range once one appears. Your own data is never sold to carriers or any third party; the only thing your history contributes back is a wider, more useful comparison for operators like you.

Empty and awaiting states

The card only ever shows what your own history actually supports:

• Nothing mined yet. If none of your registered processes have enough of your own history to produce a single timing read, the Flow tab shows one line instead of a list: "Add your job history and we'll show how long each step takes, and where jobs slow down. Nothing has enough history to chart yet." The mobile "How your work flows" row shows the shorter companion line: "Add your job history and we'll show how long each step takes, and where jobs slow down."
• Some processes still awaiting data. Once at least one card exists, a line beneath the list names any registered process that hasn't cleared its own sample floor yet, in plain language, for example: "Your recruiting pipeline and incident follow-through will appear here as that data flows in."
• Peer comparisons still pending. Separately, once your account has peer reads unlocked but none of your stage timings have a matching cohort yet, a second line lets you know comparisons will light up as more operators contribute the same kind of data. It never states how many, only that the comparison isn't ready.
• Drying, before a median exists. The drying tile itself carries its own honest interim state: a running count of drying logs and how many have finished, rather than a median built on too few jobs.

Every one of these states resolves itself as data flows in through your normal ingestion, connecting a source under connecting your data or forwarding documents. Nothing needs to be logged by hand for a card to start filling in.

How to use it

1. 1Open Processes from the sidebar (web) or the Processes home (mobile), then open a card, either from the Flow tab's full list or a tile in "How your work flows."
2. 2Read the lead verdict first. It's written to be the whole answer for most people; the sections below it are there for whoever wants to check the number.
3. 3If a Where your time goes section is present, look at which bar is longest and whether it's the one you opened. That tells you if this stage is genuinely your process's bottleneck or just the one you happened to click.
4. 4If a How you compare row is present, read the peer range, not just the single median, before deciding whether your own number is actually slow. Being inside the range on the slow side is a different situation than being outside it entirely.
5. 5For a Pace and outcomes card, treat the finding as a prompt to look at what the flagged group of jobs has in common, not as proof that speeding up automatically improves the outcome.
6. 6On mobile, swipe between tiles in the same row to move through every process without closing the deck; on web, swipe (or use the slider's paging) to move through the full Flow tab list in order.

Best-practice example

Say the "Your jobs" discovered-flow tile reads "12d," with the verdict naming "billing the job" as where the most time goes, and a peer comparison showing operators like you clear that same gap in about 7 days. Open the card: Where your time goes confirms every other leg of the lifecycle is fast by comparison, so this isn't a general slowdown, it's specifically the estimate-to-invoice handoff. How you compare shows most peers clear it in a tighter range than your own number. Before assuming it's a scheduling or crew problem, check Pace and outcomes: if a "Billed → Paid · Margin" card shows your fastest-paid jobs also carry a materially better margin, that reinforces this is worth prioritizing. The fix, tightening whatever is slowing the estimate-to-invoice step, is yours to make; Verinode's job stops at showing exactly where the time is going and how that compares to operators like you.

Related reading

• The Flow tab: every stage-timing metric in one place
• Excellence (Processes): the fractional-COO process coach
• How Verinode's benchmarks work
• Reading a benchmark
• The Benchmarks section
• Understanding your margin
• The decision workspace
• Acting on decisions
• Clients and carriers
• Forwarding documents
• Connecting your data

Data sources