The network's read on demand (the synthesis)

What it is

The two hero gauges at the top of Forecasting, Network demand and What it means, each give you a number and a word. They sit side by side and they do not talk to each other in prose. The network's read on demand is the paragraph directly beneath both of them that does: it takes the dominant posture, the busier/steady/cooling split across your locations, what that split means for the network's next move, and the top published drivers behind it, and strings them into one short, connected paragraph, the way a fractional COO would summarize two charts before telling leadership what to do next.

It is not a chart, a score, or a clickable element. It is the bridge between the two gauges above it and the By region row further down the page: the gauges are the data, this paragraph is the meaning, and it closes by pointing you at exactly where to look next.

Visually, the paragraph sits on its own lifted, accent-tinted glass surface with an HQ mark and a steel blue uppercase label, "The network's read on demand", the same "speaker" identity treatment used for IQ's read on demand on the IQ side of Forecasting. That treatment is reserved for page-level reads that sit directly on the page background rather than inside an already-framed deck, so it never reads as a card inside a card.

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 paragraph sits directly beneath the two hero gauges (Network demand on the left, What it means on the right) and directly above the By region row. There is no tab bar on this page and nothing to switch on: once you have HQ access, Forecasting is always live.

The five parts, in order

The paragraph is always built in the same fixed order. Depending on what your network's demand summary contains, some parts are included and some are left out, but the order never changes and the closing line never changes.

1. 1The dominant posture. One plain sentence naming the network's overall read for the next 90 days: "Your network is trending busier over the next 90 days." when the dominant level is busier, "Your network is cooling over the next 90 days." when it is slower, or "Your network is holding steady over the next 90 days." when it is steady. If your network's dominant level has not resolved yet for the current snapshot, this sentence defaults to the steady wording rather than leaving the paragraph blank, the same fallback the two gauges above it use.
2. 2The split across locations. Only appears when at least two of the three buckets (busier, steady, cooling) actually carry locations. It reads "Across [N] locations, [busier count] busier, [steady count] steady, and [cooling count] cooling." (or just two of the three terms, joined with "and", when only two buckets are populated). If every one of your locations sits in a single bucket, for example a network that is uniformly busier with nothing steady or cooling, this sentence is left out entirely rather than stating the obvious.
3. 3The network move. One sentence naming what the posture means for your network's next step, tied to the dominant level, not to a specific number:
4. 4- Busier: "The busier locations are where crew and equipment get tight first, so that is where to get ahead of capacity before the work lands."
5. 5- Cooling: "The cooling locations have a window to tighten cost and work the backlog on hand."
6. 6- Steady: "Hold capacity where it is across the network and watch the drivers."
7. 7What is moving it. Only appears when your network's demand summary has at least one shared driver on file. It reads "What is moving it: [driver one] and [driver two]." using up to two of the top published drivers behind the read, in plain language (a claims-frequency shift, a rate change, and similar). When no drivers are on file for the current snapshot, this sentence is skipped, it never appears as an empty "What is moving it:" line.
8. 8The close, always the same. "The by-region split below shows where it concentrates." This line never varies and never disappears. It is the explicit handoff from the network-wide read to the By region row directly beneath it, where the same split breaks out location by location.

Worked examples

A network trending busier, all three buckets populated, with drivers on file: "Your network is trending busier over the next 90 days. Across 14 locations, 5 busier, 7 steady, and 2 cooling. The busier locations are where crew and equipment get tight first, so that is where to get ahead of capacity before the work lands. What is moving it: claims frequency rising and severe storm losses climbing. The by-region split below shows where it concentrates."

A network cooling, with only two buckets populated: "Your network is cooling over the next 90 days. Across 9 locations, 6 steady and 3 cooling. The cooling locations have a window to tighten cost and work the backlog on hand. The by-region split below shows where it concentrates." Notice there is no driver sentence here: this network's snapshot simply has none on file for the current period.

A network holding steady, uniformly, no split sentence: "Your network is holding steady over the next 90 days. Hold capacity where it is across the network and watch the drivers. The by-region split below shows where it concentrates." Every location in this network sits in the same steady bucket, so the split sentence, which only exists to show how a posture divides across more than one group, is left out rather than stating that all locations agree.

No dominant level resolved yet, no drivers, nothing populated: "Your network is holding steady over the next 90 days. Hold capacity where it is across the network and watch the drivers. The by-region split below shows where it concentrates." This is the shortest the paragraph ever gets, the split sentence and the driver sentence both drop out, but the paragraph itself is never blank and the closing pointer to By region always appears.

How this differs from the two gauges above it

The Network demand gauge and the What it means gauge each show one fact on their own: a posture word plus a distribution bar, and an actionable location count plus a planning verb. This paragraph does not add a new number. It restates exactly those same facts, the dominant posture, the same busier/steady/cooling counts behind the distribution bar, and the same top drivers named on the What it means gauge, connected into sentences a leadership team can read once and act on, instead of reading two separate cards and doing the connecting themselves. If a line here makes you want the underlying mechanics, that is what the two gauges are for: see "Network demand outlook": Busier, Steady, or Cooling and What it means": the locations to plan for and the network move.

How to use it

Read this paragraph first if you only have thirty seconds on the page: it tells you the network's overall lean, how evenly that lean is shared across your locations, what to do about it, and what published signal is behind it, all in one pass. Then follow its own closing instruction: scroll to By region directly below it to see where that posture actually concentrates. A network that reads "Busier" because one storm-exposed region is running hot behaves very differently from one that is evenly busier everywhere, and the right network-wide move, a regional equipment push versus a network-wide hiring conversation, usually follows the region, not the network-wide sentence alone.

The privacy boundary in this paragraph

Every fact this paragraph draws on, the dominant posture, the busier/steady/cooling counts, and the driver notes, comes from your network's pre-aggregated demand summary and from published national indicators. None of it is, or is derived from, any single location's private jobs, invoices, or margin data. The same structural boundary that governs the rest of HQ governs this paragraph: it can only ever describe a location's demand posture, computed from that location's state against public industry data, never that location's actual business figures. See What HQ sees: the network privacy boundary for the full mechanics.

Empty state: when the network is too small to show a read

This paragraph does not have its own separate empty state. It is part of the same hero block as the two gauges above it, and until your network has enough active, contributing locations to protect any single location's posture from being inferred, that entire block, both gauges and this paragraph, is replaced by one full-width card:

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.

Below that floor, the paragraph is not shown in a degraded or partial form, it simply does not render at all, because the same distribution it would summarize is what is being withheld. Once your network clears the floor, the gauges, this paragraph, and the By region row all appear together in the same page load.

Best-practice example

Say your network's dominant level is busier, with the distribution bar above showing 5 of 14 locations busier, 7 steady, and 2 cooling, and the What it means gauge naming "claims frequency rising" and "severe storm losses climbing" as drivers. The network's read on demand ties all of that into one paragraph: your network is trending busier, the split shows most locations are still steady rather than a network-wide surge, the busier locations are where to get ahead of crew and equipment first, and the storm-driven claims activity is what is behind it. That reading points you at one next step immediately: open By region below to see whether those 5 busier locations sit in one storm-exposed region (route an equipment push there specifically) or are scattered across the network (a broader trend worth a network-wide capacity conversation), before committing budget either way.

Related articles

• "Network demand outlook": Busier, Steady, or Cooling
• "What it means": the locations to plan for and the network move
• Forecasting: your network's demand posture, next 90 days
• What HQ sees: the network privacy boundary
• Network Health: the network home
• HQ Benchmarks
• Industry Data tab: macro series for the whole network
• IQ's read on demand, the same synthesis pattern from a single location's own IQ account