Catastrophe Claims Management: Lessons from Hurricane Ian

When Hurricane Ian made landfall in Florida as a Category 4 storm, it did not only devastate communities. It exposed the weak points in the insurance industry's catastrophe claims infrastructure: overwhelmed adjusters, insolvent carriers, and a fragile state insurance market.

Ian is now a case study rather than a current event, which is why it is worth reading. The storm did not create the problems that surfaced afterwards. It made them impossible to ignore, and the operational lessons have outlasted the news cycle.

The costliest hurricane in Florida's history

The financial scale was extraordinary. CoreLogic put total insured and uninsured losses between $41 billion and $70 billion, with insured wind losses in Florida alone estimated between $22 billion and $32 billion, flood losses between $8 billion and $16 billion, and uninsured losses between $10 billion and $16 billion.

RMS estimated roughly $67 billion in insured losses across Florida and the Carolinas, making Ian the costliest storm to strike Florida and the second-costliest in US history, behind Hurricane Katrina's roughly $89 billion in insured losses in 2021 dollars, according to the Insurance Information Institute.

For claims organizations, numbers on that scale translate into volume: hundreds of thousands of claims filed at once, across a region with damaged infrastructure, displaced residents, and a depleted local contractor market. That is the scenario that stress-tests a claims management system to its limits.

A Florida insurance market already under pressure

Ian did not arrive in a vacuum. It hit at close to the worst possible moment for Florida's property insurance market.

Florida had long been a litigation hotspot. The Governor's Office reported that 79% of all homeowners insurance lawsuits in the country occur in Florida, as cited by The Actuary. Premiums were already running far above the national average.

Before Ian made landfall, six Florida insurers had already been declared insolvent in 2022, and the Florida Office of Insurance Regulation had placed 27 more companies on its watchlist over financial stability concerns. When Ian hit, the immediate fear was that more carriers would fail under the weight of the claims surge.

That is the context in which carrier claims management software stops being a productivity question. A carrier that processes claims faster, with better accuracy and lower loss adjustment expense, has more room to absorb a catastrophic loss year than one that does not.

Claim disputes, litigation, and the FIGA safety net

When a Florida insurer fails, the Florida Insurance Guaranty Association steps in to pay outstanding claims. Relying on a guaranty association as a backstop during an active catastrophe response is a poor outcome for policyholders and for the industry.

Even among solvent carriers, Ian's aftermath brought a wave of disputes. Records from the Florida Office of Insurance Regulation showed that insurers denied approximately 30% of claims from Hurricane Irma in 2017 and 40% of claims from Hurricane Matthew in 2016. With Ian's losses far larger, litigation was close to inevitable.

Questions about how damage assessments were handled followed. Licensed adjusters testified before Florida lawmakers about carrier handling of post-hurricane damage reports, and Florida's Office of Insurance Regulation subsequently took enforcement action against carriers over post-hurricane claims handling.

That environment puts pressure on independent adjusters and TPAs, who can be asked years later to show what they inspected and what they reported. Firms working on paper or on disconnected systems have no record to produce. Independent adjuster claims software and TPA claims management software create a time-stamped record of every inspection, document, and communication, which is the only thing that answers that question after the fact.

The flood coverage gap

One of the starkest challenges handlers faced was a coverage mismatch no amount of operational efficiency could solve: only 18% of Florida homes carry flood insurance, according to Bloomberg.

For adjusters, that created a difficult human dynamic. Homeowners with devastating flood losses, losses that were not covered under a standard homeowners policy, expected their claims to be paid. When they learned otherwise, the reaction landed on the claims handler.

Some of this is addressable at intake. When a catastrophe event is declared and a flood zone is involved, a structured FNOL process can flag a claim for coverage eligibility review before a field adjuster is dispatched, which at least lets the handler set accurate expectations at first contact. Our guide to flood claims for independent adjusters goes through what makes these files different.

The volume challenge

More than 708,000 Hurricane Ian claims were reported to insurers. Six months after landfall, more than 143,000 of them, over 20%, were still open and pending, according to the Florida Office of Insurance Regulation.

