Roof insurance inspection checklist: what homeowners should have ready

A roof insurance inspection is an evidence appointment, not a promise that the claim will be approved, denied, paid at a certain amount, or converted into a full roof replacement. The useful homeowner goal is narrower: prepare the claim record, keep everyone in the right role, document visible conditions safely, ask specific questions, and wait for the written claim response before making assumptions.

The safest way to prepare is to build an inspection packet before the appointment. The packet should include the claim number, policy contact, storm date, safe photos, interior leak photos, contractor photos if available, temporary repair receipts, questions for the adjuster, and a place to log the next written document. NAIC homeowner claim guidance supports the basic claim-preparation lane: list damaged property, take photos and videos, contact the insurer or agent, provide policy and contact information, explain what happened, and describe the extent of damage.

Keep the boundaries clear. A contractor can explain roof conditions, repair scope, measurements, and photos. An insurer or adjuster handles claim review, coverage communication, deductible questions, depreciation, payment explanation, and the next step in the claim file. A homeowner can organize records and ask questions. A structured record system can keep the packet usable. RoofPredict can support roofing teams with roof age, storm exposure context, branded homeowner reports, CRM-connected workflow, and follow-up context where available. None of those roles should be blurred.

Direct Answer

During a roof insurance inspection, expect the inspector or adjuster to verify the claim information, review the reported storm or damage timeline, inspect the roof and related areas when safe and within their role, take photos or measurements, ask about leaks or temporary repairs, and later issue or contribute to a written claim document. Before the appointment, prepare safe photos, interior damage photos, contractor documentation, receipts, policy/claim information, and a short question list. Do not climb the roof for extra proof.

What a roof insurance inspection is

A roof insurance inspection is part of a claim workflow. It is usually triggered after a homeowner reports possible covered damage, often after hail, wind, hurricane, tornado, falling debris, or leak activity. The appointment may involve a company adjuster, independent adjuster, contractor, field inspector, engineer, or other reviewer depending on the insurer, claim type, and facts.

The inspection can involve several tasks:

The most important mental model is simple: the inspection produces evidence and review notes. The written claim response explains the insurer's position. A friendly inspection conversation is not the written claim response. A difficult inspection conversation is not a denial. Wait for the document, then compare it to the packet.

What it is not

A roof insurance inspection is not a homeowner roof-climbing assignment. It is not a contractor sales appointment by default. It is not a public-adjusting script. It is not a software-generated claim decision. It is not a guarantee that weather records prove roof damage. It is not proof that a roof must be replaced because a storm occurred nearby.

Hold these lines:

This boundary matters for trust. A homeowner needs clarity, not false certainty. A roofing company needs a cleaner evidence packet, not language that sounds like it is deciding coverage. A product page needs a defensible lane, not a claim that software can replace inspection or policy review.

Who may be involved

NAIC's Post-Disaster Claims Guide describes different adjuster roles and explains claim-payment concepts such as deductible, Actual Cash Value, and Replacement Cost Value. For a roof inspection, the homeowner should know who is present and what role each person has.

Ask every person for their name, company, role, phone, email, and what document they will produce or review. That is basic file hygiene. If a new person enters the claim later, the record should show who attended, what was inspected, and what follow-up was promised.

The inspection timeline

The roof insurance inspection usually sits in the middle of a longer process.

The timeline helps homeowners avoid two common mistakes. The first is treating the inspection as the final answer. The second is treating the contractor estimate as the final answer. The actual file often moves through several documents, and each version needs a date and owner.

If water is actively entering, keep the safety response separate from the claim argument. Move belongings away from water if safe, use buckets or towels where practical, avoid wet electrical fixtures, shut off affected circuits only if it can be done safely, and call qualified mitigation, roofing, or emergency help when needed. Do not install tarps, patch roofing, or inspect roof surfaces yourself if that requires roof access or ladder work.

Before the inspection: build the packet

