Write Claim Activity Notes That Point to Evidence

Decide what the note is for

A claim activity note records what happened, when it happened, what source supports it, and what happens next. It is not a place for speculation about the insured's motives or a summary of the adjuster's coverage theory. A good note lets another person pick up the file without calling the author.

Before writing, identify the event: a call, an email, a document receipt, a payment, a site visit, or a system change. The event type determines the fields. A call note needs the caller, the number, the topic, and the outcome. A document note needs the document name, source, date, and page count.

Use four fields and keep them separate

The fields are observation, source, action, and next step. Observation states what was said or received. Source names the record: the call log, the email, the portal upload, the inspection report. Action states what the assistant did. Next step names the owner and the date.

Example: observation says the insured reported that mitigation began on June 14. Source says the recorded call at 10:22 a.m. Action says the statement was added to the loss facts and the mitigation invoice was requested. Next step says the document clerk will request the invoice by June 20. None of those fields claims the mitigation was adequate or covered.

Separate fact from inference in the wording

Write what the record shows, not what it suggests. The insured was upset is an inference; the insured said this was the third call this week is an observation. The contractor was late is an inference; the contractor arrived at 3:40 p.m. for a 1:00 p.m. appointment is an observation.

When a conclusion is necessary, label it as a question or a concern and attach the evidence. A note that says the damage looks pre-existing invites a dispute the file cannot support. A note that says the 2019 inspection photo shows the same stain and asks the adjuster to compare dates preserves the issue without deciding it.

Use the specialist service role as a starting point for scope, source evidence, and decision boundaries.

Use time, source, and version discipline

Record the time zone when a call or message time matters. Use the system timestamp for documents received through a portal, and the sender's stated date for material received by email. If a document is replaced, keep the original and note the version that superseded it.

Do not backdate a note to match the event if the note is written later. Write the current date and say when the event occurred. A note written on the 27th about a call on the 24th should say so. Backdating destroys the audit trail even when the content is accurate.

Review notes as a sample, not a scoreboard

Sample notes across event types and owners. Check whether the source is identifiable, the next step has an owner and date, and inference is labeled. Look for notes that repeat the same sentence with no new information. Those notes add length without adding evidence.

Feed the findings into a short note template and an example library drawn from the team's own files. Do not publish a template that encourages staff to write more rather than to write down the source. The measure is whether a reviewer can reconstruct the event, not the word count.

The public guidance from United States Government Accountability Office can help the accountable team test assumptions without replacing local professional review.