Skip to content
HomeFree Tools › Tool

Claim Timeline Tracker

A dated log is what turns a series of phone calls into a record.

Free · Saved in your browser · Nothing uploaded · By Miguel Contreras, based in Colombia

Every guide on this site that touches a disputed claim says the same thing: keep a dated log. It is the single most useful thing a policyholder can do, and it is the thing almost nobody does, because in the moment it feels like bureaucracy.

This makes it a two-minute habit instead.

Nothing is uploaded. The log stays in your own browser. Export it before you need it — if the matter reaches an appeal, a regulator, or a lawyer, the record of what was said and when is what the discussion turns on.

What makes a log useful

  • Facts, not adjectives. "Called 11 March, left message, no response by 18 March" is checkable. "They ignored me" is not.
  • Names and roles. Ask who you are speaking to and write it down.
  • What was promised, and by when. Promised callbacks that did not happen are among the most useful entries.
  • What you submitted and when. Most regulatory deadlines run from the point the insurer has what it needs, so the date you sent each item matters.

Follow up in writing

After a phone call, send a short email summarising what was said and inviting correction. That converts a conversation into a document, and it takes two minutes.

Log the email too. The pair — call plus written summary — is considerably stronger than either alone.

Where this ends up being used

An internal appeal, a complaint to your state Department of Insurance, an appraisal or arbitration, or a lawyer's file. All four are built on the same material, and all four are easier if it already exists.

Why a dated log changes outcomes

Every guide on this site that touches a disputed claim says the same thing: keep a dated record. It is the single most useful thing a policyholder can do, and almost nobody does it, because in the moment it feels like bureaucracy.

The reason it matters is that the disputes which actually get resolved are the ones that turn on checkable facts. A regulator can verify that you called on three dates and received no written response until the sixth week. Nobody can verify that an insurer was unreasonable.

WeakCheckable
“They ignored me for weeks”“Called 11 March, left message. Called 18 March, ref 44821. No response by 26 March”
“They kept losing my documents”“Plumber’s report emailed 4 March, delivery confirmed. Requested again 19 March”
“The adjuster barely looked”“Inspection 19 March, approximately 20 minutes, crawl space not entered”
“They promised to call back”“J. Rivera undertook on 11 March to respond by 15 March. No contact received”

What to record, and what to leave out

Record

  • Facts, not adjectives. What was asked, what was promised, what date was given
  • Names and roles. Ask who you are speaking to and write it down
  • Reference numbers for every call
  • What you submitted and when, with proof of delivery
  • What was promised and by when — unfulfilled callbacks are among the most useful entries
  • Inspections: who attended, how long, what was examined and what was not

Leave the frustration out of the log. It is entirely legitimate to feel it, and it belongs somewhere private. The log is the document you may one day hand to a regulator, an appraiser, or a lawyer, and its value lies in being checkable.

Follow every call with an email

After a phone call, send a short message summarising what was said and inviting correction. Two minutes, and it converts a conversation into a document.

Then log the email as its own entry. The pair — call plus written summary — is considerably stronger than either alone, because it gives the insurer the opportunity to disagree in writing and creates a record whether they do or not.

Export the log and keep it outside the property. It is saved in your browser and never uploaded, which means it lives only on this device. If the claim concerns damage to your home, the device may be in the affected building.

The deadlines to record alongside it

The log tracks what happened. A separate short list should track what must happen, because these run simultaneously and come from different places.

  • Set by your policy

    Notice of loss

    Prompt reporting. Delay invites the argument that the investigation was prejudiced.

  • Often 60 days from request

    Proof of loss

    A sworn statement of what was lost and its value. Missing it can be treated as breaching a policy condition.

  • Set by the policy or plan

    Internal appeal window

    File inside it even if evidence is still coming, stating that supplemental material will follow.

  • Set by state regulation

    The insurer’s response deadlines

    Acknowledgement, decision, and payment. These generally run from when the insurer has complete information — which is why your submission dates matter.

  • Frequently from the date of loss

    Suit limitation

    The hard outer boundary, frequently shorter than the state’s general statute of limitations. It does not pause while you appeal or while a regulator reviews a complaint.

Write the suit limitation date at the top of your claim folder in larger letters than anything else. Of all the dates involved, it is the only one that closes a door permanently, and the only one nobody will remind you of.

Where the log gets used

RouteWhat it draws from the log
Internal appealEvidence of what was submitted and when, and of gaps in the investigation
Regulator complaintThe chronology, which is exactly what an analyst assesses against the claim handling rules
AppraisalThe record of estimates exchanged and positions taken
An attorneyA contemporaneous account, which carries more weight than one reconstructed later