The packet should be short enough to use and complete enough to prevent repeated questions.

FEMA guidance on documenting severe-weather damage supports the broad disaster-documentation habit: take photos and videos of damage, keep receipts, and consult the insurance adjuster or insurance company before signing repair or cleanup agreements. The FEMA page is flood-oriented, so do not stretch it into roof-specific claim advice. Use it for the general principle of safety-first documentation and recordkeeping after severe weather.

Safe photo map for homeowners

Homeowners should not climb roofs for inspection evidence. That point needs to be plain. OSHA's roof inspection, tarping, and repair guidance describes roof inspection and repair work as involving hazards such as ladders, raised surfaces, steep or slippery surfaces, deteriorated roofs, tools, power lines, and fall risks. That is enough to keep homeowner instructions at the ground, interior, and document level.

Use a safe photo map:

Photo labels matter. "IMG_4821" is weaker than "Kitchen ceiling stain, May 29, 2026, 8:15 a.m." A claim record should help the next person understand what they are looking at without guessing.

What the inspector may look at

The exact inspection scope varies. Still, homeowners can expect the reviewer to focus on areas connected to the reported damage.

Common inspection areas include:

• roof slopes and visible roof coverings;
• roof accessories such as vents, pipe boots, ridge vents, skylights, chimneys, flashing, and satellite mounts;
• gutters, downspouts, fascia, soffit, and drip edges;
• exterior elevations, screens, window wraps, siding, fencing, or soft metals when relevant;
• attic access, roof deck, insulation, or water paths if accessible and relevant;
• interior rooms with stains, active leaks, wet areas, damaged paint, or damaged personal property;
• temporary repairs, qualified temporary protection, mitigation work, drying equipment, and receipts;
• prior repair areas or visible pre-existing conditions.

The homeowner's job is not to force a conclusion during the appointment. The homeowner's job is to make the evidence easy to find. If the kitchen ceiling leaked after the storm, label the kitchen photos. If the contractor photographed a missing vent cap, place that photo near the contractor estimate. If the roof age is uncertain, collect records instead of guessing.

What to say during the inspection

Use factual language. Avoid conclusions that the written record cannot yet support.

This wording is not timid. It is useful. It gives the reviewer information and keeps the homeowner away from unsupported claim conclusions.

Questions to ask at or after the appointment

Ask questions that produce records and next steps.

Write down the answers. Include the date, person, role, and follow-up owner. A phone note with no name is better than nothing, but a structured note is stronger.

Inspection Attendance Notes

The appointment can move quickly. The homeowner may be answering questions, the adjuster may be taking photos, the contractor may be pointing to roof areas, and someone may be asking for documents. Attendance notes keep the file from becoming a memory contest later.

Use a simple attendance sheet:

Do not turn attendance notes into argument notes. A better note is: "Adjuster inspected front and left slopes; rear upper slope not viewed because access was limited; contractor photos R-04 through R-09 offered through portal." A weaker note is: "Adjuster agreed roof is damaged." The first note can be verified. The second may not survive the written response.

If the contractor attends, record whether the contractor provided photos, measurements, roof-area notes, temporary-protection details, or a written estimate. If the contractor only gave a verbal scope, ask for the written version before relying on it.

After the inspection: read the next document

After the appointment, the next useful milestone is the written document. Depending on the file, that might be:

• an insurer estimate;
• a coverage letter;
• a payment explanation;
• an ACV/RCV/depreciation explanation;
• a request for more information;
• a reinspection request;
• a denial explanation;
• a revised estimate;
• a supplement response.

When the document arrives, read it against the packet.

Do not mix numbers. ACV, RCV, deductible, prior payments, depreciation, and contractor totals are different things. The NAIC's ACV versus replacement cost explainer says actual cash value considers age, wear and tear, and depreciation, while replacement cost coverage is tied to repair or replacement with similar quality and is still subject to policy terms and the deductible. That is a vocabulary boundary, not a claim answer. Ask the insurer to explain the values in the actual claim document.

