Weather Alert Times: Issued, Onset, Expires and Event End
Read the different clocks in an NWS alert without mistaking an expired message for an all-clear. Includes a fictional timeline and a sharing checklist.
First ask which clock the label describes
An alert message has its own timeline, separate from the weather event it describes. NWS CAP documentation distinguishes when a message is sent, when it becomes effective, and the onset of the subject event. A website refresh time is yet another clock. Read the field label and time zone before comparing two numbers.
Source: NWS CAP documentation ↗
Expiration is not a universal all-clear
In NWS CAP, expires identifies when the information becomes stale. The eventEndingTime parameter instead describes the expected end of the subject event. NWS training says long-duration or open-ended alerts may omit that parameter. An expired saved message therefore does not establish that conditions at your location are safe; seek the current official message and local instructions.
Source: NWS CAP user training: expires versus eventEndingTime ↗
Work through a fictional timeline
Suppose a training-only alert is sent at 09:00 UTC, describes onset at 12:00 UTC, and has a message expiry of 15:00 UTC. A separately labeled expected event end is 18:00 UTC. These invented values describe four different things, not contradictory forecasts. At 15:10, the useful next step is to find an update—not to announce that the hazard ended ten minutes ago. The table keeps each label attached to its value.
Check the replacement rather than patching a screenshot
Our reading checklist is to open the issuing agency, confirm the affected area, read the latest instructions, and compare the message identifier and issue time. Do not manually change the time printed on an old graphic. If a replacement changes the affected area, keep that context with the new message instead of forwarding only the headline. If no current message can be retrieved, say that verification is unavailable.
Keep time-zone conversions explicit
For your own notes, preserve the original timestamp alongside any local conversion. In a fictional example, 18:00 UTC is 14:00 at an explicitly stated UTC−04:00 offset. Do not assume that offset applies to every place or every date. Before sharing, record the source link, full date, original zone, message time and any separately labeled hazard end. This worksheet explains reading habits; it does not replace emergency directions.
Put it into practice
| Field or example | Value or action | Meaning |
|---|---|---|
| Sent | 09:00 UTC | Message sent, not necessarily hazard onset. |
| Onset | 12:00 UTC | Beginning described for the example event. |
| Expires | 15:00 UTC | Find current information; do not infer an all-clear. |
| Event end | 18:00 UTC | Separate expected end in this fictional exercise. |
Official sources
Keep reading
Follow official-source updates via RSS · Browse all explainers
For an active emergency, follow the issuing agency and local authorities. Read our editorial policy.
