JR&CO
Storm mobilization triage
Online help
← Back to board

Storm mobilization triage

This board ranks JRCO branch offices by storm pressure so PITCH and storm commanders can decide where to mobilize first. It combines hail and wind events from the intelligence pipeline with geo-hail automation results — properties evaluated, properties tagged, and opportunities created — in a single daily view.

On the live board, the ? button (header or bottom-right) opens Guide & Training: spotlight walkthroughs for each area, plus plain-English explainers of the analysis, the data, and what it tells you to do. This page is the longer written reference.

Contents

Page layout

Read top to bottom: filters, headline KPIs, ranked branches, then trend charts.

HeaderWindow · theme · sign-in
Sub-barFreshness · follow · preview email
KPI stripProperties damaged · customers · leads · HailTrace
Branch boardRanked offices · expand for city list
ChartsHail severity mix · properties vs events

The board reloads automatically when you change the triage window. Click any branch row to expand or collapse its city-level breakdown.

Header & controls

Top bar and sub-bar actions.

ControlWhat it does
48h / 7d / 30d / 45d / 90d / 120d / YearSwitches the triage time window. 48h is the primary storm-command framework (rolling last 48 hours on ingest time). Longer buttons use calendar alert dates: week, month, 45 / 90 / 120 days, or the last year.
Dark / LightTheme toggle. Your choice is saved in the browser.
User pillShows your email when signed in via JRCO SSO. On localhost, click to set a dev email for testing.
Follow reportSubscribe to the branded daily email digest at 6:00 AM Central. Includes the storm damage map and square-footage analytics for the most-impacted office. Uses your signed-in email.
Preview emailOpens the digest HTML for the current window in a new tab (no send).
Write action planOn demand, Claude writes a storm summary and lean action plan for the selected office and window: serve hail-hit commercial and residential customers first, protect in-flight revenue, keep headcount small. Uses hail-hit counts, AM book, top customer dollars, last sold/service, and saved territories. Copy the plan or close it; changing 48h/7d/30d clears it.

Triage windows

WindowFilter logicTypical use
48hEvents ingested in the last 48 hours (created_at rolling)Daily storm command — default view
7dAlert date within the last 7 calendar daysWeek-at-a-glance after a multi-day outbreak
30dAlert date within the last 30 calendar daysMonth context and post-storm review
45dAlert date within the last 45 calendar daysSix-week outbreak / residual claims
90dAlert date within the last 90 calendar daysQuarter lookback
120dAlert date within the last 120 calendar daysSeason-to-date
YearAlert date within the last 365 calendar daysFull-year storm inventory
Pipeline filter: Only storm locations with at least one tagged property or one opportunity appear on the board. Zero-pipeline hail hits are suppressed so the board stays action-focused.

KPI metrics

Headline counts for the active window — same numbers as the daily email.

MetricMeaning
Properties damagedUnique hail/wind-hit buildings for the selected branch (same count as Unique properties / Hail-hit).
CustomersThose damaged buildings that already have a CE customer id.
Unique leadsHail-hit buildings that are not already customers.
HailTrace damagedLatest HailTrace Assets Impacted mailbox count. Hover the card for matched / ≥1.25″ / storm-event detail.

Branch mobilization board

Offices ranked by combined storm pressure score — highest at the top.

Branch tabs

1
Rank — #1 is the most-impacted branch for the window (most properties evaluated). Top three ranks are color-highlighted.
2
Office name — nearest JRCO branch to the storm events in that rollup. Switch offices with the numbered tabs; the map below follows the selected branch.

Tiers & scoring

How distance and severity roll up into mobilization priority.

Travel tiers

TierDistance from nearest officeWeight
Tier 0≤ 70 miles5 points
Tier 171 – 200 miles2 points
Tier 2> 200 miles0 points

Event score components

Each storm location gets a mobilization score used to rank cities within a branch and pick the "top event" headline:

