Forecasting: your network's demand posture, next 90 days

What the Forecasting section is

Forecasting is where Verinode HQ reads where demand is heading for your network as a whole over the next 90 days: how many of your locations are trending busier, holding steady, or cooling off, where that split concentrates by region, and what the wider industry's published indicators are doing right now. It is the network-scale sibling of the Forecasting section every location sees inside its own IQ account (see Forecasting: past, present, and future demand), but it never shows a single location's own numbers. HQ's page answers one question only: what does the network, taken together, look like for the season ahead.

Forecasting is not a booking calendar, a staffing planner, or a P&L projection. It surfaces a posture and a set of public reference series so leadership can decide where to point a call, a program, or an equipment push, the same way Margin & Cash surfaces profitability and Benchmarks surfaces operating performance. Verinode does not decide anything here. It reads the signals and lays out the read; your team makes the call.

The privacy boundary holds completely on this page. Every number here is a network aggregate or a public industry figure. Nothing on Forecasting is, or is derived from, a franchisee's private business data, not revenue, not margin, not jobs, not invoices. The section that follows on how the page is built explains exactly why that is true structurally, not just by policy.

Where to find it

Open Forecasting from the HQ sidebar, in the Intelligence group alongside Benchmarks, Margin & Cash, and Impact, or go directly to hq.verinode.ai/forecasting.

The page loads as a single stack: a hero band at the top, a network-read paragraph directly under it, then two horizontally scrolling rows, By region and Industry signals. There is no tab bar and nothing to switch on: unlike IQ's Forecasting section, which is section-activation-gated per operator, the HQ page is always live once you have HQ access at all.

The hero band: your network's demand posture

At the top of the page sit two glass cards side by side.

Left card, "Network demand · next 90 days." A single large word states the network's dominant posture: Busier (green), Steady (copper), or Cooling (red), next to how many locations are behind the read, for example "14 locations." Underneath, a stacked distribution bar shows the busier / steady / slower split across every location as one continuous bar, colored green, copper, and red in that order, with a legend beneath it reading the exact percentage in each band, for example "36% busier," "50% steady," "14% slower."

