--- title: "NWS alert zones, updates, and landscape account review" description: "Read NWS alert coverage, identifiers, times, updates, and cancellations before preparing a landscape account review. Keep site conditions unconfirmed." canonical: "https://scalewithsearch.com/articles/nws-alert-zones-updates-landscape-account-review" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # NWS alerts for landscape accounts: handle zones, updates, and expiration A weather alert can prompt a landscape operations manager to review accounts in its coverage area. Before using it, check the geography, message identifier, and times. An old screenshot or a matching county name leaves important questions unanswered. Use an evidence card to record what the source says and which account match remains unresolved. Keep work authorization, crew dispatch, tree hazard assessment, and emergency instructions in their responsible operational channels. This article explains account review documentation, not field safety decisions. The [tree services and landscaping overview](/for/tree-services-and-landscaping) describes those wider responsibilities. The [public-signal guide](/intelligence/tree-services-and-landscaping) introduces an account exposure board. This guide explains how to read the alert behind one proposed board entry. ## Separate alert coverage from a property finding The National Weather Service provides watches, warnings, advisories, and related products through its alerts service. The service uses Common Alerting Protocol messages and provides API access for decision-support applications. [NWS alerts documentation](https://www.weather.gov/documentation/services-web-alerts). A geographic match answers whether the available alert coverage relates to an account location. It does not establish that a branch fell, that access is blocked, or that a customer's planting was damaged. Give each account two separate states: coverage review and site condition. Coverage might be matched, not matched, or unresolved. Site condition might be unconfirmed or supported by a dated observation. Require a source for any confirmed condition. Keep customer reports separate from public weather information. If a customer reports a fallen limb, preserve that report and its time. Do not rewrite it as an NWS observation or assume the alert establishes what happened on the property. Likewise, a reviewed alert match does not add work to a service agreement. A manager may need to inspect the agreement and access record before deciding what response belongs to the company. The evidence card leaves that decision visible. ## Understand the account point and alert geometry Start with the account location approved for this review. Record what the point represents, such as the maintained property rather than a billing office. An uncertain location should remain an uncertain match. NWS exposes a point query for alerts using latitude and longitude. Its API also provides point metadata with separate forecast-zone, county, and fire-weather-zone references. These are distinct fields in the official schema. [NWS API specification](https://api.weather.gov/openapi.json). Do not treat an account point as the alert's geographic shape. The point represents the location being checked. The alert's geometry or affected zones describe its coverage. Keep the method used for the match on the review card. For a large account, one approved point may not represent every maintained area. Ask the record owner which site area the point describes. Avoid silently extending a match at one entrance to every parcel under the same customer name. If a boundary question remains unresolved, write down the question. A reviewer should be able to see whether the uncertainty comes from the account location, the alert coverage, or the matching method. Do not compress those causes into “probably affected.” ## Read affected zones when a polygon is absent NWS permits null geometry in its API schema. Its CAP guidance describes polygons and zone-based geographic codes. [NWS geometry schema](https://api.weather.gov/openapi.json), [NWS CAP geographic definitions](https://vlab.noaa.gov/web/nws-common-alerting-protocol/cap-documentation#area). The API schema defines `affectedZones` as links to affected zones. It also defines UGC codes for public zones or counties and a textual `areaDesc`. [NWS alert field definitions](https://api.weather.gov/openapi.json). When geometry is absent, follow the source's zone references rather than inventing a boundary. Keep the zone identifier and type. A place name in a headline is useful context, but the worksheet should preserve the machine-readable reference used for the match. NWS CAP guidance uses C for county codes and Z for zone codes. It warns against mixing fire-weather and public-zone numbering. [NWS geographic code guidance](https://vlab.noaa.gov/web/nws-common-alerting-protocol/cap-documentation#geocode). Read the available county and zone references as different geographic records. Do not substitute one merely because the names resemble each other. Ask the reviewer to resolve the relationship using the current official zone information. An unresolved zone lookup is an incomplete review. It does not mean the account lies outside the alert. Retain the alert reference and explain which zone information could not be confirmed. The office can still prepare a review item with that limitation. Put it in an unresolved group rather than coloring it as a positive or negative match. The reader should not need to open a second screen to discover the gap. ## Keep message identity separate from the event label Two messages can describe the same general weather event while containing different information. Preserve the message identifier and source link instead of grouping records only by a headline such as “Wind Advisory.” CAP defines message types including Alert, Update, and Cancel. It uses references to identify related messages. [OASIS CAP 1.2 standard](https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf). In the proposed account record, retain the earlier message and point to its replacement when the relationship is confirmed. Show which message the current review uses. A historical message should remain readable without appearing current. Do not infer an update relationship from similar text. Check the source references. If the relationship cannot be established, identify the two records and leave the comparison unresolved for the reviewer. Keep status visible as well. The API lists Actual, Exercise, System, Test, and Draft as status values, separately from message type. [NWS status and message-type definitions](https://api.weather.gov/openapi.json). A practice card should be labeled synthetic, and exercise material should remain distinct from operational material. Familiar formatting should never supply authority that the source record lacks. ## Read the times as different fields The NWS API distinguishes `sent`, `effective`, `onset`, `expires`, and `ends`. They refer respectively to message origination, information effectiveness, expected event beginning, information expiry, and expected event end. Onset and ends can be null. [NWS alert time fields](https://api.weather.gov/openapi.json). Do not replace all of them with “alert time.” Preserve the original values and offsets. If the office displays a local-time conversion, label the conversion and retain the source timestamp for comparison. CAP also distinguishes when information becomes effective, when the event is expected to begin, and when the information expires. [CAP timing definitions](https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf). A worksheet should keep information expiry separate from any conclusion about conditions at a property. NWS says information is stale at its `expires` time and should no longer be used. [NWS expiration guidance](https://vlab.noaa.gov/web/nws-common-alerting-protocol/cap-documentation#expires). Mark the retained card expired and remove it from current evidence when that time arrives. Check for an update or cancellation; if retrieval fails, show that failure without extending the old message's validity. Retrieval time is another field. It tells a manager when the office last obtained that record. A recent retrieval of an old message does not make the message newly issued. A cached card should say when its current-source check occurred. If an expected end time is absent, leave it absent. Do not copy the expiration time into that field to make the card look complete. Missing values are useful information when a manager decides whether the record needs another check. ## Read one synthetic coverage-review card The following card is invented. Its account reference, message labels, zone label, and times are placeholders. It is not a live alert, a current forecast, or a set of emergency instructions. | Card field | Synthetic example | | --- | --- | | Account reference | L-318, example maintained site | | Source message | Example-message-B, source link slot unfilled | | Status | Synthetic exercise card; no live source status | | Message type | Update | | Previous reference | Example-message-A, relationship awaiting confirmation | | Account geography | Approved property point available | | Alert geometry | No polygon in this example | | Affected zone | Example-zone-Z, official identifier awaiting entry | | Zone match | Unresolved because the zone boundary has not been checked | | Sent | 2026-10-28 12:00 UTC, invented | | Effective | 2026-10-28 12:00 UTC, invented | | Expected onset | 2026-10-28 14:00 UTC, invented | | Information expires | 2026-10-28 18:00 UTC, invented | | Expected event end | Unknown in this example | | Retrieved | 2026-10-28 12:05 UTC, invented | | Site condition | Unconfirmed | | Review owner | Operations manager | | Decision state | Awaiting geography and current-message review | This card supports two clear questions. Which official zone does the source identify? Does the approved account location match that coverage? Neither question can be answered by the placeholder label. The manager can request the missing source reference without making a field decision. A qualified person may later record a site observation in its own record. Keep that observation separate from the public alert even if their dates overlap. Do not add a “dispatch approved” field to this evidence example. Dispatch belongs in the company's authorized scheduling process. Keeping the evidence card focused makes its unresolved facts easier to inspect. ## Handle updates and cancellations visibly For a proposed office review, compare the current message with the version used for the last card. Check coverage, times, headline, and references. Preserve the earlier values so a reviewer can understand why the account appeared previously. An update may require another look at the account match. Do not carry a prior match forward without checking whether the relevant source fields changed. If the office cannot obtain the current record, state that failure and the last successful retrieval. A cancellation should appear as a source lifecycle change. Preserve the cancellation reference and retire the earlier message from the current review view when its relationship is confirmed. Keep the history available for the account discussion. A cancellation does not certify that a property is safe. Expiration does not certify that a tree is sound. Those conclusions require their own observations and authorized judgment, beyond this card's purpose. Similarly, disappearance from a saved list does not explain why a message is absent. The office should distinguish a confirmed lifecycle change from an unsuccessful retrieval. An unavailable source should not silently become a clean account list. ## Review source age before reviewing service capacity The NWS API documentation describes a cache-aware service whose content expires according to its information lifecycle. [NWS API overview](https://www.weather.gov/documentation/services-web-api). The office still needs to expose when its own copy was checked. Put the current-source check near the coverage state. A manager reviewing a card later should see its age without inspecting file properties. Record an unavailable check as unavailable, with the last usable observation identified. Keep capacity discussions in a separate management record. Account coverage alone cannot establish available staff, access permission, equipment suitability, or authorized work. A manager should review those records through the company's established process. Use the [business memory guide](/articles/business-memory-for-ai-agents-guide) to structure the retained observations and corrections. Preserve the reviewed message reference, match explanation, and later decision rather than keeping only the final summary. For slower county context, use the companion [drought percentage reading guide](/articles/county-drought-percentages-landscape-account-review). Weekly county statistics should keep their own dates and measures alongside alert records. Bring Scale With Search a sample service territory, the location records approved for review, and the person who checks coverage. A written scope can define the evidence card and its human handoff without expanding it into dispatch or tree-risk decisions. [Send your brief](/work) ## Source note NWS alerts guidance, API guidance, the current API schema, NWS CAP documentation, and the linked OASIS CAP 1.2 standard were reopened on 2026-10-28. No live alerts or private account locations were fetched. Examples are synthetic. Recheck official documentation before relying on a changed field or message lifecycle. Continue the website review: [AI-native tree and landscape firms: first functions to build](/articles/ai-native-tree-landscape-first-functions); [County drought percentages: read cumulative categories before reviewing landscape accounts](/articles/county-drought-percentages-landscape-account-review); [Landscape design inquiry page: set the agenda](/articles/landscape-design-consultation-website-page); [Landscape maintenance page: explain the recurring scope](/articles/landscape-maintenance-website-service-scope); [Landscaping website updates when the season changes](/articles/landscaping-seasonal-website-update-checklist); [Landscaping website portfolio: show what each job includes](/articles/landscaping-website-project-portfolio); [Landscaping website testimonials: keep the source words](/articles/landscaping-website-testimonial-evidence); [SEO for landscapers: plan services, places, and inquiries](/articles/seo-for-landscapers-service-and-location-plan); [Tree and landscape AI rules: data, approvals, and spend](/articles/tree-landscape-ai-data-approval-spend-rules); [Tree service Google profile: should you hide the address?](/articles/tree-service-google-profile-home-address); [How to ask tree service customers for Google reviews](/articles/tree-service-google-review-requests); [Tree service SEO: map removal, pruning, and stump pages](/articles/tree-service-seo-page-plan); [Tree service storm page: publish the hours you can support](/articles/tree-service-storm-website-availability-page); [Tree service website: make arborist credentials checkable](/articles/tree-service-website-arborist-credentials); [Tree service estimate form: request a site assessment](/articles/tree-service-website-estimate-request-form). [tree services and landscaping companies](/for/tree-services-and-landscaping): website and search resources. ## Related: tree services and landscaping companies - [SEO for landscapers: plan services, places, and inquiries](/articles/seo-for-landscapers-service-and-location-plan) - [Tree and landscape AI rules: data, approvals, and spend](/articles/tree-landscape-ai-data-approval-spend-rules) - [Tree service Google profile: should you hide the address?](/articles/tree-service-google-profile-home-address) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```