Photo Documentation Checklist For Hail And Wind Supplements

A hail or wind supplement photo packet should make every requested review item easy to trace. A reviewer should be able to open the packet, see the property, understand the storm-date context, locate the roof face, find the close-up photo, verify the related measurement or file source, and read the factual estimate note without calling the contractor for missing context.

That does not mean the packet proves coverage or guarantees supplement approval. It means the packet is organized. Weather records give date and area context. Photos show observed conditions. Safety notes explain what could and could not be collected. Estimate notes connect observed facts to the requested review. The policy, insurer review, adjuster review, local licensing rules, and any public-adjuster restrictions still matter.

Use official weather and safety sources carefully. NOAA's Storm Events Database is useful for storm-date, area, event-type, and narrative context. It is not property-specific proof of roof damage. OSHA's roof inspection, tarping, and repair guidance is useful for safety boundaries. It is not a substitute for a job-specific safety plan.

Hail/Wind Photo Packet Checklist

Build the packet in the same order every time. The order keeps the review from turning into a loose pile of photos.

Packet section	What to include	Why it matters
Cover sheet	Property identifier, inspection date, packet date, contact, and claim or project reference if provided by the file	Separates this packet from older estimates and unrelated photos
Weather context	Storm date being reviewed, NOAA or NWS source link, event type, area, and source limitation note	Gives date/area context without overstating proof
Safety/access note	Access method, roof faces not accessed, attic limits, steep/slick/damaged areas, power-line or ladder concerns	Shows that missing photos may be a safety decision
Orientation photos	Front, rear, left, right, roof face overview, and address marker where appropriate	Helps the reviewer place close-ups on the building
Slope-by-slope log	Roof face label, direction, material, access status, overview photo IDs, close-up photo IDs	Prevents photos from floating without location
Hail photo group	Wide, mid-range, and close-up photos of observed conditions, plus collateral context where relevant	Shows condition and location without diagnosing from one mark
Wind photo group	Missing, torn, creased, lifted, displaced, exposed, or related component photos with roof-face context	Supports item review with location and sequence
Collateral photos	Gutters, downspouts, vents, soft metals, screens, fascia, siding, fencing, or other exterior context where relevant	Helps compare storm context across materials
Interior/attic photos	Ceiling stain, active leak, attic moisture, underlayment view, decking view, or temporary mitigation when safe and relevant	Connects exterior observations with interior symptoms
Measurement support	Roof report, sketch, field measurement, facet label, count sheet, or quantity note	Shows where requested quantities came from
Estimate note support	Item ID, reason for review, photo IDs, measurement IDs, and source file IDs	Turns the packet into a traceable supplement file

The cover sheet should not argue. It should identify the packet. The revision summary should not say an item is owed. It should say the item is being submitted for review and point to the evidence. This tone matters because a clean supplement packet is a documentation file, not a demand letter.

Slope-By-Slope Photo Log Template

The photo log is where many supplement packets break down. Photos may be good, but the file does not say where they belong. A slope-by-slope log fixes that.

Use a simple structure:

Roof face	Access status	Overview photo IDs	Detail photo IDs	Related item	Notes
Front slope F1	Roof accessed by trained crew	F1-001 to F1-004	F1-020 to F1-036	Hail observation, ridge accessory review	Wide, mid, close-up, collateral soft-metal context
Left slope L1	Ground and ladder only	L1-001 to L1-006	L1-014 to L1-018	Wind observation near rake	Close roof access not used due to slope and wet surface
Rear slope R2	Not accessed	R2-001 to R2-004	None	Access limitation	Ground photos only; safety note SAFE-03
Garage slope G1	Roof accessed	G1-001 to G1-003	G1-009 to G1-021	Vent and shingle review	Vent close-ups and surrounding material photos

The point is consistency. If the estimate note says "west slope," the photo log should use that same face name. If the roof report labels the same slope S3, the packet should include a crosswalk: S3 = west slope W1. Review slows down when photos, roof reports, and estimates use three naming systems.

Every photo should have a purpose. A packet with 200 images and no index is weaker than a packet with 45 labeled photos that show orientation, condition, close-up, collateral context, and measurement support. The office should be able to delete duplicates, blurry photos, unrelated photos, and photos that add no context before the packet leaves the company.

Photo Naming And Annotation Rules

Use filenames that describe the photo without arguing the claim. Good names identify the packet order, roof face, component, view type, and date.