Written Response Decoder

The first written response can be hard to read because it may combine scope, price, deductible, depreciation, policy wording, and requests for more information. Decode it before reacting.

Use this decoder:

The decoder should produce one sentence:

Written response status: insurer estimate received; front-slope shingles and gutter item listed; kitchen ceiling stain not referenced; contractor photos and room-labeled photos will be submitted with a specific question about whether the kitchen was inspected.

That sentence gives the next owner a clean task. It does not argue from emotion or from the total price. It points to a document, an omitted item, and the evidence attached.

When the contractor disagrees with the insurer estimate

Estimate differences are common. The useful question is what kind of difference exists.

The contractor should not write a broad accusation. The stronger packet says: "The insurer estimate lists this line or scope area. The contractor estimate and photos show this condition. Please review whether the attached documentation changes the scope, quantity, or explanation."

That structure protects the homeowner. It also protects the contractor from turning a real roof issue into an unsupported claim-handling statement.

For a deeper line-by-line reading habit, use how to read a roofer inspection report as a homeowner after the written documents arrive. This page stays focused on the insurance inspection appointment and the first written response.

Reinspection And Supplement Tracker

If the written response misses an area or the contractor identifies a scope difference, the file may need a reinspection, supplement request, contractor clarification, or insurer question. Track those paths separately.

The tracker should not say "supplement approved" until the responsible party says so in writing. Use neutral status labels:

• submitted;
• waiting for response;
• more information requested;
• reinspection scheduled;
• revised document received;
• closed with explanation;
• routed to insurer, agent, mortgage servicer, licensed claim professional where appropriate, attorney, or state insurance department.

This is where many homeowners lose control of the file. A contractor may send photos to one address, the homeowner may upload receipts to a portal, the insurer may request a different form, and the mortgage company may have its own release process. Keep one tracker so each open item has an owner, date, document, and next step.

Inspection File Routing Matrix

The same claim packet should not go to every recipient in the same form. The insurer, contractor, lender, state insurance department, public adjuster, attorney, and internal roofing team may need different parts of the record. Good routing protects privacy and keeps the next question clear.

Routing matters because a claim file can become noisy fast. A homeowner who sends every document to everyone may create confusion, privacy risk, and conflicting expectations. A homeowner who sends too little may slow the next step. The best packet is specific: it names the recipient, the evidence attached, the exact question, and the boundary.

Use this note at the top of a routed packet:

Packet purpose: document the inspection record and ask the next process question.
Attached: labeled photos, contractor notes, receipts, and written claim response dated June 3.
Boundary: homeowner observations and contractor findings are not coverage, legal, payment, or deductible conclusions.
Question: please confirm the next document or review path for the attached item.

That note tells the recipient what to do with the file. It also prevents a contractor photo upload from sounding like a demand letter or a lender packet from sounding like a roof-damage argument.

Evidence Version Control

Storm and claim files often change after the inspection. A contractor may add photos. The insurer may send a revised estimate. A mitigation company may add an invoice. A lender may request a completion form. Without version control, the homeowner may not know which document was sent, who saw it, or whether a newer file replaced an older one.

Use a version table:

Every version should answer three questions:

• What changed since the prior version?
• Who received the new version?
• What question remains open?

Version control is especially important when contractor photos arrive after the adjuster appointment. Label them as contractor photos, include the inspection date, identify the roof area, and explain the exact question they support. Do not upload a large folder with no note and expect the insurer, contractor, or homeowner to infer the point.

If a document is superseded, keep it, but label it:

Superseded by insurer revised estimate dated June 7, 2026. Kept for history only.

That prevents old totals, old scope, and old payment explanations from being quoted as if they are current.

Minimum Packet By Inspection Situation

