The Flow tab: every stage-timing metric in one place

What the Flow tab shows

Every job, supplement, recruit, incident, purchase, lead, and review you run leaves a trail of dates: when it started, when it moved to the next stage, when it finally closed out. Verinode reads that trail directly from your own records and turns it into stage-by-stage timing, without you tagging or logging anything extra. The Flow tab is where every one of those readings lives, in one flat, groupable list, each one a row you can open for the full picture.

Where the home page's "How your work flows" row is a curated highlight reel, one tile per process, the Flow tab is the complete list: every stage transition, every job-path variant, every claim-journey spotlight, every pace-and-outcome finding, and every drying figure that has enough of your own history behind it to be trustworthy. Nothing here is invented or benchmarked against a fixed industry standard by default; it is all mined from your book, and any peer comparison rides alongside only once Verinode can back it with real data from operators like you.

Verinode does not judge or decide anything from this tab. It surfaces where your time is actually going, in your own words as much as possible, and leaves the read on it to you.

Where to find it

Open Processes from the sidebar, under Operations, at /processes. The Flow tab is the second tab across the card slider, after Findings: Findings, Flow, All Processes, By Standard, Coverage, Benchmarks. Findings holds open process decisions and drills into the decision workspace; Flow is the mining list itself.

Processes is a Premier-tier feature: on Contributor or Executive it shows a preview summary, and the full mining list, the fractional-COO process coach, and the drill-in cards described below unlock at Premier.

The grouped list

Inside the Flow tab, every metric is grouped under a heading for the process it belongs to, so a row about hiring never sits next to a row about getting paid. Groups appear only when you have data behind them, in this order:

• Your jobs: everything about the job lifecycle as a whole, stage-to-stage timing (Assigned to Started, Started to Completed, Completed to Billed, Billed to Paid, plus Estimate Submitted and Carrier Approved once those dates are populated), the routes your completed jobs actually took, individual claim-journey spotlights, and a discovered job-flow summary once there's enough case history to trust it.
• Pace and outcomes: findings that connect how fast a stage moved to how the job turned out (margin, satisfaction).
• Drying performance: days-to-dry figures, overall and by IICRC water-damage class.
• Recruiting, Supplements, Safety: the same stage-timing treatment applied to your hiring pipeline, supplement turnaround, and incident follow-through.
• Any other process you run with enough history: Purchasing, Lead Response, Review Response, and a segment lens like Exterior Job Lifecycle each get their own heading, named after that process.

Each row is a plain line: a small colored dot, a title, and a value with a short subtitle underneath. The dot's color tells you which of the three underlying math families the row comes from, not which heading it's grouped under.

• Steel blue: a flow reading, a stage duration, a job-path variant, a claim-journey spotlight, or the discovered job flow.
• Copper: a pace-and-outcomes finding.
• Teal: a drying figure.

What each kind of row tells you

• A stage duration (e.g. "Billed → Paid") shows the median time in days for that stage, and underneath, either the peer comparison ("Peers 6d (3–9d)") when one exists, a "Slowest stage · median" flag on your worst stage, or your own sample count ("38 jobs · median").
• A job path (e.g. "Job Path · Standard Flow") shows how many of your completed jobs followed that exact route out of the total, plus the median cycle time when there's enough history behind it.
• A claim journey (e.g. "Claim Journey · Water Damage") is a single open job, showing which stage it's reached and when.
• A pace-and-outcomes finding (e.g. "Billed → Paid · Margin") shows the point spread between your fastest and slowest jobs on that stage, with the sample sizes behind each group.
• Drying Performance shows your typical days-to-dry across every dried job, or, before you've dried enough jobs for a median, a running count of drying logs instead.
• A drying class row (e.g. "Class 3 Losses") shows the median days to dry for that IICRC water class alone.
• Your job flow (the discovered flow tile) shows either the time at your slowest observed handoff or, if none stands out, simply how many jobs the discovery is built from.

The awaiting and peer-pending notes

Two honest notes can appear below the list, whichever apply:

• Awaiting data. When a registered process (jobs, supplements, recruiting, safety, purchasing, leads, or reviews) doesn't yet have enough of your own history to produce a timing read, it's named directly: "Your [process names] will appear here as that data flows in." For example, if recruiting and reviews haven't cleared that bar yet, the line reads "Your recruiting pipeline and review response will appear here as that data flows in."
• Peer comparisons still pending. Once your account is set up to see peer comparisons but none of your stage timings have a matching cohort yet, a second line appears letting you know comparisons will light up as more operators contribute the same kind of data. No specific operator count is shown; Verinode never surfaces the exact size of a peer cohort, only whether the comparison is ready.

