A carrier-ready file should let an authorised reviewer understand the observations, check the estimate and see unresolved issues without reconstructing the inspection. Use a carrier-approved acceptance checklist rather than a supplier’s general claim of completeness.
The following is a proposed procurement checklist, not a universal legal minimum:
| Component | Proposed acceptance test |
|---|---|
| Identity and assignment | Correct claim, property, inspection date and production assignment |
| Evidence inventory | Source files listed; missing, superseded and late-arriving evidence identified |
| Damage narrative | Observations distinguished from reported statements, assumptions and conclusions |
| Photographs | Relevant images labelled and linked to location and estimated work |
| Measurements and sketch | Units, dimensions, calculation basis and unresolved discrepancies visible |
| Estimate | Editable output; quantities, pricing basis and material assumptions documented |
| Rule and exception record | Applicable carrier-rule version and approved departures recorded |
| QA record | Checks performed, defects found and their disposition visible |
| Change history | Producer, reviewer, revisions, timestamps and superseded versions traceable |
| Handoff | Package successfully associated with the correct claim and review queue |
FEMA’s NFIP guidance provides a programme-specific example of annotated photographs supporting the cause and extent of damage. It is useful evidence of documentation discipline, but NFIP requirements should not be imported wholesale into non-flood homeowners workflows. (agents.floodsmart.gov)
Accept the package only against the agreed production standard. Coverage questions and unsupported material assumptions should be escalated, not silently converted into facts to make the checklist pass.
Sources cited on this page
- agents.floodsmart.govagents.floodsmart.gov