The homeowner does not need the same packet for every claim appointment. Use the smallest complete packet that fits the situation, then add detail only when the next reviewer needs it.

This table keeps the packet from becoming bloated. A homeowner with a small leak should not have to build a lender packet before the first inspection. A homeowner with a claim check should not send the lender a roof-causation argument. Match the file to the decision in front of you.

The minimum packet also helps a roofing team decide what to ask for next. If the issue is a missing roof area, ask for labeled roof photos and the insurer estimate line. If the issue is a payment explanation, route it back to the insurer or agent. If the issue is lender release, route it to the mortgage servicer. Each path should have one owner, one question, one document set, one date, one expected response, one unresolved item list, one current owner, and one follow-up date.

Three inspection scenarios that need different packets

Not every roof insurance inspection needs the same preparation. The homeowner should match the packet to the problem. A leak-only file, a widespread hail file, and a contractor-scope disagreement can all involve a roof, but the documents and questions differ.

Scenario 1: Interior Leak After Wind-Driven Rain

The homeowner notices a ceiling stain in the hallway the morning after a severe thunderstorm. The roof edge is visible from the yard, but the homeowner cannot see an obvious missing shingle. The first instinct may be to photograph the roof from a ladder. That is the wrong evidence path for a homeowner.

Build a leak packet instead:

This packet does not say wind-driven rain is covered. It says the homeowner has an interior condition and a timeline. The insurer or adjuster still has to evaluate the claim file, and any legal or policy dispute belongs with the appropriate licensed professional or state resource.

Scenario 2: Hail Reported Nearby, No Active Leak

The homeowner sees a local storm report and neighbors are calling roofers. There is no active leak, but the homeowner is concerned about possible roof damage. The evidence packet should avoid two extremes: ignoring the concern completely or treating a storm report as proof.

Build a weather-context packet:

NOAA and IBHS sources help set the boundary: severe weather can matter, and impact resistance can matter, but property-level interpretation still needs evidence. The homeowner's file should make that evidence easier to review without claiming diagnosis from ground photos.

For the broader pre-roofer storm file, use how to document storm damage before calling a roofer. The inspection packet here should include only the storm details needed for the insurance appointment.

Scenario 3: Insurer Estimate And Contractor Estimate Do Not Match

The inspection happened, the insurer estimate arrived, and the contractor says the scope is incomplete. This is where many files become messy. The homeowner forwards a stack of PDFs with no explanation, the contractor argues from the total, and the insurer asks what specific item is being disputed.

Build a difference packet:

The difference packet should be narrow. One well-labeled scope question is easier to answer than a large upload that asks everyone to "reconsider the roof."

One-Page Inspection Packet Example

Use fictional examples when training a team or building product templates. Do not publish customer claim files, addresses, photos, checks, insurer letters, or contractor documents.

Here is a compact packet for a fictional property:

The same packet can be converted into a homeowner message:

This is the kind of wording a structured claim packet should make easy to assemble. It is specific, calm, and easy to audit. It also avoids the two highest-risk patterns: diagnosing roof damage from photos and promising a claim outcome.

Mistakes That Make Inspection Files Harder To Review

The first mistake is waiting until after the appointment to organize evidence. The homeowner may still recover, but it is easier to prepare before the adjuster arrives.

The second mistake is sending a photo dump. Fifty unlabeled images are weaker than ten labeled images that show room, elevation, date, source, and reason.

The third mistake is mixing roof conditions with payment conclusions. "The kitchen ceiling stain is visible in photos K-01 through K-04" is useful. "The insurer has to pay for the kitchen" is a different kind of statement and needs policy/claim review.

The fourth mistake is letting a contractor speak for the policy. A contractor can be extremely useful for roof scope, photos, measurements, materials, and repair sequence. That does not make the contractor the coverage authority.

The fifth mistake is treating weather data as a claim decision. Weather context belongs in the file, but the roof still needs property-level evidence.