If nothing in your book has enough history to mine at all yet, the Flow tab shows a single message instead of an empty 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." Data flows in as your jobs, supplements, recruiting records, incidents, purchases, leads, and reviews accumulate through connecting your data or forwarding documents; nothing needs to be logged by hand for the Flow tab to start filling in.

Opening a row: the FlowMetricDetail card

Click any row and it flips into its own detail card. Swiping left or right pages through the full mining list in the same order it's listed, so you can move stage by stage without closing and reopening. Every card leads with a plain-English verdict, not a raw statistic, and every card that has peer data shows it through the same benchmark row used across jobs, clients, and benchmarks detail views, so the whole platform reads as one surface.

Every card opens with an eyebrow naming which family it belongs to: How your work flows, Pace and outcomes, or Drying performance. What follows depends on the kind of row you opened:

Stage duration. A big number (the median days) leads with a sentence like "Going from billed to paid takes about 12 days on a typical job, 3 days faster than operators like you." If your process has more than one stage that cleared the bar, a Where your time goes section lists every stage of that process as bars on a shared scale, with the one you opened bolded, so the slowest stage is visibly the longest bar. When a peer figure exists, a How you compare section shows the benchmark row (your value vs. the peer median) and the middle range peers typically run in. A closing note gives your sample size and how far your slow jobs stretch past the median, and calls out when it's your single slowest stage.

Job path. Leads with the share of your completed jobs that took this exact route ("47% of completed jobs"), naming it "This is how most of your jobs run" for the top route or "One of the ways your jobs run" otherwise, plus the median cycle time when there's enough history. A The rest took other routes section bars out where the remaining jobs went. The closing note reminds you that different routes usually reflect real differences (a deposit-first job, a same-day mobilization) rather than mistakes, and states the trailing window the routes are drawn from.

Pace and outcomes. Leads with the point spread between your fastest and slowest jobs on that stage (e.g. "+6.2 points margin"). A bar section compares your fastest-band jobs against your slowest-band jobs on that outcome, each bar showing its own sample size. The closing note is explicit that this is a pattern in your own book, not proof of cause and effect, and points you toward looking at what the slow (or fast) jobs have in common.

Drying performance, overall. Leads with your typical days-to-dry and, when available, your typical equipment-days per job. A By water damage class section bars out the median dry time for each IICRC class you have enough logs for, with a note that higher classes are wetter and take longer to dry. Before you've dried enough jobs for a median, this card shows your running drying-log count and completed count instead, with a note that a typical dry time appears once a few more jobs wrap up.

Drying performance, by class. A single class's median dry time, with the sample size behind it and the same "higher classes take longer" context.

Claim journey. Leads with which lifecycle stage the job has reached and how many of its five stages it has moved through, then an Open job button that takes you straight to that job to trace the full timeline.

Your job flow (discovered). Leads with the actual sequence most of your jobs follow, named in plain terms (e.g. "starting the job," "getting drying set up," "billing the job") rather than raw milestone keys, and calls out where the most time goes. A Where your time goes section bars out every leg of that main path with the slowest leg emphasized. When a peer figure exists for that slowest leg, a How you compare benchmark row follows. An Other routes jobs took section shows the next most common paths your jobs actually followed. If any step tends to repeat before a job moves on, a note calls that out as a likely handoff bouncing back and forth. The closing note states how many jobs the discovery is built from and reminds you this is the order work actually happened in, not a template.

How to use it

1. 1Open Processes in the sidebar, then the Flow tab.
2. 2Scan the group headings first. A group that's missing (or flagged as awaiting) tells you which of your processes doesn't have enough history yet, not that something is broken.
3. 3Within Your jobs, open the discovered job-flow row if it's there. It names your slowest real handoff in plain language and is usually the fastest way to see where time leaks.
4. 4Open the stage-duration rows flagged Slowest stage across your other processes (Recruiting, Supplements, Safety, and any other you run) to see each process's own bottleneck.
5. 5Check Pace and outcomes for any row showing a real point spread. It won't tell you why, but it tells you which stage's fast/slow split is worth a closer look.
6. 6If a row shows a peer comparison, read the range peers run in, not just the single median, before deciding whether your number is actually slow.

Best-practice example

Say the Your jobs group shows a discovered job-flow row reading "12d · Slowest: Completed → Billed," with a peer comparison showing operators like you clear that same gap in about 7 days. Open the row: the verdict names the delay plainly ("the most time goes into billing the job, about 12 days"), the bar section shows every other leg of the lifecycle is fast by comparison, and the benchmark row confirms the gap against peers. That's a concrete, single-process signal: billing is where your jobs stall, not scheduling or drying. The fix (tightening the estimate-to-invoice handoff) is yours to make; Verinode's job stops at surfacing exactly where the time is going.

Related reading

• How Verinode builds benchmarks
• Reading a benchmark
• Benchmarks overview
• The decision workspace
• Connecting your data
• Forwarding documents

Data sources