USAA's Patent Turns Storm Density Into a Coded Severity Score

The U.S. Patent and Trademark Office granted USAA's US 12,682,402 on July 14, 2026, a method that draws a boundary around a weather event, profiles how densely insured properties sit inside it, and assigns a severity code from sensor data, on a six-level scale, before a policyholder files a single loss report (USPTO, July 14, 2026).

actuary.info counted this patent among nineteen USAA grants across three July issue dates of the USPTO Official Gazette, one line in a month that inverted the industry's AI patent league table (see the site's July grant roundup). Read at claim level rather than as a tally entry, the patent is not a customer-service upgrade. It is a severity model: a repeatable, patented method for converting storm geometry and policyholder geography into a numeric loss estimate that exists before the first FNOL call. That timing shift touches two things actuaries price and reserve separately, loss adjustment expense and the shape of the catastrophe development triangle, and it does so through a mechanism worth reading claim by claim.

The Claim: Boundary, Density, Sensor Code

Claim 1 of the patent, filed October 1, 2024 as the latest link in a continuation chain reaching back to a March 2013 application, and classified in the insurance data-processing art unit G06Q 40/08, recites three inputs before it recites an output. The system identifies "a bounded geographical area affected by a weather event," generates "a customer density profile in the bounded geographical area," and collects "sensor data from one or more sensors located in the bounded geographical area" (US 12,682,402, USPTO, July 14, 2026). Those three inputs feed a severity code, a discrete estimate of expected property-loss severity, and the code in turn drives a prediction of resource utilization: which adjusters, which contractors, which materials, and where they get sent first.

The density step is the one actuary.info's July grant roundup did not linger on, and it is the one doing the analytical work. A storm boundary alone tells a carrier where wind or water crossed a map. A density profile tells the carrier where its own book is thickest inside that boundary, the blocks where a hundred claims will cluster against the ten that will arrive from a sparsely-insured exurb sitting on the same storm's edge. The specification's worked examples describe a severity scale running from one to six, with the lowest codes routed to independent adjusters handling routine losses, the middle codes to preferred-provider networks, and the top codes reserved for staff adjusters carrying the carrier's most complex, highest-value files. A carrier that knows both where the storm hit hardest and where its own policies concentrate can commit its scarcest resource, senior staff-adjuster time, to the intersection of those two maps before a single call comes in.

Severity code	Estimated loss tier	Adjuster routing (specification examples)
1-2	Minor, routine damage	Independent adjuster
3-4	Moderate, contractor-scope repair	Preferred-provider network
5-6	Severe, total-loss or complex structural	Staff adjuster

A Different Kind of Catastrophe Threshold

The patent's boundary-and-severity method sits next to, but is not the same instrument as, the industry's existing catastrophe threshold. Verisk's Property Claim Services unit designates a U.S. event a catastrophe when it is expected to cause more than $25 million in insured property damage and affect a significant number of insureds and insurers (Verisk PCS methodology, 2026). That threshold is an industry-wide aggregation trigger, decided after enough carriers report enough loss data to estimate the total. USAA's claimed method operates entirely inside one carrier's own book, at the moment the weather event is still unfolding, and it never needs a PCS number to activate. A hailstorm well under the $25 million industry threshold can still trip a dense severity-coding response inside a single carrier's claims system if that carrier's policies happen to cluster in the storm's path. The two thresholds measure different things, one an industry loss estimate for reinsurance and cat-bond triggers, the other a single insurer's internal resource-allocation signal, and a carrier running both can act on its own book well before the market-wide number exists.

Staging Before FNOL: What It Does to the LAE Line

The claim's back half is where the mechanism becomes an expense-line story. After the severity code is assigned, the system opens loss reports for selected customers before those customers call in a loss, then schedules adjusters, contractors and materials against the predicted resource need. That is a direct intervention in loss adjustment expense, both allocated and unallocated. Pre-staged contractor capacity and pre-assigned adjuster skill reduce the re-inspection trips and cross-referral churn that inflate ALAE on catastrophe files; opening the loss report ahead of the policyholder's call compresses the windshield time between an insurer knowing a loss likely occurred and a person being dispatched to confirm it.

The capacity problem this addresses is real and getting worse by the industry's own count. Billion-dollar U.S. weather disasters occurred roughly every 82 days in the 1980s; they now occur about every 10 days, and 2025 alone produced 23 such events, with non-hurricane perils accounting for 99% of 2025's insured catastrophe losses, up nearly 50% from 2024 (Claims Journal, June 2026). The same reporting put a number on the adjuster side of the shortage: roughly 25% of claim adjusters are expected to retire by the end of 2027. "2026 is shaping up to be one of the most complex catastrophe seasons that carriers have ever faced, and the response models most carriers have in place aren't built for this new reality," said David Armstrong, executive vice president at Sedgwick (Claims Journal, June 2026). A severity-coding method that tells a shrinking adjuster pool exactly which streets need a staff adjuster and which need an independent one is a direct response to that constraint, not an incidental feature.

The Reserving Read: Real Improvement or Faster Emergence

The harder actuarial question sits one layer down, in how a reserving actuary should read the triangle once a book adopts this kind of pre-FNOL triage. There are two distinct effects, and they pull the triangle in opposite directions if conflated.