The sixth mistake is losing revised versions. Save every insurer estimate, contractor estimate, coverage letter, payment explanation, request for information, and denial explanation with a date and version label.

The seventh mistake is making any software sound like a claim decision tool. A product or record system should make the file cleaner, not overstate what the file proves.

Weather Records: Useful Context, Not Damage Proof

Weather records can help establish timeline context. They should not be treated as proof that a specific roof was damaged or that the policy covers the damage.

NOAA's Storm Events Database can be used for historical storm-event context. NOAA/NSSL's severe thunderstorm FAQ is useful for general severe-weather context. But neither source can replace property-level inspection evidence.

Use weather records carefully:

A structured record can keep weather context beside photos and claim notes. It should not convert weather context into a damage or coverage conclusion.

Hail And Roof Condition Boundaries

Homeowners often ask whether visible marks are hail damage. That question is risky to answer from ground photos alone. IBHS's Impact Resistance Test Protocol for Asphalt Shingles is useful as a research and product-comparison boundary: it should not be stretched into insurance claims, warranties, legal standards, or claim handling.

That boundary is valuable. A homeowner packet should not pretend to diagnose hail from a few photos. It can show what to organize:

• safe ground-level photos;
• contractor-supplied roof photos if a qualified person inspected the roof;
• photos of related exterior clues such as gutters, downspouts, vents, screens, siding, or soft metals;
• interior leak photos if water entered the home;
• storm date and timeline notes;
• roof age records and prior repair records;
• written contractor estimate or report;
• the insurer's written estimate or response when received.

The point is not to diagnose. The point is to build a file that a qualified reviewer can understand.

Contractor and payment boundaries

The FTC's weather-emergency scam guidance is directly relevant after storms. It cautions consumers to verify insurance coverage rather than rely on a contractor to say what is covered, avoid signing insurance checks over to a contractor, compare written estimates, confirm licensing and insurance where applicable, and avoid blank contracts.

Contractor and public-adjuster rules are state-specific. The NAIC state insurance department map is the right starting point for state regulator contacts. State examples show why the article cannot give national legal advice: Texas Department of Insurance roofing guidance warns Texas consumers about deductible-waiver and claim-handling rules after storms. Those examples prove that state rules matter; they do not create a national rule for every homeowner.

For a roof insurance inspection, that means:

This is not anti-contractor. Good contractors benefit from clean documents too. The problem is role confusion and pressure. Keep the contractor's repair expertise in the file, but let insurer/policy questions stay with the proper reviewer.

Mortgage company and claim check questions

Some claim payments involve a mortgage company, mortgage servicer, or lender. The inspection itself may not answer those logistics. The CFPB claim-payment guidance explains that some insurance checks may include both the homeowner and mortgage servicer or lender, and that funds may be released in stages as repairs progress. Ask early:

• Will the claim check include the mortgage company?
• What documents does the lender need before endorsing or releasing funds?
• Are inspections required before draws are released?
• How are contractor invoices handled?
• What happens if the repair cost changes after the first estimate?
• Who is responsible for sending completion photos or invoices?

Do not wait until the contractor is ready to start work to ask these questions. Payment logistics can delay repairs even when the scope discussion is clear.

For Xactimate-style insurer estimates, how to read Xactimate estimates like a pro can help with line labels and estimate structure. Keep that separate from coverage or payment conclusions.

Inspection-Day Scorecard

Use this scorecard before the appointment. Score each row 0, 1, or 2.

Interpret the score:

The scorecard keeps the inspection from becoming a memory test. A homeowner under stress should not have to remember every leak, text, receipt, and conversation on the spot.

Claim Wording Release Card

Before sending a message to the insurer, contractor, or lender, write a one-page release card.

Example:

This release card is useful for homeowners and contractors. It forces the message to name the evidence and the ask. It also stops the message before it becomes a claim argument.

Where RoofPredict fits