ComponentPoints
Tier weight0 – 5 (see above)
Roofing-grade hail+3 if max hail ≥ 1.75"
Corroboration+0.5 per report, capped at 5 reports
Recency+3 (≤3 days) · +2 (≤7 days) · +1 (≤14 days) · 0 older

Branch score is the sum of mobilization scores for all clean events assigned to that office in the window.

Needs review: Events with bad geocodes, misspelled cities, MO/MS mix-ups, or missing branch assignment are excluded from the board until corrected in hail admin.

Branch detail

The board opens on a damage map for the most-impacted branch (heat + numbered clusters), defaulted to Hail-hit — every confirmed hail or wind hit. Worst 10% ranks buildings by hail size in this branch window and keeps only the top tenth of pins (same-size stones break ties by roof SF). The legend shows that cutoff — it is not a fixed 2". Big buildings maps known properties whose Microsoft Mapping footprint is 10,000 SF or more — pin size follows roof size, red is worst-10% hail on those big roofs, and the KPIs on the left of the map total square footage hit. Use Leads for non-customer sites. Switch branches with the numbered tabs. Unique properties is the default table — one count per building across every overlapping storm cell. Switch to Events for the city-by-city storm table.

Unique KPIMeaning
Properties damagedUnique buildings with HailTrace confirmation (same as the headline KPI).
CustomersDamaged buildings that already have a CE customer id.
Unique leadsHail-hit buildings that are not already customers.

Damage analysis sits next to Impacted AMs. It lists hail-hit buildings in the selected branch window and scores each by segment: commercial uses mid-age TPO; residential uses asphalt shingle. A residential roof over 8,000 SF is treated as commercial (TPO) on the table, filters, and CSV. Unlikely leads (band 0–20, not already customers) are hidden from the table, map, KPIs, and CSV. A map above the table plots scored buildings with coordinates: marker size is the median replacement estimate, color is likelihood band. A square HQ pin marks the selected branch office; Fit to map still uses damage locations only. Use All / Commercial / Residential or click a row in the list to open one building. Same shape — hail and wind logistic scores, a 0–100 replacement likelihood (stronger peril + 25% of the weaker), a band (Unlikely → Near-certain), and an independent low/high replacement range. Residential cost converts footprint to roof area (typical 4–6/12 pitch × waste). The ? next to the table title opens both formulas. Search matches building name, address, or city. Use the segment dropdown for Commercial / Residential and the kind dropdown for Customer / Lead. Roof SF uses Microsoft footprint first, then assessor; the SF dropdown (and the Missing SF button) lists buildings with no size so you can spot-check them — Missing Microsoft is the stricter Microsoft-only gap. Each building has a map link. KPIs and CSV follow the same filters. Likelihood answers “will this deal exist”; the range answers “what is it worth if it does.” Expected pipeline on the KPI strip is the rollup only (midpoint × likelihood / 100). Missing SF still gets a likelihood. Constants live in tbl_storm_model_config keyed by market (commercial_tpo, residential_shingle) so they can be retuned from closed storm deals.

Impacted AMs sits next to Unique properties. It is a ranked bar chart of hail-hit customer buildings in the selected branch window — commercial RMS companies and residential CE customers — rolled up by account manager. Commercial uses RMS company ownership. Residential uses RMS property ownership, then the CE Sales Rep if that is empty. Three charts: customers per AM, buildings per AM, and roof square footage per AM. Bars sort high → low. The table adds historical revenue — won / closed-won RMS deal value for those customers, counted once per customer (same dollars as Invite analytics). Roof SF and historical $ are heat-shaded high → low like Invite analytics in-flight revenue. Unassigned means no owner on that account. Roof SF uses Microsoft footprint, then assessor, so some sites still show 0 SF.

