Insurance Claim Communication Log: What to Record After Every Call and Email
A practical system for converting calls, emails, letters, portal messages, document requests, and promised follow-up into one chronological claim history.
1. The log is an index, not a transcript
The goal is not to recreate every word. It is to preserve the material event and connect it to the supporting record. A concise entry such as “adjuster requested the mitigation invoice by Sept. 8; sent through portal as DOC-017” is more useful than several paragraphs that never identify the request, owner, deadline, or file.
The California Department of Insurance advises consumers in its residential property claims guide to keep a log of calls and correspondence and retain copies sent to or received from the insurer. The same organizational principle is useful nationwide, while specific rights, deadlines, and communication rules remain state- and policy-dependent.
2. Record seven fields after every material contact
Use names and roles exactly as provided. If the person cannot provide a surname or direct number, record the available identifier and department. Distinguish what was said from what you inferred. Use quotation marks only for words you are confident are exact; otherwise summarize neutrally.
| Instead of | Write |
|---|---|
| Called insurance. They will handle it. | Sept. 2, 10:20 a.m. · Jordan, property claims intake · claim opened; confirmation expected by email today. |
| Adjuster approved repairs. | Adjuster said emergency extraction may proceed; no statement made about permanent cabinet replacement. Written confirmation requested. |
| Sent everything. | Portal batch 03 sent: mitigation invoice, 18 photographs, and room inventory; receipt ID P-8472 saved. |
3. Confirm decisions and requests with a short written follow-up
A follow-up message should identify the claim, date of conversation, your understanding of the material points, documents attached or requested, the next action, and the date expected. It should be factual and easy to correct.
Subject: Claim [reference] — follow-up to September 2 call
Thank you for speaking with me today. My understanding is that: (1) the inspection remains scheduled for September 5; (2) you requested the mitigation invoice and room photographs; and (3) you expect to confirm receipt after upload. I uploaded those items as portal batch 03 and saved the receipt. Please let me know if this summary is incomplete or inaccurate and whether any additional material is needed.
Do not use a follow-up email to introduce assumptions as agreed facts. If the call was unclear, say so and ask a precise question. Save the sent message in its final form, including attachments, and record any automatic or portal confirmation.
4. Build a document chain for every request
Each document request has at least four events: the request, your preparation, delivery, and the recipient’s response. Track all four. A file sitting in “Sent” does not necessarily show which version was delivered, which attachments were included, or whether the portal accepted them.
| Event | Record | Evidence |
|---|---|---|
| Requested | Who requested what and when | Call note, email, letter, or portal message |
| Prepared | Exact filename and version | Frozen copy in the claim folder |
| Delivered | Channel, date, batch, and recipient | Sent email, tracking, or portal receipt |
| Reviewed | Received, accepted, questioned, or replaced | Written response and next action |
If a corrected version is sent, do not silently overwrite the old file. Preserve both, identify the replacement, and explain what changed. This prevents an old estimate, inventory, or spreadsheet from being mistaken for the current submission.
Protect the communication archive as you would other sensitive claim material. Keep an independent backup, limit unnecessary personal data in filenames, and do not forward a long email chain without checking what private information or unrelated attachments it contains. The Home Claim Ledger workspace stores its log locally, but linked emails and documents remain the user’s responsibility.
5. Maintain an unanswered-question queue
Long claims generate questions faster than they generate answers. Keep each question separate and actionable. “What is happening with my claim?” is difficult to resolve. “Has portal batch 03 been assigned for review, and what is the expected response date?” identifies the record and desired answer.
- Write one question per line. Avoid hiding four issues in one paragraph.
- Connect the question to a document or event. Add the estimate version, payment explanation, inspection date, or request ID.
- Assign the next action. Waiting is a status; it should still have a review date.
- Close the loop. Record the answer, source, date, and any new action.
6. Example of a complete communication record
Spoke with A. Rivera, desk adjuster. Subject: mitigation invoice. Rivera said pages 4–5 were not visible in portal batch 03 and asked for a replacement PDF. No decision on the invoice was made. Action: homeowner to upload readable PDF by Sept. 7; Rivera to confirm receipt within one business day. Files: CALL-012 note; MIT-INV-v2.pdf; portal receipt pending.This entry separates the technical file problem from a coverage decision, identifies both owners, and makes the next review point visible. If confirmation does not arrive, the action list already explains what to follow up on.
Questions about maintaining a claim communication log
Should every routine contact be logged?
Log contacts that change the file or help explain it: new requests, decisions, inspection arrangements, submissions, payment explanations, deadlines, disputed facts, promised follow-up, and unsuccessful attempts that become relevant. A one-line entry is enough for a routine status check. Avoid turning the log into a transcript of greetings and repeated background.
What if a phone summary is disputed?
Preserve both records. Do not silently rewrite the original note. Add the correction or disagreement, its source, and date. If your own note was inaccurate, label the correction clearly. The aim is an honest chronology, not a document that always makes the homeowner appear correct.
What if the portal has no export function?
Save available confirmations, message text, attachment lists, receipt numbers, dates, and screenshots that show the transaction without exposing unnecessary personal data. Keep the exact files uploaded in a frozen submission folder. A portal screenshot alone may not preserve the attachment contents, while the folder alone may not prove delivery; keep both sides of the chain.
How should unanswered calls be recorded?
Record the date, time, number or department, purpose, voicemail left, callback information, and next review date. Grouping several unsuccessful contacts into a clear timeline is more useful than repeatedly writing “no answer.” Follow the insurer’s escalation and formal complaint channels when appropriate and use the state regulator’s official resources for applicable help.
Is an email enough for a formal notice or proof of loss?
Not necessarily. A communication log does not change the channel, form, signature, content, or deadline required by a policy, insurer, or law. Use the specified method for formal notices and preserve confirmation. The log should point to the completed formal record rather than substitute for it.
Sources and limits
- California Department of Insurance: Residential Property Claims Guide — log calls and correspondence and retain copies.
- NAIC: Navigating the Claims Process — general claim documentation and reporting context.
- NAIC directory of state insurance departments — locate official state help and complaint information.
This organizational method does not establish legal notice, satisfy a proof-of-loss requirement, extend a deadline, or replace an insurer’s required channel or form. Confirm formal requirements and time limits with the policy, insurer, and applicable state authority.