"Forecasting: past, present, and future demand"

Margin tells you how a job did. Benchmarks tell you how you compare to peers today. Forecasting is the forward-looking piece: where the industry's demand is heading over the next 90 days, whether y…

12 min read·Updated July 13, 2026
On this page

What Forecasting is

Margin tells you how a job did. Benchmarks tell you how you compare to peers today. Forecasting is the forward-looking piece: where the industry's demand is heading over the next 90 days, whether your own crew, equipment, and cash can absorb it, and what to do about the gap between the two. It is the Co-COO's read on the future, not a crystal ball. Verinode reads published macro and industry data alongside your own operating picture, projects it forward, and lays out the options. You decide what to do with them.

Forecasting completes a three-part view: your performance (Margin), how you compare (Benchmarks), and where things are going (Forecasting).

Where to find it

Open Forecasting from the sidebar at iq.verinode.ai/forecasting.

Note

Forecasting is a section-activation-gated section. If you have not switched it on yet, the route shows a "Switch on Forecasting" panel instead of the live page: a blurred preview of the real layout underneath, the line "Where your cash and your workload are headed in the weeks ahead," and a single button, Switch on Forecasting. Click it and the same page loads in place, no separate confirmation step. If IQ has flagged Forecasting as a fit for you, the panel adds a small Suggested for you label above the heading and a plain-language reason. If you have told IQ which areas matter most right now, the panel may note that too: "You can switch this on anytime. For now, I'd stay focused on [your stated areas]." Either way, nothing is switched on until you click the button, and the panel's closing line is exact: "Data will appear here as it flows in. Nothing is switched on until you say so."

Once it is on, the page loads with four things stacked top to bottom: two gauge reads, IQ's connected read, a seasonal strip, and a Take Action row.

1. The two gauge reads

At the top of the page, two side-by-side gauges give you the whole read at a glance. Both are clickable and open a detail overlay with the evidence behind them.

Demand outlook

Labeled Demand outlook · next 90 days. The headline is one of three words: Busier (green), Steady (copper), or Cooling (red), next to a momentum figure like "momentum +34" or "momentum -12". Momentum runs from -100 (much slower) to +100 (much busier) and is shown on a small rail marked Slower / Steady / Busier, with a dot marking where you sit.

Below that, a "Top driver" line names the single strongest published indicator behind the read, in plain language, for example "claims frequency rising" or "borrowing costs elevated." Clicking anywhere on this gauge, or the "what's driving this →" link, opens the full What's driving demand overlay.

How the outlook is built. Verinode pulls published macro and industry series scoped to your region (claims frequency, catastrophe and severe-storm losses, hurricane season outlooks, residential construction, contractor backlogs, water-damage claim share, home sales, consumer sentiment, mortgage rates), weighs each one by how strongly it moves restoration work volume, and reads its recent trend. Indicators that point toward more restoration work push the score up; a couple (mainly elevated mortgage rates, which soften discretionary remodel demand) pull it down. The blended result is the momentum score, and the level (Busier / Steady / Cooling) is just that score read against a threshold: strongly positive reads Busier, strongly negative reads Cooling, everything in the middle reads Steady.

If no industry data is connected yet for your region, the gauge still renders with a neutral "Steady" read and the driver line says "Industry data fills in as it connects."

Your capacity

Labeled Your capacity. The headline is a headroom percentage (for example "62%") with the word headroom beside it, colored green when you have plenty of slack, yellow when it is getting tight, and red when you are close to maxed. Under the number, a status line reads one of three things: Can absorb the outlook, At capacity for the outlook, or Capacity loading while the underlying reads are still assembling.

Below that, a "Breaks first" line names the single most severe operating constraint right now, for example "Water line has no qualified crew," followed by "see all N constraints →" when there is more than one, or "see the detail →" when there is just the one. If nothing is currently constrained, it reads "No binding constraint right now."

How headroom is built. Headroom blends several operational reads into one 0-100 number: your equipment capacity adequacy (are you deployed above or below what your fleet can support), whether your crews are showing a surge signal (jobs per crew member spiking in the last 30 days versus your 90-day rate), how many service lines have no qualified crew at all or are running one-deep on coverage, and whether training compliance has slipped. Each of those subtracts from a starting baseline; a fully staffed, well-equipped shop with no coverage gaps sits high, a shop running hot with uncovered lines sits low. Whether that headroom is "enough" depends on the demand outlook: a Busier read needs meaningfully more spare capacity to count as "can absorb" than a Cooling one does, since more work is coming whether or not you have the room for it.

