Field Notes from the Compendium: Part 2

Field Notes from the Compendium: Part 2

Where State Claims Regulations Meet Local Hazard Profiles

A tour of 22 more city-specific claims pages, and the local exposures that shape what early correspondence has to say.

Part 2 of Field Notes from the Compendium. The 22 city pages that went live this week shift the regulatory texture toward New England deadline regimes, Gulf Coast hurricane-specific extensions, and a long tail of mid-market jurisdictions whose rules don’t share much DNA with their better-known state neighbors.

Same setup as Part 1: state statutory framework from the Claims Correspondence Compendium, local hazard and exposure profile, examples from the local claim ledger. State-level compendium references are linked inline below.

Over 150 city profiles are coming across the next several weeks. This is the second batch.

The next 22 cities

Honolulu, Hawaii

Honolulu has a regulatory rhythm that flows directly from the supply chain. Hawaii (covered in our Hawaii Compendium reference) requires a reasonable written explanation for any claim delay every 30 calendar days, which lands hard on island claims because roughly 80% of repair goods arrive by ocean freight. Extended rebuild timelines mean recurring status correspondence on a 30-day cadence for as long as the file stays open.

Tacoma, Washington

Tacoma lives under the same Washington framework as Seattle (our Washington Compendium reference walks through it), but a different content rule drives the early correspondence here. Partial denials are governed by WAC § 284-30-770(2)(b), which requires word-for-word insertion of the OIC consumer protection hotline notice. On historic North End homeowner claims, that verbatim language has to appear in the letter exactly as the regulation specifies.

West Jordan, Utah

West Jordan sits on the Wasatch Fault Zone with liquefaction exposure near the Jordan River. Utah (see our Utah Compendium reference) requires a 15-day acknowledgment on catastrophe claims plus 45-day status update letters under Utah Admin. Code R590-190-10. Those dual cadences land together on seismic and ground-failure files, where investigations routinely run long and the file has to document why.

Cheyenne, Wyoming

In Cheyenne, the Wyoming Supreme Court has already done the work on what a reservation of rights has to look like. Under Doctors’ Co. v. Ins. Corp. of Am., 864 P.2d 1018 (Wyo. 1993), an ROR must identify specific coverage issues and cite the exact policy defenses and exclusions the insurer intends to assert (our Wyoming Compendium reference carries the broader framework). Boilerplate reservations do not survive in Cheyenne commercial auto or property files.

Aberdeen, South Dakota

Aberdeen runs through one of the country’s quieter regulatory environments for property claims. South Dakota’s prompt payment statutes (SDCL §§ 58-12-19 to 58-12-21) apply only to health insurance, so P&C claims default to the broader unfair claims practices framework in SDCL § 58-33-67 (our South Dakota Compendium reference walks through the gap). On grain-elevator and freight-corridor commercial files in the upper Plains, content quality and reasonableness, not statutory deadlines, are the compliance lens.

Springfield, Missouri

Springfield runs under a Missouri rule that takes a clause off the table entirely. Mo. Rev. Stat. § 431.030 (see our Missouri Compendium reference) declares null and void any policy language that tries to “directly or indirectly limit the time in which a suit may be instituted.” For commercial logistics files at Springfield Underground and similar facilities, that means correspondence cannot lean on suit-restriction clauses for closure timing; the underlying policy provisions are unenforceable from the start.

Oklahoma City, Oklahoma

Oklahoma City‘s claim calendar is dominated by tornado season, and Oklahoma builds that directly into the statute. The 60-day deadline to accept or deny a claim under 36 O.S. § 1250.7(A) can be extended by the Insurance Commissioner by up to 20 additional days during declared catastrophes (broader framework in our Oklahoma Compendium reference). That extension has to be tracked deliberately so the file documents whether the standard or extended clock is running on any given letter.

Fort Worth, Texas

