"What it means": the locations to plan for and the network move

What this gauge is

Forecasting is where Verinode HQ turns the network's demand read into a decision. The section opens with two gauges sitting side by side. The left one, Network demand, tells you the shape of the next 90 days across every location. The right one, What it means, is this article's subject: it takes that shape and turns it into the one number, one verb, and one paragraph a network leadership team actually needs to act on. Where the left gauge describes the network, the right gauge tells you what to do about it.

Both gauges read from the same underlying data, your network's demand summary for today's snapshot. Nothing on the "What it means" gauge is a separate calculation; it is the same posture and the same location counts as the Network demand gauge, reframed as an instruction.

Where to find it

Open Forecasting from the HQ sidebar at hq.verinode.ai/forecasting. The two gauges sit at the very top of the page, above the network's read-on-demand paragraph and the by-region and industry-signal rows below. "What it means" is the right-hand gauge in that top pair.

What you see

Eyebrow. The gauge is labeled "What it means" in small caps.

The location count. A large number, followed by the word "locations." This is the actionable subset described below, not your full network. It answers "how many of my locations does this call apply to," not "how many locations do I have."

The verb. Directly beneath the count, in small caps and colored to match the network's dominant posture, one of three network planning verbs:

• Plan capacity, in Deere Green, when the network is trending busier.
• Hold steady, in Copper, when the network is holding steady.
• Tighten, in Ember Red, when the network is cooling.

The guidance line. A short paragraph beneath the verb, in plain language, restating the count and telling you what the posture means for the network's next move.

The driver line. Where Verinode has identified what is pushing the read, a line below the guidance reads "Drivers:" followed by up to two short plain-language notes about what is moving demand (for example, a claims-frequency shift or a rate change), separated by a middle dot. This line is omitted entirely when no drivers are on file for the current snapshot; it never appears empty or as a placeholder.

How the location count is chosen

The count on this gauge is not "everyone" and not a fixed slice, it is whichever bucket matches the network's dominant level for the current snapshot:

• If the dominant level is busier, the count is your network's busier-location count, the same number shown in the green segment of the distribution bar on the left-hand gauge.
• If the dominant level is slower (shown to you as Cooling), the count is your network's slower-location count, the ember segment.
• Otherwise, the dominant level is steady, and the count is your network's steady-location count, the copper segment.

In practice this means the gauge always points you at the group of locations that matches whatever the network as a whole is doing, busier locations when the network is trending busier, cooling locations when it is cooling, steady locations otherwise. It is never a sum of all three segments and never an arbitrary fixed share of the roster; it moves with the actual distribution snapshot to snapshot.

The three planning verbs, in plain terms

Each verb is a network-level instruction, not a prediction and not a guarantee:

• Plan capacity (busier). The named locations are trending toward more work over the next 90 days. The guidance line spells out the busier count against your full roster, for example "4 of 12 locations are trending busier," and the instruction underneath is to get ahead of crew and equipment across the network before the demand actually lands, not after crews are already stretched.
• Hold steady (steady). Demand is holding across the network. The guidance line names your full active location count and the instruction is to keep capacity where it currently sits and keep watching the drivers, rather than making a capacity move on a flat read.
• Tighten (cooling, shown in the verb as "Tighten" and in the location count and guidance as "cooling"). The named locations are seeing demand cool off. The guidance calls out the count and frames the cooling window as an opportunity: a chance to tighten cost and work down whatever backlog is already on hand, rather than a warning to react to.

Verinode surfaces this read. It does not decide staffing levels, budgets, or timing for you, leadership makes that call, using the count, verb, and drivers as the starting brief.

Reading the two gauges together

The Network demand gauge on the left shows the network's overall word (Busier, Steady, or Cooling), your total active location count, and a stacked bar breaking that total into busier / steady / cooling shares with percentages. The "What it means" gauge on the right takes exactly one of those three shares, the one matching the dominant word, and turns it into the count-plus-verb-plus-guidance you act on. If you want to see how the actionable count relates to the full split, or which locations fall into the other two buckets, look at the distribution bar on the left gauge; the by-region breakdown further down the page shows where those buckets concentrate geographically.

Below both gauges, a network synthesis paragraph (labeled "The network's read on demand") restates the same posture, split, and driver information as connected prose, and points you at the by-region row as the next place to look. It is a narrative wrapper around the same numbers, not a new data source.

Where the drivers come from

The driver notes on this gauge are the strongest shared indicators behind the network's demand read, drawn from the same industry-signal data that populates the Industry signals row further down the Forecasting page (claims activity, storm and weather indicators, rate and cost pressure, and similar published series). Only the top two are shown here, worded as short plain clauses. For the full set of indicators, with their trend lines, published sources, and plain-language operator reads, scroll down to the Industry signals row.

Empty state: the network is too small to show a split

Forecasting protects a small network's individual locations the same way every other HQ surface does. Until your network has enough active, contributing locations, Verinode will not publish a busier/steady/cooling split, because a split over too few locations risks reverse-identifying one member's private demand posture. Verinode counts qualifying distinct locations against a floor for this purpose; the exact floor number is not exposed in the interface qualitatively beyond what the empty state below tells you.

Below that floor, both hero gauges collapse into a single full-width card reading:

Building the network read Once at least [N] locations are contributing, the network's demand posture, the busier / steady / slower split, and the by-region breakdown appear here.

There is no separate "What it means" placeholder in this state; the whole top-of-page hero is the one cold card until the network clears the floor. This is the same discipline you'll see across HQ: an absence of qualifying data produces an honest empty state, never a number stretched to look complete.

Best-practice example

Say your network's dominant level is busier, with 4 of your 12 active locations trending that way. The "What it means" gauge shows 4 locations, the verb Plan capacity in green, and a guidance line reading something like "4 of 12 locations are trending busier. Get ahead of crew and equipment across the network before the work lands." A driver line beneath it might read "Drivers: claims frequency rising · storm activity above normal." Before making a network-wide capacity call, check the by-region row further down the page to see whether those 4 locations cluster in one region (a regional surge you can staff toward specifically) or are spread across the network (a broader trend worth a network-wide move). The industry signals row gives you the underlying series behind each driver note if you want the full trend before committing crew or equipment budget.

Related articles

• Network Health: your HQ command home
• What HQ sees: the network privacy boundary
• Benchmarks at HQ