- Document requests are contractual, not optional: nearly every property policy conditions coverage on providing records and documents the insurer reasonably requests, and unanswered demands can put the whole claim at risk.
- Reasonableness is the boundary — requests have a scope, a time period, and a relevance link to the loss, and those three axes are how you evaluate every demand.
- The winning response format never changes: in writing, dated, with an itemized inventory of what is enclosed, what is coming, and what does not exist — with the why.
- Silence is the only wrong answer. A narrow, specific objection paired with a scoped offer protects you; ignoring a request protects no one.
- A second opinion on a heavy demand costs nothing — we review requests and response strategy at no cost. Our residential and commercial property work is generally on contingency — we only get paid from the recovery, not your pocket.
Somewhere between the first inspection and the settlement conversation, most serious property claims produce a letter that begins with some version of: please provide the following. Receipts. Photographs. Repair invoices. Bank statements. Leases. The list can be short and sensible or long and startling — and how you answer it shapes the claim more than most policyholders realize.
This guide keeps things general: what the produce-records condition in a standard policy actually requires, how to test any request for reasonableness, the response format that protects you, how to object without stonewalling — and why a demand heavy enough to worry about is worth legal eyes early, while the response is still being shaped.
What no playbook replaces is the contract in your own file. The duties, the deadlines, and the consequences all start with the policy's actual words. Every policy is different, every claim turns on its own facts.
The Playbook, in Four Moves
Know What the Condition Actually Covers
The standard produce-records condition obligates the insured, after a loss, to provide records and documents the insurer requests and to permit copies — usually alongside its cousins: the inspection duty, the recorded-statement request, and the examination under oath. Read your policy's version once, closely — however, every policy is different — and its exact words control. The condition's language is the source of the duty and also its outer limit: it speaks of requested records that relate to the claim, not of unlimited access to your life.
Because it is a coverage condition, the stakes are structural. Courts across the country treat noncompliance with post-loss duties as a serious matter — in some places outright forfeiture territory, in others a question of whether the carrier was prejudiced. The document demand deserves the same respect as the formal proceedings: it is part of the same conditions machinery.
Test Every Request on Three Axes
Scope: what categories of documents, and how many? Time period: how far back, and does the window make sense for this loss? Relevance: what does each category have to do with what happened and what it costs? A request for two years of utility bills on a vacancy question passes the test easily; a demand for a decade of complete financial records on a straightforward roof claim invites questions on all three axes.
The test is an evaluation tool, not a refusal license. Most requests, most of the time, are ordinary investigation — the carrier is entitled to verify the loss, the ownership, and the amounts, and prompt production is both a duty and good strategy. The axes exist for the outlier demand, and their purpose is to help you articulate precisely what makes it an outlier.
Respond in Writing, with an Inventory
Every response should be a dated transmittal letter with an itemized list: these documents are enclosed, item by item; these are being gathered and will follow by an estimated date; these do not exist or are not in my possession, and here is why. Number the items, keep a copy of everything, and send it by a method that proves delivery. Do this every single time, even for small productions.
The inventory habit pays twice. In the moment, it converts a vague obligation into a completed checklist and makes follow-up requests easy to reconcile against what was already sent. Later — if the claim ever becomes a dispute about who cooperated — the dated inventories are the record, and the party with the record usually wins the characterization fight.
Object with Specificity, Never with Silence
When a request fails the three-axis test, say so in writing, narrowly: identify the specific items you question, state the reason — overbreadth, an unexplained time window, no apparent connection to the loss — and pair the objection with a scoped offer. Not the decade of records, but the two years surrounding the loss; not every account, but the account that paid for the repairs. Ask, in the same letter, for the carrier's explanation of relevance if it disagrees.
What never works is the null response. Ignoring a demand creates exactly the noncompliance record the conditions machinery punishes, and it hands the carrier a better story than the one it started with. If a request feels invasive enough that you are tempted to go silent, that is precisely the moment for a professional read instead — which costs nothing and preserves everything.
Where Document Demands Meet the Other Procedures
Document requests rarely travel alone. They arrive bundled with recorded-statement requests, as homework before an examination under oath, or as the stated reason a valuation conversation has paused — and each pairing has its own logic. The pattern worth noticing is sequence: paper demands that keep expanding while nothing else moves are telling you something about the claim's real posture.
There is also an honest boundary to name. Answering what the request covers, organizing the production, and building the inventory record is work you can do yourself or with claim-side professionals. Deciding whether a demand has crossed from investigation into something the law treats differently — and what to do about it — is legal judgment — and getting that judgment early, while the response is still being shaped, is what keeps a paper problem from becoming a coverage problem.
How Property People Law Approaches Document Demands
We read the request against the policy's condition and the claim's facts — and against the coverages and benefits the file may not have surfaced — and we answer the practical question first: what should be produced, what should be questioned, and how should the response be papered. You get that answer straight, along with an honest read of whether the demand pattern itself is telling you something.
When the demand pattern is the problem — expanding requests on a stalled file, invasive scope with no stated relevance, paper bundled with formal proceedings — the legal lane takes over: objections framed to the standard that governs them, the cooperation record built deliberately, and the claim's momentum protected while the paper gets answered.
Our residential and commercial property work is generally on contingency — we only get paid from the recovery, not your pocket. Past results in other cases don't guarantee outcomes in any new matter, and every claim turns on its own facts.
State-Specific Guides
The playbook above is general. The cooperation standards, the consequences of noncompliance, and the remedies when demands become leverage are set by each state's own law, and each guide below applies this playbook under that law:
- Requests for Information in Florida Property Claims: Order Out of the Paper
- Requests for Information in South Carolina Property Claims: The Second-Request Problem
- Requests for Information in North Carolina Property Claims: Classify Before You Copy
- Requests for Information in Kentucky Property Claims: Cooperation Runs Both Ways
- Requests for Information in Indiana Property Claims: Stall-Proofing the File
- Requests for Information in Illinois Property Claims: Stepping Off the Request Treadmill
- Requests for Information in New York Property Claims: Document Logistics for Layered Losses