All four are built from the same material, and all four are easier if it already exists.

The habit that makes it work

Add an entry the same day, every time. A log written contemporaneously carries weight that one assembled months later does not, and the difference is visible to anyone reading it.

Two minutes after each contact is the whole discipline. By the time you need the record, building it is no longer possible.

What we are not saying

Nothing you enter is uploaded or sent anywhere. The log lives in your own browser and the CSV export goes straight to your device. ClaimWise does not sell services, take referrals, or receive anything from any insurer, adjuster or law firm.

What a well-kept log looks like in practice

A short worked example, showing the level of detail that makes entries useful without making them a burden.

DateTypeEntry
4 MarchPhone callReported loss. Spoke to intake, ref 44712. Claim number issued. Told an adjuster would contact within 3 working days.
4 MarchEmail sentConfirmed the report in writing with photographs attached. Delivery receipt saved.
11 MarchPhone callNo adjuster contact received. Called, ref 45008. Told the file was assigned to J. Rivera and he would call by 15 March.
19 MarchInspectionJ. Rivera attended approx 20 minutes. Examined kitchen and hallway. Did not enter the crawl space. Took photographs. Said a decision would follow within two weeks.
19 MarchEmail sentSummarised the visit and asked for correction if anything was recorded differently. No reply received.
14 AprilLetter receivedDenial citing the wear and tear exclusion. Requested the claim file in writing the same day.

Six entries, none taking more than two minutes to write. Together they establish the timeline, the names, what was promised, what was inspected and what was not, and that written summaries went unanswered — which is precisely the material an appeal or a regulator complaint is built from.

One thing to do before you close this page

If a claim is already open, add today’s entry now and set a reminder to add one after every contact from here on. If you are reading this before anything has happened, the useful thing is simply knowing the tool is here.

The log cannot be built retrospectively. That is the entire argument for starting it on the day the claim opens rather than on the day it goes wrong.

What to do at the same time as starting the log

Five things, once

  • Find your suit limitation clause and write the date at the top of your claim folder
  • Photograph everything before any repair or cleanup, including the failure point itself
  • Keep any failed component — a cut-out section of pipe is the most informative evidence in a water claim, and tradespeople discard it as routine
  • Save the policy and declarations page somewhere outside the property
  • Note what the insurer asks for, and the date you supply each item

That last line connects directly to the log. Most regulatory deadlines run from the point the insurer has complete information, so the date you submitted each document is frequently the pivotal fact in any argument about delay.

If the claim resolves without difficulty

Most do, and the log costs almost nothing in that case — a handful of two-minute entries that turned out not to be needed.

That asymmetry is the argument for keeping one. The cost of an unnecessary log is a few minutes. The cost of a missing log, when a claim is denied and the question turns on what was said and when, is that the answer no longer exists.

Exporting and keeping it

When to export

  • As soon as the claim shows signs of becoming difficult
  • Before filing an internal appeal, so the chronology is attached
  • Before filing a complaint with your Department of Insurance
  • Before any meeting with an attorney or a public adjuster
  • Periodically regardless, since the log lives only in this browser

The CSV opens in any spreadsheet, which makes it straightforward to attach to a complaint or hand to a professional. It is also plain text, so it stays readable indefinitely.

Store it with your claim file — the policy, the declarations page, the denial letter, your photographs — in one folder outside the property. Everything that matters in a disputed claim is in that folder, and building it as you go is far easier than assembling it under pressure later.

One thing to do before you close this page

If you have an open claim, add every contact you can remember so far — dates, names, what was said — even if some of it is approximate. Note where you are unsure rather than guessing at a date.

An incomplete log started today is worth considerably more than a perfect one started after the denial arrives. From here on, add an entry the same day as every call, email and inspection, and export it whenever the claim looks like it may become difficult.

Two minutes after each contact is the whole discipline this tool is asking for. By the time you need the record, building it is no longer possible — and that is the only reason it is worth doing while everything still seems to be going fine.

Set a note on your phone to remind you after each call for the first few weeks. After that it becomes automatic, and the log builds itself as the claim progresses rather than needing to be reconstructed from memory when something goes wrong.

The first few weeks are when the habit is hardest and when the entries matter most, because that is the period a delay argument would later turn on.

After that, the entries become shorter and the habit costs almost nothing.

This is general education, not advice. Insurance law and claim rules vary by state and change over time. Nothing here is legal, financial, or insurance advice for your situation, and reading it does not create any professional relationship. For your specific case, consult a licensed professional in your state or contact your state Department of Insurance.