Storm Report turns storm evidence into a practical briefing a field team can open, share, and act on. It is the first end-to-end release target: a Missouri hail report that explains the affected geography and where to investigate first, before parcel-by-storm matching is available.
This is a product and release contract. The report generator, dashboard, delivery workflow, and geographic prioritization are not implemented by these documentation changes.
Use a responsive web report as the canonical view. A supervisor finds it on a dashboard, reviews its evidence and proposed work areas, publishes a revision, and sends an email link to authorized canvassers. The recipient opens the same revision on a phone, selects an area, and records acknowledgment or an observation. A generation log or successful email API call alone does not complete this journey.
PDF downloads, scheduled digests, additional channels, automated routing, and parcel dossiers can follow. They should reuse the report record rather than create independent interpretations of the storm.
Lead with the storm summary, observation window, evidence freshness, and operational status. Then show the assessed Missouri counties in investigation priority order, why each county ranks where it does, and its reviewed canvassing areas on a map and in a list. Each area needs a stable identity, an understandable name, boundary provenance, and a starting-area marker where a supervisor has reviewed one. A map centroid is not automatically an accessible meeting point.
Separate counties under warning from counties with radar-derived exposure. Use “as of” times for an active event and retain the selected report revision when fresh observations arrive. A report made yesterday must not read as a claim about which counties are being hit now.
The first mode is weather-exposure priority. It can say that a county or work area has stronger qualifying radar evidence under a declared rule. It cannot establish residential damage counts or roof-replacement likelihood without the required property data and validated outcomes.
Use language such as “Radar indicates hail exposure in these areas; investigate these reviewed areas first.” Use “hail reported” only with attributable report evidence. NOAA's MRMS description ↗ identifies radar-based hazard products; those products are inputs to the investigation, not property inspection findings.
The report release contract owns the ranking inputs, quality gates, and output fields. Storm Impact owns the shared prioritization methods, including later parcel and roof models.
Named neighborhood boundaries require an accepted source and version. Where that source is unavailable, let the supervisor review a drawn territory or explicitly labeled grid area as a canvassing area. Do not invent neighborhood names or call Census units neighborhoods.
The first report path is Missouri → counties → reviewed canvassing areas. It does not require ZIP/ZCTA or parcel steps. Geographic intersections, overlap handling, and boundary evidence are still required. The state jurisdiction registry supplies identities, not polygons or neighborhood coverage.
If no suitable areas exist for a county, retain the county briefing with an explicit “work areas not prepared” state. It is not a complete field assignment. The first end-to-end pilot needs at least one reviewed area and an authorized recipient, not statewide parcel ingestion.
An active-event report supports remote awareness and planning. Field deployment remains on hold during dangerous conditions and requires the supervisor's release under the team's operating policy. A warning's expiry alone does not prove an area is safe. Keep current official warning information separate from the report's frozen evidence window.
Storm History lets users find an earlier report or pilot window. Storm Replay opens its retained observations with the report's evidence and rule versions pinned. This is part of the product experience as well as how the team tests it. A later correction or rerun is visible without changing the original publication.
One report ID and revision connect the dashboard, email link, web view, and future exports. Access can be revoked; previously delivered static copies cannot be recalled. Corrections create a new revision and a visible supersession notice. The shared reports and evidence model owns general evidence custody, branding, and other report families.