Clicking through. Both gauges open an overlay:

  • What's driving demand shows the full headline and momentum score again, the plain-language rationale sentence (for example, "The signals point up: claims frequency rising, catastrophe losses climbing. Plan capacity before the work lands, not after."), a margin-pressure note when input costs or wages are running hot separately from demand, and the full demand driver table: one row per published indicator, its category, a recent-trend sparkline, its current value, and its recent percent change, colored by whether the move helps or hurts your pipeline. A closing note points you to the Industry Data tab in Benchmarks for the full series, the named public source, and the methodology, and states plainly: "Industry data is never your data, and is never sold."
  • Your capacity shows the headroom number again, the can-absorb status, and the full list of binding constraints worst-first, each with its domain (coverage, people, equipment, cash, or safety), a severity tag (Critical, Tight, or OK), and a plain note explaining what is actually tight. If nothing is constrained it reads, "No binding constraint right now. You have room to take on more work. Model a plan to see how far you can push."

2. IQ's read on demand

Directly under the two gauges, flowing flat with no card frame around it, is IQ's read on demand: a short paragraph that connects what the two gauges show separately into one plain-language "here's what this means for you." It always follows the same shape:

  1. States the demand read plainly ("Demand is pointing up over the next 90 days," "Demand looks steady," or "Demand is cooling").
  2. States your capacity against that read (for example, "You are running at about 22% headroom, so you can't fully take on a busier season without adding capacity first," or "You have about 68% capacity headroom right now").
  3. Names the first thing that would break if you took on more work, when there is one, in one sentence.
  4. Adds a margin-pressure note when input costs or wages are running ahead of normal, kept as a separate point from volume, because more work at thinner margins is a different decision than more work.
  5. Closes with the same instruction every time: "Model a plan below to see how far you can push, then turn it into a decision."

This paragraph is the bridge between the read above it and the Take Action row below it: it is why the modeler tile always says "model a plan" right after telling you what breaks first.

3. The seasonal strip

Below a hairline divider, a Season strip shows where you are in the restoration demand calendar right now: a row of 12 small bars, one per month, colored by phase, with the current month highlighted and labeled (for example, "Spring storms · April"). Four phases run through the year:

  • Winter freeze (December through February): freeze and burst-pipe water losses spike, sharpest in cold-climate states, while new-work volume typically slows and the storm-season backlog pays through.
  • Spring storms (March through May): severe-storm season ramps (hail, wind, flood), building toward the summer peak.
  • Hurricane / CAT (June through November): Atlantic hurricane season, peaking August through October, drives catastrophe surges for Gulf, Atlantic, and coastal operators; summer storm and flood volume runs at its highest nationally.
  • Shoulder: the quieter stretch between phases.

Under the strip, a plain-language note explains what the current phase means for you. If you are in hurricane/CAT season but your state carries little coastal hurricane exposure, the note is softened so you are not told to prep for a coastal surge you will not feel: "Peak storm and flood season nationally. Your market carries less coastal hurricane exposure, so lean on your own bookings; summer volume still runs high." This is the same calendar prior the decision engine reasons over elsewhere, so a seasonal decision card you see in the feed and this strip always agree.

4. Material cost outlook

When you have material spend on file, a Material cost outlook block appears below the seasonal strip. It reads your material spend against the family-matched producer price index (PPI) trend and states, in one sentence, whether material prices are trending up or down year over year and by roughly how much, translates that into a dollar figure at your current run-rate ("At your current run-rate that is about $18k more a year"), and projects next quarter's material spend in dollars. This block is omitted entirely when you have no material spend connected yet.

5. Take Action

The bottom of the page is a single horizontal row titled Take Action. Two kinds of tiles live here.

The scenario modeler (always first)

The first tile is always Model a growth plan, labeled "Plan ahead," with the sub-line "Test adding crew, a margin target, or a busier season against your real capacity and cash cycle. IQ pressure-tests it." This tile never disappears, so Forecasting is never truly "empty": even with no open decisions, there is always something to do. Clicking it opens the full modeler in an overlay.

