Ask for the exact item, date range or question preventing a decision. Match it to what you sent and confirm four different stages: sent, received, usable and reviewed. If payment was refused, get the decision and reason; if a record is missing, identify its holder and the next action.
What you can do with this guide
- Ask for the precise missing document or unanswered question, not another generic status update.
- A receipt does not prove the file was readable, responsive or reviewed.
- Choose the next contact from the actual blockage; a refusal needs a different response from a missing record.
You sent the paperwork. You checked the portal. The claim still says “pending,” and the next message asks for something you thought you already supplied. Meanwhile, you still have bills, missed time or a vehicle problem to deal with. Another unsorted upload is unlikely to tell you where the process stopped.
Make the next conversation about one exact gap. Was the file received? Could it be opened? Did it cover the requested dates? Has anyone reviewed it? Those questions turn “still waiting” into something you can follow up on.
This guide gives you an itemized response, a document ledger and a way to decide whom to contact next. It also separates an unfinished review from a refusal to pay, because those call for different responses. The state-law examples below retain their own limits and do not create a national deadline.
Identify the item that is pending
Save the insurer's actual request, including attachments and the date received. Write the company, claim number, crash date, contact person and claim component at the top of your notes. If vehicle damage and injuries have different contacts, identify which one sent the request.
Read the message for an actual question: Does the insurer need proof of repair cost, a particular service date, a wage period or something else? “Additional documents required” is not specific enough to tell you what to obtain. Ask for the document type, period, version or missing field that would address the question.
Keep a pending request separate from a decision. A portal label does not establish that every part of the claim is undecided, and a decision about one expense may not resolve another. If the company says it has refused payment, ask which item was refused and why; use the separate written claim-decision guide for that task.
The Texas Department of Insurance's claim guide recommends making a list of requested information and keeping notes of conversations. The ledger below adds a practical way to reconcile that list with files, receipts and follow-up messages.
Separate sent, received, usable and reviewed
These four labels are editorial tools for your own records. They are not official insurer statuses, legal findings or a promise about how a claim system works. A document can reach one stage without reaching the next.
On a phone, swipe across the table to read all columns.
| State | Evidence to keep | What it does not establish |
|---|---|---|
| Sent | The exact message and attachment list, upload result or mailing record. | That the correct claim team received every file. |
| Received | A receipt or acknowledgment identifying the destination and, ideally, the files. | That each file opens, covers the requested period or answers the question. |
| Usable for the request | A check of legibility, pages and scope, plus the recipient's confirmation or stated defect. | That the contents are accepted as accurate, sufficient proof or covered loss. |
| Reviewed | The reviewer confirms considering the identified document or explains what it did not resolve. | That the claim is approved, fully valued or payable. |
Distinguish your observation from the recipient's. Write “opens on my device; recipient check not confirmed” rather than “accepted.” If an automated receipt does not name attachments, record that limitation. If the adjuster says “I have your email,” ask whether the relevant files are present and accessible.
Likewise, “reviewed” is not a successful claim outcome. A record might be considered but leave a factual question unresolved. Your notes should show the remaining question instead of converting an administrative update into a conclusion about payment.

