"Capacity: weather, seasonal utilization, and hiring signals"

What the Capacity tab shows

Capacity answers three separate questions about your crew: what is the weather about to throw at you, is your roster sized for the season you are actually in, and does the math support hiring, holding, or reducing headcount right now. Verinode does not run payroll or make the staffing call for you. It reads your team roster, your job history, and a live weather feed for your operator profile's location, does the math a fractional COO would do by hand, and lays out the recommendation with the numbers behind it. You decide.

The tab sits inside the Team section, which mirrors the same card-slider used elsewhere on the platform, with six tabs across the top: Findings, Team, Depth Chart, Performance, Capacity, Benchmarks. Capacity is fourth from the right, tinted amber.

Where to find it

Open Team from the sidebar at iq.verinode.ai/team, then select the Capacity tab. Capacity is lazy-loaded: it is not fetched when the Team page first loads, only when you open the tab, so switching to it shows "Loading weather, seasonal, and hiring signals..." for a moment on first open. If the fetch fails, the tab reads "Capacity data could not load. Retry by reopening the tab."

The tab has three stacked sections, in this order: Weather And Alerts, Seasonal Utilization, and Hiring Signal.

Weather And Alerts

What it is. A live forecast for your operator profile's city and state, paired with restoration-specific alerts (freeze, flood, storm, hurricane, tornado, heat, wind) that carry a staffing recommendation and an expected volume change, not just a weather warning.

Two things have to be true before this section shows real data:

1. Verinode's weather service has to be configured on your account. If it is not, the section reads: "Weather service not configured. Set it up in admin to surface storm / flood alerts alongside your service-line coverage."
2. Your operator profile needs a city and state on file. If the service is configured but your profile is missing location, the section reads: "Add your city and state to your operator profile to surface local weather forecasts and restoration alerts."

What you see once both are in place:

• Current conditions. Your city and state, then a large temperature reading and the current condition (for example, "72°F" and "Partly Cloudy"), with humidity and wind speed underneath ("Humidity 58% · Wind 12 mph"). Temperature and wind units follow your account's measurement system, imperial (°F, mph) or metric (°C, km/h).
• 7-Day Forecast. One card per day: the day and date (e.g. "Mon, Jul 13"), the high temperature, the low temperature underneath it, and a short condition label. A day only shows a precipitation line when the modeled probability is above 30%, formatted as a percentage plus the precipitation type ("40% rain," "20% snow," or similar). Days at or under that probability show no precipitation line at all, they are not hidden, the number simply is not worth calling out.
• Restoration Alerts. Each active alert is its own card with a type pill (freeze, flood, storm, hurricane, tornado, heat, wind) and a severity label:

- Watch: teal accent, lowest urgency. - Warning: amber accent. - Emergency pending: also amber. This is a long-lead catastrophe event, several days out, where the track is still uncertain enough that Verinode does not treat it as a confirmed emergency yet, but it is close enough to plan for. - Emergency: red accent, an active, confirmed event.

Alongside the pill, a prep window in hours tells you how much runway you have ("72h prep window"). The card body has a title and a plain-language description of the event, then a staffing recommendation in bold (a specific line like "Add 2 extraction crews on standby" rather than a generic warning) and the expected volume change ("Expected volume: +30-40% water damage calls next 5-7 days"). If the alert names specific job categories it will affect, they show as small chips underneath (for example, Water Mitigation, Contents).

When there is nothing active, the section reads plainly: "No active restoration alerts for your region."

Seasonal Utilization

What it is. Every restoration business has a busy season and a slow one. This section looks at your last 12 months of jobs against your current active headcount and finds your peak month and your trough month, so you can see how much your workload actually swings and what carrying a full crew through the slow month costs you.

Empty state. Until Verinode has enough job history to find a real peak and trough, the section reads: "Seasonal utilization appears once you have 12 months of job history on file." Underneath, this needs both a headcount on your roster and enough job volume spread across enough distinct months in the trailing year, a single busy month with everything else empty will not produce a usable peak/trough comparison.

What you see once there is enough history, a four-figure grid:

