Pebble Chronology
In beta · available for controlled testing
Case notes and records become a dated timeline you can review and export, with filenames and source references still attached to every event.
The practice problem
A chronology is one of the most useful documents in a case and one of the least likely to be up to date. Building one by hand means reading a bundle end to end and retyping dates into a table.
Pebble Chronology reads the bundle and produces a dated timeline you review, correct and export, with every event still pointing back to the record it came from.
Evidence stays attached
Every event keeps its filename and source reference, so anything in the chronology can be checked against the record it came from. You review the timeline and decide what it means. Pebble does the reading and the ordering, not the analysis.
Creating a chronology
Case notes, assessments and supporting documents go in together. Pebble reads the bundle and builds the timeline; you review it before anything is exported.
Guidance from your own organisation can be applied; Pebble's defaults are used otherwise.
Building on existing work
Upload a current chronology alongside new records. Additions are proposed and reviewed separately, so the work already done is preserved rather than regenerated.
Duplicates are flagged for your attention rather than silently merged.
Filenames and source references remain on every event, so anything can be checked back to its record.
An uncertain date is recorded as uncertain, rather than tidied into false precision.
Anything Pebble cannot read is listed by name, so you know what was left out instead of guessing.
If material looks like it belongs to another child or family, you are told. It is never quietly merged.
Social work first. Everything else supports it.
Chronology is in beta and available for controlled testing. Get in touch to see it working on the kind of bundle your service actually deals with.
See Pebble in practice
