Claims / Catastrophe
Stand up a storm deployment in minutes
An event names the adjusters you sent, the ZIP codes they cover, their limits on this event and its managers. New claims in that territory route only to the adjusters on the event.
Bulk FNOL Upload then checks, files and tags hundreds of catastrophe claims to the event in one batch, each routed by its loss ZIP.
The question this answers
What breaks first in a catastrophe?
Assignment discipline. Volume arrives faster than supervisors can triage. Here a claim on an event is offered only to adjusters on that event, in rotation, who hold the right license and line and have room under their cap — and a ZIP nobody covers sends the claim to the queue with the reason, rather than to the wrong person.
How an event is absorbed
Event, upload, route
Create The Event
Name, dates, loss type, managers, event-wide indemnity and expense limits, max claims per adjuster, and ZIP or address basis for assignment.
Give Out The Territory
Paste the ZIPs, give some to named adjusters, and leave the rest in the event’s pool to be shared among everyone eligible.
Upload The Claims
A spreadsheet of up to 50 MB with no row limit. Check This Batch says what would be filed, row by row, and writes nothing; then file, promote or discard.
Rotation And Catch-up
Claims go round the event’s adjusters in turn, and catch-up feeds anyone a full gap behind until they are level.
Watch The ZIP Load
Every ZIP worst first: open claims, the capacity covering it and the shortfall — and, on a button, who could take work there.
After the event
What the operation is left with
The month after a catastrophe is where the operational cost really lands, and it is mostly the cost of reconstructing what happened.
Who Handled What?
An assignment history on every claim that cannot be changed
Was Everyone Licensed?
License was a gate on every automatic assignment, and every unlicensed open was recorded
What Do We Bill?
Fee invoices calculated from the event’s invoicing structure
Who Ran Out Of Work?
Low claim volume alerts when an adjuster falls to the event’s minimum
Is The Event Gone?
Never deleted — archived, and reversible
Where we are honest
The platform does not create capacity
It removes the failures that make surge worse. It cannot substitute for adjusters you do not have.
No Capacity From Software
Rotation allocates the people you sent. A genuine shortfall stays a shortfall, and the ZIP Load card shows it.
Loss ZIP Is Required
Every bulk row needs its loss ZIP, because the event’s ZIP map does the routing. A ZIP not on the event is not assigned automatically.
Catastrophe Pricing Is Commercial
Fee structures for surge events are your agreements. We carry them; we do not suggest them.
Read next
Bring last season’s event
Tell us what broke: assignment, licensing, deadlines or the invoice. We will set up the event and run a batch through it.