StormLead • Field Ops

Property-first storm intelligence that actually looks deployment-ready.

A property-first severe weather workflow for roofers, adjusters, and storm operators. This build turns the storm tracker into a cleaner command surface for dispatch decisions, property triage, team workflow, and evidence-backed field action.

Role-aware workflow Observed vs corroborated evidence Top markets and corridors Property impact queue Snapshot export Team sync ready
Best use
Dispatch + field triage
Workflow layer
StormLead CRM Lite
Deployment model
Static front end + optional shared sync
What changed from the original tracker This build keeps the live-source resilience, but shifts the product toward dispatch decisions, property triage, and evidence-backed field action instead of just storm browsing.
Why it feels better now
  • Cleaner hierarchy for operators under time pressure
  • Better visual separation between storm intelligence and sales workflow
  • More polished presentation for local file use and demos
Query and filters

Run the storm view, tighten the signal, then route the work.

Set the target property, choose the operating mode, tighten the weather thresholds, then export or hand off what matters.
Use Roofer when you want canvassing and inspection value first, Adjuster when you want evidence quality first, and Storm ops when you are thinking deployment and routing.
Portfolio snapshot
Raw loaded
0
source rows fetched
Showing
0
filtered evidence points
Top score
0
max damage score
Closest
n/a
nearest relevant point
Max hail
0.00
inches
Max wind
0
mph
Tornadoes
0
displayed
Status
Ready
awaiting query
Field map

Map and field view

Observed reports are mapped as hail, wind, and tornado evidence. Property markers and optional alert polygons add context.
Hail Wind Tornado Property Alert polygon

Selected evidence

Click a storm point, market, corridor, property row, or evidence row to see the detailed decision card.

Source log

Sources have not been queried yet.
Observed data currently comes from IEM, NWS LSR, and NOAA/SPC fallback layers. Modeled hail context is not wired into this prototype yet.

Decision notes

This prototype now emphasizes property triage, top markets, and evidence-backed action instead of just raw storm browsing.
Ranking

Top markets

Markets are ranked by event quality, severity, corroboration, clustering, and practical field value.
RankMarketSignalWhy it mattersPriority
Routing

Storm corridors

Reports within roughly 25 miles and 6 hours are grouped into corridors to make routing and territory triage easier.
NameStatesReportsMax signalPriority
Portfolio queue

Property impact queue

Optional CSV columns now supported: name, address, lat/latitude, lon/lng/longitude, contact_name, contact_role, contact_phone, contact_email, owner_name, property_type, units, notes, website. Click any property to see contact info plus nearby storm aggregation.
No property file loaded yet.
PropertyPipelineAssigned repInspectionNearby storm summaryContact
Pipeline view

StormLead pipeline board

Load properties to see saved pipeline counts and scheduled inspections.

Team Sync

Offline
Keep the board in sync across devices without turning the main screen into admin soup. Reps just sign in and sync. Office setup stays tucked away below.
Crew-friendly Shared job board Password not stored
Office setup (admin only)
These are backend setup fields for whoever is wiring company sync. Roofers should not need to touch this.
This device is in local mode until office setup is added.
Run a query to generate field-priority recommendations.
Evidence rows

Evidence table

This is the row-level evidence list. Click any row to inspect its details and supporting logic.
WhenClassTypeMagnitudePriorityDistanceCityCountyStateSourceRemarks
Current source stack: IEM current + legacy GeoJSON, NOAA NWS LSR recent layer, NOAA/SPC fallback layers, and optional weather.gov alert polygons.