Best practices worth propagating across the network

What this is

Verinode HQ is the network intelligence layer that sits above the tools your franchisees or locations already run day to day. HQ never opens a single location's private business data: no individual P&L, no named job list, no one location's numbers held up next to another's. What HQ sees is aggregates, rankings, and compliance across the network, and it surfaces patterns you can act on as leadership.

Best Practices To Propagate is one of those patterns. Once a day, Verinode's network aggregator compares your top-performing locations against the rest of the network on two operational dimensions, SOP coverage and job cycle time, and checks whether the gap between them is large enough to matter. When it is, the row names the practice worth rolling out and states the gap in plain language. When it isn't, the row says so and stays quiet rather than manufacturing a recommendation out of noise.

This is a read-only section. There is nothing to click and no per-location names appear in it. It reports what the top cohort does differently as a group, not what any one franchisee or location does individually, that is the privacy boundary that makes the comparison safe to publish in the first place.

Where to find it

Open the sidebar's Network group and click the item labeled Network (this reads Franchisees or Locations instead, depending on how your network is set up), which lands on hq.verinode.ai/network. That single page is Verinode's Network Health home, and Best Practices To Propagate is the third row down:

1. Hero: the network's composite health score and its 90-day trend.
2. Take Action: open critical and warning signals across the network.
3. Best Practices To Propagate: this row.
4. Network Flow: stage-by-stage medians for how work moves through the network, plus Standards Conformance if you've set stage-time standards.
5. Explore: the tile row into Location Directory, Leaderboard, Top Quartile, Risers & Fallers, Watchlist, and the rest of the roster views.

The row title is literal: Best Practices To Propagate. It sits directly under Take Action and above Network Flow, and it has no separate page of its own, everything it shows renders inline on the Network Health home.

What you see when there's a gap

Each recommendation is a short block: a small pill labeling the dimension (SOP or Cycle time), followed by one sentence of plain-language guidance. Up to three recommendations show at once, ranked with the largest gap first. Today there are two dimensions the aggregator evaluates, so in practice you will see one or two blocks, never more.

SOP coverage. Verinode checks eight procedure categories every location can document a standard operating procedure against, spanning the core restoration disciplines (water damage restoration, structural drying, microbial remediation) and the operational side of the business (estimating, billing, safety, field operations, office administration). A location's SOP coverage is the share of those eight categories where it has at least one active, documented SOP on file. When the top cohort's median coverage clears the rest of the network's median by a wide enough margin, the row reads something like:

Top locations run 72% SOP coverage vs 54% across the rest. Roll out the documented SOP set the top cohort uses.

Cycle time. This is the average number of days from job start to job completion, measured across jobs completed in the trailing 90 days. Canceled jobs are excluded from the average, a job that gets canceled quickly would otherwise flatter the number without reflecting real completed work. When the top cohort finishes jobs meaningfully faster than the rest, the row reads something like:

Top locations close jobs in 18 days vs 27 across the rest. Study the top cohort's scheduling and handoff flow and push it as a playbook.

The numbers above are illustrative. Your own row shows your network's real medians and the real gap between them.

How the "top cohort" is chosen

Verinode never singles out one named location as "the best." The comparison is always cohort versus cohort, and which locations land in the top group depends on what data your network has:

• When your network has real Verinode operator scores on file for enough locations, the top cohort is the top quarter of locations by score, and the rest of the network is everyone else. This is the same top-cohort concept behind the Top Quartile tile in the Explore row below.
• Before scores are populated across the network, the top cohort falls back to locations sitting above the network's own strongest margin band (net margin when enough locations report it, gross margin otherwise), and the rest is everyone below that band.

Either way, the contrast only runs, and a recommendation only appears, once there are enough distinct locations on each side of the comparison for the medians to mean something. A network too small to form two stable groups shows the empty state below instead of forcing a comparison that would really just be one location's number against everyone else's.

The row also only surfaces a dimension when the gap between the two medians is wide enough to represent a genuine operating difference, not the kind of month-to-month noise that would have you chasing a pattern that isn't really there. If your network's SOP coverage or cycle times are broadly similar network-wide, the row stays empty on that dimension, which is itself a useful (quiet) signal: nothing systemic to fix there right now.

Empty state

When the aggregator finds no material gap on either dimension, the row reads, verbatim:

No material gap between your top and other locations right now. Practices appear as the top cohort pulls ahead on SOP coverage or cycle time.

This is the common state for smaller networks, newly onboarded networks still building up SOP and job history, or networks where performance is genuinely even across locations. It is not an error and it is not a sign the feature is broken, it means there is nothing systemic worth flagging today.

How to act on a recommendation

The row tells you what to propagate and how big the gap is; it does not push a button for you, because rolling a practice out network-wide is a leadership decision, not something Verinode should make unilaterally. Two direct paths from a recommendation:

1. 1If the recommendation is an SOP coverage gap, package the procedure the top cohort is running (safety, estimating, billing, whichever category is thin across the rest of the network) as a network SOP and push it. Locations pull it into their own operations through the same import flow covered in Network SOPs: importing SOPs shared by your HQ and Network SOPs: importing playbooks shared across your network.
2. 2If the recommendation is a cycle time gap, use Process Standards to set a stage-time target based on what the top cohort is actually achieving, then track adoption on the Standards Conformance tile in the Network Flow row.
3. 3Either way, if you want the rollout to land as a directive rather than a quiet SOP update, send it through Broadcasting to your network so every location sees the same message at the same time.

How this fits the rest of Network Health

Best Practices To Propagate is diagnostic, not a scoreboard. It shares its underlying cohort logic with a few other places on this page and elsewhere in HQ, worth knowing so the numbers read as one consistent picture rather than several disconnected ones:

• Top Quartile and Watchlist, both in the Explore row on this same page, use the same score-first, margin-band-fallback logic to define "top" and "bottom." Best Practices To Propagate is the operational explanation for why the Top Quartile locations are where they are.
• Network Flow and its Standards Conformance tile show you the stage-by-stage medians a cycle-time gap is drawn from, and let you set the targets a rollout should aim at.
• Leaderboard, reachable from the Explore row and from /benchmarks, ranks every location on the full set of network benchmarks; Best Practices To Propagate calls out only the two dimensions with a large enough gap to be worth a rollout, not the full leaderboard.
• For the overview of the whole page, hero composite, Take Action, quartiles, movers, and the Explore tiles, see Network Health.

If your network is preparing a Discovery Day pitch or substantiating an Item 19 financial performance representation, a documented, systemic operational edge (not an anecdote from one location) is exactly the kind of evidence that holds up. See Discovery Day and Item 19 basics for how network performance data gets used in those conversations.

Data sources