Network Hiring Flow: time-to-hire benchmarks

What Network Hiring Flow shows

Network Hiring Flow is the recruiting-process read on your network: how many days it takes to move a candidate from one stage of the hiring pipeline to the next, pooled across every office. Verinode mines this from the same applicant timestamps each franchisee already logs in their own IQ Recruiting section, the same dates that power that office's own hiring-pipeline view. This row rolls those dates up to the network level, one tile per stage transition, so you can see at a glance how fast the network moves candidates through the pipeline and how that pace compares to the wider restoration industry.

The recruiting pipeline has three stages: Received (an application comes in), Interviewed (the applicant's first interview is completed), and Hired (an offer is accepted). Network Hiring Flow can show a tile for each transition between those stages, Received to Interviewed and Interviewed to Hired, once each transition has enough pooled data behind it. There is no offer-extended timestamp anywhere in the pipeline, so Hired is the next real milestone after an interview, and a declined applicant simply never reaches it, dropping out of the pipeline rather than distorting the median with an incomplete case.

This is the same aggregator and the same underlying data as Network Health's Network Flow row, one process out of the four it covers (job lifecycle, supplement turnaround, recruiting pipeline, incident follow-through). Network Hiring Flow is that recruiting slice, surfaced a second time on the Recruiting page itself, next to the pipeline it describes, so you don't have to leave Recruiting to see how the network is trending on time-to-hire. See Network Flow: how work moves through the network for the full mechanics shared across all four processes.

Where to find it

Open Recruiting from the HQ sidebar (hq.verinode.ai/recruit-grow). Network Hiring Flow is its own row, below Active Prospects and above Territories. Each tile in the row is one stage transition.

Reading a tile

Each Network Hiring Flow tile is a metric tile with four parts:

• Label: always Time To Hire.
• Value: the network median for that transition, in days, rounded to a whole day (for example, "4d"). This is the pooled median across every in-order recruiting case from every office that has one, not an average of each office's own median. An office running a high volume of hiring weighs into the pooled number more than a low-volume office, by design, so the tile answers "how long does it actually take the network to move candidates through this stage" rather than "what does the typical office experience."
• Sub-line: the stage transition in plain language, written as "Stage A to Stage B" (for example, "Received to Interviewed" or "Interviewed to Hired").
• Industry comparison: a delta line beneath the value, described in the next section.

Clicking a tile behaves the same as any Network Flow tile elsewhere on HQ: it opens the full drill-in with the network median, the case count behind it, and the office-by-office breakdown. See Network Flow: how work moves through the network for what that drill-in shows in full, since the mechanics are identical for the recruiting slice shown here.

The n≥5 pooled floor

A tile only renders once the pooled sample behind that specific transition, every in-order recruiting case across the whole network combined, clears a minimum floor. Below that floor, Verinode does not publish a median built on too few cases to trust: the transition simply produces no number, and no tile appears for it.

This floor exists because a median calculated from a handful of cases can swing wildly on the strength of one unusually fast or unusually slow hire. A "typical" time-to-hire built from two or three candidates network-wide isn't a typical anything, it's an anecdote wearing a statistic's label. Verinode would rather show nothing for a transition than show a number that looks precise but isn't.

The same floor governs the per-office breakdown inside the drill-in: an individual office's own median for a stage only appears in that list once the office's own case count clears the floor. An office below it stays off that list entirely, no dash, no placeholder row, it simply isn't listed, exactly as covered in Network Flow: how work moves through the network.

Per the platform's disclosure policy, Verinode does not publish the exact case-count threshold behind this floor anywhere in the product. What you see on screen is qualitative: a tile is present because the pooled sample cleared the bar, or absent because it hasn't yet. Read "the floor" as a trust gate, not a number to reverse-engineer.

Why offices below the floor stay off the row

Two different things can each be "below the floor" here, and it helps to keep them separate:

• The network-level tile itself depends on the pooled sample across all offices combined. If Received to Interviewed hasn't cleared that pooled floor yet, no tile for that transition appears in the row at all, regardless of how any single office is doing.
• An individual office's row inside the drill-in depends on that office's own case count for that same transition. A network-level tile can be showing a solid median built from many offices' cases while a specific small or new office still has too few of its own hires logged to earn a row in the office-by-office list underneath it.

Either way, the behavior is the same: absence, not a fabricated number. A brand-new franchise that has made two hires this quarter does not get a "2-day time to hire" data point sitting next to established offices with dozens of hires behind their number, because that comparison would be misleading in both directions. The office's hires still count toward the network-level pooled median once they're in the data, they just don't get their own line in the per-office breakdown until there are enough of them to mean something on their own.

The industry-comparison delta

Beneath the value, a delta line compares your network's median for that transition against an anonymous industry benchmark, drawn from Verinode's peer restoration-business cohort:

• "On Pace With Industry", in neutral gray, when your network's median and the industry median are within half a day of each other.
• "Nd vs Industry", colored green when your network is faster (a smaller median than the industry) and red when your network is slower (a larger median than the industry), where N is the whole-day gap between the two.

The industry figure only appears once the anonymous peer cohort behind that specific transition is broad enough that no single contributor's hiring data could be identified from it. Below that bar, the tile shows the network's own median with no comparison line at all, the same behavior as every other cross-network industry read on HQ. Verinode does not disclose how many peer businesses sit behind a published industry figure, only that the anonymity floor was cleared before the comparison shows.

How to use it

1. 1Open the Network Hiring Flow row on the Recruiting page and read each tile's value against its sub-line, so you know exactly which stage of the pipeline the number describes.
2. 2Check the delta line. A transition reading "Nd vs Industry" in red is worth a closer look before one reading "On Pace With Industry."
3. 3Click into a tile that's running slow. The office-by-office breakdown shows which locations are pulling the network median up, once each office has enough of its own hires logged to appear.
4. 4If a handful of offices are consistently slower than the rest on the same stage, that's usually a process or staffing-capacity conversation for your leadership team, not a data problem. Verinode surfaces the pattern; it does not tell you what to change.

Empty states

This entire row disappears rather than showing a placeholder tile until at least one recruiting transition clears the pooled floor. There is no "no data yet" tile here: if the network hasn't logged enough recruiting transitions, the row is simply absent from the Recruiting page, the same way Coverage Gaps and Territories fall back to their own plain-language empty states when they have nothing to show (see Recruiting & Growth: section overview).

A quiet Network Hiring Flow row usually means offices haven't logged enough applicant timestamps yet in their own Recruiting sections, not that nothing is happening on the ground. As franchisees log more of the pipeline (received dates, completed interview dates, hire dates), the pooled sample grows and tiles appear on their own on the next nightly refresh.

The privacy boundary

Network Hiring Flow is aggregate intelligence, not a hiring-pipeline lookup tool. Verinode HQ never surfaces an individual applicant's record, their name, their interview notes, or which specific candidate is behind a slow or fast case. What crosses from a franchisee's own Recruiting data into this row is a small set of pooled numbers: a median, the sample size behind it, and, in the drill-in, each office's own median once it clears its own floor. Franchisees own their applicant data; HQ sees the network-level and office-level aggregate, never the underlying record. Office identity in the per-office breakdown follows the same rule as the rest of HQ: an anonymized code for independent-operator networks, the real location name for single-entity networks. See Network Flow: how work moves through the network for the full explanation of that naming behavior.

Related

• Network Flow: how work moves through the network, the full mechanics shared across all four mined processes (job lifecycle, supplement turnaround, recruiting pipeline, incident follow-through), read on Network Health.
• Recruiting & Growth: section overview, the full Recruiting page this row sits on, including the territory map, pipeline, and prospect deck.
• The warming-up sample floor on recruitment stats, the separate 10-franchisee floor that gates the recruitment-story stats on the Take Action tile above this row, not this row's own pooled floor.
• HQ Standards: conformance tracking for offices once stage-time standards are defined, a related but distinct feature from the industry comparison shown here.