Key takeaways
- Separate weather-event evidence from property-specific damage evidence.
- Preserve original photographs, tool settings, locations, and inspection conditions.
- Drone, thermal, laboratory, and weather data each answer limited questions.
- Use qualified specialists for causation, engineering, roofing, and material opinions.
- Build a chronology that can survive disagreement about date, cause, and condition.
What evidence should a Florida hail-claim file contain?
A Florida hail-claim file should contain an event-date record, official weather sources, inspection authority and safety notes, a location map, original wide/context/detail photographs, collateral observations, material-condition records, tool outputs with limitations, expert findings, estimates, and a versioned submission history. No single weather report, photograph, drone map, or thermal image proves hail caused a particular condition.
Establish the event chronology carefully
Florida Statute 627.70132(3) addresses date of loss for claims resulting from hurricanes, tornadoes, windstorms, severe rain, or other weather-related events, using landfall or NOAA verification as stated in the subsection.
Preserve the official event source, property location, report time zone, observation radius, and any uncertainty. Do not substitute a social post, commercial swath screenshot, or neighbor recollection for the source required by the policy or statute.
Build an inspection map before collecting close-ups
Record who authorized access, who attended, weather and lighting, safety limitations, roof faces or property areas inspected, and inaccessible areas. Create a simple location ID for every observation.
Capture three levels:
- Wide image showing the area
- Context image showing the component and nearby condition
- Detail image showing the observation with scale when appropriate
Keep originals and metadata. An unlabeled close-up cannot establish where or when a condition was observed.
Document collateral observations neutrally
Inspect relevant soft metals, screens, coatings, HVAC components, gutters, vents, fencing, vehicles, vegetation, and other exposed surfaces when authorized and safe. Record both observed and absent conditions.
Use descriptive language such as “circular depression approximately…” rather than “hail hit.” Causation belongs to the complete evidence set and qualified analysis.
Preserve material condition and alternative explanations
Document age when known, product type, repairs, maintenance, foot traffic, installation features, manufacturing conditions, blistering, wear, mechanical marks, and prior claims. Evidence that does not support the working theory remains part of a trustworthy file.
The matching and repairability guide provides a separate workflow for availability and repair feasibility; do not merge that question into hail causation.
Use technology within its limits
| Tool | May help document | Does not independently prove |
|---|---|---|
| Drone imagery | Coverage, location, and visible surface condition | Cause, date, or subsurface damage |
| Thermal imaging | Temperature patterns under stated conditions | Hail causation or moisture without corroboration |
| Moisture meter | Reading at a point with device settings | Source, timing, or covered cause |
| Weather database | Reported event conditions | Damage at the property |
| Material test | Result for the tested sample | Condition of every component |
Save operator, equipment, calibration or settings, method, raw output, and limitations.
Coordinate qualified testing and expert review
When the question requires roofing, engineering, laboratory, meteorological, or building-science expertise, define the assignment and retain a qualified professional. Preserve sample location, chain of custody, destructive-testing authorization, method, results, photographs, and limitations.
Do not turn industry “test squares” or visual rules of thumb into universal scientific standards. Explain who used the method and why.
Package the evidence as a chronology
Organize the submission from event source to property inspection to testing to estimate. Include an evidence index with date, author, location, original filename, and what question each item informs.
Florida Administrative Rule 69B-220.201 requires truthful and unbiased reporting after complete investigation. Preserve unfavorable, duplicate, and inconclusive observations rather than curating only the strongest images.
Run a pre-release integrity check
Confirm original media exists, edits are documented, timestamps and time zones are consistent, location IDs match the diagram, tool outputs state limits, experts are identified, alternative causes are not hidden, and a licensed reviewer approved the carrier-facing narrative.
Florida hail-evidence FAQs
Does NOAA data prove hail damaged the property?
No. It can support event timing and conditions, but property-specific damage requires physical evidence and appropriate expert analysis.
Can thermal imaging prove hail damage?
No. It records temperature patterns under the inspection conditions and needs corroboration.
Should photos be enhanced?
Preserve originals. Document any ordinary processing and never alter an image to create or exaggerate a condition.
What if some roof areas were inaccessible?
Record the limitation and avoid extrapolating as though they were inspected.
Is a commercial hail report enough for the date of loss?
Not by itself. Verify the policy and current law and preserve the applicable official source.
This guide is operational information, not legal, compliance, estimating, coverage, or claim-value advice. Verify procedures against current Florida law, applicable rules, policy terms, firm counsel, and licensed professional judgment.