Examples:

• F1-001_front-slope_overview_2026-05-23.jpg
• F1-021_front-slope_shingle-close_2026-05-23.jpg
• COL-014_rear-downspout_close_2026-05-23.jpg
• INT-006_bedroom-ceiling-stain_context_2026-05-23.jpg
• SAFE-003_north-slope_access-limit_2026-05-23.jpg

Avoid filenames that argue causation or payment:

• hail-hit-proof.jpg
• carrier-missed-this.jpg
• must-pay-wind.jpg
• totaled-roof.jpg

Annotations are useful when they point to location, scale, roof face, or component. They are risky when they turn a photo into an argument. If the packet uses arrows, circles, labels, or callouts, keep both files: the original and the annotated version. Label the annotated version clearly, such as F1-021A_front-slope_shingle-close_annotation_2026-05-23.jpg.

The annotation should say what the photo shows, not what the policy owes. Use labels like "front slope," "missing shingle area," "close-up," "soft metal collateral," or "access limitation." Avoid labels like "covered damage," "hail confirmed," or "insurer owes replacement."

Weather Context: Useful, But Limited

NOAA Storm Events records can help a contractor document that hail, thunderstorm wind, high wind, tornado, or other severe weather was recorded in the broader area and date range being reviewed. The National Weather Service glossary helps explain severe weather terminology, including hail and wind context. Those sources belong in the packet, but they need limits.

Use weather context like this:

Weather file field	Good packet language	Avoid
NOAA event type	"NOAA Storm Events lists a hail event in the county on the date being reviewed."	"NOAA proves this roof was hit."
NWS criteria	"NWS terminology helps frame hail and wind severity context."	"Any storm meeting this threshold damaged the roof."
Storm date	"The inspection packet is organized around this reported storm date."	"All visible conditions came from this storm."
Narrative	"The narrative provides area context."	"The narrative settles causation."

A roof-specific packet still needs field observations, location-specific photos, material condition notes, and reviewer judgment. Weather context is a supporting file. It is not the whole case.

Safety And Access Notes

A missing photo is not always a documentation mistake. Sometimes it is the correct safety decision.

OSHA identifies roof inspection, tarping, and repair hazards such as ladders, raised work surfaces, steep or slippery surfaces, damaged roofs, tools, power lines, and fall hazards. OSHA's roof tarping safety fact sheet adds post-storm tarping and fall-protection context. Contractors should plan photo collection with trained workers, safe access, proper equipment, and a job-specific safety plan.

Add a safety/access note to every packet:

• Which roof faces were inspected from the roof, ladder, drone, ground, attic, or not accessed.
• Which areas were unsafe, wet, steep, brittle, damaged, obstructed, or near power lines.
• Whether attic access was available and safe.
• Whether temporary mitigation was already installed.
• Whether photos were taken before or after tarp, board-up, dry-in, or emergency work.
• Which photos were not taken because access was unsafe.

This note protects the integrity of the packet. It tells the reviewer why a roof face has ground photos but no close-up, why the attic was not entered, or why tarp photos exist before permanent repair photos.

Hail Photo Set

Hail photos should move from context to detail. A close-up without orientation is weak because the reviewer cannot place it. A roof overview without close-ups is weak because the condition is hard to evaluate.

Use three photo distances:

• Wide: roof face, elevation, or area overview.
• Mid-range: smaller roof section showing the condition pattern and surrounding material.
• Close-up: specific observed condition with scale when appropriate and safe.

For each hail-related observation, record:

• Roof face or slope label.
• Approximate location on the face.
• Material and component type.
• Photo IDs for wide, mid-range, and close-up images.
• Whether the photo is original or annotated.
• Whether collateral context exists.
• Whether the condition is being submitted as observed, not as final causation.

GAF's roof damage guidance supports looking for visible roof-damage signs and inspection context, and GAF's storm damage resources support storm-damage repair context. Use those sources for general context only. Do not use them to claim that a particular blemish is hail damage, that a warranty applies, or that an insurer must approve the item.

Collateral photos can make the packet easier to review. Photograph gutters, downspouts, vents, soft metals, window screens, siding, fencing, garage doors, HVAC fins, and other exterior components when they are relevant and safely accessible. Label them as collateral context. Do not claim collateral automatically proves roof damage.

Collateral Photo Matrix