Build one row per requested item
A single row called “medical paperwork” hides too much. Separate the visit note, itemized bill and any other specifically requested record. For a large request, group genuinely related files under a numbered item, but keep their names and periods visible.
| Field | What to record | Why it helps |
|---|---|---|
| Request and purpose | Request date, requester and the precise unresolved question. | Connects the attachment to the issue it is meant to address. |
| Exact item | Document type, issuer, date range, version and required pages or fields. | Distinguishes a missing record from the wrong version. |
| Holder and action owner | Who maintains the record and who is arranging the next step. | Prevents assuming someone else has requested it. |
| Submission | Verified route, destination, filename, sent date and attachment count. | Shows exactly what was transmitted and where. |
| Receipt and usability | Receipt reference, recipient confirmation and any stated opening, page or scope problem. | Separates transmission from a usable response. |
| Review and remaining gap | Reviewer response, unresolved field and date of the explanation. | Shows whether the issue changed after the document arrived. |
| Next action and check date | Named person or team, specific task and agreed or requested follow-up date. | Turns a general waiting period into a task you can follow. |
Keep a row's history when something changes. For example, retain “October 19: requested readable page 3,” then add “October 21: replacement delivered.” Do not overwrite the original request or make it look as though the corrected file was sent earlier.
Use “not confirmed” when you do not know. A blank receipt field is not proof of nondelivery, just as an unanswered email is not proof of refusal. The record should make uncertainty visible, so the next question is easy to identify.
Match the requested period and version before resending
Open the attachment you intend to send, not merely a similarly named file. Check its issuer, date range, page count and document type against the request. A filename saying “final” does not demonstrate that it is the version the reviewer needs.
Common mismatches include a pay stub for the wrong pay period, an estimate instead of an invoice, a visit summary instead of the requested clinical note, or an initial repair estimate instead of a later supplement. Ask for clarification if the insurer's wording could describe more than one record.
For policy questions, identify the package that applied on the accident date. A later renewal is not a substitute simply because it is the newest download. Our auto policy document guide explains how to distinguish the declarations, policy forms and endorsements without treating any listed limit as a promised payment.
If a new file replaces an earlier one, label the change in your cover message: “This is the shop's October 22 supplement; the October 16 estimate remains in the history.” If you resend an unchanged file, call it a duplicate and refer to the earlier receipt. Both approaches let the reviewer understand what is new.
If you do not have the record, identify who does
Tell the insurer accurately whether the item has been requested, is being prepared, is unavailable to you or appears not to exist. Those situations need different next steps. Do not turn “I cannot locate it” into “the provider lost it,” or create a document to fill the gap.
Confirm what the holder can supply. An employer's payroll team may maintain earnings records while a supervisor confirms scheduled shifts. A hospital may release visit notes through one office and images through another. Record the actual contact and request reference rather than assuming one request covers every source.
- For existing treatment documents, use the medical-record access guide to identify holders, visits and requested categories. Your own-copy request and an insurer's request are not automatically the same process.
- For earnings, use the lost-wage record guide to distinguish payroll, time records, paid leave and employer explanations.
- For a police report, use the crash-report retrieval guide to locate the correct agency and report type. An incident number is not the completed report.
If a holder gives an estimated release date, label it as that holder's estimate. Send the insurer the current status and ask whether a specifically identified interim record would help. Do not promise the unavailable report will arrive on a date you cannot control.
If a requested document does not exist, explain what does exist and ask what alternative the insurer will consider. Acceptance of a substitute should be confirmed; a homemade summary should not be presented as an employer's record, clinical opinion or official agency report.

