From the file
How many claims can one CAT adjuster close in a day after a hail event?

Every CAT manager asks this during the first 48 hours of deployment: how many stops can we realistically put on one adjuster's board today? The honest answer is that it depends on the swath, the roof type, and how much of the queue is already sorted before the truck leaves the staging lot.
What actually limits a closure rate
Drive time eats more of the day than most scoping models account for. A rural hail swath with quarter-mile driveways and gravel roads burns hours that a dense suburban tract doesn't. An adjuster working a tight subdivision can knock out stop after stop; the same adjuster in open country might spend half the day behind the wheel.
Scope complexity matters just as much. A straightforward hail claim, bruised shingles, some soft-metal denting, a quick ladder-assist inspection, moves fast. Wind claims slow things down: torn flashing, partial tear-offs, tarped sections that need to come off before anyone can see what's underneath. Add a homeowner who wants to walk the roof with the adjuster and explain every dent, and one stop eats the time budgeted for two.
Then there's the paperwork. Writing the estimate in the field, photographing every elevation, documenting pre-existing wear versus storm damage, that's often as time-consuming as the physical inspection. An adjuster who closes the file on-site before leaving the driveway moves faster than one who reopens it back at the hotel that night.
Re-inspections pull from the same daily capacity too. Supplement requests, contractor disputes, a homeowner who found more damage after the first visit, all of that competes with fresh assignments for the same eight-or-so working hours.
Rough ranges field teams work with
Ask ten CAT desk leads and you'll get ten slightly different numbers, but most land somewhere in a similar band for a full hail swath with decent road access: a handful of full-scope roof inspections on a dense, straightforward day, fewer when wind damage or access problems slow things down. The range narrows fast once an adjuster is working a known, pre-screened set of addresses instead of knocking on every door in a ten-mile radius hoping for a claim.
That last part is the lever most desks underuse. An adjuster's daily closure rate isn't fixed. It moves with how much guesswork gets removed before the dispatch sheet is printed. Sending a crew into a swath with no sense of which addresses have shingle loss versus which ones are cosmetic or untouched means a chunk of the day goes to inspections that didn't need to happen, and claims with real damage sit in the queue longer than they should.
Where pre-dispatch triage changes the math
Desks that start the day with a flagged, address-by-address read of which roofs show bruising, missing shingles, or displaced ridge caps across the whole swath aren't guessing at the route. They're sending adjusters to the stops that need a full inspection first and pushing the marginal or undamaged addresses to the back of the queue, or off it entirely. That doesn't change how long one roof takes to scope. It changes how many of the day's stops are worth the drive.
Capacity planning for a CAT event has always been part art, part spreadsheet. The variable most desks can control before the first truck rolls isn't adjuster speed, it's whether that adjuster is driving to a known loss or a cold address.
If you're sizing a deployment and want the swath sorted before dispatch instead of after, that's the problem Hail & Wind Damage is built to solve.