THOR Storm Mapper 3.0 makes the path from a storm to a useful next step more direct: easier account access, shareable Storm Awareness pages, and a more deliberate field workflow on phone, tablet, and desktop.
A storm map is only useful if it helps someone make a decision while the event still matters. Roofing teams do not need another disconnected dashboard or a screenshot that loses its context as soon as it is forwarded. They need to see the storm, understand the evidence, decide which market deserves attention, create the report, and communicate clearly with the people who need to see it.
That is the idea behind THOR Storm Mapper 3.0. THOR remains built around nationwide severe-weather research, including hail, tornado, and wind reports from official NOAA and Storm Prediction Center sources, with NEXRAD radar context where available. What changes in 3.0 is how naturally that information moves through the rest of a contractor's workday.
| What is new in THOR 3.0 | What it changes in practice |
|---|---|
| Google Sign-In and account linking | Returning subscribers can use a familiar sign-in path without giving up the existing username-or-email and password workflow. |
| Public Storm Report sharing | Teams can turn a saved storm report into a branded, time-limited Storm Awareness page that is ready to share. |
| Permission-aware public pages | Public viewers can see useful storm context without receiving private leads, gated tools, or operational evidence. |
| Improved property-report flow | Clearer map guidance makes it easier to create a lead when appropriate or generate a Property Storm History Report directly. |
| More polished mobile field workflow | Important controls, reporting actions, and sharing tools have been refined for phone and tablet use as well as desktop. |
Easier access should not mean a weaker account
A password should not become a reason for a customer to disappear from the workflow. THOR 3.0 adds Google Sign-In alongside the existing username-or-email and password experience. New users can choose the route that is most convenient for them, while existing subscribers keep the access method they already trust.
The release also gives existing subscribers a way to link a Google account from Account Settings. A Gmail-based THOR recovery address can only be linked to the matching Google identity, while users with a business-domain or non-Gmail recovery address can explicitly choose a Google account to link. The result is simple: a subscriber who prefers Google can use Google, a subscriber who prefers a password can keep using a password, and both paths continue to lead back to the same THOR account.
Share the storm without giving away the platform
One of the most important additions in THOR 3.0 is the new Storm Report sharing workflow. A saved storm report can now become a public, branded Storm Awareness page with a stable link, a radar-first visual, a fact-grounded storm summary, a limited set of relevant SPC event details, and geography-aware social copy. It gives a contractor a more useful way to say, “Were you affected by this event?” than a cropped map image with no context.
The sharing system is intentionally selective. Standard public pages are designed to communicate awareness, not expose a contractor's working data. They can include meaningful storm context, but they do not reveal private leads, interactive mapping tools, raw source remarks, or exact operational data. Radar context is available by default. Hail-swath evidence remains gated unless an authorized administrator deliberately creates an Official Full THOR Report version.
Public Storm Awareness is meant to open the conversation. The full THOR workflow is where the research, targeting, and follow-through continue.
Every public share is revocable, expires after 60 days, and is removed after its short expiration window. If the underlying private report is deleted, its connected public pages are removed as well. That keeps sharing purposeful rather than turning every saved report into a permanent, uncontrolled public record.
A report should be easy to create in the moment
THOR has always been built around the moment when someone needs to make a call: Is this property worth a closer look? Is this storm corridor worth a route change? What evidence is available near this address?
THOR 3.0 clarifies the path to the answer. The map now presents direct guidance for two distinct actions. A user can long-press to create a lead when the address belongs in the team's active follow-up workflow, or choose Create Property Report when the immediate goal is research rather than lead creation. That removes unnecessary ambiguity and lets a user generate a report without creating a lead first.
Saved reports are also easier to continue working with. From the private report viewer, users can return to My Reports, download the PDF when appropriate, or open the sharing composer for that exact report. The report stays connected to the next job instead of becoming a static endpoint.
A better view of the evidence behind the event
THOR 3.0 continues the product's emphasis on event certainty rather than a single isolated signal. The map can bring together official NOAA/SPC severe-weather reports, available NWS spotter context, radar-derived hail information, NEXRAD replay, and geographic market context. No one data layer answers every question. The value comes from seeing how the layers relate before deciding where a field inspection or outreach effort makes sense.
The underlying product remains useful before and after the shareable moment. Teams can scan for hail, tornado, and wind events, review historical storm activity, compare radar and event markers, use Market Priority to compare affected areas with residential context, generate Property Storm History Reports, and monitor saved leads for qualifying future events. These workflows keep storm research and field action in one operating view rather than split across a map, a spreadsheet, and a separate canvassing tool.
Built for the field, not just the office
THOR Storm Mapper runs in a supported browser on phone, tablet, and desktop and can be installed as a Progressive Web App. That matters because storm decisions rarely happen only at a desk. They happen in a truck, between appointments, during a morning territory review, or while someone is already standing at an address.
This release continues the mobile-first refinement of the map. Reporting guidance is clearer, sharing controls are responsive, touch targets are easier to use, and the difference between map exploration, lead creation, and report generation is more explicit. The goal is not to add more buttons. It is to make the right next action easier to recognize when time and screen space are limited.
What THOR 3.0 means for roofing teams
THOR 3.0 is not a cosmetic refresh. It is a tighter operating system for the work that happens around a storm. It lowers sign-in friction for real subscribers without forcing them to abandon familiar access and recovery methods. It gives contractors a safe way to publish useful, credible storm awareness content without exposing the data and tools that make their own workflow valuable. And it makes the route from storm evidence to report, lead, or follow-up more understandable on the devices crews actually carry.
The best storm map does not stop at showing where weather occurred. It helps a team decide what to do next—and helps them explain that decision with confidence.
Start with the next storm in front of you
If you are researching a recent hail event, planning a territory, reviewing historical weather near an address, or preparing a storm-awareness post for your market, THOR is built to keep the evidence and the next action close together. Start a THOR Storm Mapper trial and use the same nationwide workspace to research the event, generate the report, and decide where your team goes next.
Frequently asked questions about THOR Storm Mapper 3.0
What is THOR Storm Mapper 3.0?
THOR Storm Mapper 3.0 is the current release of THOR's storm-intelligence platform for roofing teams. It adds Google Sign-In and account linking, public Storm Report sharing, clearer property-report actions, and mobile workflow refinements while retaining THOR's nationwide hail, tornado, wind, radar, reporting, lead-monitoring, and market-analysis tools.
Can contractors share a THOR Storm Report publicly?
Yes. A user can create a time-limited Storm Awareness share from a saved report. The public page is designed around useful, public-safe storm context such as radar, a storm summary, and selected event details. Private leads, interactive tools, raw source remarks, and gated evidence are not included in standard shares.
Does THOR Storm Mapper 3.0 work on a phone?
Yes. THOR is a responsive web application designed for supported phones, tablets, and desktop browsers. It can also be installed to a supported device's home screen as a Progressive Web App.
Does THOR include more than hail data?
Yes. THOR supports hail, tornado, and wind event research, radar context, historical storm review, Property Storm History Reports, Market Priority, lead monitoring, exports, and built-in field follow-through tools. See the full THOR Storm Mapper feature overview.
© 2026 THOR Storm Mapper. All rights reserved.