Catastrophe events — hurricanes, major hailstorms, wildfires, severe winter ice storms — impose a specific operational test on carrier intake infrastructure that differs in kind from routine claim volume. The test is not gradual. A named storm making landfall in Florida, or a large-cell hailstorm tracking through a corridor of suburban Texas, can generate first notices of loss at a rate that is eight to twelve times the carrier's baseline daily intake volume within the first 48 hours. Intake systems designed and staffed for baseline operations are not automatically capable of handling that volume without degradation in file quality, acknowledgment timeliness, or routing accuracy.
The carriers that handle CAT intake well are not those with the largest claims operations. They are those whose intake architecture was designed with a CAT scenario in mind before the event occurred.
What a CAT Event Does to FNOL Volume and File Completeness
During a CAT event, FNOL submissions arrive faster than intake staff can process them at normal quality levels. In the surge period — typically the first 24 to 72 hours after a weather event concludes — the carrier is receiving notices from policyholders who have just experienced damage and are calling, submitting portals, and texting agents simultaneously. Many of these FNOL submissions are incomplete. The claimant is calling from a car in a flooded neighborhood; they have a policy number and a phone number, and that is approximately all they can provide. A field adjuster has not yet been dispatched because the carrier's adjuster queue is already overloaded.
The result, without pre-designed CAT intake protocols, is a wave of thin, unstructured FNOL records entering the CMS simultaneously. Each record requires manual follow-up to collect the information needed for a complete claim file. The follow-up calls compete with the incoming FNOL volume for claims staff time. Reserve estimates on the accumulating files are rough because the intake data is too sparse to support structured severity scoring. The CAT codes need to be applied to every file to enable aggregate loss tracking, but if the catastrophe code assignment depends on manual intake review, it will lag behind the actual event timeline.
Catastrophe Codes and Why They Must Be Applied at Intake
Catastrophe coding — assigning ISO PCS (Property Claim Services) CAT codes or carrier-proprietary CAT codes to claim files associated with a specific weather event — is an aggregate loss tracking function. It tells the carrier how many claims are attributable to a specific event, enables reinsurance treaty reporting, and drives the actuarial analysis of event-specific loss experience. A claim file created during a CAT event that does not carry the correct CAT code at creation will not appear in the CAT event's aggregate count unless it is manually coded after the fact.
Manual post-event CAT coding is a common source of aggregate loss undercount in the immediate aftermath of a CAT event. The carrier's Guidewire ClaimCenter or Duck Creek Claims environment shows a claim count associated with the CAT code that is lower than the actual number of affected losses because some files were created without the code and the correction queue is behind. Reinsurance treaty reporting that runs on incomplete CAT-coded data produces inaccurate event totals that must be corrected in subsequent reports.
The solution is straightforward in principle but requires advance configuration: establish a mechanism for activating a CAT intake mode that automatically applies the correct CAT code to every FNOL received from an affected geographic area during the event window. This requires knowing, before the event begins, what the geographic boundaries of the affected area are and what the event's CAT code will be. ISO PCS assigns CAT codes to qualifying events; carriers can use PCS event notification as the trigger for activating CAT intake mode in their systems.
Provisional Severity Scoring During the Surge
Normal FNOL triage logic assumes a minimum level of data completeness — policy in force, loss type identified, property location confirmed, damage description provided. During a CAT event, many FNOL submissions arrive without that completeness. A claimant calling from a storm shelter to report that their home "took a lot of damage" has provided notice, but the intake record does not support a structured severity score under normal triage logic.
CAT intake mode should include a provisional severity scoring approach that operates on reduced data. For a commercial property CAT, the minimum severity indicators available even from a sparse FNOL are: the property location (can be scored against the PCS event intensity map), the property type (commercial vs. residential, occupancy class), and the reported condition of the property ("building intact but significant roof damage" versus "I can't access the building"). These three signals support a rough severity stratification: light damage candidate, moderate damage candidate, heavy damage or potential total loss candidate. That stratification, even provisional, is enough to prioritize adjuster dispatch and preferred vendor notification during the event's first 72 hours.
We are not saying that provisional severity scoring produces reserve-quality estimates. It does not, and carriers should not set initial reserves based on provisional scores alone. What provisional scoring produces is a priority queue — which files need field adjuster dispatch first, which files are candidates for inside adjuster handling, and which files need a preferred mitigation vendor on site immediately to prevent further damage. That queue prevents the alternative: a flat list of several hundred CAT files all in a single undifferentiated intake queue, with adjuster assignment determined by which file the claims supervisor happened to open first.
Preferred Vendor Pre-Dispatch for Commercial Property CAT
Commercial property losses in a CAT event often require immediate mitigation — water extraction, temporary roofing, board-up and security. The sooner a preferred vendor reaches the loss site, the lower the total mitigation cost and the smaller the secondary damage that accumulates while water sits in a building or wind-driven rain continues to enter through a damaged roof. Every day of delay in mitigation dispatch on a commercial property water loss multiplies the mold exposure and the structural damage scope.
Carriers that have pre-negotiated CAT response agreements with preferred vendors — water mitigation contractors, emergency roofing companies, commercial restoration specialists — can activate those agreements during a CAT event. But activation requires knowing which claims need vendor dispatch and which don't. A claim file with a preliminary severity indicator of "commercial, large reported structural damage, multi-tenant building" is a candidate for immediate vendor dispatch. A claim file with a preliminary indicator of "commercial, minor roof damage, functioning tenant operations" is not an immediate priority for on-site mitigation.
The intake record that supports this differentiation is one where the FNOL captured enough structured information about the property and the damage description to produce a preliminary severity score — even a rough one. That score is what makes the vendor dispatch queue manageable rather than arbitrary.
Capacity Planning Before the Event Season
For carriers with significant hurricane-exposed property portfolios — Florida, Gulf Coast, Carolinas — and hail-exposed commercial auto and property portfolios in the Midwest and Texas, CAT intake capacity planning should happen at the start of each storm season, not after a named event is identified. The planning questions are operational and architectural:
- Can the CMS intake layer handle a ten-fold increase in daily FNOL volume without performance degradation? Cloud-hosted CMS platforms like Guidewire Cloud typically scale better than on-premise installations, but the scaling capability needs to be confirmed, not assumed.
- Is the web portal — which will see the majority of the self-service CAT FNOL volume — tested for high-concurrency submission? A portal that handles 50 simultaneous submissions under normal conditions may queue or time out under 500 simultaneous submissions during a CAT event.
- Does the carrier have a documented protocol for activating CAT intake mode, including who authorizes activation, what triggers automatic CAT code assignment, and what provisional severity rules apply during the event window?
- What is the staffing augmentation plan for the intake queue during the first 72 hours? CAT event vendor agreements often include claims staffing provisions; those provisions need to be in place before the event, not negotiated after the storm.
The Limitation of CAT Preparedness Planning
Even well-designed CAT intake systems face limits that planning cannot fully address. A CAT event that produces an unexpectedly wide affected area — a tornado outbreak covering multiple states instead of a single corridor — will present a geographic scope challenge that no finite geographic activation logic fully anticipates. An event that produces a mix of claim types (wind damage, flooding, downed trees, auto losses from debris) will stress intake triage rules designed for a single dominant claim type.
The honest assessment is that CAT preparedness reduces the operational impact of surge events; it does not eliminate it. The carrier that enters a major event with a well-configured CAT intake mode, provisional severity scoring, and pre-authorized vendor agreements will handle the surge better than one that does not — fewer files will be lost in queues, more will be acknowledged within statutory windows, and the reserve picture will develop more quickly. But claims leaders should not expect zero degradation. The honest benchmark is: how much faster can we reach stable operations after the event starts?
Carriers preparing their FNOL systems for CAT season, or reviewing their current CAT intake configuration in Guidewire ClaimCenter or Duck Creek Claims, can discuss surge-capacity triage design with the Fnolwise team.
