The Runaround

The Runaround: Building a Clear Insurance Communication Record

Claim Wars is a fictional dramatization, and this short scene compresses facts a real claim would require. It treats Tom Briggs as the other driver’s liability adjuster. A communication log can clarify what happened, but a repeated request alone does not prove misconduct.

Create one claim timeline

Use one log for dates, participants, claim numbers, requests, submissions, delivery methods, and responses. Keep delivery confirmations, email threads, upload receipts, and copies of what you sent. Note the exact file name or document description so a later request can be matched to the earlier submission.

Preserve originals and store medical, financial, and identifying information securely. A useful log shows what occurred without adding conclusions that the records do not support.

Clarify a repeated request in writing

Ask the adjuster to identify the missing item. Ask whether the prior submission was incomplete, unreadable, misrouted, or sent through an unapproved method. Then confirm the approved delivery method and whether the insurer can locate the earlier transmission.

Do not keep sending sensitive records through insecure channels. A brief written follow-up can identify the request, date sent, delivery confirmation, and the specific point that still needs an answer.

A paper trail documents events; it does not prove misconduct

A repeated request can result from routing, format, authorization, or completeness problems. The timeline helps determine which explanation fits. A.R.S. 20-461(A)(13) addresses delay caused by requiring preliminary and later proof-of-loss submissions containing substantially the same information when the conduct occurs frequently enough to indicate a general business practice. Subsection D makes the statute an administrative remedy and says it creates no private cause of action.

Arizona Administrative Code R20-6-801 also requires insurer claim files to document events in enough detail to reconstruct them. Those rules provide context after the insurer, coverage, claim posture, and facts are known. One repeated request or slow response does not by itself establish bad faith or a violation.

Questions this episode raises

What should an insurance communication log include?

Record dates, names, insurer, claim number, what was requested, what was sent, the delivery method, confirmation details, and each response. Keep copies with the log.

What should I do if an adjuster asks for the same document again?

Ask in writing what is missing and whether the earlier copy was incomplete, unreadable, or misrouted. Confirm a secure delivery method before sending private information again.