In Fort Worth, the regulatory backbone is shared with the rest of Texas (our Texas Compendium reference carries it), but the exposure profile shifts the operational picture. Under Tex. Ins. Code § 542.059 the TDI commissioner can extend prompt-pay deadlines by 15 days for weather-related catastrophes, and that matters disproportionately for Fort Worth because spring hail lands on AllianceTexas logistics inventory and aerospace manufacturing facilities: high unit value, complex business-interruption exposure, and tight reopening pressure.

New Orleans and Shreveport, Louisiana

Louisiana’s claims-handling framework is in our Louisiana Compendium reference, and these two cities sit on opposite catastrophe profiles. New Orleans is the hurricane case: La. R.S. 22:1264 extends proof-of-loss deadlines to no less than 180 days from the disaster date for declared events, well beyond standard timelines, and adjusters have to surface the extended clock in catastrophe acknowledgments before the file moves. Shreveport, by contrast, is the inland-severe-weather case: under La. R.S. 22:1892(A)(3), loss adjustment initiation extends to 30 days for catastrophe-declared events. North Louisiana’s straight-line wind and severe-hail exposure means that 30-day initiation window gets used often, on a different rhythm than the Gulf Coast files.

Birmingham and Mobile, Alabama

Alabama’s regulatory framework lives in our Alabama Compendium reference, with these two cities pulling on different parts of it. Birmingham sits in Dixie Alley, where tornado season peaks March through May. Alabama Administrative Code Rule 482-1-135 requires specific mediation protocols for disputed claims arising from tornadoes, hurricanes, and tropical storms: a regulatory step that has to be cleared on top of the standard acknowledgment cycle when severe-storm files come in. Mobile, on the Gulf, layers a different rhythm: Ala. Admin. Code r. 482-1-125-.07 requires written status updates every 45 calendar days explaining why additional investigation time is needed, which routinely pulls into year-long territory when historic district material sourcing extends repairs.

Aurora, Illinois

Aurora runs under an Illinois rule that turns the closing letter into a hard procedural lever. Under 215 ILCS 5/143.1 (our Illinois Compendium reference covers the framework), suit limitation periods are tolled from the date proof of loss is filed until the claim is denied in whole or in part, and tolling never ends if no formal written closing letter is sent. On historic homes in Aurora’s pre-1920 stock and on I-88 logistics-corridor commercial files, the closing letter is the artifact that actually starts the clock back up.

Evansville, Indiana

Evansville sits in the Ohio River basin with a housing stock that includes the Riverside Historic District’s Victorian and Gothic Revival homes. Indiana’s homeowners suit-limitation rule (Ind. Code § 27-1-13-17(b), in our Indiana Compendium reference) requires a minimum two-year suit window from the date of loss, a longer runway than many states, and material when complex roof and siding damage on century-old houses extends investigation and re-inspection cycles.

Grand Rapids, Michigan

Grand Rapids runs the same Michigan regulatory framework as Detroit (covered in our Michigan Compendium reference), but the operative rule for early correspondence is the case law on reservations of rights. Under Meirthew v. Last, 376 Mich. 33 (1965), a valid Michigan ROR must identify specific coverage issues, cite specific policy provisions, and apply the facts to the policy: a stricter threshold than boilerplate language survives. On high-value commercial property and lake-effect snow files in the Grand Rapids metro, that bar is what the early correspondence has to clear.

Concord and Manchester, New Hampshire

New Hampshire’s framework (our New Hampshire Compendium reference) carries a large-commercial-risk exemption that gets operationalized differently in the state’s two largest cities. Under N.H. Rev. Stat. Ann. § 412:3, XI and N.H. Admin. Code Ins 1002.01(a), commercial entities meeting specific financial criteria (e.g., $10M net worth or 25+ employees, with a risk manager in place) are exempted from the standard P&C claims settlement timelines and standards. In Concord, the operational reality is state government, legal services, and institutional warehouse exposure: claims handlers verify exemption eligibility before applying standard timelines. In Manchester, the Amoskeag Millyard concentrates biotech tenants like the Advanced Regenerative Manufacturing Institute and DEKA Research, whose policy structures routinely cross the exemption threshold. Same statute, different verification path.

