Incident & Contact Chronology
An advocate, a solicitor or a court will ask for a chronology: every date, what happened, what was said, whether police came. One row per incident, in your own words, with the date - and a count of what is missing from the record, such as an entry nobody can place in the sequence because it has no date. It assesses nothing. It does not score severity, say whether any legal threshold is met, or predict an outcome, because those differ by jurisdiction and belong to people qualified to judge them. Everything stays on this device; export or print it to hand over.
Your database
Fields
| Field | Type |
|---|---|
| Date | date |
| Time (roughly is fine) | text |
| What happened, in your own words | text |
| What was said | text |
| Where | text |
| Who was involved | text |
| Anyone who saw or heard it | text |
| Police | select |
| Incident / reference number | text |
| Effect on you (injury, damage, time off, cost) | text |
| Evidence kept (photos, messages, medical notes) | text |
| Where that evidence is | text |
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.
Will it tell me whether I have a strong enough case?
No, and it would be wrong to try. What any order or complaint requires differs by jurisdiction and turns on facts a tool cannot weigh. What it does is make sure that when somebody qualified does look, there is a dated record to look at rather than a memory.