RoofPredict can support roofing teams with roof age, storm exposure context, branded homeowner reports, CRM-connected workflow, and follow-up context where those product features are available.

That support can make an inspection packet easier to discuss because the roofer is not starting from a blank page. The homeowner still needs a separate claim file for insurer documents, receipts, private claim notes, payment records, and legal or policy questions.

Use this boundary:

The strongest product message is restraint. RoofPredict can help make a roofer's workflow and homeowner-facing report clearer. It should never be framed as an inspector, adjuster, insurer, public adjuster, lawyer, contractor selector, damage verifier, or payment predictor.

After The Written Response: Close The Loop

The file should not end with "inspection done." Close the loop after the written response arrives.

The closeout step is not busywork. It helps the homeowner, roofer, insurer, and lender work from dated records instead of memory.

If The Written Response Is Partial

Many claim files do not arrive as one perfect answer. The written response may include an estimate but no explanation of depreciation. It may include a payment note but leave out a room. It may request more information. It may address the roof but not interior damage. It may explain the deductible but not the mortgage-company process.

Treat a partial response as a sorting task, not as a reason to guess.

The strongest follow-up is narrow. A broad message such as "please fix this claim" is hard to process. A narrow message says:

Please confirm whether the upstairs bedroom ceiling photos B-01 through B-04 were included in the inspection review. The written estimate dated June 3 includes roof items but does not mention that room. If another document or reinspection request is needed, please identify the correct process.

That message does not decide coverage. It asks whether a specific part of the record was reviewed and what process comes next.

Homeowner Follow-Up Scripts

Scripts help homeowners stay factual when the claim file gets stressful. Use them as starting points and adjust them to the actual document.

Every script should include the claim number, document date, property address, and attachment list. Keep the tone neutral. A clear question is more useful than a long argument.

Do not use scripts to pressure a contractor into claim advocacy or to ask software to answer coverage questions. Use them to move the right evidence to the right reviewer.

How to use the sources without overclaiming

FAQ

Will the roof insurance inspection approve my claim?

No. The inspection gathers and reviews information. The written claim response communicates the insurer's position. Treat the appointment as evidence collection, not an approval event.

Should my roofer be present for the inspection?

It may help if the insurer allows it and the contractor can provide photos, measurements, repair-scope notes, or a written estimate. Keep the role clear: the contractor explains observed roof conditions and repair scope; the insurer or adjuster handles claim review and policy communication. The contractor should not negotiate coverage or settlement unless properly licensed and allowed to do so where the property is located.

Do I need to climb the roof before the adjuster arrives?

No. Use ground-level photos, interior photos, receipts, documents, and contractor-supplied roof photos if a qualified person inspected the roof. Do not climb the roof to create extra evidence.

What should I have ready before the appointment?

Have the claim number, insurer or agent contact, storm date, safe photos, interior leak photos, contractor estimate if available, temporary repair receipts, prior roof records, and a short question list.

Can weather reports prove my roof was damaged?

No. Weather reports can support timeline context. They do not prove property-level roof damage, causation, coverage, or payment by themselves.

What if the contractor estimate is higher than the insurer estimate?

Compare the difference by scope, quantity, material, price context, and policy/coverage questions. Send specific photos, measurements, receipts, or line references instead of arguing from the total alone.

What is ACV and RCV?

ACV generally refers to Actual Cash Value and RCV to Replacement Cost Value. ACV usually accounts for age, wear and depreciation; RCV is policy-dependent replacement cost language and can still be subject to deductible, limits, and claim conditions. Ask the insurer to explain the values shown in the written document.

Should I sign a contractor agreement before the inspection?

Be careful. Emergency mitigation may be needed, but do not sign blank contracts, unclear assignments, or payment terms you do not understand. FTC guidance supports written estimates, contractor checks, and caution around insurance checks.

What if the inspection misses an interior leak room?