Right card, "What it means." A large number states how many locations sit in the actionable, dominant bucket (the same count the left card's posture is drawn from), followed by a short verb label in the posture's color: Plan capacity (busier), Hold steady (steady), or Tighten (cooling). Below that, a guidance sentence spells out what the posture means in practice:

• Busier: "N of N locations are trending busier. Get ahead of crew and equipment across the network before the work lands."
• Cooling: "N of N locations are cooling. A window to tighten cost and chase the backlog on hand."
• Steady: "Demand is holding steady across N locations. Keep capacity where it is and watch the drivers."

When the network has shared drivers behind the read, a closing line, "Drivers:...", names up to two of them in plain language, for example "claims frequency rising · rebuild input costs elevated."

The network's read on demand

Directly beneath the hero band, flowing flat on the page background with no card frame separating it from the hero above, sits the network's read on demand: a short paragraph that ties the two hero cards together into one plain-language narrative. It states the dominant posture, then the actual split across locations ("Across 14 locations, 5 busier, 7 steady, and 2 cooling"), then what that means for the network (the busier locations are where crew and equipment tighten first, the cooling ones have room to tighten cost and work the backlog, or to hold capacity and watch the drivers on a steady read), then what is moving demand when drivers exist, and it closes by pointing you to the by-region split below as where the posture concentrates. This is the same identity treatment used across the platform for an AI-authored read, an HQ mark and label on a lifted glass surface, distinct from a plain data tile, so it clearly reads as Verinode speaking rather than another metric.

When the network is too small to show a split

Below a certain number of contributing locations, showing a busier/steady/slower distribution would really be describing one or two locations dressed up as a "network split," so HQ withholds it instead. In that state, the hero band collapses to a single full-width card reading:

Network demand · next 90 days Building the network read Once enough locations are contributing, the network's demand posture, the busier / steady / slower split, and the by-region breakdown appear here.

When the network hasn't cleared that bar, the network's read paragraph, the By region row, and the Industry signals row all still respect the same gate for anything that depends on locations, so the page never shows a distribution built on too few contributors. This is the same coverage discipline described in Coverage labels and the anonymity floor: Verinode would rather show nothing than show a number that could effectively identify one location's own read.

Row 1: By region

This row breaks the same busier/steady/slower split out by where your locations sit, one tile per region, sorted with the region carrying the most locations first, capped at the first twelve regions. Each tile shows:

• Label: the region, generally your locations' state. Locations with no state on file roll up under a single tile labeled Unspecified.
• Value: how many locations in that region carry the region's dominant read.
• Sub: the plain-language posture for that region, Trending busier, Holding steady, or Cooling off.
• Accent color: green for a busier region, copper for steady, red (ember) for cooling, matching the hero band's palette.

Use this row to see where a busier or cooling read concentrates geographically, a network that is "Busier overall" because of a hurricane-exposed region behaves very differently from one that is broadly busier everywhere, and the right network-wide move (equipment staging, a regional hiring push, a cost-tightening conversation) usually follows the region, not the network-wide average alone.

This row is governed by the same locations-floor gate as the hero band: it renders no tiles at all until the network clears it, and it also renders nothing if there is simply no regional data yet.

Row 2: Industry signals

The bottom row is the network's shared reference to the wider industry, the same national published macro and industry series described in What's driving demand: the industry driver table on the IQ side. One tile per indicator:

• Label: the indicator's plain-language name, for example "Property Claims Frequency" or "Rebuild Input Costs."
• Value: formatted for its own unit, a percentage reads with a trailing "%", a dollar figure with a leading "$", any other unit as the number followed by its unit word.
• Sub: the plain-language operator read on what the figure means, the same translation IQ gives each individual location.
• Accent color: by category, copper for Demand, violet for Economic, steel blue for Insurance, teal for Weather, amber for Input Cost and for Labor.
• A sparkline, when the indicator has more than one point of recent history, tracing its recent trend.

Because this row draws entirely on published national series, it is not gated by your network's size at all, it appears the same way whether your network has two locations or two hundred, and it never carries a franchisee's own figures. See Industry Data tab: macro series for the whole network for the full series list, every named publisher, and the methodology behind each one.

Empty state. If nothing has connected yet, this row simply shows no tiles, the same "data will appear as it flows in" pattern used across the platform rather than an error or a placeholder card.

How the page is built, and why the boundary holds

Every figure on Forecasting comes from one of two places, and neither one is a franchisee's private business data:

• The busier/steady/slower posture (hero band, network read, By region) is computed by a scheduled aggregation job that runs against your group's roster, entirely inside the the network layer schema HQ's server is allowed to query. For each of your locations, that job looks up only the location's state (nothing else about its business) and computes what that location's own demand outlook would be, using the same published, public industry indicators (claims frequency, catastrophe losses, construction activity, input costs, and the rest) that feed every individual location's own Forecasting page, scoped to that location's region. It then counts how many locations land in each posture bucket and writes only that count, the region breakdown, and the resulting network-wide snapshot into the network data. HQ's Forecasting page reads that one pre-computed snapshot and nothing else, it never touches a location's revenue, margin, jobs, invoices, or any other business record to build this read.
• Industry signals reads the same published national indicator catalog directly, the identical public reference data every operator's own IQ account reads.

Put together: the only thing that ever crosses from an individual location into this page is which state it operates in, used purely to select which region's public indicators apply to it, and the resulting busier/steady/cooling classification that public data alone produces. No dollar figure, no job count, no client name, and no operational detail belonging to any one location ever appears on this page, in the network read, or in the by-region breakdown. This is the same structural boundary described in What HQ sees: the network privacy boundary, applied to demand instead of margin.

Best-practice example

Say the hero band reads Busier, 14 locations, with the distribution bar showing 50% busier, 36% steady, 14% slower, and the "what it means" card reading "7 of 14 locations are trending busier. Get ahead of crew and equipment across the network before the work lands," with drivers "claims frequency rising · catastrophe losses climbing." The network read paragraph below ties it together and points to By region. There, the by-region row shows your Gulf Coast state carrying the largest busier count, while an inland state sits in the cooling tile. That is the cue to route equipment staging and any hiring push toward the Gulf Coast locations specifically rather than treating the whole network as uniformly busier, and to check whether the cooling inland locations have room to tighten cost in the meantime. Industry signals underneath confirms the same claims-frequency and catastrophe-loss series driving the read, with rebuild input costs also trending up, a signal that the busier season is arriving alongside real cost pressure, worth flagging in the same conversation.

Related help articles

• HQ overview
• Network health
• HQ Benchmarks
• Coverage labels and the anonymity floor
• Industry Data tab: macro series for the whole network
• What HQ sees: the network privacy boundary
• Margin & Cash: how HQ reads network profitability
• HQ Programs
• HQ Standards
• HQ Report Library
• HQ Compliance
• Broadcasting to your network
• Forecasting: past, present, and future demand, the same read from a single location's own IQ account
• What's driving demand: the industry driver table

Data sources