How to Build a Chronology from Scattered Records
Most people arrive at this with a box, a hard drive, or four years of email. Hundreds of documents, no order, and a date by which someone needs to understand what happened. A chronology is how that material becomes usable.
It is one of the most tedious pieces of work there is, and one of the most valuable, because nobody can reason about a situation they cannot see in order.
This is the method. It works whether you have forty documents or four thousand.
What a chronology is, and what it is not
A chronology is a dated list of events, each one tied to the document it came from.
It is not a summary. It is not a narrative. It is not an argument about what the events mean. The moment you start writing what you think happened rather than what the record shows, you have made something else — and something less useful, because it can no longer be checked.
A good chronology is boring to read and impossible to argue with. That is the point.
Build the index before you build the chronology
The instinct is to start reading document one and writing entries. Resist it. You will get four hundred documents in and discover that document twelve was the important one.
Index first. Every document gets a row: a number, a date, a type, who it came from, who it went to, and a one-line description of what it is. Nothing about what it says — just what it is.
This does two things. It tells you what you actually have before you invest weeks in reading it, and it gives every document a number you can point at later. The index is the spine. The chronology hangs off it.
Date everything, including the things that resist it
Some documents date themselves. Others do not — undated letters, photographs, notes, text messages exported without timestamps, scans of scans.
Give every document a date anyway, and record how certain that date is. A letter referring to "last Tuesday's meeting" can be placed. A photograph can sometimes be placed by what is in it. Where you are estimating, say so in the entry, and say what you estimated from.
An entry dated "approximately March 2023, based on reference in document 114" is honest and useful. An entry dated "March 2023" with no basis is a guess dressed up as a fact, and it will eventually be found out.
One event per row, not one document per row
This is where most homemade chronologies go wrong.
A single email can contain three events: a meeting that happened, a payment that was promised, and a decision that was made. Those are three entries, each on its own line, each pointing back to the same document.
Equally, six documents can describe one event. That is one entry citing six sources — not six entries saying nearly the same thing.
The chronology tracks what happened. The index tracks what you have. Keep them separate and neither one gets corrupted.
Cite the source on every single line
Every entry names the document it came from and, where the document is long, the page or paragraph.
This is not bureaucratic tidiness. It is what makes the document survive scrutiny. Anyone reading it — a lawyer, an adjuster, a board, a judge — will at some point want to know where a particular line came from. If the answer is "it's in there somewhere," the whole chronology loses its authority, including the parts that were right.
An uncited chronology is a rumour with dates on it.
Keep what happened separate from what it means
You will form opinions while you work. Some of them will be correct and some will be important. Write them down — somewhere else.
Keep a separate column, or a separate document, for observations, questions and things that look inconsistent. This keeps the chronology clean while preserving the thinking, and the observations are often the most valuable output of the whole exercise. They are the things only someone who read every page would notice.
What you must not do is blend them. The value of the chronology is that a reader
can trust every line without checking your reasoning.
Mark the gaps and the conflicts
Two documents will say different things about the same event. A month will have no documents at all. A document will refer to an attachment you do not have.
Record all three. A note reading "gap: no correspondence between 14 May and 2 August" is a finding. So is "document 87 refers to an enclosure not present in the material provided." So is a flat statement that two sources disagree, with both cited and no attempt to decide between them.
Deciding which version is correct is somebody else's job. Showing clearly that there are two versions is yours.
Read it back from the end
When you think you are finished, read the chronology from the last entry to the first.
Working backwards breaks the narrative momentum that hides errors. Dates out of sequence, events that appear twice under different descriptions, entries that cite a document that does not say what you remembered it saying — these surface on a reverse read and stay hidden on a forward one.
Then check every citation against its source. Not a sample. Every one.
The mistakes that cost the most time
Starting the chronology before the index is complete. You will rebuild it.
Renaming or reorganising the source files. Whatever numbering you assign at the index stage must never change, or every citation you have written becomes wrong at once.
Working from copies of copies. Go back to the original file whenever there is any question about what a document says.
Writing entries in the language of the document rather than plain description. "Advised that remittance would follow" is the document's voice. "Said payment would be sent" is what happened.
Leaving the uncertainty out to make it look tidier. The uncertainty is information.
When it makes sense to hand it over
The work is not difficult. It is long, and it demands the same standard of attention on document three hundred as on document three.
Most people can build a chronology of forty documents themselves and should. Past a few hundred, or where the material is in more than one language, or where someone other than you will have to rely on it, the arithmetic changes — not because the task becomes harder, but because it becomes very easy to lose consistency across weeks of it.
That is the work ADH Executive Services does: indexes and chronologies built from the material you have, every entry tied to its source, with the gaps and conflicts set out rather than smoothed over.
A note on what this is
This page describes a method for organising documents. It is not legal advice, and a chronology is a record of what your documents say — not an opinion about what any of it means or what you should do about it.