--- title: "NCEI storm records and roof inspection history" description: "Compare NCEI storm events with roof inspection history using dated sources, explicit match decisions, and separate findings, access limits, and unknowns." canonical: "https://scalewithsearch.com/articles/ncei-storm-records-roof-inspection-history" --- ## 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) # Roof inspection history: compare field findings with NCEI storm records Compare a historical storm with the roofs your company inspected by keeping two records side by side. One describes public weather evidence. The other describes your firm's field observations, access limits, and unresolved findings. A reviewer records why any proposed connection is acceptable. Start with a bounded question: among the properties we inspected during this review period, which findings have a plausible connection to the selected weather event? Keep “plausible connection” separate from a determination of cause. The worksheet below organizes a review; it does not diagnose a roof. The [roofing company overview](/for/roofing-companies) explains the broader business record. The [public storm signals guide](/intelligence/roofing-companies) describes the proposed evidence board. This article handles the historical comparison, after the first capacity discussion has passed. ## Choose the historical question before the records Write down the territory, time window, hazard, and inspection scope before selecting outcomes. Include who owns the review and what decision the owner expects to make. Avoid starting with a handful of damaged roofs and searching backward for weather that fits. For example, an owner could review whether an earlier capacity decision used a reasonable interpretation of the weather evidence available then. Another review could examine why certain proposed matches were repeatedly rejected. These questions need different notes and should retain their own boundaries. State which records are available. If the firm lacks earlier no-damage visits or access notes, disclose that gap before comparing outcomes. Do not recreate missing findings from invoices, replacement work, or a later employee's recollection. Set a review cutoff. A repeatable historical comparison needs a defined version of the public source and the private inspection export. Keep later corrections as later evidence rather than quietly substituting them into the original decision record. ## Read event and episode as different identifiers The National Centers for Environmental Information (NCEI) bulk guide defines an episode identifier for a storm episode. An episode may contain multiple events. Its event identifier names an individual event and links the details, locations, and fatalities tables. These keys describe NCEI's records. [NCEI bulk format guide, accessed 2026.10.28](https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/Storm-Data-Bulk-csv-Format.pdf). Keep both identifiers in the historical worksheet. Use an event reference when discussing a particular candidate. Use the episode reference to preserve its broader context. Do not count an episode and its component events as separate roof findings. Do not treat an NCEI event identifier as a property identifier. Keep the inspection's internal job reference in its own column. Give the proposed relationship a separate review status, with a reason and reviewer. For this comparison, do not assume that a preliminary SPC row shares an identifier with an NCEI event. Compare time, hazard, and geography explicitly. The companion guide explains [how to read the SPC report day](/articles/spc-hail-report-day-roof-inspection-planning) before carrying preliminary observations into this history. ## Preserve source versions before matching Use the [NCEI bulk archive](https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/) to identify the file you read. Its [README](https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/README) explains the data-year and creation-date parts of the file name. It also says earlier years can receive corrections. Both sources were reopened on 2026.10.28. Record the full file name, source link, retrieval date, and year selected for the review. Keep the guide used to interpret the fields with those references. An unexplained label such as “latest storm data” cannot support a later comparison. Keep the company's inspection export date beside the source version. If an inspector corrects a finding afterward, retain the earlier entry and the accepted correction. Name the person who accepted it. Preserve the reason rather than replacing the old text without explanation. When a later public file becomes available, decide whether to rerun the comparison. Record that as a new review. A changed source may justify changing a proposed match, but the original decision should remain understandable from its original evidence. ## Prepare an editorial matching worksheet The following worksheet is a proposed review structure. It is not a format required by NOAA and does not claim a deployed matching service. Fill each cell from an identified source or leave it unresolved. | Review field | What to retain | | --- | --- | | Public record | Source file, retrieval date, event ID, and episode ID | | Time comparison | Original source time basis, converted review time, and inspection-record time basis | | Hazard comparison | Source event type and the field record's own description | | Geography comparison | State, county or zone type, location evidence, and service territory | | Private record | Internal inspection reference, visit date, and authorized inspection scope | | Proposed match | Accepted for comparison, rejected, or unresolved | | Reason | Evidence supporting the decision and remaining uncertainty | | Reviewer | Responsible person and dated decision | Keep candidate selection separate from acceptance. A record can be close enough to examine and still fail the review. Rejected candidates belong in the worksheet when they explain why a tempting connection was set aside. Avoid a single unexplained confidence score. Plain language such as “time basis unresolved” or “different hazard” tells the next reviewer what remains to check. If the firm uses a score, retain the evidence and reasoning underneath it. ## Check time before accepting proximity The bulk guide describes beginning and ending times, date-time fields usually in local standard time, and a county or zone time-zone field. Preserve that source basis before comparing dates. [NCEI time field definitions, accessed 2026.10.28](https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/Storm-Data-Bulk-csv-Format.pdf). The governing NWS instruction requires local standard time throughout the year, using the event location's time zone. Do not assume these historical records use SPC's UTC clock or the office's daylight-saving clock. Check the record's time-zone field before converting it. [NWS Storm Data Preparation, section 2.3, accessed 2026.10.28](https://www.weather.gov/media/directives/010_pdfs/pd01016005curr.pdf). Ask what each private timestamp means. An appointment date, inspection date, photograph time, and homeowner recollection are different observations. Label them individually. Do not substitute an inspection's completion date for the claimed time of the weather. If the office uses local daylight time, have the reviewer resolve its relationship to the source time basis. Keep both original values in the worksheet. A silent conversion can make an apparently precise match impossible to audit later. When the timing remains unclear, retain an unresolved match. Do not expand the window until a preferred event appears. The owner can decide whether more evidence is worth gathering without treating uncertainty as a confirmed relationship. ## Compare hazard and geography in their own columns The format guide distinguishes county, forecast-zone, and marine geography. It also specifies hail magnitude in inches to the hundredth and wind speed in knots. An NCEI hail magnitude of 1.75 already means 1.75 inches; do not apply the SPC file's division by one hundred again. This is a unit example, not an observed event. Read those definitions before combining magnitudes from different sources. [NCEI geography and magnitude definitions, accessed 2026.10.28](https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/Storm-Data-Bulk-csv-Format.pdf). Keep the event type beside any magnitude. A bare number should not travel into an inspection summary without its hazard and units. If staff cannot resolve a unit or geographic label, leave that comparison open. Record why a location is relevant to the inspected property. County membership can be a reason to examine a candidate. It should not become proof that the weather occurred at every property in that county. Use the field report's wording for the observed condition. If the report does not assign cause, the matching worksheet should not supply one. Route technical causation questions to the appropriate qualified reviewer, with the original source material available. ## Keep four inspection outcomes separate Use categories that preserve what staff could observe. Define them in the company's review instructions before counting. The suggested categories below are editorial recommendations, not official storm-data fields. | Inspection category | Meaning for this review | | --- | --- | | Confirmed findings | A completed, authorized inspection documented specific conditions within its stated scope | | No-damage visit | A completed visit recorded no damage within the inspected scope | | Inaccessible site | A planned or attempted visit could not complete the relevant inspection | | Never inspected | No completed inspection record exists for the property in this review | “Confirmed findings” confirms that the inspection recorded a condition. It does not automatically confirm storm causation, required replacement, insurance coverage, or claim value. Keep those conclusions out unless the responsible source independently establishes them. For partial access, retain the inspected scope and the inaccessible scope. Do not squeeze a partial visit into a whole-property all-clear. If a return visit changes the outcome, connect both visits without counting the property twice in a property-based summary. Keep never-inspected properties outside the completed-inspection denominator. Keep inaccessible sites visible as access gaps. Otherwise a clean-looking percentage can hide the very records that explain its limits. ## Read a fictional summary without expanding its claim Imagine a synthetic review of twelve property records selected for a territory discussion. Four contain recorded findings. Three record no damage within the inspected scope. Two could not be inspected. Three have no completed visit. None of these counts describes a real firm's history. The completed-inspection sample contains seven properties. The other five remain visible in their own categories. Do not describe the full set as twelve inspected roofs or combine access failures with no-damage outcomes. Now imagine the weather comparison accepts three candidate relationships and leaves two unresolved. Keep the match summary separate from the inspection totals. Specify whether each count represents properties, visits, or weather-record relationships before presenting it. That sample cannot establish countywide damage. It contains the firm's selected records, not observations from every county property. The selection process itself needs review: which requests arrived, which were accepted, and which sites staff could access? Use the summary to ask better internal questions. An owner might review missing notes, inconsistent scope labels, or repeated geographic uncertainty. Do not turn the sample into a claim about market demand, expected sales, or the condition of unvisited homes. ## Retain rejected matches and corrections Keep a short reason for every material rejection. Examples include a different hazard, incompatible time basis, location outside the defined review area, or insufficient field evidence. These labels should describe the actual review, not hide an unsupported guess. If another reviewer accepts a previously rejected candidate, preserve both decisions and the new evidence. Name which decision now controls the comparison. Do not erase disagreement merely to create a tidier history. Store the source references and review decisions with the company's authorized record. The [business memory guide](/articles/business-memory-for-ai-agents-guide) describes keeping working facts and corrections available to future readers. Here, that record should let a new reviewer reconstruct the comparison without relying on one employee's memory. ## Use the history for a human review Bring the source version, inspected sample, unresolved matches, and proposed next question to the owner. Have the field supervisor review technical interpretations. Keep dispatch, site access, procurement, and commercial decisions with the responsible staff. For preliminary daily evidence, the [Storm report explorer](/tools/storm-report-explorer) offers a separate reading task. Do not label its results as an NCEI historical comparison or as your firm's private inspection history. Source review occurred on 2026.10.28. The archive, README, bulk guide, and separate [export format guide](https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/Storm-Data-Export-Format.pdf) were reopened. The bulk guide's linked [NWS Storm Data Preparation instruction](https://www.weather.gov/media/directives/010_pdfs/pd01016005curr.pdf) was also reopened. This article uses the bulk guide for bulk-file fields; it does not assume every export has identical columns. Scale With Search can scope a private comparison around the records your company is authorized to use. Bring one territory, one historical question, and the inspection categories your team can support. [Discuss the scope](/work) Continue the website review: [AI-native roofing companies: the first functions to build](/articles/ai-native-roofing-first-functions); [Commercial roofing website: brief a bid request page](/articles/commercial-roofing-website-bid-request-page); [Roof repair and replacement: plan distinct service pages](/articles/roof-repair-replacement-service-pages); [Roofing company AI rules: data, approvals, and spend](/articles/roofing-ai-rules-data-approvals-spend); [Roofing blog topics from questions your office can answer](/articles/roofing-blog-topics-customer-questions); [Roofing estimate form spam: protect the real request path](/articles/roofing-estimate-form-spam-controls); [Roofing financing pages: verify the offer before writing](/articles/roofing-financing-website-copy-review); [Should a roofer hide a home address on Google?](/articles/roofing-google-profile-home-address); [Roofing review requests: build a fair Google process](/articles/roofing-google-review-request-process); [Roofing holiday hours: align the website and Google](/articles/roofing-holiday-hours-website-google); [Roofing project photos: build a useful website gallery](/articles/roofing-project-gallery-photo-seo); [SEO for roofers: review visibility and inquiry paths](/articles/roofing-seo-owner-review-plan); [Roofing storm-damage page: write a credible request path](/articles/roofing-storm-damage-landing-page); [Roofing warranty website wording: separate the promises](/articles/roofing-warranty-website-wording); [Should your roofing website publish prices?](/articles/roofing-website-estimate-pricing-page); [SPC hail reports: read the reporting day before planning roof inspections](/articles/spc-hail-report-day-roof-inspection-planning). [roofing companies](/for/roofing-companies): website and search resources. ## Related: roofing companies - [Roof repair and replacement: plan distinct service pages](/articles/roof-repair-replacement-service-pages) - [Roofing company AI rules: data, approvals, and spend](/articles/roofing-ai-rules-data-approvals-spend) - [Roofing blog topics from questions your office can answer](/articles/roofing-blog-topics-customer-questions) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```