Collateral photos should be grouped by material and location. The goal is comparison, not exaggeration.

Collateral area	Photo type	Packet note
Gutters and downspouts	Wide elevation, mid-range, close-up of observed condition	Label as collateral context and tie to elevation
Roof vents and soft metals	Roof face overview and close-up	Preserve both roof-face location and component close-up
Window screens and siding	Elevation overview and close-up	Use only when relevant to the storm-date context
HVAC fins or exterior equipment	Overall equipment view and close-up	Do not disturb equipment or create unsafe access
Fencing, garage doors, or outdoor fixtures	Orientation and close-up	Separate property condition from roof condition
Interior stains	Room overview, ceiling/wall close-up, attic context if safe	Avoid causation language unless qualified review supports it

The matrix helps the office avoid two common mistakes. The first is ignoring collateral context entirely, which can make a roof packet feel isolated. The second is overusing collateral photos as if they decide the roof question by themselves. They do not. They help the reviewer understand the broader storm-context file when the photos are relevant, labeled, and safely collected.

Wind Photo Set

Wind-related photos need sequence and location. The packet should help the reviewer understand what component moved, where it moved, and what surrounding roof context exists.

Capture:

• Missing shingles or tabs with roof-face overview.
• Lifted, displaced, torn, folded, creased, or separated components.
• Exposed underlayment, fasteners, decking, flashing, or accessories where visible.
• Ridge, hip, rake, eave, valley, dormer, chimney, sidewall, vent, or penetration context.
• Interior leak or attic photos if water entry is part of the review and access is safe.
• Temporary repair photos before and after mitigation.
• Surrounding roof condition and any prior repair context.

The wind note should stay factual. Instead of "wind definitely caused this," use a packet note such as: "Observed missing shingles on west slope. Photos W-014 to W-019 show west-slope overview, close-up of missing shingle area, exposed underlayment, and temporary dry-in. NOAA weather context attached separately. Submitted for estimate review." That wording keeps causation and coverage decisions out of the contractor's lane.

Evidence Traceability Table

Every requested supplement review should have a row like this:

Requested review	Location	Photo IDs	Measurement/file source	Weather/context file	Note
Review missing shingle area	West slope, lower third	W-014 to W-019	Sketch S-W, field count FC-02	WX-2026-05-23-01	Observed missing shingles and temporary dry-in
Review collateral soft-metal context	Rear elevation downspout and roof vent	H-030 to H-038	Collateral log C-01	WX-2026-05-23-01	Collateral context photos attached
Review interior water stain	Bedroom ceiling below south valley	I-006 to I-010	Room log R-02	Homeowner report HR-01	Interior symptom documented; causation not stated
Review access limitation	North upper slope	SAFE-004	Safety/access note	Weather/access note	Close-up not collected due to unsafe access

This table makes the supplement easier to review and easier to audit internally. It also exposes weak rows before they leave the office. If a row has a requested review but no photo IDs, no location, no measurement source, and no note, the packet is not ready.

Office QA Before Sending

Before the packet leaves the office, run a quick QA pass. The reviewer should be someone who did not collect the photos. Fresh eyes catch unlabeled files, missing context, and overstrong notes.

Use this pre-send Checklist:

QA check	Pass standard	Repair action
One H1-style packet title or cover title	Packet has one clear title, address/project ID, and date	Add cover sheet
Weather context is limited	NOAA/NWS source says date, area, event type, and limitation	Add source-limit note
Safety note exists	Unsafe or inaccessible areas are documented	Add SAFE row and explain missing close-ups
Photos are grouped	Orientation, hail, wind, collateral, interior, access, and measurement photos are separated	Re-index the file folders
Every photo ID has a description	Photo log names location, view, component, and purpose	Add missing descriptions or remove duplicates
Every requested item has evidence	Requested review row points to photo IDs and file IDs	Hold packet until evidence or limitation note is added
Estimate notes are factual	Notes describe observed condition, location, quantity, and files	Remove coverage or causation language
Originals are preserved	Annotated versions do not replace original images	Add original files back to index
Privacy is handled	Personal information and unrelated interior details are redacted where appropriate	Save redacted and original versions according to company policy
RoofPredict status is current	Property record shows packet status and reviewer owner	Assign manager or supplement coordinator

