What the storm-data grades mean, and why some addresses show "not available"
Every lead in RoofCRM carries a letter grade — A, B, C, D, or "none" — that summarizes the recorded hail history near that address. "Not available" is different from "none": it means the app could not verify anything for that address at all, and it says so instead of guessing. Here is what each grade means and why the honest empty answer exists.
The grades
Open a lead and the Storm History card shows the grade badge, the individual hail events near the property (date, size, distance), and the reasoning behind the grade. The letters mean:
- A — Prime target. Strong, repeated hail history right around the property. Work these first.
- B — Strong. Solid recorded history nearby.
- C — Worth a knock. Some history; not a hot zone, but not empty either.
- D — Light history. A little recorded activity, little more.
- None — No hail on record. The data is available for this address, and it shows no hail events.
The grade is a summary, not a verdict — the underlying event list is on the same card, so you can see the actual dates and sizes the grade came from.
Where the data comes from, and where it is strong
The storm and hail history comes from ECB TX's Texas storm data platform — the same dataset behind PermitLookup and TX Hail Leads — built from sources like NOAA Storm Events, SPC storm reports, and MRMS MESH radar hail-size swaths. Coverage is strongest in Texas. That is who the product is built for, and it is why the dataset is deepest there.
Some features have an explicit county footprint today. The unserviced-lead map layer covers a specific set of Texas counties (currently Tarrant, Dallas, Harris, Bexar, Travis, Williamson, Hays, Comal, Guadalupe, and Smith, plus parts of the surrounding area); panning outside that footprint shows an honest "no coverage for this view yet" message rather than an empty map pretending to be complete. Storm history on any individual lead is a separate lookup and is not limited to that same footprint.
Why "not available" happens — and why it is not a bug
Two situations produce a "not available" result:
- The address can't be recognized. If the address cannot be geocoded to a real location — a typo, a placeholder, or a synthetic test address — there is no point on the map to look up, so there is nothing to return.
- The address sits outside the covered data. Outside the areas the storm dataset covers well, the lookup has no verified answer.
In both cases the app returns "not available" instead of a grade. That is deliberate: a made-up "C" on an address with no verified data would be worse than useless — it would send you to knock a door based on nothing. The rule in the product is the same as the rule in this documentation: if there is no real data, the app says so.
If a real customer address shows "not available," first check the address is spelled and formatted correctly. If it is correct and still returns nothing, the address is likely outside currently covered data — the CRM itself still works fully for that lead.
Questions
Does "none" mean the roof was never hit?
No. It means no hail events are on record near that address in this dataset. Small hail that fell without being recorded, or storms outside the dataset's coverage window, would not appear. The grade reflects the data, not the physical roof.
Will coverage grow beyond Texas?
The dataset is strongest in Texas today because that is the market the product serves. There is no published coverage map beyond that — the app will tell you per-address what it does and does not have.