A demand letter goes out on a hypothetical $42,300 water loss. Three weeks later, the carrier points to a payment ledger that doesn't match the offer and a contractor estimate with no photographs for one bedroom. Nothing in the file was hidden. It was never checked against itself.

For heads of property departments, pre-litigation supervisors, managing attorneys, and review teams, a claims audit checklist should expose those disconnects before the next consequential step. This is a file-level review of evidence, consistency, outstanding work, and stage readiness, not a financial statement audit or a universal regulatory compliance checklist.

Classify each gap as a missing document, an unresolved factual question, or a potential legal issue. Record status separately as complete, incomplete, conflicting, awaiting response, or not applicable. A document can be present while the question it raises remains open.

1. Claim Identity and Policy Materials

Start by confirming that the policy applies to the claimed property and loss date. Compare insured details, claim and policy numbers, addresses, policy periods, limits, deductibles, exclusions, and relevant endorsements against the notice and inspection materials.

A renewal notice isn't a substitute for renewal declarations. In a hypothetical hail file, a loss after the recorded expiration date leaves the applicable policy period unresolved until the renewal arrives.

• Check: Keep a policy summary with page references, including percentage deductibles and roof or ordinance-or-law provisions.

• Classify: Missing declarations are a document gap. A disputed address is factual. A potentially limiting endorsement needs attorney review.

• Act: Request a certified policy and preserve version history through consistent claim-file naming conventions.

2. Loss Facts and Chronology

Build the timeline from dates inside documents, not filenames alone. Include loss, discovery, notice, mitigation, inspections, submissions, and decisions, with a source and page for each entry.

Say a plumber's invoice describes the leak before the reported loss date. That's a conflicting chronology, not proof that either document is false. Assign an insured interview and obtain the underlying service record before adopting a factual account.

Mark estimated dates as estimates. Otherwise, a tentative date can become an unsupported statement in a demand or pleading.

Wamy reconstructs events across the file and flags conflicting dates or unexplained gaps. A disciplined AI document review process preserves the source behind each entry; the attorney decides which account the firm can support.

3. Correspondence and Carrier Positions

A reservation of rights doesn't become resolved because later correspondence discusses valuation. Review letters, email, portal messages, and telephone notes to identify the carrier's current position and the unanswered questions behind it.

For each material communication, record its date, source, owner, promised action, and response status. Separate an actual denial from a request for information or a preliminary position.

• Hypothetical finding: The carrier promised a reinspection, but the file contains no appointment confirmation or subsequent report.

• Classification: Awaiting response, with an unresolved factual question about whether the inspection occurred.

• Next action: Confirm scheduling in writing and assign follow-up. Route reservation-of-rights language to counsel as a potential legal issue.

Don't treat a phone note as a substitute for written confirmation of a consequential agreement. Preserve both rather than replacing the original note with a later summary.

4. Damage Evidence, Estimates, and Expert Materials

An estimate can be detailed and still lack support. Match claimed rooms and building components to photographs, moisture logs, sketches, inspection notes, and expert conclusions.

For example, a bedroom flooring replacement with no room photograph, moisture reading, or inspection reference is unsupported, not automatically improper. Request field notes and clarification before removing the item or presenting it as established damage.

• Check scope: Compare quantities, measurements, pricing location and date, and repair methods against the documented conditions.

• Check reports: Confirm authorship, signatures, dates, attachments, assumptions, and supporting tests.

• Assign review: Missing photographs are document gaps. Competing scope opinions are factual questions requiring technical review.

Wamy audits estimates and expert reports against the firm's standards, identifies discrepancies and missing support, and cites the source clause or rule behind each flag. Attorneys determine which opinions to rely on.

5. Offers, Payments, and Supporting Records

Reconcile offers, issued payments, and confirmed receipts separately. They aren't interchangeable, and an offer letter doesn't establish that funds reached the intended payee.

Maintain a ledger showing coverage category, payee, payment date, deductible, depreciation, prior payments, and supporting worksheet. In a hypothetical file, a payment below the offer without an explanation remains an unresolved variance until the carrier provides its calculation.

Reconciliation rule: Don't infer the reason for a deduction merely because the arithmetic could fit.

Request missing worksheets and payment confirmations. If a withholding explanation appears inconsistent with the policy, escalate it as a potential legal issue rather than recording an administrative discrepancy.

For NFIP claims specifically, FEMA's Proof of Loss guidance requires a signed Proof of Loss within 60 days of loss, unless a written FEMA extension applies. Verify supporting inventories and estimates rather than applying that deadline to every property claim.

6. Outstanding Document Requests

A request log should show what was sent, not what someone intended to request. Record the recipient, requested material, transmission evidence, response date, assigned owner, and next follow-up.