The failure was usually not one of intent. It was one of capacity. Manual claims workflows built on spreadsheets, email chains, and disconnected field reports do not absorb a surge of that size, and the symptoms were consistent across the market:

• Adjuster assignment bottlenecks. Without automated routing, supervisors were manually triaging thousands of incoming notices.
• Documentation gaps. Field adjusters on consumer apps or paper forms could not capture the structured data that fast processing requires.
• Communication breakdowns. Policyholders went weeks without updates, producing a wave of complaints that consumed more staff capacity.
• No real-time visibility. Leadership had no view of claim status, adjuster workload, or settlement velocity while decisions were being made.

Assignment rules are the direct answer to the first of those: on the VCA platform they route claims automatically by loss location, adjuster workload, or client, and a claim can be assigned to the team or handler closest to the loss.

Elderly policyholders: a duty of care

Florida's population skews older, and Ian's impact zone was heavily populated with elderly residents. That carries specific obligations for claims handlers.

Florida's administrative code requires that adjusters exercise "extraordinary care when dealing with elderly clients to assure that they are not disadvantaged in their claims transactions by failing memory or impaired cognitive processes", as noted by Property Casualty 360.

In practice, a high-volume catastrophe response cannot default to fully self-service digital workflows. Policyholder-facing tools have to accommodate varying levels of digital comfort, with a clear route to a person for anyone who needs it.

InsuredConnect is VCA's policyholder self-service add-on for first notice, and it sits alongside the handler rather than in place of one.

What catastrophe claims management looks like at scale

Catastrophe claims management is not a single tool. It is an operational posture, and Ian's aftermath made the components legible:

• Scalable intake. When thousands of claims arrive in a couple of days, intake cannot be manual. Structured first-notice capture, routing by peril and severity, and assignment without a human bottleneck are the baseline.
• Real-time field documentation. Adjusters need tools that capture photo evidence, notes, and damage assessments in a structured format, including where connectivity is poor.
• Transparent claim tracking. Policyholders need visibility, and leadership needs it more: a live view across the whole catastrophe book is how staffing and reserve decisions get made on current information.
• Fast payment. Delayed payments were one of Ian's most damaging legacies for insurer reputation. Getting settled claims paid quickly reduces hardship, complaints, and litigation.
• Oversight at scale. For large carriers, TPAs running several client programs, or multi-state IA firms, role-based access, multi-entity reporting, and cross-client analytics are what keep operational control intact. That is the job of claims oversight.

Organizations that cover those five with connected technology, rather than five disconnected tools, are the ones that come through a surge with their reputation intact.

The path forward for carriers, TPAs, and IA firms

Ian revealed pre-existing vulnerabilities: the Florida market's structural weaknesses, over-reliance on manual process, the gap between flood risk and flood coverage, and claims systems never designed for surge conditions. None of those were caused by the storm, and none of them were fixed by it either.

The wider trend that keeps producing events like this one, and the loss figures behind it, are covered in claims management in the age of climate change. The claim-level view of what surge work does to a file is in complex claims management.

The organizations that came out of Ian intact had invested before the storm rather than during it, which is the only useful lesson a four-year-old catastrophe can offer. VCA implementations complete in weeks, not years, which matters mainly because catastrophe seasons do not wait for a project plan. If your team is evaluating claims technology ahead of the next one, request a demo.

Frequently asked questions

What is catastrophe claims management?

Catastrophe claims management is the end-to-end handling of a high-volume surge of claims triggered by a natural disaster or other large-scale loss event. It covers FNOL intake, adjuster deployment, damage assessment, documentation, settlement, and policyholder communication, at a scale standard workflows are not built for.

What makes hurricane claims different from standard property claims?

Hurricane claims arrive as simultaneous damage to thousands of properties, with infrastructure disruption delaying adjuster access, coverage disputes between wind and flood perils, a heightened litigation environment, and policyholders who have often been displaced from their homes. Accuracy, documentation, and speed all matter more than usual, and they pull against each other.

How does claims software help during a catastrophe event?

It handles the parts of a surge that do not scale by hand: structured intake, routing, mobile field documentation, live tracking, payment, and the audit trail that answers questions after the event. It does not add adjusters, and no system substitutes for surge capacity that was not arranged in advance.