• Peak: the calendar month with the highest jobs-per-employee figure in the trailing 12 months (for example, "Jul"), with that jobs/employee number underneath (e.g. "3.2 jobs/emp").
• Trough: the calendar month with the lowest jobs-per-employee figure, same format (e.g. "Feb," "1.1 jobs/emp").
• Peak / Trough Ratio: Peak jobs-per-employee divided by trough jobs-per-employee, shown as a multiplier (e.g. "2.9×"). A ratio near 1.0× means your workload is basically flat across the year; the higher it climbs, the more your staffing needs swing between your busiest and slowest months.
• Idle Cost / Crew / Mo: what carrying today's headcount through the trough month costs you in idle labor, in dollars. Verinode takes your labor cost as a share of revenue (from your cost profile, or an estimated ratio when you have not set one), turns that into a monthly labor cost per crew member, then multiplies it by the gap between trough utilization and peak utilization. If your trough month runs at, say, 35% of peak utilization, this figure is roughly 65% of a crew member's monthly labor cost, the part of the month your team is being paid without matching job volume to work against.

How to use it. A high peak/trough ratio paired with a meaningful idle cost is the case for seasonal or contractor staffing instead of a flat W2 roster: it says you are carrying full headcount through a month where there is not enough work to justify it. A ratio close to 1.0× says your staffing model does not need to flex with the season, whatever the Hiring Signal below recommends is about growth or contraction, not seasonality.

Hiring Signal

What it is. The direct hire, hold, or reduce recommendation, built from your revenue per employee against an industry benchmark and your recent job-volume trend. This is the section with the ROI math.

Empty state. Until Verinode has enough job history to project a trend against, this reads: "Hiring signals appear once you have 3+ months of job attribution data to project against."

The math behind every recommendation:

• Revenue per employee is your total revenue (collected amount where you have it, falling back to billed, then estimated, per job) divided by your active headcount (W2 plus contractor, active and seasonal status).
• That figure is compared against Verinode's research benchmark of $200,000 revenue per employee for a mid-size restoration operator. This is the same number quoted in your recommendation's rationale text, not a hidden threshold.
• 3-Mo Trend is job-count growth or decline: jobs opened in the trailing 90 days versus the 90 days before that, expressed as a percentage change.
• Cost of a W2 hire is Verinode's fully-loaded field-technician estimate, a flat annual figure for compensation and burden, plus a separate recruiting-and-ramp-up estimate. Added together, this is what a new hire costs you before they generate a dollar of revenue.

The three outcomes:

• Hire. Triggers when your revenue per employee is meaningfully above the benchmark and your 3-month job trend is growing. The rationale spells out both numbers, for example "Revenue per employee ($312,000) is 56% above benchmark with 12% job growth. Your team is stretched." Est. ROI is the benchmark revenue-per-employee figure minus the fully-loaded W2 cost estimate (not including the separate recruiting cost), shown per year, this is the revenue capacity a new hire is expected to unlock against what they cost to carry.
• Reduce. Triggers when revenue per employee is meaningfully below the benchmark, the 3-month job trend is declining, and you are carrying at least one contractor. The rationale names the shortfall and the decline together and counts your current contractors on roster. Instead of an ROI figure, this shows an estimated annual savings from stepping down one contractor position.
• Hold. The default when neither the hire nor the reduce conditions are met. The rationale reads "Revenue per employee ($X) is within range of the $200,000 benchmark. Job volume stable" (or "softening" if the trend is negative). No ROI or savings figure applies, staffing is aligned with demand as it stands.

What you see, a colored card (green-tinted for hire, red-tinted for reduce, neutral for hold) with the action as a pill, the estimated ROI in dollars per year beside it when one applies, a headline (e.g. "Hire 1 W2 technician"), and the rationale sentence. Below that, a three-figure row:

• Headcount: your current active headcount.
• Rev / Emp: your revenue per employee, formatted in dollars. Shows a dash when there is not enough revenue or headcount data to compute it.
• 3-Mo Trend: the same trailing 90-day job growth or decline figure used in the rationale, as a percentage with a plus sign on growth.

Best-practice example

Say Weather And Alerts shows an Emergency pending freeze warning with a 4-day prep window and a staffing recommendation to add a pipe-burst response crew. Before adding anyone, check Seasonal Utilization: if you are heading into what has historically been your trough month, taking on a temporary crew for the event, rather than a permanent hire, avoids paying idle labor once the freeze passes. Then check the Hiring Signal: if it already reads Hire because revenue per employee has been running well above benchmark with a growing job trend, the freeze event is one more argument for making that hire permanent rather than temporary. Read the three sections together, they are answering related but different questions: what is coming this week, what does the calendar say about your staffing this year, and what does your revenue math say about headcount right now.

Related reading

• Understanding your margin
• Benchmarks overview
• Reading a benchmark
• The decision workspace

Data sources