The unique view opens on the full branch damage map (heat + clustered pins). Fit to map pans and zooms so every visible hail/lead marker is on screen (the branch HQ pin is shown but does not change the fit). Customers overlays active CE pins: orange commercial, purple residential. Saved lasso territories stay hidden until you click Territories on the map toolbar (the panel also opens after you save a lasso). Each saved area has its own damage map and building / hail / lead rollup. Drag the bar between the map and that bottom panel to grow or shrink the list. Use Expand to fill the screen (Esc or Exit to leave). Use Lasso and Save territory to add another area. On any saved card, Customers + AMs starts from buildings in the lasso, then commercial RMS companies and residential CE customers on those sites. The header counts each segment; use All / Commercial / Residential to filter (All shows 40 of each on screen — click Residential to see the homeowner list). Columns: customer, segment, roof SF, historical $ (won RMS), last sold, in-flight $ (open RMS), last service, then account manager and the rest. Roof SF, dollars, and dates are heat-shaded high → low (newer dates darker) like Invite analytics. Last sold is the latest won RMS close (or status-change date if close is blank). Last service is the latest CE dispatch on that customer number. AM is the account owner from RMS ownership (residential falls back to CE Sales Rep). Customer names open that account in a new RMS tab and attach the extract address to their properties if it is missing. ZIPs lists hail-hit ZIP codes in that lasso (buildings, customers, leads, roof SF, max hail / wind) and downloads as CSV. Calling is a stem only. City lists and the building table sit behind the City & building details twistie.

ColumnMeaning
CityStorm location. Links to Geo Hail Review when an automation run exists (opens in new tab).
ReportsSpotter / source report count for the event.
Hail / windMax hail size or wind speed. Heat shading highlights the strongest values in this branch.
CategoryDamage category or event type (hail band, wind, tornado, etc.).
TierTravel tier for this location.
EvalProperties evaluated on this run (event view — can overlap other rows).
PropertiesTagged properties on this run (event view — can overlap other rows).
OppsOpportunities created (heat-shaded vs. branch max).
MilesDistance to nearest office.

Rows sort by reports descending, then by severity. Click the branch row again (or another branch) to collapse or switch.

Mobile: Miles and score columns are hidden. Date shows as MM/DD. Tier and damage appear stacked in one column.

Charts

Tier 0/1 hail severity mix

Bar chart of hail size bands for Tier 0 and Tier 1 events only: 1–1.25", 1.25–1.75", 1.75–2.5", and 2.5"+.

Properties vs events

Last 30 days. Red bars are storm events that day. The gold line is properties evaluated on those runs (each automation run counted once). Use it to tell a busy storm day from a high-inventory day.

Daily email

Get the same snapshot in your inbox every morning.

1
Sign in on the triage board (SSO or dev email on localhost).
2
Choose your preferred window (48h, 7d, or 30d) — that window is saved with your subscription.
3
Click Follow report. The button turns green (Following).
4
Each day at 6:00 AM Central you receive unique-property KPIs, the storm damage map (hail-hit buildings for the most-impacted office), square-footage analytics, and properties by branch. Event counts, tiers, and hail-event mix are omitted.

The map matches Unique properties / Hail-hit on the dashboard: light Carto tiles, an orange/red heat layer, numbered cluster bubbles, hail-size pins when zoomed in (red ≥ 1.75″, amber 1.25–1.75″, gray 1.00–1.25″ / wind), and a Branch HQ square. Fit uses damage locations only — HQ does not pull the frame. The KPI grid shows properties damaged and how many of those are customers, plus tagged properties and opportunities. Below the map: Total SF hit, Big buildings (10k+), and Worst 10% hail on big buildings.

Click Following again to unfollow, or use the Unsubscribe link in the email footer.

Related tools

ToolUse when…
Storm mobilization triageReturn to the live board.
Territory extractPre-deployment customers + AMs, buildings, mailer addresses, and hail-hit ZIP codes for a saved lasso territory.
Hail events adminFix geocodes, cities, or branch assignment for needs-review events.
Geo hail reviewReview automation run targets after clicking a city link on the board.
Command CenterDaily portfolio ops — complementary to storm mobilization.
Pitch pipelineBroader PITCH intelligence and outreach workflow.