What is a CAT code and how it changes claim handling priority

A CAT code is the tag that moves a claim out of the normal queue and into catastrophe handling. The code is assigned at the event level, so every policy touched by a qualifying hail or wind event inherits it the moment the event qualifies, not claim by claim. ISO's Property Claim Services arm is the usual source for the industry-wide number, but plenty of carriers also run an internal CAT designation that fires faster, sometimes within hours of a severe weather alert, before PCS has even finished scoping the swath.

The designation itself is just a code attached to a loss. What it triggers underneath is the part that actually changes your week.

What changes the moment a CAT code is assigned

Once an event carries a CAT code, claims tied to it stop running on the standard FNOL-to-assignment clock. A few things happen almost immediately:

• Claims route to the CAT team or a surge roster instead of the regular desk, which often means independent adjusters and overflow staff who weren't on this book last month.
• Reserve-setting shifts to average or bulk methods for a window, because nobody has line-of-sight on individual roof damage yet.
• SLA clocks reset. A 24-hour contact standard stretches to 72 hours once a state DOI catastrophe emergency is declared, and internal targets move with it.
• Reinsurance and PCS reporting kick in, which is a finance and legal concern more than a claims-handling one, but it's the reason the code exists in the first place.

None of that tells an adjuster which of the four hundred claims that just landed on the CAT desk needs a truck first. The code sorts the event. It doesn't sort the roofs inside it.

Priority inside the code: why the swath still needs triage

This is where most CAT teams lose the first 48 hours. The designation gets the claims into the right bucket, but the bucket itself is still a flat list, usually sorted by nothing more useful than FNOL timestamp or policy number. A total loss with a tarp needed before the next front comes through sits in the same queue as a dented gutter screen, because the code has no view of the roof itself.

Some shops handle this with a windshield survey: a crew drives the hardest-hit streets and calls out what they see. It works, but it's slow against a swath that can run forty miles long, and it puts a person on the road before anyone knows which blocks took the worst of it.

The faster version is to look at the swath before dispatching anyone. Post-event aerial imagery flagged for bruising, missing shingle tabs, and displaced ridge caps turns that flat FNOL list into something closer to a sort order: which addresses show hard hits, which show cosmetic noise, which show nothing worth an inspection yet. A numbered memo built off the imagery, delivered the morning after the storm, does the job the windshield survey is trying to do, just without the truck and the extra day.

CAT code priority versus imagery-based priority

The two aren't competing systems. The CAT code decides which claims get pulled into surge handling, which reserve method applies, and which SLA clock governs the file. Imagery-based triage decides the order those claims get worked once they're in that bucket. A carrier can run both: code assigns the claim to the CAT desk, imagery tells the desk which address to send a truck to on day one versus day twelve.

Skip the imagery step and the CAT designation just moves the bottleneck. Instead of four hundred claims stuck in a normal queue, you've got four hundred claims stuck in a CAT queue, still sorted by nothing more than the order they came in.

If your swath is already mapped and you want the address-level read before the first truck rolls, that's the memo Hail & Wind Damage puts together.