The first is a genuine severity effect. Denser, faster field response to the highest-severity codes can plausibly reduce ultimate loss cost, not just its timing. A roof breached by wind and left uncovered for days accumulates water intrusion and mold exposure that a same-day tarp prevents; a burst pipe found and shut off within hours does less structural damage than one running for a week. If the density-and-severity code genuinely routes the scarcest resource to the properties where speed prevents secondary damage, ultimate severity on those files falls in real dollar terms. That is an improvement a reserving actuary should expect to see and should not discount.

The second effect is pure timing, and it can look identical to the first on a quick read of the diagonal. Opening a loss report before the customer calls moves the claim's reported date earlier without changing anything about the underlying loss. An accident-year triangle built on historical FNOL-to-report lag will show a stronger, faster-developing first diagonal purely because reports now arrive sooner, even if the true ultimate severity per claim is unchanged. An actuary comparing pre-adoption and post-adoption accident years on standard age-to-age factors, without adjusting for the shift in reporting mechanism, risks reading accelerated emergence as loss-cost improvement and understating the ultimate reserve, or, if working from paid-to-incurred ratios sensitive to timing, misreading the same shift as deterioration. Separating the two effects requires holding claim-level severity constant and isolating the reporting-lag change on its own, the kind of methodology adjustment carriers have had to make before whenever a claims-reporting channel changed structurally, as the site has covered in the context of agentic claims AI forcing ULAE reserves into uncharted territory.

A worked comparison shows why the distinction matters for reserve adequacy rather than just methodology hygiene. Consider a hurricane accident quarter where historical experience shows 60% of ultimate claim counts reported within 30 days of landfall, a lag pattern baked into the selected age-to-age factors. If pre-FNOL triage under this kind of severity-coding system pulls that 60% mark to 10 days for the highest-density, highest-severity-code neighborhoods, the observed 30-day reported count on the new accident quarter will run well above the historical benchmark even if the true ultimate claim count and ultimate severity per claim are unchanged. An actuary applying the old development factors to the new, faster-emerging diagonal will project too high an ultimate, not because losses got worse, but because the factor no longer describes the reporting process generating the data. The correction is not a new severity trend selection; it is a revised reporting-pattern curve fit to the post-adoption diagonal, kept separate from any severity trend adjustment layered on top of it.

The unallocated side carries its own wrinkle. The two workhorse ULAE reserving methods, the paid-to-paid method and the claim-count-based Johnson method, both depend on a stable relationship between claims department expense and a claim-count or paid-loss base (Allen and Mango, Casualty Actuarial Society, Fall 1999). A method that opens loss reports for "selected customers" ahead of any customer-initiated report changes what a claim count even measures. If the severity-coding system opens a file for a property inside a dense storm footprint that turns out to have no covered damage, that record either inflates the claim count the Johnson method divides by, or it has to be filtered out through a definitional change to what counts as an open claim, a change an actuary needs to trace through the expense ratio before trusting the resulting ULAE reserve.

Density as USAA's Structural Edge

The density-profiling half of the claim is more powerful for USAA specifically than it would be for a geographically diffuse national carrier, and the reason is structural rather than technological. USAA's membership eligibility runs through military service, which concentrates its book around installations that sit disproportionately on hurricane-exposed coastlines and wildfire-exposed interior corridors. A customer density profile is most informative when the underlying portfolio is genuinely non-uniform, and a book built around bases rather than population centers produces sharper, more stable density gradients storm to storm than a carrier whose policies track the general population. USAA's own 2025 results show the scale that concentration produces in practice: the company responded to 62 catastrophes in 2025, paying nearly $5 billion in catastrophe losses to members at an average of nine days per catastrophe claim, while its net worth grew roughly 20% to $38.6 billion (USAA 2025 Annual Report to Members).

That volume lands against a severity backdrop that makes faster, better-targeted triage worth more per claim than it would have been even three years ago. All-peril homeowners claim severity hit an all-time high in 2025, up 25.9% year-over-year and 93.2% above 2019 levels, even as all-peril frequency fell 23.8% over the same year (LexisNexis Risk Solutions, July 2026). Fewer claims, each worth substantially more, is exactly the environment in which a carrier gains the most from routing its most experienced adjusters to the highest-severity codes and its independent-adjuster network to the rest, rather than working a queue in the order calls happen to arrive.

What the Next Cat Triangle Will Show

Three implications follow for the actuaries who will be pricing and reserving books that adopt this kind of pre-FNOL triage, whether through USAA's issued claim, a licensed vendor product, or a design-around architecture that performs the same three-input pipeline. First, any comparison of loss development before and after adoption needs a reporting-lag adjustment built in from the start, not bolted on after the first diagonal looks unusual; treating the change as a pure severity signal in either direction will misstate the reserve. Second, ULAE claim-count bases need a definitional audit wherever a carrier opens files ahead of customer-reported losses, since a Johnson-method ratio built on an inflated or shifted claim count will misprice the unallocated expense reserve regardless of how well the underlying triage works. Third, the density-profiling half of the mechanism is a genuine underwriting advantage for carriers whose books cluster non-randomly, which means its actuarial value will not transfer evenly across the industry even if the technology itself becomes commoditized. The patent formalizes what catastrophe claims teams have tried to do informally for years, and formalizing it is what makes the reserving question unavoidable rather than optional.