This QA pass is also where the office should check tone. The packet should sound like a careful contractor file. It should not sound like an argument with the carrier, a legal brief, or a weather report pretending to be a roof inspection. A reviewer should see organized facts and know exactly what is being requested.

Example Estimate Notes

Good notes are short and traceable:

Situation	Better note
Hail observation	"Observed condition on front slope F1. See overview photos F1-001 to F1-004 and close-ups F1-020 to F1-026. Collateral context photos COL-010 to COL-014 attached. Submitted for estimate review."
Wind observation	"Observed missing shingles on west slope W1. See W1-006 to W1-013 and temporary dry-in photos MIT-002 to MIT-005. Weather context attached as WX-01. Coverage not stated."
Interior symptom	"Bedroom ceiling stain documented in INT-006 to INT-010. Exterior south valley photos S2-014 to S2-022 attached. Causation not stated in contractor note."
Access limit	"North upper slope not accessed due to unsafe condition. See ground overview N1-001 to N1-004 and safety note SAFE-03. Close-up photos not collected."
Measurement support	"Quantity review tied to roof report MEAS-01, sketch face W1, and field count FC-02. Photos W1-014 to W1-020 attached."

These notes do not guarantee anything. They reduce confusion. They give the reviewer a path from requested review to photos and files.

RoofPredict Workflow

RoofPredict can help the team keep the photo packet from becoming a messy folder. Use it to organize:

• Property record and route priority.
• Roof age and prior visit context.
• Storm-date and NOAA/NWS source links.
• Slope labels and photo IDs.
• Ground, roof, attic, interior, collateral, and safety photo groups.
• Access limitations.
• Homeowner report or office intake note.
• Measurement source.
• Supplement status.
• Manager or reviewer assignment.

The boundary is important. RoofPredict can organize the evidence and show review status. It does not decide weather causation, inspect the roof, approve a supplement, interpret policy language, act as a public adjuster, or replace a safety plan.

Insurance And Mitigation Boundaries

NAIC post-storm guidance tells consumers to document damage with photos or video, make a list, save damaged items when possible, and take reasonable mitigation steps after documenting. FEMA's claim FAQ says homeowners should gather insurance information, list damaged or missing items, and document property damage with photographs or videos.

Those sources support photo documentation. They do not let a contractor promise claim outcomes. Use careful language:

• "Photos attached for review."
• "Weather context attached for date and area."
• "Observed condition documented."
• "Access limitation noted."
• "Temporary mitigation photographed before and after."
• "Coverage and settlement are subject to insurer and policy review."

Avoid:

• "This proves coverage."
• "The carrier must pay."
• "NOAA confirms the roof was damaged."
• "The supplement will be approved."
• "Every mark is hail."

Source Limits

Source	Use it for	Do not use it for
NOAA Storm Events	Date, area, event-type, and narrative weather context	Property-specific roof damage proof
NWS glossary	Severe weather terminology context	Damage diagnosis
OSHA roof safety sources	Safety boundaries for roof inspection, tarping, repair, and fall hazards	Complete site-specific safety plan
GAF roof/storm damage pages	Manufacturer context for visible damage and storm-repair conversations	Causation, warranty, or insurance approval
NAIC and FEMA	General documentation guidance for photos/videos and damage lists	Private policy interpretation or payment promise
RoofPredict	Packet organization, photo IDs, source links, routes, and reviewer status	Inspection, adjusting, legal, safety, weather, or coverage decision

FAQ

Should every hail or wind supplement include NOAA records?

Weather context is useful when it is relevant to the date and area being reviewed. It should be labeled as context only. The roof packet still needs property-specific observations and photos.

How many photos are enough?

Enough photos to show orientation, location, condition, close-up detail, measurement support, and any safety/access limits for each requested review item. A small supplement may need fewer photos than a complex reinspection, but every photo should have a job.

Should contractors annotate photos?

Annotations can help when they are factual and the original photo is preserved. Keep both original and annotated versions in the file index. Do not use annotations to argue coverage or causation.

What if the crew cannot safely reach a roof face?

Record the safety/access limitation. Use safe ground photos, drone photos where lawful and company-approved, roof reports, interior photos, or a later qualified inspection if needed. Do not pressure staff or homeowners into unsafe access.

Can RoofPredict approve a supplement?

No. RoofPredict can organize the packet, source links, routes, photos, and review status. Approval, coverage, safety, causation, and payment decisions belong to the appropriate human reviewers and policy process.