Roofing Insurance Claim Follow-Up: Keep the Adjuster Step From Stalling the Request

The homeowner is waiting on an adjuster. The Request still needs a path.

A homeowner may want to repair the roof, have already met with your team, and still be waiting on an insurance adjuster before deciding what to do next. That pause does not necessarily mean the homeowner lost interest. It means an external process now sits between the roofing team and the next decision.

The claim process can involve an adjuster inspection, documentation, estimates, and settlement discussions. The National Association of Insurance Commissioners explains that an adjuster may work for the insurer or independently and reviews damage in the context of the policy. For a roofing team, the operational question is simpler: how do you keep the Request from disappearing while that step is happening?

The insurance step is a dependency, not a reason to lose the Request

Your team cannot decide when an adjuster will arrive, what an insurer will cover, or what a claim payment will be. It can preserve what is known about the roofing Request: what the homeowner said, whether an adjuster has been scheduled, the expected inspection date if one exists, the owner, the last known event, and the team’s next action.

The goal is not to manage the insurance claim for the homeowner. It is to keep a roofing Request visible while another process is underway.

“Waiting on insurance” is too vague

A note that says “waiting on insurance; follow up later” leaves the next person with more questions than answers. Has a claim been filed? Is an adjuster assigned or an inspection scheduled? Did the inspection already happen? Is the homeowner waiting for paperwork, or did they ask the roofer to reconnect?

You do not need to answer questions the homeowner has not answered. Preserve the facts you have instead. For example: “Homeowner says an adjuster inspection is scheduled for October 8. Jordan owns the Request. Reconnect after the inspection to discuss next steps.” That record gives the team a concrete place to resume.

Do not guess what the insurer will decide

A homeowner saying “they told me the roof should be covered” is not the same as an insurance approval. Likewise, “the adjuster is coming Friday” is not a claim outcome. Keep the Request history tied to what the homeowner or team actually knows.

The NAIC notes that coverage, deductibles, limits, and claim calculations depend on the applicable policy and circumstances. Record an inspection, a conversation, an assignment, or a date as an event. Do not turn any of those events into a coverage decision your team cannot verify.

Capture the adjuster step as a sequence of events

A Request is easier to pick up when the team can reconstruct the sequence: “Claim filed Sept. 18.” “Adjuster assigned Sept. 21.” “Inspection scheduled Oct. 3.” “Homeowner will send claim documents after the inspection.” Those entries describe the process without making an insurance conclusion.

The NAIC’s Post-Disaster Claims Guide encourages homeowners to keep dates, contacts, and next steps available during a claim. The same habit gives a roofing team the context it needs to maintain its own Request history.

Give the Request an owner and a next action

Insurance delays can create an ownership gap: the Request is still active, the adjuster owns the external step, and nobody inside the roofing company is clearly responsible for what follows. A Request owner does not control the claim. They own the roofing team’s next action.

That action may be to check in after a scheduled inspection, wait for the homeowner to send information, or reconnect on an agreed date if no update arrives. When a date is known, retain it. When no date is known, do not invent one. A status describes the situation; a next action tells the team what it should do about it.

If the adjuster has not contacted the homeowner yet

A generic follow-up sequence can create noise when the homeowner is still waiting for an external step. The insurer may be handling a large event, an adjuster may not yet be assigned, or the homeowner may simply not know the timing. None of those possibilities should become an assumption in your record.

Instead, record the homeowner’s current update and the next roofing-team action. For example: “Homeowner says the claim was filed and they are waiting for adjuster assignment. No inspection date given. Jordan owns follow-up; check with homeowner next week for an update.”

Update the Request after the inspection

The adjuster inspection is another point in the Request history, not the end of the roofing workflow. The Insurance Information Institute’s overview of the claims-payment process describes an adjuster inspection as part of that process. Afterward, record what the homeowner says happened and what your team will do next: “Homeowner expects claim documents later this week; follow up Friday,” or “Homeowner has not received an update; reconnect next Tuesday.”

Those statements lead to different next actions. Collapsing them into “insurance done” removes the context the next person needs.

Keep the roofing context attached to the Request

Insurance discussions can stretch across days or weeks. When the homeowner comes back, the team should not have to reconstruct the original inquiry, the inspection or visit already completed, the work discussed, the claim-related update, the owner, and the next action.

For teams that struggle to retain that history without adding another complicated system, How to Track Roofing Leads Without Another CRM covers the broader lightweight workflow. If the larger question is where Requests stop moving, use Roofing Lead Conversion: Find Where Your Leads Stop Moving.

An insurance delay is not automatically a dead lead

A quiet Request may eventually become signed work, a postponement, a decline, another estimate request, or another unresolved step. You cannot know which outcome will happen simply because the homeowner has been quiet for a few days.

The practical question is: what is the current state, and what is the next known action? If the estimate has already been sent and the homeowner has simply not decided, Unsold Roofing Estimates: A Follow-Up Playbook for Roofers covers that narrower post-estimate situation. A Request waiting on an external insurance step is a different dependency.

Where Kaldwick fits

For Requests that arrive through a Kaldwick shareable quote link, Kaldwick can keep the Request context, recorded activity, owner, current status, and next action visible to the roofing team. That can help preserve context while a homeowner waits on an external insurance step.

Kaldwick does not determine coverage, interpret a policy, predict claim approval, or contact an insurer for the roofing team. This article also does not claim that Kaldwick automatically detects adjuster activity or sends automatic insurance follow-up reminders. The roofing team still records what happened, assigns ownership, and decides the next action.

A simple insurance-delay check

For every Request described as “waiting on insurance,” make sure the team can answer these questions. If the only record is “insurance pending,” someone may have to rebuild the situation later.

• What exactly is the team waiting for?
• What has the homeowner actually told us?
• Has an adjuster been assigned or scheduled?
• Who owns the Request inside our team?
• What is the next action, and is there a date for it?
• What happened most recently?

What Happens in Your Roofing Shop?

When a roofing Request is waiting on an insurance adjuster, what does your team record so it does not disappear? Do you track the adjuster appointment, claim number, next homeowner contact, owner, or something else?

Every roofing shop handles insurance-related Requests differently. If you want to compare workflows with other contractors, share what happens in yours.

Join the Kaldwick contractor community and compare notes with other contractors →

Frequently asked questions