Say the contractor supplies an estimate but omits invoices requested in the same message. Mark the request incomplete, identify the outstanding invoices, and retain the partial response.

• Missing document: The requested invoice hasn't arrived.

• Awaiting response: The request was transmitted and remains unanswered.

• Potential legal issue: Missing material may affect an approaching policy or court obligation.

Keep litigation disclosure obligations separate from informal carrier and vendor requests. Counsel should distinguish initial disclosures under Rule 26(a)(1) from production requests under Rule 34, and verify the governing rules and orders.

Use the same item description in follow-ups so staff can match responses without guessing.

7. Conflicting Information

A measurement difference may reflect different methods rather than an actual contradiction. Compare definitions and context before escalating it.

For a hypothetical property-size discrepancy, retain both figures, identify whether each describes living area or total building area, and obtain assessor records or a measurement check. Don't select whichever figure produces the preferred valuation.

• Record both sources: Include document names, pages, dates, and the actual conflicting statements.

• Explain the significance: State whether the difference affects scope, credibility, causation, valuation, or coverage.

• Assign resolution: Identify the person and evidence needed to settle the question.

Wamy's claim audit and review workflow surfaces inconsistencies across correspondence, photographs, estimates, and reports. The reviewer confirms the underlying documents before treating a flag as an established conflict.

A discrepancy is a finding to investigate, not a conclusion about dishonesty.

8. Assigned Actions and Dates Requiring Review

Every open finding needs a named owner, review date, status, and source-backed next action. Review policy proof-of-loss requirements, suit-limitation language, appraisal provisions, carrier response dates, statutes of limitation, and court orders.

A deadline buried in an email is a control gap. Enter it in the firm's calendar with its source, while counsel confirms the controlling trigger, jurisdiction, exceptions, and calculation through the firm's docketing process.

• Hypothetical finding: Several files have overdue proof-of-loss requests because intake never captured the relevant dates.

• Action: Address urgent files individually, then repair the intake template.

• Ownership: Wamy tracks overdue actions and procedural gaps; the attorney confirms legal deadlines and approves consequential responses.

Portfolio review should identify recurring overdue requests, not merely produce a longer list of individual reminders.

9. Stage-Specific Readiness

Intake-ready doesn't mean demand-ready, and demand-ready doesn't mean litigation-ready. Apply written criteria appropriate to the next step.

• Intake: Confirm identity, retainer, policy, notice, initial photographs, estimate, and practice-relevant identification or incident records.

• Pre-demand: Verify support for the factual account, claimed scope, requested amount, payment reconciliation, and unresolved coverage questions.

• Litigation: Review preservation, discovery status, witness preparation, expert materials, missing affidavits, depositions not taken, and upcoming obligations.

For litigation involving electronic records, the District of Oregon's discovery guidance illustrates why repositories, custodians, preservation methods, production formats, and an ESI liaison belong in the review.

Hypothetically, an unsigned expert report may block pre-demand approval under the firm's standards even though intake is complete. Wamy applies stage-specific requirements and surfaces unfinished work; attorneys approve advancement and legal conclusions.

10. Documentation of Findings and Resolutions

A closed finding needs evidence that resolves it. Keep the original issue, source, classification, status, owner, resolution date, and verifier in the audit record.

For each finding, record the checkpoint and documents reviewed, the issue and why it matters to the next stage, the owner and required action, and the evidence that supports resolution. Note any question that remains open.

If a missing endorsement arrives after the audit, reassess the coverage assumptions and any correspondence that relied on them. Recording the document as received does not resolve its effect on the claim.

Wamy works as a digital claim analyst that re-evaluates the claim file as new information arrives, flags new gaps and inconsistencies, and surfaces issues with their sources for attorney review. An audit does not guarantee compliance or detection of every issue.

How each claim file checkpoint is reviewed, where gaps usually appear, and who acts on them

Turn the Checklist Into a Routine for Every Claim File

A claim file changes as documents arrive, positions shift, and deadlines approach. Recheck it at intake, before a demand or filing, and when new material changes the record. Keep confirmed facts separate from open questions.

Classify each gap as a missing document, an unresolved factual question, or a potential legal issue. The first calls for collection, the second for investigation, and the third for attorney analysis. A complete file can still contain unanswered factual or legal questions.

Supervisors can use recurring gaps to identify process problems. Missing endorsements across files may point to an intake weakness; overdue requests may indicate unclear ownership or escalation steps. Address the shared process while keeping follow-up assigned on each claim.

Wamy continuously evaluates the claim file against the firm's standards, flags gaps, and supports follow-up preparation. Attorneys remain responsible for legal conclusions and consequential decisions.

Visit Wamy to explore claim-file review and follow-up preparation built around your firm's standards.