NWS Watches, Warnings, and Advisories on a Personal Weather Site

A National Weather Service (NWS) watch, warning, or advisory is an official product: an office issued it at a stated time, for named zones, with a valid window. A personal weather station (PWS) page may link that product. It must not rewrite it into a second alert. TNET Weather is not a warning service. For anything in force now, use weather.gov and local emergency authorities. This article is about how a station site should treat those products—and why a Mesa-era Phoenix page was an audience, not a forecast office.

Historical context

The recovered URL /hazards.php sat in the observations cluster of the historical TNET Weather site. Wayback captures show a Greater Phoenix heading, a Western Region warning map credited to NOAA, a product-code legend, and a status line that read as if the page itself were declaring “no current advisories.” That interface is not restored here. Product inventories change. A snapshot of empty checkboxes is a historical screen, not today’s hazard state.

What the URL still names is a real publishing problem. Hobby templates of that era often pulled NWS headline lists or colored maps into the same chrome as backyard temperature. Visitors in Mesa and Phoenix treated the station page as a weather desk. The honest job was narrower: point at the issuing office, keep the clocks, and refuse to compete with the product.

Official products, not station copy

NWS uses a multi-tier headline system so the public can tell possibility from imminent threat and inconvenience from life-and-property danger. Local office wording is consistent on the jobs of the three headline classes (NWS San Angelo explanation; last checked 13 August 2026):

Watch. The risk of a hazardous weather or hydrologic event has increased, but occurrence, location, or timing is still uncertain. The watch is lead time: set plans in motion and keep listening.
Warning. A hazardous event is occurring, imminent, or likely, and conditions pose a threat to life or property. Protective action is the point of the product.
Advisory. A hazardous event is occurring, imminent, or likely, but the expected conditions are less serious than a warning. They can still cause significant inconvenience and, without caution, threaten life or property.

Those are NWS definitions. They are not TNET severity ranks. A heat advisory, a flash-flood warning, and a fire-weather watch are different products with different phenomena, zones, and clocks. Collapsing them into one red “alert” badge on a PWS dashboard is a competing product, even if the operator meant only to be helpful.

Outlooks, statements, and short-term forecasts are still other classes. A Hazardous Weather Outlook is not a warning. A Special Weather Statement is not an advisory. If the historical page listed those names in a legend, treat the legend as UI chrome from a recovered map, not as a current catalog of what NWS Phoenix is issuing today.

Phoenix and Mesa were the audience

The historical station served Greater Phoenix. The official office for that metro is NWS Phoenix (Weather Forecast Office PSR). PSR issues watches, warnings, and advisories for its county warning area when its criteria are met. Neighboring offices (Flagstaff, Tucson, Las Vegas, and others) can be in force a short drive away and still not apply to a Mesa backyard.

A PWS in Mesa does not inherit PSR’s authority by displaying PSR’s map. The station’s thermometer, anemometer, and rain gauge are observed at that site. An NWS warning is an authored official product for zones the office named. Mixing a 40 mph gust on the roof with a high-wind warning for a different zone is how hobby pages contradict the forecast office without meaning to.

Use Phoenix/Mesa in this article the way the old URL used them: to say who was reading. Do not use them to imply that TNET maintains a live Phoenix warning list.

A PWS may link; it must not paraphrase

Linking is the legitimate pattern:

Name the issuing office (for this historical audience, NWS Phoenix, unless the product is from another office).
Name the product class and phenomenon as NWS named them.
Give issuance time and valid window (see below).
Link the official text on weather.gov or the NWS product page.
State that the station page is unofficial.

Paraphrase is the failure mode. Restyling “Flash Flood Warning” as “FLOOD ALERT — TAKE COVER,” summarizing three paragraphs into a severity score, or merging several offices into one county-colored icon creates a second warning channel. Readers will act on the badge. The badge is not NWS.

Do not:

Invent a “TNET warning” or a station-derived watch.
Keep a recovered “no current advisories” line as if it were live.
Paste a historical list of product names as what is in effect now.
Use the station’s rain rate, lightning count, or webcam as verification that a warning is over.

If you archive a product, archive the official URL and the issuance timestamp. Do not republish the body. How to read a tropical local statement as a decision document is a different URL: Reading an NWS Hurricane Statement. This page is the linking rule for the hazard headline itself.

How to label issuance time

NWS products carry more than one clock. Labeling the wrong one is how a PWS implies a warning is “now” when it has expired, or “soon” when it has already begun.

Issuance time is when the office released this version of the product. In the WMO heading it appears as a UTC date-time group. In the body it usually appears again in local time with an explicit time zone. Those two representations should agree after conversion. If they do not, the page is mis-parsed.

Valid time / event window is when the named hazard is expected, or when the watch, warning, or advisory is in force. Valid Time Event Code (VTEC) lines encode action, office, phenomenon, significance, and beginning–ending times in UTC. The body headlines often restate that window in local time (“in effect from 4 PM MST through 6 AM MST Thursday”).

Expiration or cancellation is a later product. A warning that was issued at 2 PM can still be in force at 8 PM, or it can have been cancelled. A PWS that caches the 2 PM headline without the issuance time and without a link to the current office page is displaying a stale decision document.

Write the caption as a citation, not as an alarm:

NWS Phoenix issued a [product name] at 4:55 a.m. PDT Friday (11:55 UTC). The product named its own valid window. Official text: [weather.gov link]. This station page is not the warning.

Keep the zone abbreviation. Do not strip “MST” or “PDT” and print “4:55 a.m.” as if the station’s clock were the authority.

Why Phoenix clocks need extra care

Most of Arizona does not observe daylight saving time and remains on Mountain Standard Time (UTC−7) year-round. The Navajo Nation does observe daylight saving time. NWS Phoenix also serves southeast California, which does observe Pacific Daylight Time. A single PSR product bundle can therefore show MST on one zone line and PDT on another. That is not a station bug. It is geography. A Mesa page that normalizes every PSR timestamp to “Arizona time” will mis-label Imperial County products.

If you convert to UTC for an archive or for comparison with model fields, show UTC and the office’s local string. UTC-only captions on a public Phoenix page hide the clock residents actually use.

Practical checklist for a hazard module

Default destination is weather.gov or weather.gov/psr, not a restyled station graphic.
Every headline includes office, product name, issuance time with zone, and a link.
“None displayed here” is allowed. “NWS has issued nothing” is not, unless you are quoting a current official empty list and dating that check.
Station observations stay in the observation column. Official products stay in the product column.
Life-safety actions come from NWS and local emergency management, not from a PWS color scale.

This URL does not display live watches, warnings, or advisories.

Modern relevance

The same discipline applies anywhere TNET later groups atmospheric evidence: say whether a field is an official warning, a model forecast, a station observation, or a derived index. Mixing those families is how a connection-research page would accidentally look like an alert service. TNET’s public account of those groups is the evidence families behind a connection outlook. That brief is not a warning feed and it does not estimate a link speed from a heat advisory.

Sources

NWS: watches, warnings, and advisories explained (last checked 13 August 2026)
NWS Phoenix (PSR) (last checked 13 August 2026)
weather.gov
TNET: evidence families
TNET observations hub