Send a packet the recipient can check
Use the insurer's confirmed submission process. Before sending sensitive records through a new link, verify it independently. The FTC's phishing guidance recommends contacting a company through a phone number or website you already know is genuine instead of trusting the contact details in a suspicious message.
Keep the cover message short: identify the claim, list the numbered request items, name each attachment and state which pages or dates address it. Preserve originals. If you highlight a working copy, label it and retain the unmodified source separately.
Check file size, format and access requirements with the recipient. If a permitted upload must be split into parts, number the parts and say how many to expect. Save the receipt for each part. A password-protected file may be unreadable to the team unless an agreed secure access method is supplied.
Do not send an entire unrelated record archive merely because it is convenient. If the scope of a sensitive request is unclear, ask about its purpose, period and delivery method promptly. Clarifying scope is different from ignoring the request or assuming no cooperation is required.
The NAIC's auto-claim guidance recommends cooperating with the investigation, keeping conversation notes and asking for written explanations. Retain your request, response and receipts together so you can show the sequence without reconstructing it from memory.
An itemized response you can adapt
Use this as a writing aid, not an official form, sworn proof of loss or substitute for required documents. Complete it privately; this article does not collect your claim or medical files.
Subject: Claim [number] — response to document request dated [date]
Hello [claims contact],
I am following up on your request concerning [specific claim component]. Here is the status of each requested item:
- [Item, issuer and period/version]: [filename] was sent through [route] on [date], with receipt [reference]. Please confirm whether the file is present, readable and responsive to the request. If not, please identify the exact missing page, field, period or other issue.
- [Second item]: I requested this from [holder] on [date]. The holder's current response is [accurate status]. Please confirm whether [identified existing alternative] would be useful while that request remains open.
- [Repeated or unclear item]: Your latest message appears to request [description]. Does this repeat the item submitted on [date], seek a newer version or concern a different period? Please clarify what remains needed.
Please identify any other outstanding items for this claim component, who is expected to provide them and the accepted secure delivery method. Which submitted items have been reviewed, and what question remains after that review?
Please confirm the next step, the person or team responsible and when I should check back. If you have already made a decision on an item, please distinguish that decision from the remaining document request.
Thank you,
[name and appropriate contact information]
Delete questions that the insurer has already answered. A focused message should reduce uncertainty, not require the adjuster to restate the entire file. Keep any agreed follow-up date in the ledger; a requested reply date is not automatically a legal deadline.
Example: three requests with three different gaps
Fictional recordkeeping example: Following an October 8, 2026 crash, Jordan receives a request for an employer attendance letter, payroll records covering October 1–15 and a completed police collision report. This example illustrates document handling, not coverage, fault or a settlement result.
Jordan sends two files on October 20 and keeps the portal receipt. On October 22, the insurer repeats the request. A comparison reveals that “both files uploaded” and “all three requests answered” are different statements.
| Requested item | What the record shows | Next action |
|---|---|---|
| Employer attendance letter | Correct letter sent; the claims contact confirms receipt and readability. Review has not been confirmed. | Ask whether it was reviewed and what, if anything, remains unresolved. |
| October 1–15 payroll records | Attachment covers October 1–7 only. The later pay period is missing. | Request the identified later period from payroll, then send it as an additional file. |
| Completed collision report | Jordan has only an exchange slip. The agency says the report is not yet available. | Save that response, follow the agency's retrieval process and ask the insurer about interim information. |
Jordan's reply refers to the October 20 receipt but does not claim it proves completeness. It asks the reviewer to confirm the letter's status, explains the missing payroll period and identifies the report's actual availability. Each item has a different owner and next step.
When the later payroll file arrives, Jordan adds its receipt instead of replacing the first submission date. If the reviewer later needs an explanation of paid leave, that becomes a new question linked to the payroll item. It is not silently marked resolved merely because the file opened.
If the insurer ultimately refuses a particular claimed expense, Jordan saves that decision and its stated reason. A document ledger can clarify what was submitted and considered; it cannot decide whether the refusal was justified or guarantee a payment.

