Claims Pages
claimspages

The File Note Will Be Read Aloud

How to Write Claim Notes That Hold Up When a Regulator, a Judge, or a Plaintiff's Attorney Reads Them Back to You

Claim notes are written for the next person on the file and read, years later, by people looking for a reason the claim went wrong. This article rewrites six common note habits into entries that record facts, dates, and reasons in plain language.

— An attorney deposing an adjuster rarely needs clever questions when the file notes are bad. She puts the note on the screen, reads it slowly, and asks the adjuster what it means. "Insured seems to be padding contents" takes four seconds to type on a Friday afternoon. Explaining it under oath, two years later, to a room that includes a court reporter and the insured, takes much longer.

Most adjusters write notes for one reader, the next person who opens the file. That reader knows the abbreviations, knows the carrier's workflow, and wants the short version. The people who read the file after a lawsuit is filed know none of that. They read every entry in order, they notice gaps, and they assume that anything left out was left out on purpose.

Who reads the file after you

Three kinds of readers end up with a claim file in front of them, and each one reads it for a different reason.

The first is the regulator. State claims-handling rules generally require a file complete enough that someone else can rebuild what happened. California's version is unusually direct. Its file and record documentation regulation, 10 CCR § 2695.3, requires claim files to contain all notes and work papers "in such detail that pertinent events and the dates of the events can be reconstructed and the licensee's actions pertaining to the claim can be determined." A market conduct examiner pulls a sample of files and reads them against that standard. Many states built their rules on the NAIC Unfair Claims Settlement Practices Act, which lists refusing to pay "without conducting a reasonable investigation" and failing to give "a reasonable and accurate explanation" for a denial among its unfair practices. A file that never records the investigation or the explanation looks like a file where neither happened.

The second is the court. Claim notes are business records, and business records can come into evidence. Federal Rule of Evidence 803(6) admits a record made "at or near the time" by someone with knowledge, kept in the course of a regularly conducted activity, when making that record was a regular practice. Most state evidence codes have a similar rule. The jury sees the note as written, typos and shorthand included.

The third is opposing counsel, who will ask for everything. The federal discovery rule on document requests, Federal Rule of Civil Procedure 34, reaches electronically stored information including "data or data compilations," which covers the claim system's notes, the timestamps on them, and in many cases the audit trail of edits. Adjusters sometimes assume their notes are protected because a lawsuit was always possible. Federal Rule of Civil Procedure 26(b)(3) protects documents prepared "in anticipation of litigation or for trial," and a note written to adjust a claim in the ordinary course is a weak candidate for that protection. The safer working assumption is that every note will be produced.

Six notes, rewritten

Every note below is an invented example, built from habits that show up in real files. Each "before" is the kind of entry adjusters write when they are busy. Each "after" takes about thirty seconds longer.

1. The opinion

Before:

Insd seems to be padding contents. Will scrutinize.

After:

4/14. Received contents inventory, 212 line items. Inventory lists three laptops purchased in 2025. Insured provided a receipt for one (Best Buy, 3/2025). Sent letter today requesting purchase records or bank statements for the other two by 5/1. Letter saved as doc 14.

The first version records a conclusion and a mood. The second records what the adjuster saw, what was missing, and what the adjuster did about it. If the other two laptops turn out to be real, the second note shows a reasonable request. If they turn out to be invented, it shows exactly when the question was first raised. In both cases the adjuster can testify to every word of it without explaining what "seems" meant.

Suspicion belongs in the file only as facts and actions. If the facts support a referral to the special investigations unit, make the referral through the carrier's process and note that it was made. Leave adjectives about the insured's honesty out of the note entirely.

2. The phone call that left no trace

Before:

Spoke w/ insd re: roof.

After:

6/3, 2:40 p.m. Outbound call to insured, Maria Lopez, at the number on the policy. About 12 minutes. Explained that the field inspection found hail damage to the north and west slopes only. She said the contractor told her the full roof needs replacing. I explained the carrier will review any contractor estimate she sends and that she can ask for a reinspection. She said she would send the estimate this week. Diary set for 6/10.

A phone call that is not documented leaves two memories and no record. When those memories disagree in a deposition, the adjuster's account carries no more weight than the insured's, and sometimes less. California makes the rule explicit: under 10 CCR § 2695.7(l), an insurer may not deny a claim based on information from a phone call or interview unless the conversation is documented in the claim file. Even outside California, the habit protects the adjuster. Record who called whom, the date and time, roughly how long, what the adjuster explained, what the other person said, and what happens next.

3. The abbreviation stack

Before:

RCV/ACV disc w/ PH. PH ok. 2nd pmt iss. NFA pending recpts.

After:

Explained to the insured that the first payment was actual cash value and that the withheld depreciation, $8,410, will be paid when she sends the final invoice for the completed roof. She said she understood. Issued the second payment today for the interior estimate, $3,212. No further action until the roofing invoice arrives.

Every adjuster knows what RCV, ACV, and NFA mean. A juror does not, and a plaintiff's attorney will ask the adjuster to define each one, one at a time, on the record. "PH ok" is worse, because it records agreement without saying what was agreed to. Abbreviations are fine for policy forms, dollar amounts, and dates. Spell out anything that describes what a person said or understood.