Inside the modeler:

  1. 1Set three levers. Field crew (technicians and crew who run jobs, not office staff) as a delta from your current headcount, shown as "8 → 11 crew" style so a zero never reads as "no crew." Gross margin target, defaulting to your current margin. Demand adjustment, defaulting to a percentage IQ derives from the demand outlook score (roughly proportional, capped around plus or minus 15%), with a hint telling you what the outlook set it to and inviting you to override it if you read the season differently.
  2. 2Read the projection. A 12-month chart shows your current run-rate as a dashed ghost line against the modeled plan as a solid copper line, with projected annual revenue and the dollar delta versus today above it, and projected gross profit and working capital tied up (revenue at your average days-to-pay, divided by 365) below it.
  3. 3Have IQ pressure-test it. Click Have IQ pressure-test this plan. IQ reasons over the exact numbers on screen against your real capacity, cash cycle, and binding constraint, and returns a verdict (Go, Caution, or Stop), a headline, a short read explaining what the plan actually does, a "what to watch" list, a cash-and-financing note when relevant, and a single next move. If the plan grows headcount or demand while a coverage, people, or equipment constraint is active, a flag appears even before you run the analysis: "Capacity matters here: [the constraint] is what breaks first. Fix that alongside this plan or the growth won't land."
  4. 4Turn it into a plan. Click Turn this into a plan to save it. A confirmation reads "Plan created. Find it in Take Action and your Decisions."

The baseline the modeler starts from is your own operating numbers (revenue, gross margin, headcount, average days-to-pay) where you have them, with peer medians filling any gap so a thin-data operator can still model a plan on day one. A small label above the sliders tells you plainly which situation you are in: "Built on your own numbers," "Your numbers, peer-filled where missing," or "Peer medians until your data fills in." If you are out of Intelligence Capacity when you try to run the analysis, it says so directly: "You're out of Intelligence Capacity for now. Upgrade or top up to have IQ analyze plans," and the pressure-test simply does not run until you do.

Demand decisions

Following the modeler tile, any open forecasting decisions render as standard decision tiles: personalized recommendations Verinode has surfaced from your demand and capacity data. If there are none, a tile reads:

Demand decisions: No open demand decisions As the outlook shifts, IQ drafts what to do about it. Model a plan to test how far you can push.

How the page's data assembles

Forecasting's read is built from three layers, joined server-side each time the page loads:

  • Published industry indicators, scoped to your operating region: claims and catastrophe series, construction and labor cost trends, residential activity, and weather-driven signals, sourced from federal and public data providers (the Federal Reserve's FRED aggregate, which itself rolls up Bureau of Labor Statistics, Census, and other federal series; NOAA/National Weather Service alerts; OpenFEMA disaster declarations; USGS; and other public feeds). These never carry your data, and your data is never fed into them.
  • The operating model, a cross-section snapshot of your own business: workforce, crew capacity and coverage, recruiting pipeline, equipment adequacy, cash position and days-to-pay, cost ratios, and safety compliance. This is the same composed snapshot the decision engine and the scenario modeler read, so the number on this page never disagrees with a decision card elsewhere.
  • Your operator baseline: your own revenue, margin, headcount, and days-to-pay where you have enough data on file, with peer medians filling any gap so the modeler always has something real to start from. The baseline always carries a plain label (operator, mixed, or cohort-derived) so you know exactly how much of it is yours.

Because the operating model, the demand outlook, and the scenario modeler all share this one assembled snapshot, the headline on the page, the read IQ gives you, and the plan you model are always talking about the same underlying facts.

Best-practice example

Say the demand gauge reads Busier, momentum +38, driven by claims frequency rising and severe storm losses climbing. Your capacity gauge reads 34% headroom, At capacity for the outlook, with the binding constraint "2 service lines are one-deep." IQ's read below ties it together: demand is pointing up, you have enough headroom to take on some of it but not all, and one-deep coverage is the first thing that would break if the season lands as forecast. Rather than waiting for that to become a crisis, open the modeler, add two field crew against the outlook's demand adjustment, and have IQ pressure-test the plan. If the read comes back Caution with a note that hiring lead time will lag the storm ramp, the next move is clear before the season arrives, not after.

Data sources

Data sources

  1. 1.Claims, catastrophe, and construction/labor indicators. Federal Reserve FRED (aggregating Bureau of Labor Statistics, Census, and other federal sources).
  2. 2.Severe weather alerts. NOAA / National Weather Service.
  3. 3.Disaster declarations. OpenFEMA.
  4. 4.Earthquake activity. USGS.
  5. 5.Material price trend. Producer price index series, family-matched to your material spend.
  6. 6.Your capacity, workforce, cash, and cost picture. Your business.
  7. 7.Your revenue, margin, and headcount baseline. Your business, peer-filled where missing.
Was this helpful?