Label the room photos, save the written response, and ask how to submit the missing information or request review. Keep the message factual: room, date, photos, and question.

Can RoofPredict tell me whether the claim will pay?

No. RoofPredict can support roof age, storm exposure context, branded homeowner reports, and roofing-team workflow where available. It does not decide coverage, verify damage, adjust claims, manage private claim files, or predict payment.

Who should explain coverage or payment questions?

Ask the insurer, agent, licensed claim professional where appropriate, mortgage servicer, attorney, or state insurance department depending on the question. A roofer can explain observed roof conditions and repair scope, but coverage, payment, deductible, depreciation, public-adjuster, and lender questions belong in the proper review lane.

What makes the packet strong enough for the next step?

A strong packet has the claim identity, timeline, safe photos, contractor documentation, receipts, written response, exact question, and role boundary. It avoids roof access, coverage promises, weather-proof claims, and contractor payment pressure.

What if the adjuster cannot inspect every roof area?

Record the limitation by area, date, and reason. Do not fill the gap with your own roof access. Ask how to submit contractor photos, request reinspection, or document the limited area in the written response.

How should I send contractor photos to the insurer?

Send labeled photos with roof area, date, contractor name, inspection date, and the exact question they support. Avoid a large unlabeled upload. Tie each photo set to a scope, quantity, material, temporary-repair, or missing-area question.

What if the mortgage company is listed on the claim check?

Ask the insurer and mortgage servicer what endorsement, inspection, invoice, completion, and draw-release process applies. Keep that payment process separate from roof damage, coverage, and contractor-scope questions.

What if I do not understand the written response?

Ask the insurer or agent to explain the exact line, value, exclusion, request, or next step in writing. Send a focused question with the document date, page or line reference, and attached evidence. Do not rely on a contractor summary alone for policy language.

Should I send the same inspection packet to everyone?

No. Send the parts that fit the recipient and question. The insurer may need claim photos and receipts, the contractor may need roof-scope evidence, and the mortgage servicer may need payment or completion documents.

How should I track revised estimates or new photos?

Use version control. Record the date, owner, what changed, who received it, and what question remains open. Keep superseded documents, but label them as history so old totals are not treated as current.

What if the written response only answers part of the claim?

Sort the missing piece before responding. A missing room, missing roof area, unclear depreciation line, document request, and mortgage-payment question each need a different packet and recipient.

Can I use a script for follow-up messages?

Yes, but keep the script factual. Include the claim number, document date, attachment list, exact question, and boundary. Do not use a script to make coverage, payment, legal, or deductible conclusions.

Inspection-Day Checklist

Before the appointment:

• Confirm the date, time, person, company, role, and claim number.
• Save insurer, adjuster, contractor, and agent contact information.
• Collect policy and claim identifiers in one place.
• Record storm date, leak date, claim-report date, and temporary repair date.
• Photograph visible conditions from safe ground-level and interior locations.
• Label photos by room, elevation, date, and source.
• Save contractor photos, measurement reports, and written estimates if available.
• Save receipts for qualified temporary protection, drying, temporary repairs, or mitigation.
• Prepare questions about areas inspected, documents needed, deductible, ACV/RCV, depreciation, supplement process, and next written document.
• Keep contractor repair-scope questions separate from insurer coverage/payment questions.
• Do not climb the roof.
• Do not sign blank contracts or hand over claim checks without understanding insurer, lender, and contract requirements.
• Store everything in an organized claim folder or record system.

After the appointment:

• Record what was inspected and who attended.
• Ask when the written document should arrive.
• Save the estimate, coverage letter, payment explanation, request for information, or denial explanation.
• Compare the written response to your packet.
• Send only specific follow-up questions with evidence attached.
• Keep policy, legal, deductible, public-adjusting, and payment questions with the insurer, adjuster, mortgage servicer, state insurance department, licensed public adjuster where allowed, attorney, or other appropriate reviewer.