4. The decision without a reason

Before:

Denied per mgr.

After:

Reviewed with claims manager J. Ortiz on 8/22. The water damage in the hall bath came from a slow leak at the shower valve, which the plumber's report (doc 9) says went on for months. Denial based on the policy's exclusion for constant or repeated seepage or leakage of water, quoted in full in the letter. Ortiz approved. Denial letter quoting the exclusion and explaining how the plumber's findings apply was mailed and emailed to the insured 8/23 (doc 11).

"Denied per mgr" invites three questions in a row: which manager, why, and did anyone tell the insured why. California's § 2695.7(b)(1) requires a written first-party denial to list every basis for the denial and to explain how the cited policy provision applies to the claim. The NAIC model act requires a reasonable explanation for denials and compromise offers. The note should match the letter: the facts relied on, the provision applied, who made the call, and when the insured was told.

A manager's approval does not move responsibility off the file handler. In a deposition, the adjuster will still be asked whether they agreed with the decision. The note should make it possible to answer yes and point to the reason.

5. The silent gap

Before: no entry at all between April 2 and May 19.

After:

4/2. Waiting on engineer's report on foundation cracks. Engineer's office says report expected by 4/30. Sent insured a status letter today explaining the delay and the expected date (doc 6). Diary 4/30.

4/30. Report not received. Called engineer's office, report now expected 5/15. Sent insured an updated status letter (doc 7). Diary 5/15.

Forty-seven days with no entry reads as forty-seven days of nothing, even when the adjuster was waiting on a report the whole time. Delay arguments are built from gaps like this one, because the file cannot show that anyone was working the claim. In California, § 2695.7(c)(1) requires written notice to the claimant when more time is needed, repeated every thirty calendar days until a decision is made. Other states set their own intervals. A short note at each diary date, even when the note says nothing new has arrived, closes the gap.

6. The note written later

Before, entered on 10/28:

Per conversation, insd agreed to the scope.

After, entered on 10/28:

Late entry for a call on 10/6 that I did not note at the time. Called insured about the revised scope. To the best of my recollection, she agreed to the revised scope for the kitchen but wanted to talk to her contractor about the cabinets. Sent a scope confirmation letter today asking her to confirm in writing (doc 18).

Late entries happen, and a late entry labeled as one is easy to explain. Claim systems timestamp every note, and opposing counsel will compare the note date to the event date. A note written three weeks after a call, phrased as if it were written that day, looks like it was written for the lawsuit. Label the entry as late, give the date of the event, say how sure you are, and confirm anything important in writing with the other person.

Never edit or delete an earlier note to fix it. Add a new note that corrects the old one and says why. Most claim systems keep an edit history, and a changed note found in an audit trail is much harder to explain than an honest correction.

What every note should be able to survive

A short note holds up fine if it answers the questions a stranger would ask when reading it out loud. Before saving, check that the note:

  • States the date of the event, and the time if a call or meeting is involved

  • Names the people involved by name and role, not by initials alone

  • Records facts the adjuster observed or was told, with the source of each

  • Gives a reason for every decision, tied to a policy provision, report, or document in the file

  • Says what the adjuster told the insured or claimant and how it was sent

  • Ends with the next step and the diary date

  • Leaves out opinions about anyone's honesty, intelligence, attitude, or lawyer

That last item covers more than the insured. Notes about the public adjuster being "difficult," the contractor being "a known storm chaser," or the attorney being "a jerk" all get read aloud too. If the conduct matters, describe the conduct: "Public adjuster declined two reinspection dates offered for 7/8 and 7/10" is a fact. "PA stonewalling" is a characterization the adjuster will have to defend.

Templates deserve a warning of their own. Many claim systems offer canned note text for common steps, and adjusters build their own. A template that says "Explained coverage and claim process to insured; insured verbalized understanding" can appear word for word on forty files in a week. Read in a deposition, it shows that the adjuster typed the same sentence forty times, and it says nothing about what this insured was told or what they understood. Use templates for structure, and fill them with the facts of the call.

The same standard applies to emails, text messages, and comments inside estimating software. Those are part of the file as well, and the third article in this series covers what happens to them once litigation is anticipated. For notes, the test is simple enough to apply on every entry: if the insured, a regulator, and a jury heard this note read back word for word, would it describe what happened, when, and why?

Sources

  1. Cornell Law School, Legal Information Institute. Cal. Code Regs. Tit. 10, § 2695.3. File and Record Documentation.

  2. National Association of Insurance Commissioners. Unfair Claims Settlement Practices Act (Model 900). 1997.

  3. Cornell Law School, Legal Information Institute. Federal Rules of Evidence, Rule 803. Exceptions to the Rule Against Hearsay.

  4. Cornell Law School, Legal Information Institute. Federal Rules of Civil Procedure, Rule 34. Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes.

  5. Cornell Law School, Legal Information Institute. Federal Rules of Civil Procedure, Rule 26. Duty to Disclose; General Provisions Governing Discovery.

  6. Cornell Law School, Legal Information Institute. Cal. Code Regs. Tit. 10, § 2695.7. Standards for Prompt, Fair and Equitable Settlements.