THOR Storm Mapper
Turn weather into a focused route.
Connect THOR Storm Mapper data as an independent event layer, then work by date, event type, or roof-damage threshold.
What this means in the field
Storm information is treated as an independent decision layer, not a replacement for the lead system. Representatives can inspect event context while leads, appointments, and territory ownership remain in the company workspace where the team already works.
How the workflow fits together
- Open the independent storm-event layer from the map.
- Filter event context by the operational criteria the team uses.
- Use resulting geography to prioritize routes without mixing storm data into lead ownership.
Frequently asked questions
- Does storm data replace the lead workflow?
- No. It is an independent map layer that can inform route prioritization while lead records and company boundaries remain separate.
- What can a team use storm context for?
- Teams can review date, event type, and roof-damage-threshold context before deciding where to work.