Network demand outlook: Busier, Steady, or Cooling

What this gauge is

The Network demand outlook is the first thing you see when you open Forecasting: a single dominant word, Busier, Steady, or Cooling, that reads the whole network's next 90 days of restoration demand in one glance. It is the HQ-scale sibling of the demand read every location already sees in its own IQ account, rolled up so leadership can see where the network as a whole is heading and how evenly that read is shared across locations, without opening a single office's books.

Verinode does not run your capacity plan for you. This gauge tells you what the published, public signals imply about work volume across your locations over the next quarter. What you do with that, hire ahead, redeploy equipment, hold, or tighten, is a leadership call.

Where to find it

Open Forecasting from the HQ sidebar, under the Intelligence group alongside Benchmarks, Margin & Cash, and Impact, at hq.verinode.ai/forecasting. The Network demand outlook is the left-hand card of two side-by-side hero cards at the top of the page. Its partner on the right, What it means, translates the same read into an actionable location count and a network move (a separate topic from this article, but the two cards are read together, left to right: first the posture, then what to do about it).

What it shows

The label

A small uppercase line at the top of the card reads "Network demand · next 90 days," so the card is never mistaken for a read on the present, this is a forward-looking window, not what is happening in your network right now.

The dominant posture word

Directly under the label sits the headline: one of three words, in large bold type, color-coded so the read registers before you've finished reading it:

• Busier, in green. More restoration work is implied across the network over the next quarter than the network is currently holding.
• Steady, in copper. The network's demand is holding at its current level, no significant shift implied either way.
• Cooling, in ember red. Less work is implied over the next quarter than the network is currently holding.

This word is not a vote or an average sentiment, it is whichever of the three groups (busier, steady, cooling) contains the most locations. If busier locations outnumber both steady and cooling, the network reads Busier; if cooling locations lead, it reads Cooling; otherwise it settles on Steady. A near-tie between busier and cooling, with neither clearly ahead, also resolves to Steady, the card only calls a direction when one side clearly leads.

The location count

Beside the posture word, in smaller muted type, sits the total location count behind the read, for example "42 locations." This is every location in your network with enough profile data (specifically, a state on file) to compute a demand read. It is the denominator for everything else on the card: the distribution bar and its percentages are all shares of this number.

The distribution bar and percentage split

Below the headline sits a thin horizontal bar, stacked in three colored segments sized to their share of the network: green for busier, copper for steady, ember red for cooling. A location that isn't in a segment (for example, a network with zero cooling locations) simply leaves that segment out, so the bar always sums to the full width across whichever groups are actually populated.

Under the bar, a row of three labeled figures spells out the same split in numbers: a colored dot, a bold percentage, and the word it belongs to, "62% busier," "24% steady," "14% slower." Each percentage is that group's location count divided by the total, rounded to the nearest whole percent. Read together, the dominant word tells you the headline; the bar and the percentages tell you how lopsided or how close that headline actually is. A network that reads Busier at "58% busier · 35% steady · 7% slower" is a much more even split than one that reads Busier at "91% busier · 9% steady," even though both show the same headline word.

How a location's posture is decided (and why HQ can show this without crossing the privacy boundary)

This is the part worth understanding, because it is what makes this gauge possible at all under HQ's privacy rules. Every location's own busier, steady, or slower read is built entirely from published, public industry indicators, national and state-level series like claims frequency, catastrophe and severe storm losses, the hurricane season outlook, residential construction activity, contractor backlogs, water damage claim share, home sales activity, consumer sentiment, and mortgage rates, weighted and scored into a single momentum read, scoped to the state that location operates in. None of it comes from a location's own jobs, invoices, margins, or any other private business data.

Because the read is built from public data rather than a franchisee's own numbers, HQ can safely show the full network distribution, and the by-region breakdown further down the page, without ever touching a single location's books. Two locations in the same state will always show the same posture, because the network only computes one demand read per state represented among your locations, not one per location, then counts how many locations fall in each state to build the distribution. For the full rules on what HQ can and cannot see across the network, read What HQ sees: the network privacy boundary.

How to read it in practice

• Busier: the network as a whole is leaning toward more work than it currently holds. The "What it means" card to the right frames this as a capacity planning window, get ahead of crew and equipment across the network before the demand lands, because the busier locations are where crew and equipment get tight first.
• Steady: no clear lean either way. The guidance is to hold capacity where it is and keep watching the drivers, not to sit still indefinitely, just that nothing here calls for a network-wide capacity move yet.
• Cooling: the network as a whole is leaning toward less work than it currently holds. This reads as a window to tighten cost and chase the backlog already on hand, not a crisis signal, a softer quarter is a normal part of a demand cycle.

Below the two hero cards, a synthesis line, labeled "The network's read on demand," strings the same facts into a short plain-English paragraph: the dominant posture, how many locations sit in each group, what that implies for the network, and the top one or two published indicators actually driving the read (for example, "claims frequency rising" or "severe storm losses climbing"). It closes by pointing you to the By region row further down the page, where the same distribution breaks out location by location, so you can see where the posture concentrates rather than just how it splits overall.

The cold state: building the network read

The network distribution only appears once enough locations are contributing profile data to protect any single location's read from being inferred. Below that point, the card shows a single full-width placeholder instead of the split: the label "Network demand · next 90 days," the headline "Building the network read," and an explanation that once enough locations are contributing, the network's demand posture, the busier / steady / slower split, and the by-region breakdown will appear here. This is not a bug or a stalled page, it is the same anonymity discipline that governs every aggregate view at HQ: a distribution small enough to name individual locations by elimination simply doesn't render until it's large enough not to.

Related reading

• What HQ sees: the network privacy boundary, the trust rules that let this gauge exist without exposing any one location's data.
• Industry Data tab: macro series for the whole network, the same published series that feed this outlook, shown in full with sources on Benchmarks.
• Network Health: the network home, for the rest of what your Network Health page shows above and below the demand read.
• HQ Benchmarks, the wider set of network comparison tools this section sits alongside.