Hail hit within two miles of your roof

A seven-step play for a commercial roofer. It starts from NOAA Storm Events, stacks ArcGIS layers and City permit portals on top, and ends in a message to the property manager that is useful before anyone replies.

Deploy in Glider

Installs this workflow, five project tables and a draft campaign. Source access and any external outputs are checked before research.

Category: Property and construction
Sources: 3
Steps: 7

The workflow

TriggerNOAA Storm EventsHail size, location and date
Evidence
ArcGIS layersLarge buildings near the reports and their owners City permit portalsThe last roof replacement for each building
Artifact
What you hand overA building-specific storm report: the nearest hail reports, the roof's permit history and an inspection offer.
Contact
GliderFinds the property manager, with a verified work email and a phone
Message
Send itFrom your own mailboxes, evidence attached

Why it earns attention

Hail damage to an old roof often shows up inside months later. A storm report near the building plus a roof that permits show is fifteen years old is a reason to inspect now.

The play in seven steps

01
Catch the storm
NOAA Storm Events
What you pull
Hail reports from the last 30 days: hail size, location, time and the reporting source.
Why it matters
Hail over an inch can damage roofing. The size and distance are the facts that make the message credible.
Example
1.75 inch hail · Oct 14, 4:20pm · reported 1.8 miles from the industrial park
02
Find the large roofs nearby
ArcGIS layers
What you pull
Parcels within two miles of the reports with commercial buildings over 20,000 sq ft: footprint, owner and use.
Why it matters
Large flat roofs are where damage goes unnoticed and where a repair is worth your time.
Example
Warehouse · 120,000 sq ft footprint · owner Ridge Industrial LLC
03
Find how old each roof is
City permit portals
What you pull
Roofing permits for each address: date and scope.
Why it matters
An old roof plus hail is the combination that leaks. A new roof is probably under warranty and not worth the message.
Example
Last roof replacement permit: 2009 · full tear-off · 17 years old
04
Build the storm report
Your artifact
What you build
A one-page report for the building: a map of the hail reports, the roof's permit history and what to look for.
Why it works
It is specific to their building, so it reads like a notice, not an ad.
Example
Map of 3 reports within 2 miles · roof age 17 years · free inspection with drone photos
05
Check before you send
A nearby report is not proof of damage. Offer an inspection, never claim the roof is damaged, and check your state's rules on contacting owners after a storm.
06
Find the property manager in Glider
Glider
Search for
Property managerFacilities managerAsset managerBuilding owner
Why them
The property manager schedules inspections. The asset manager cares about the insurance claim window.
What you get
A work email and a direct phone, with the email verified before it goes into a sequence.
07
Send the evidence, then run the first test
To: the property managerEvery line comes from a step above
Hail of 1.75 inches was reported 1.8 miles from your warehouse on October 14.¹ City permits show the roof was last replaced in 2009.³ At 120,000 square feet, damage there can go unnoticed for months.² I put the storm reports and your roof's history in a one-page report.⁴ Can we inspect before any leak shows up inside?
- Facts from the data (the number is the step)
- What you built for them
- One small ask
Why it works
Every fact is about their building and can be checked. The ask is an inspection, which costs them nothing and protects a claim.
First test
One storm, twenty commercial buildings with old roof permits.
Success looks like
Four inspections out of twenty buildings.