The Network Health composite score explained

What the composite score shows

The Network Health composite is the single number at the top of your Network page: a 0-100 read on the state of your network right now, blending compliance, how many locations are actually active, and net margin into one figure. It exists so a leadership team with dozens of locations does not have to open three separate reports to answer "how is the network doing this week." Verinode reads what your membership base has already reported in, rolls it up, and hands you one number with a plain-language band underneath it. It never reaches into a single membership's private books to build this number, it works entirely from the network-level rollup your locations' own data feeds each day (more on that boundary below).

Where to find it

Open the sidebar group labeled Network (this reads "Franchisees" or "Locations" depending on how your network is set up) and click the top item, which lands you on hq.verinode.ai/network. The composite sits in the hero band at the very top of the page, above Take Action, Best Practices To Propagate, Network Flow, and the Explore row of tiles. There is no separate settings toggle or drill-down page for the composite itself, it is a hero number, not a slider tab, though the sibling article at Network Health, the full page walks through everything below it.

How the score is built

The composite averages up to three inputs, each converted onto a 0-100 scale first. It is a straight average of whichever inputs currently have data, not a weighted formula and not a penalty for a missing input. A network reporting only two of the three still gets a real composite from those two; it does not get marked down for the one that has not landed yet.

Compliance rate. Your network's certification and program compliance rate, already expressed 0-100. See Network compliance for what feeds this number and how it is computed per location.

Recent-activity share. The share of active locations that have shown at least one signal in the last 30 days: a data upload, a benchmark update, a signed-in session, anything that tells Verinode a location is live. This is named for exactly what it measures. It is a "we heard from this location recently" signal, not a login-count or engagement score, so do not read it as a usage metric.

Net margin. The network's median net margin (what locations keep after cost of goods and overhead), scaled so that a 15% net margin, a healthy number for a restoration book, lands at 100 on the composite scale. Net margin over 15% still caps at 100, it does not push the composite past full marks. Until enough locations have operating-expense lines on file for net margin to compute, the composite falls back to median gross margin instead, scaled so 50% gross lands at 100. Whichever one feeds the composite is also the one labeled next to the score (see below), so you always know which basis you are looking at.

The three bands: Healthy, Watch, Action needed

The number carries a pill next to it that translates the score into a plain-language read:

• Healthy (green), composite 75 or above.
• Watch (yellow), composite 50 to 74.
• Action needed (red), composite under 50.

The pill only appears once the composite has at least one input to work from. If your network is brand new and none of the three inputs has landed yet, the headline number reads 0 with no pill and no band, because there is nothing yet to band. Once your first daily rollup carries even one input, the pill appears and starts telling you where the network stands.

Reading the two lines under the number

Under the headline, the subtext tells you how many locations are behind the number: how many members are active out of your total roster, in the last 30 days. Once part of the network is not yet feeding the score, an extra sentence appears explaining the gap, for example a network with a handful of locations still onboarding might read something like "42 of 50 members active in the last 30 days. Based on reporting locations. 8 not yet reporting." That second sentence is the coverage basis.

What "based on reporting locations" means

The composite's margin and compliance inputs are computed only across the locations that have actually reported the underlying data, not across your full directory. A location that has not yet uploaded a P&L, or has no certification on file at all, is not counted as failing, it is counted as not yet reporting, and the coverage note tells you how many locations that covers. This matters because a network with a lot of very new or very quiet locations could otherwise read the composite as covering the whole roster when it only reflects the part of the network with data on file. The note disappears once every active location has both a computable margin and a certification on file, or once your directory has nothing to report on yet.

The three numbers beside the headline

To the right of the composite, three flat metrics give quick context without leaving the hero:

• Active, the count of members active in the last 30 days, out of your total roster. Shown in green once at least one location is active; a network with none shows in neutral gray.
• Net Margin (or Gross Margin if net is not yet on file, the label always names which one you are looking at), your network's median, as a percentage. The line underneath reads "Median" once every reporting location is counted, or "Median of N reporting" once only part of the network has a computable margin. Until any margin exists at all, it reads "Awaiting Data."
• Critical Signals, how many of your currently open network-wide signals (shown in the Take Action row just below the hero) are marked critical severity. Reads "Need attention" in red when there is at least one, "All clear" in green when there is none.

The 90-day trend line

Behind the headline, on wider screens, a small sparkline traces your composite over roughly the last 90 days, recomputed from your network's daily history rather than pulled from a separate log. Each point on the line is the same composite formula run against that day's snapshot, using the same net-margin-preferred basis as the live headline, so the last point on the chart always agrees with the number you are looking at. A filled dot marks the most recent point, and underneath the chart a small label reads "90d trend" with the point change over the window, in green if the network gained ground, in red if it lost ground.

The trend line only appears once there are at least two days of history with a computable composite in the window. A brand-new network, or one that has gone 90 days without two valid snapshots, simply shows the hero without a trend line, there is no placeholder chart or "no data" chart drawn in its place.

Empty states

• No members yet. If your directory has zero members, the subtext reads "Network Health will appear as members come online," and no coverage note or band pill shows.
• Aggregator hasn't run its first pass. A brand-new network whose first daily rollup has not landed yet shows the composite as 0 with no band pill, while Active and the two other secondary metrics show their own defaults (Active at 0 of your directory count, margin at "Awaiting Data").
• Trend not established. Fewer than two days of computable composite history: no sparkline renders, the hero simply shows the headline, band, subtext, and the three flat metrics.

Best-practice example

Say your composite reads 61, Watch, with the subtext "44 of 52 members active in the last 30 days. Based on reporting locations. 6 not yet reporting." and the sparkline shows a 9-point drop over the last 90 days. Before assuming a network-wide slide, check the flat metrics: Net Margin reads "18%, median of 40 reporting", which is respectable, so margin is not the drag. Critical Signals reads 4, "Need attention." That points you straight at the Take Action row: the composite told you something moved, the signals underneath tell you what to do about it, and Best Practices To Propagate may already have a recommendation drawn from what your top-performing locations are doing differently.

The privacy boundary behind the number

Every input behind the composite (compliance rate, recent-activity share, net margin) is a network-level rollup, a median, a rate, or a count across your membership base, written once a day by Verinode's aggregator. HQ never sees a single membership's underlying financials, job-level detail, or day-to-day business records to build this score. Your locations own their data; what reaches this page is the aggregate your network already agreed to share by being part of it. That boundary holds everywhere else on the Network page too, see Network Health, the full page for how it is enforced tile by tile.

Related reading

• Network Health, the full page, the hero plus Take Action, Best Practices, Network Flow, and the full Explore row.
• Network compliance, what feeds the compliance-rate input.
• Network benchmarks, where the per-location Verinode operator score and the Leaderboard live.
• Broadcasting to your network, for turning a network-wide pattern into a message to your membership.

Data sources