From the file
Matching a hail claim's loss date to the right storm swath

A policyholder calls in a hail claim and gives you a loss date. Nine times out of ten that date is fine. The tenth time, it's the date they noticed the leak, not the date the hail fell, or it's a guess because two storms rolled through the same county three weeks apart and nobody kept the receipt. Before that claim goes to an adjuster, it's worth five minutes to check whether the reported date lines up with a storm that touched that address.
Why the FNOL date and the storm date drift apart
Most date mismatches trace back to memory, not fraud. A roof takes a hit, nothing shows for weeks, then a ceiling stain turns up after a heavy rain and that becomes the day the homeowner reports it. Other times a region catches two separate hail events in the same season, sometimes the same month, and the caller picks whichever one they remember hearing about on the news.
The problem for your desk is that each event has its own swath, its own PCS catastrophe designation if it's large enough, and its own reinsurance and reporting implications. A claim coded to the wrong event can throw off your cat-level loss counts for both storms, not just one.
Checking the loss date against the swath boundary
Start with the radar-derived hail swath for the date the policyholder gave you. These are usually built from MESH or similar radar estimates and plotted as a polygon. Drop the address pin and see if it falls inside the boundary for that date.
Three things come up a lot:
The address sits just outside the drawn polygon. Radar-estimated swaths are smoothed and can underrepresent the actual footprint at the edges, so a near-miss isn't automatically a red flag. But it's worth a second look.
The address sits inside two overlapping swaths from different dates. This is common in a multi-event week. The reported loss date tells you which one the policyholder thinks applies, but it doesn't confirm it.
The address sits inside neither. That's the case worth flagging before you send anyone out, because either the date is wrong, the address is wrong, or the damage has another cause entirely.
Using imagery to anchor the loss date
Radar swaths tell you where hail was probable. They don't tell you what happened to a given roof. That's where dated post-event imagery earns its keep. If you've got aerial passes flown close to each storm date, you can compare what a roof looked like right after Event A against right after Event B. Fresh bruising and displaced ridge caps that show up in the imagery dated to the second storm but not the first are a cleaner answer than asking a homeowner to remember a Tuesday from six weeks ago.
This is the gap Hail & Wind Damage is built around: imagery flown across the whole swath after a hail or wind event, flagged per address and delivered as a numbered memo the morning after, so the loss date your desk is working with has something to check against besides a phone call.
When the dates still don't match
If the swath check and the imagery both come back clean but the loss date still doesn't fit, don't just overwrite the FNOL field. Document what you checked, note which event the address falls under based on the swath and imagery, and route it for a date correction through your normal claim-file process. A corrected loss date on a cat claim has downstream effects on reserves and reporting, so it should leave a trail, not just a quiet edit.
Getting the loss date right matters because it puts each claim in the right storm bucket before an adjuster's truck is rolling toward the wrong address. A quick swath check and a look at the dated imagery usually settle it before the file needs a second look.
Run your next swath list through that same check before the first adjuster goes out.