Severe Weather Alert Message Templates
Watch, warning, upgrade, and multi-day tracking templates for the messages weather events actually generate.
When Weather Templates Matter
Severe weather events unfold on a timeline that is partly known in advance and partly compressed into minutes. A tornado warning demands an immediate protective action; a hurricane advisory needs updates over multiple days; a severe storm can move from watch to warning while the on-call activator is still reading the initial NWS bulletin. The templates below are structured so the same activator can send the right message in seconds regardless of where in that timeline the event is - the wording pattern is familiar, only the situational fields change.
All templates use bracketed fields for the values that vary by incident. See the Tornado Response and Hurricane Response guides for the underlying response frameworks these messages are sent inside.
Template Variants
a. Watch / Advisory
Informational. Sent when conditions favor severe weather but no protective action is required yet.
b. Warning / Immediate Action
Time-critical. Sent the moment a warning covers the site. Front-loads the protective action.
c. Escalation / Upgrade
Sent when the situation changes after an earlier message. Explicitly replaces the prior instruction.
d. Extended / Multi-Day Tracking
For hurricane-style events with days of lead time. Establishes cadence and decision timing.
Customization Checklist
- Fill site or area name in every template - never send with the bracket still visible
- Specify the actual hazard (tornado, severe thunderstorm, hurricane, etc.) rather than generic "weather"
- Map shelter locations to specific buildings and floors before the event, not during it
- Add outdoor-crew or field-team instructions where relevant to the site
- Identify who has activation authority for each variant and document backups for 24×7 coverage
- Define the threshold that triggers each variant (which NWS product, which polygon match, which internal condition) so activators don't have to interpret under time pressure
- Establish an update cadence for the multi-day tracking variant and never let it go silent longer than the promised interval
- Have all templates reviewed by safety, legal, and communications leadership before storing them in the system
Related Guides
- Message Templates Library
- Tornado Response and Employee Communication
- Hurricane Response and Employee Communication
- How to Write Emergency Notification Templates
- Message Clarity and Plain Language
Frequently Asked Questions
Should a watch message request acknowledgement?
Usually no. A watch is informational and asking for an ack on every advisory dilutes the signal of your acknowledgement mechanism. Reserve ack requests for the warning and the accountability check afterward.
How is a weather template different for TTS voice delivery than for SMS?
Voice delivery reads punctuation and abbreviations. Spell out site names or write a separate voice variant that avoids ALL CAPS emphasis, uses full words instead of abbreviations, and uses short sentences that read cleanly aloud.
Who should have authority to send a weather warning template?
A named on-call activator with 24×7 coverage, plus documented backups. Weather warnings are time-critical and should not wait on an approval chain - the activation authority is granted in advance for defined trigger conditions.
Do we need a separate template for each hazard type?
You need consistent structure across templates but hazard-specific instructions. Use one template family (watch, warning, upgrade, all-clear) with a HAZARD field, so the wording pattern is familiar but the protective action reflects the actual threat.
When should the upgrade/escalation template be used instead of a new warning?
When the situation changes materially after a message already went out - a watch upgraded to warning, or a warning intensified. The upgrade template explicitly references and replaces the earlier message so recipients aren't left comparing two conflicting instructions.