fieldwork

What Separates Teams That Win a Storm Season

The public hail record keeps moving for months after a storm, and the teams that wrote down what they pulled still have an argument.

The record changes under you

Three months after a storm, the argument is not really about roofs. It is about what happened, when, and where, and the other side has a file. The teams that come out of that conversation well are not the ones with the best story. They are the ones who wrote down what they pulled and when, because the public record of a hail event is not finished on the day of the storm. It keeps moving for months.

On day one you have preliminary reports. SPC takes its storm reports from NWS Local Storm Reports, usually sent in near real time, and labels them preliminary and shows them as is. Those reports are grouped into a day that runs from 1200 UTC to 1159 UTC, which is its own trap if you search by the date a homeowner gave you. Then there is a long gap. Both the Storm Data publication and the reports in the Storm Events Database are available 90 to 120 days after the event. And if you need a copy that will carry weight as an official document, certified copies must be requested from NCEI rather than from a local NWS office.

So a single storm has at least three stages in the record: a preliminary feed on the day, a settled version after the 90 to 120 day window, and a certified copy on request. A team that pulled the preliminary feed, saved it with its pull date, and then pulled the settled version owns a documented change history. A team that looked at a website in May and saved nothing has only a memory in September.

One more piece of that record deserves its own sentence, because it gets misread constantly. If an event is missing from both Storm Data and the Storm Events Database, the NWS says plainly that "it was not reported to the National Weather Service". Absence is a statement about reporting, not about weather. The database covers tornadoes since 1950, severe thunderstorms since 1955 and all other weather events since 1996. Inside that coverage, a gap means nobody told them.

Geometry beats place names

The second difference between teams is whether they work in shapes or in names.

The National Weather Service upgraded warning capabilities on October 1, 2007. Before that, warnings were county based and encompassed the entire county regardless of what portion the storm was in. After it, warning polygons only cover the portion of the county actually threatened by the storm. That change is nearly twenty years old and still has not reached how storm work gets scoped.

The clearest illustration is on the NWS Birmingham handout itself. It shows tornado warnings in effect for Hale, Bibb, Perry, Tuscaloosa, Jefferson and Shelby counties, while the cities of Tuscaloosa, Birmingham and Calera were not in the polygons and therefore not under a tornado warning. Three named cities, inside warned counties, outside the warning. If your canvass plan says "Jefferson County," you have described an area that includes a large city the polygon did not touch.

Working in geometry is a one time setup cost. Working in place names costs crew time on every event, forever.

Compliance is a scheduling constraint, not a tax

The third difference is how a company treats the statutes that govern storm work. Read as a tax, they are an annoyance to minimize. Read correctly, they are facts about how fast a season can move.

Colorado's residential roofing article is a useful example because it is specific. It applies to roofing work where the compensation is more than one thousand dollars per contract, and it requires that before engaging in any roofing work a roofing contractor provide a written contract to the property owner, signed by both, stating at least the scope of services and materials, the approximate dates of service, the approximate costs based on damages known at the time, the contractor's contact information including physical address, email and telephone, identification of the contractor's surety and liability insurer if applicable, and the contractor's cancellation and deposit refund policy. That policy has to include a rescission clause letting the owner rescind and get a full refund of any deposit within seventy-two hours after entering the contract. The contract must also state on its face, in bold faced type, that the contractor will hold in trust any payment from the owner until roofing materials have been delivered to the site or a majority of the work has been performed.

Then there is a second and separate seventy-two hour clock. An owner whose roofing contract will be paid from property and casualty insurance proceeds may rescind within seventy-two hours after receiving written notice from the insurer that the claim for payment for roofing work is denied in whole or in part. Written notice of rescission goes to the physical address in the contract, and within ten days the contractor must return any payments or deposits, keeping only an amount for work actually performed in a workmanlike manner.

And the provision with teeth: a Colorado roofing contractor paid from property and casualty insurance proceeds shall not advertise or promise to pay, waive, or rebate all or part of any insurance deductible, and if that is violated, the insurer is not obligated to consider the contractor's estimate of costs, and the owner or the insurer may bring an action against the contractor.

Read that last one as an operations fact, not a legal one. A deductible promise does not only create exposure. It hands the carrier a stated reason to disregard your estimate, which is the document your whole file rests on. Minnesota carries the same prohibition: a residential contractor paid from the proceeds of a property insurance claim may not advertise or promise to pay, directly or indirectly, all or part of any applicable insurance deductible, and compensation for allowing an inspection, filing a claim, or referring work is barred as well. Minnesota goes further on a point that shapes sales training: a contractor may not interpret policy terms, advise on coverage or duties, or adjust a property claim unless licensed as a public adjuster under chapter 72B. There too, if the section is violated the insurer need not consider the contractor's estimate.

That is two states, and the details differ elsewhere. Check your own state's statute and your own customer's policy with a lawyer licensed where you work, and do not assume that what is allowed in one of your markets is allowed in the next. The competitive point is narrower than the legal one: a company that knows these requirements writes them into its contract template and sales script once and never slows down for them. A company that does not know them finds out in the middle of its busiest month.

The quiet months are quiet for structural reasons

The fourth difference is what a team does with the months that are not peak.

The USDA Midwest Climate Hub's 2024 hail factsheet compared monthly hail fraction over 1991 to 2020 against 1961 to 1990. Averaged across all states, monthly hail fraction slightly increased in April and May, decreased in June and July, and increased from August through November, but the changes are minimal, about 2 percent or less, and are not statistically significant for most states. The same factsheet reports that crop insurance hail indemnity payments over 2014 to 2023 are highest in June, July and August for most states, and that comparing back to 1989 showed no clear shift.

The honest conclusion is unglamorous. The shoulder months are quiet because hail is seasonal and the seasonality has barely moved, not because the industry overlooked a window. There is no hidden second season waiting in the data.

What that implies is the opposite of what it sounds like. If the quiet months are structurally quiet, they are the only time you can build anything. Contract templates, geocoding pipelines, provenance habits, crew training, and the pull and save routine above all have to be built when nothing is happening, because none of them can be built in the week after a storm. The difference between two companies in July is usually a decision one of them made in February.

Habits that compound

None of this is a technique. It is a short list of habits, boring on purpose.

Save every pull with its date and source, including the preliminary one you expect to be superseded. Re-pull the same event after the Storm Data window has passed and keep both versions. Define every target area as a geometry and never as a county or city name. Put your state's contract requirements into your template and script once, and have a lawyer in that state read them. Do your building in the months the climatology says are quiet.

None of those will win you a single job. They are the reason that, in month four, you still have a file.