From the file
What is a load balancing report in catastrophe claims management?

A load balancing report is the document a CAT team lead builds in the first day or two after a hail or wind event to answer one question: which adjusters are carrying too much, and which ones have room. The report exists to drive a staffing decision, and it only holds up if the workload numbers feeding it are accurate.
What goes into a load balancing report
At minimum, the report ties three things together for every adjuster on the roster: open claim count, geographic spread of those claims, and some signal of severity per claim. Without the severity piece, you're balancing on claim count alone, and that's how one adjuster ends up with eleven roof tears and another ends up with eleven downed fences. Same number, very different week.
Most teams build this by hand in the first 48 hours. Someone pulls the FNOL list, geocodes it against adjuster territories, and eyeballs severity off whatever's come in so far, usually a mix of policyholder photos, prior satellite passes, and gut feel from similar storms. It works, but it's slow and it's only as good as the inputs. If severity data doesn't exist yet when the report gets built, the balancing happens on guesswork and gets corrected days later when adjusters start calling in overwhelmed.
Where adjuster capacity numbers come from
An adjuster capacity report is usually the half of this that's already solid: how many claims a given adjuster can reasonably close in a week, adjusted for claim type and travel time within their territory. That number rarely changes storm to storm. What changes is the demand side, and that's where most load balancing reports fall short, because demand isn't just claim count. A block with three total roof tear-offs needs more adjuster time than a block with ten claims for a few missing shingles each.
This is where catastrophe claims workload distribution gets harder than it sounds on paper. You can't distribute evenly by address count and call it balanced. You have to know, street by street, which claims are going to take an hour and which ones are going to take a morning.
Why severity data usually arrives too late
The honest problem with most load balancing reports is timing. Severity signal from field reports, adjuster callbacks, or even drive-by surveys takes days to accumulate across a full swath. By the time you have enough to balance on, half the adjusters are already three days into their routes and the rebalancing conversation is happening with a crew that's annoyed and behind.
A claim load balancing process that waits for the field to self-report severity is always going to be reactive. The alternative is having severity flagged at the address level before anyone's dispatched, so the first assignment pass is already weighted toward the roofs with bruising, missing shingles, or displaced ridge caps instead of toward whichever claims happened to call in first.
That's the gap Hail & Wind Damage is built to close. It runs post-event imagery across the whole swath and flags per-address damage, bruising, missing shingles, displaced ridge caps, into a numbered memo delivered the morning after the storm. That memo isn't a load balancing report on its own, but it gives whoever's building one a severity column that doesn't depend on which claims happened to call in first. Pair it with your existing claim counts and territory assignments, and the balancing pass starts from something closer to the real picture instead of three days of catch-up.
If your team is still balancing the queue off FNOL order and gut feel, it's worth seeing what a severity-flagged address list looks like before the next swath hits.