When the same request keeps returning
Compare the two requests word for word before escalating. Is the issuer, period or version different? Did the first response omit a signature or page? Did a link expire? Has the insurer identified a new question arising from the earlier records? Ask which explanation applies rather than assuming intentional delay.
If the request is genuinely unchanged, send the earlier receipt and filename with a narrow question: “Please confirm whether this document is in the claim file and identify any remaining defect.” If the team cannot locate it, arrange one clearly labeled resend through a verified route and preserve both receipts.
After an adjuster change, provide a short open-item list and refer to the existing submissions. Ask whether the new reviewer can access them. Avoid sending fresh copies to several unverified addresses; that can make the history harder to follow and spread sensitive information unnecessarily.
A one-page chronology helps if the issue remains unresolved: request date, response date, receipt, stated gap and latest follow-up. Attach only the supporting messages needed to demonstrate that sequence. Separate what the company said from your interpretation of it.
Choose your next call by the blockage—not the portal label
“Pending” describes very little on its own. Use the evidence in your ledger to choose a useful contact and a specific request. Keep any actual response or filing deadline on your calendar while you work through the blockage.
- You do not have the record: Contact its holder. Ask whether it exists, what request process applies and whether anything is needed from you.
- You sent it, but receipt is unclear: Contact the receiving claim team with the filename, date and receipt. Confirm the destination before sending sensitive information again.
- The file arrived but cannot be used: Ask for the precise defect—wrong period, unreadable page, missing signature or another identified issue. Fix that issue rather than rebuilding the entire packet.
- The file was reviewed but the issue remains: Ask what question the record did not answer and what would address it. Keep the answer with the reviewed document.
- The company refused the item: Request the actual decision and its stated basis. Use the written-decision worksheet instead of treating the matter as a missing-upload problem.
Fictional example: A clinic confirms it sent a note to a records vendor. The adjuster says the note is absent from the claim file. Neither answer tells you whether the vendor completed delivery to the insurer. Your follow-up identifies the authorized receiving route and asks the responsible party to confirm that specific transfer. You keep the clinic's receipt and the insurer's answer rather than deciding either proves the whole chain.
When several parties are involved, name the next owner in the ledger. “Waiting on documents” becomes “records service checking delivery to the confirmed claims destination; follow up on the date supplied.” This does not promise approval. It gives you a concrete task and a record if the same problem returns.
Why the claim type and state still matter
An organized packet does not start every legal clock or eliminate other claim requirements. Keep any actual policy, claim or legal deadline separate from your document follow-up dates. Seek qualified advice promptly when a deadline or formal notice is involved rather than waiting for every record to arrive.
Texas: additional requests and first-party scope
Texas Insurance Code Chapter 542, Subchapter B defines the first-party claims it covers. Section 542.055 addresses initial information requests and allows necessary additional requests during the investigation. Section 542.056 connects its acceptance-or-rejection notice process to receipt of the required information, with qualifications. A later request therefore is not automatically improper, and a generic upload receipt does not by itself establish when the applicable requirements were met.
The TDI process guide expressly says its listed deadlines do not apply when another driver's insurer is paying. Its other-driver claims guidance also explains that the claimant lacks the same contractual relationship with that company. This article does not calculate a Texas deadline or transfer a first-party rule to a third-party claim.
Washington: identify what the investigation is waiting for
The version of WAC 284-30-370 effective October 18, 2026 addresses written explanations when an investigation needs more time. Its subsequent notices include pertinent outstanding items and, when an adjuster has changed since the last notice, confirmation of the new adjuster's review and readiness to continue. The section excludes medical professional liability claims.
That wording was checked against the permanent adoption notice. It supports asking a specific question about what remains outstanding. It does not supply a nationwide deadline, establish retroactive application to an earlier claim or mean every pending investigation must already be paid.
Choose the next step from the remaining gap
If the record is missing, follow up with its holder. If delivery failed, confirm a workable route. If the record is usable but review is unconfirmed, ask the claims contact about that stage. If review produced a refusal, obtain the decision and its explanation instead of continuing to treat it as an upload problem.
For an unresolved handling concern, ask the insurer's appropriate supervisor or complaint contact to address the documented gap. Your state's insurance department can explain its complaint process and limits. For example, TDI's auto complaint page describes supporting-document submissions but also says it cannot decide accident fault or require payment absent a violation of law or policy terms. A complaint is not a guaranteed claim approval.
If your injury claim remains stalled, bring the requests, receipts and remaining questions to a review rather than trying to make an ambiguous status sound like an approval or denial. A consultation can start with what is known, what is disputed and any deadline you have been given. See your free injury case-review options. Continue meeting applicable claim requirements while seeking advice.
Your next step
Still waiting for an answer on an injury claim?
You can ask about your options with an unfinished file. Bring the requests, what you supplied and any deadline or decision to a free case review.
Explore My Free Injury Case Review →Free initial review through an independent provider. No obligation to hire.Sources and scope
Core sources checked October 26, 2026; editorial update October 31, 2026. State examples apply only to the named jurisdiction. This guide is editorially researched; it has not been reviewed by an attorney and does not assess your individual claim.
- Texas Department of Insurance: Steps to Getting Your Home or Car Insurance Claim Paid
- NAIC: What You Should Know About Filing an Auto Claim
- FTC: How to Recognize and Avoid Phishing Scams
- Texas Insurance Code Chapter 542: Processing and Settlement of Claims
- Texas Department of Insurance: How to Deal With the Other Driver's Insurance
- Washington WAC 284-30-370: Standards for Prompt Investigation of a Claim
- Washington State Register 26-17-089: Permanent Claims-Handling Rules
- Texas Department of Insurance: Get Help With an Auto Insurance Complaint
Spot an error? Contact support@injurylawadvisor.us with the page and source. Please do not email medical records or sensitive case details.



