What's moving demand: the network's top drivers

What this is

Every demand read on Forecasting, the network's dominant posture, the busier/steady/cooling split, the by-region breakdown, comes with a "why": a short list of the published industry indicators actually behind the read, worded in plain language, for example "claims frequency rising" or "severe storm losses climbing." This article is about that "why": how Verinode decides which two or three drivers are the network's shared top drivers, out of the much longer list of indicators that could, in principle, be behind any one location's read.

This is not a separate tool or a page of its own. It is a computation that runs once a day behind the two places the drivers actually show up: the hero card's Drivers: line and the network's-read paragraph's What is moving it clause. If you have already read Network demand outlook: Busier, Steady, or Cooling and What it means: the locations to plan for and the network move, this article is the methodology underneath the driver notes both of those describe.

Where it surfaces

The hero card's "Drivers:" line

On the right-hand hero card, What it means, a line beneath the guidance paragraph reads "Drivers:" followed by up to two short plain-language notes, separated by a middle dot, for example "Drivers: claims frequency rising · rebuild input costs elevated." This line is left off entirely when the network has no shared drivers on file for the current snapshot. It never appears empty or as a placeholder dash, the row simply is not there.

The synthesis paragraph's "What is moving it" clause

Directly under the two hero cards, the network's-read paragraph, labeled "The network's read on demand," ties the posture, the split, and the drivers into one piece of prose. Near the end of that paragraph sits a clause that starts "What is moving it:" followed by the same top driver notes, joined in plain English (a single driver stands alone, two are joined with "and," and if a third were ever surfaced this way it would take an Oxford comma). Like the hero card's line, this clause is skipped entirely when there is nothing to report, the paragraph simply moves from "what the posture means" straight to pointing you at the by-region row below.

Both places pull from the exact same computed list. Neither one recalculates anything on its own, they are two different renderings of one daily result.

How the top drivers are computed

The computation happens in two passes: first per state, then across the network. Understanding both passes is what makes the difference between "a driver that matters somewhere" and "a driver that counts as one of the network's top three" clear.

1. 1Every distinct state gets its own demand outlook, computed once. Verinode looks at the state on file for every location in your network, not the location count, the distinct state count, so a network with forty locations spread across six states computes six outlooks, not forty. A location with no state on file falls into a shared "national" bucket rather than being dropped.
2. 2Each state's outlook keeps its own top three drivers, ranked by pull, not by name. For every state, Verinode scores the published indicators that apply to that state's region (claims frequency, catastrophe and severe storm losses, the count of above-average severe-weather events, the hurricane season outlook, residential construction activity, contractor backlogs, the water damage share of claims, existing home sales, consumer sentiment, and mortgage rates, weighted so claims activity and catastrophe losses carry the most pull, construction activity and backlogs a middle amount, and home sales, sentiment, and borrowing costs the least) into that state's own busier/steady/cooling score. Whichever three indicators pulled that score hardest, up or down, become that state's own top three drivers. This is the identical calculation behind every individual location's own demand read inside its IQ account; see What's driving demand: the industry driver table for the full indicator table from that side.
3. 3Verinode counts how many distinct state outlooks share each driver. Across every state's top-three list, Verinode tallies, for each indicator, how many separate states had it in their own top three. This is a frequency count of states, not a re-scored network average and not a count of locations, a driver that shows up in three of your six states' top-three lists scores higher than one that shows up in only one state's list, regardless of how many locations happen to sit in those states.
4. 4The three most-shared drivers become the network's top drivers. Verinode sorts every indicator by that state-count, highest first, and keeps the top three. Those three, each carrying the plain-language note from wherever it was first found (for example "claims frequency rising"), are written to today's network snapshot as the network's shared top drivers.

Only two of the three computed drivers are shown today

The network snapshot stores three top drivers, but both places they surface, the hero card's line and the synthesis paragraph's clause, only ever print the first two. This is a deliberate readability choice: two short plain-language clauses read cleanly in one line or one sentence, a third tends to make either spot feel like a list rather than a plain read. The third driver is real and computed the same way as the other two, it is simply not part of either rendering today.

What each driver note actually contains

A driver is stored as three parts: a plain label (the indicator's name, for example "Property Claims Frequency"), a direction (whether the indicator is pulling the read up, down, or holding flat), and the short note that actually gets printed ("claims frequency rising"). Only the note is shown on Forecasting today, the label and direction ride along with it in the underlying record but are not rendered as separate text or an up/down icon on this page. If you want the indicator's own value, its trend line, and its published source, scroll down to the Industry signals row on the same Forecasting page, or read the full catalog in Industry Data tab: macro series for the whole network.

Refresh cadence

Drivers are recomputed once a day, in the same run that recomputes the whole demand snapshot, the posture counts, the busier/steady/cooling split, and the by-region breakdown. There is no separate schedule for drivers alone: whatever the hero card and by-region row show as today's snapshot is exactly what the drivers were computed from, using that same day's set of published indicators.

Empty state: no shared drivers on file

If none of your network's state outlooks have any drivers, most commonly because the underlying published indicators have not connected for any of your states yet, or if your network is small enough that Forecasting is still in its cold state (see the callout below), both the hero card's Drivers line and the synthesis paragraph's What is moving it clause are simply left out. Nothing reads "no drivers found" or shows a dash, the surfaces that would show drivers just move straight to the next thing they have to say.

Best-practice example

Say your network operates across six states. Four of those states' own top-three lists include "severe storm losses climbing," three include "claims frequency rising," and two include "rebuild input costs elevated." No other indicator appears in more than one state's top three. The network's top drivers, ranked by that count, are severe storm losses (4 states), claims frequency (3 states), and rebuild input costs (2 states), in that order. The hero card's Drivers line and the synthesis clause both show the first two, "Drivers: severe storm losses climbing · claims frequency rising", because those are the two most widely shared across your states this snapshot. Rebuild input costs is the third-ranked driver, computed and stored, but not printed on the page today. If you wanted the full picture, including that third driver and the raw indicator values behind all of them, the Industry signals row further down the page carries the complete national series with sparklines and sources.

Related help articles

• Forecasting: your network's demand posture, next 90 days
• Network demand outlook: Busier, Steady, or Cooling
• What it means: the locations to plan for and the network move
• Industry Data tab: macro series for the whole network
• What HQ sees: the network privacy boundary
• What's driving demand: the industry driver table, the same indicator scoring from a single location's own IQ account
• Forecasting: past, present, and future demand

Data sources