gg
Home › Data & databases › Claim Evidence & Correspondence Index
Data & databases

Claim Evidence & Correspondence Index

A claim turns on what you can prove you sent and when. Every photograph, receipt, estimate, report, letter and phone call, with the date it went to the insurer and the reference it went under. The most valuable column is the least obvious one - sent on - because a claimant who can say 'the roofer's estimate went on the 4th, reference 88231' is in a different conversation from one who thinks she probably did. It also counts replies the insurer promised by a date and has not sent.

Your database

Fields

FieldType
Date of the item or eventdate
What it isselect
Descriptiontext
What it shows / what was saidtext
Who it was withtext
Sent to the insurer ondate
Their reference for ittext
Where the original istext
Reply expected by (if they gave you a date)date
Notestext

Frequently asked

Where is this stored?

Only on this device, in your browser. Nothing is uploaded and there is no account. Export to CSV or JSON to back it up, hand it to an auditor, or move it to another machine.

Does it know my deadlines and required frequencies?

No, and that is deliberate. Inspection intervals, retention periods and review cadences are set by your standard, your jurisdiction, your certifier or your own procedure, and they change. This runs offline and cannot know if one changed last month, so it never asserts one. You enter the dates that apply to you and it does the arithmetic on those.

Does it know how long my insurer has to respond?

No. Response times are in your policy and your regulator's rules, they differ by insurer and product, and they change. If the insurer gave you a date, enter it and this counts to it - a missed date they set is worth far more in a complaint than one you assumed.