Insurance Claim Supplement Documentation: Show What Changed and Why
A useful property-claim supplement explains what changed from the earlier estimate, why it changed and which evidence supports each requested revision. A larger estimate and an unlabeled photo folder do not provide that explanation.
Consider a fictional example: a contractor submits a revised estimate after materials are removed. The total has increased, but the reviewer cannot tell which line reflects newly exposed damage and which corrects an earlier quantity. The missing document is not another persuasive letter. It is a clear record of the differences.
Download the blank supplement evidence matrix. Use it alongside the required estimate format—not as a replacement for it.
Separate the reason for each change
- Newly observed condition: identify when and how it became visible, with before/after or exposure records where available.
- Quantity correction: show the revised measurement and calculation, not only the new total.
- Scope clarification: identify the operation, component and supporting explanation.
- Pricing or specification question: identify the source and applicable date, location and product. A quote does not automatically establish a covered amount.
Keep these reasons separate from coverage decisions. Contractors can document their work and observations; negotiating a claim may involve licensing or representation rules that vary by state. Follow the assignment, applicable law and the insurer's submission process.
One row per proposed change
The matrix asks for the prior estimate version and item reference, location, requested change, reason, supporting documents or photos, quantity/unit basis and unresolved questions. These are practical fields, not a universally mandated insurer form.
Illustrative row: “Estimate v1, item 42; kitchen north wall; quantity revision requested; revised dimension recorded in sketch S-03 and measurement photo P044; original and proposed quantities shown separately; repair scope remains subject to review.”
Do not insert an invented price, code citation or measurement to fill an empty cell. An explicit missing item is safer than a plausible-looking assertion. If a change depends on a code requirement, verify the applicable jurisdiction, adopted edition and provision, and explain how it applies to this work.
Give the reviewer a navigable package
- Identify the baseline. Include the estimate version being revised and the date of the new submission.
- Summarize the changes. Separate new observations, corrections and remaining disputes.
- Attach the revised estimate. Keep line references consistent with the evidence matrix. If you use Xactimate, follow the requested export and handoff format.
- Link the support. Add labeled photos, measurement records, invoices, quotes or relevant correspondence. State the source of third-party documents.
- Track the response. Record what was accepted, questioned or still awaiting evidence; preserve prior versions.
Xactimate already supports project photographs; see Verisk's capture guide. A separate drafting tool may help explain the evidence, but that is not proof of a native Xactimate integration. Check the actual handoff before changing your workflow.
What not to promise
A supplement is a request for review, not a guaranteed additional payment. Better documentation does not override exclusions, limits, deductibles or disputes about cause and scope. Avoid “approved in 24 hours” and “recover 30% more” claims unless you have applicable, defensible evidence.
If AI helps draft the explanation, compare every proposed change with its source. Check for invented dimensions, duplicated operations, missing qualifications and mismatched photo references. Our AI claim-report review checklist covers that final pass.
Evaluate the output before adopting another app
Download a FieldScribe AI sample report to assess its structure, or watch the product walkthrough. These are general reporting examples, not an insurer-approved supplement package.
For a broader tool decision, read the source-checked field-adjuster apps comparison. If drafting is the gap in your process, try one authorized file in FieldScribe AI's 14-day trial, with no credit card and a first-report setup call. Judge it on the review work it saves—not the size of a promised settlement.
FieldScribe AI editorial team
Practical documentation guides
Source-linked working guides from FieldScribe AI. Examples are illustrative, not customer case studies. These articles are educational and do not replace professional judgement, policy wording or local requirements.
Find more of our reporting in Google Search
If our articles are useful to you, add FieldScribe AI as a preferred source on Google so our content shows up more often when you search.
Related Articles
Marine Cargo Claim Assessment: What the Policy and Evidence Must Support
Twenty cartons arrive wet. What loss can you support, and what is actually covered? A worked example separates evidence, valuation, and coverage.
Wind and Hail Inspection Documentation: A Field Checklist for Adjusters
A storm map and thirty roof close-ups can still leave the reviewer guessing. Connect site observations to their locations and sources without overstating cause.
Insurance Claim Photo Log: Free Template and Caption Examples
The damage is visible. The room is not. Give each claim photograph a location, a finding and a clear link to the report—with a free photo-log CSV.