That verification step is exactly the kind of conditional logic AI claims correspondence is meant to carry: the question of whether a given commercial file qualifies for the exemption shouldn’t get answered by hand on every letter.

Burlington, Vermont

Burlington sits on Vermont’s bilateral non-waiver requirement for premises liability. Under Antley v. Allstate Insurance Co. and Vermont’s broader regulatory framework (covered in our Vermont Compendium reference), an effective reservation of rights in a liability claim requires an executed bilateral non-waiver agreement that cites specific policy provisions and avoids the “mending the hold” doctrine. With 38.4% of the city’s housing stock built before 1940 and hospitality concentration driving slip-and-fall volume, that bilateral document is the actual ROR, not a unilateral letter from the carrier.

Lewiston, Maine

Lewiston sits along the Androscoggin River, where the historic textile mills have been adaptively reused into high-value commercial and residential property. Maine’s fire policy framework (covered in our Maine Compendium reference) requires immediate written notice of loss and a formal proof of loss within 60 days under 24-A M.R.S. § 3002. That deadline lands hard during spring thaw and ice-jam flooding events, when the converted mill stock concentrates exposure into a handful of large files.

Providence, Rhode Island

Providence runs a tight initial-notice cadence: Rhode Island (see our Rhode Island Compendium reference) requires initial claim notice within 21 days of proof of loss, then status updates every 45 days for as long as the file stays open. That structure compresses the early correspondence and sets a recurring rhythm for prolonged investigations across the state’s older housing and historic mill conversions.

Jersey City, New Jersey

Jersey City has a regulatory carve-out tied directly to its commercial real estate concentration. N.J.A.C. 11:2-17.2 (in our New Jersey Compendium reference) exempts large commercial risks, policies above the $10,000-annual-premium threshold, from the standard UCPA timelines, and the Exchange Place financial district’s 18 million square feet of commercial inventory frequently triggers it. Claims handlers there work with two regulatory clocks depending on the policy in front of them.

Rochester, New York

Rochester sits in lake-effect snow country, averaging 100 inches of snowfall a year, and New York’s catastrophe rules compress the early-investigation deadline accordingly. Emergency Amendment 17 to Regulation 64 (11 NYCRR 216) drops the investigation commencement deadline from 15 business days to 6 for catastrophe events (covered in our New York Compendium reference). On winter-weather property files in Monroe County, that 6-day clock changes everything about how the early correspondence has to be staged.

A 6-business-day catastrophe investigation window is exactly the kind of compressed deadline that drafting automation is meant to absorb. The early correspondence shouldn’t be built from scratch when the clock is that short.

What this batch means for letter automation

This batch packs a lot of compressed timing: Rochester’s 6-business-day catastrophe investigation window, Hawaii’s recurring 30-day delay-explanation cadence, Providence’s 21-day initial notice plus 45-day updates, Utah’s stacked 15-day acknowledgment and 45-day status rhythm. It also packs a lot of conditional rules: New Hampshire’s large-commercial-risk exemption, Jersey City’s $10,000-premium threshold for the UCPA carve-out, South Dakota’s no-statutory-deadline default. Each of those conditions requires a verification step before the standard timeline applies.

That conditional structure is where AI claims letter automation earns its keep. The same Compendium data that anchors these city pages drives Voltaire’s drafting layer: every letter starts with the right jurisdictional verification (does the policy qualify for the exemption?), the right deadline already in the draft, and the required disclosures already in place before the adjuster touches it. Adjusters spend their time on judgment, not on the regulatory plumbing.

What’s next

Stand by for more coverage of more cities over the next several weeks.

The Claims Correspondence Compendium is a free public resource. If you want to see how Voltaire operationalizes this regulatory and local context inside an adjuster’s workflow, request a demo.

Yo Sub Kwon, CEO

Yo Sub Kwon is the CEO of Voltaire, an AI platform that streamlines claims correspondence for insurance carriers. A serial entrepreneur with a background in cybersecurity and risk management, Yo Sub has founded and exited multiple venture-backed companies, including Coinsetter and LaunchKey. Most recently, he led the company to win several 2026 Best in Biz Awards for innovation in AI.