Tutorial ID | T-10 |
Section | Evidence Processing |
Title | Building and Using the Case Timeline and Calendar |
Subtitle | Build a timeline from verified events, investigate its gaps, and keep it current before presenting it. |
Before You Begin
You have events and dates already captured and verified against their source documents.
You know which issue or story the timeline needs to make visible — sequence, gaps, or contradictions.
What You Will Accomplish
By the end of this tutorial, your timeline will be built entirely from verified events, its gaps and clusters investigated rather than assumed, focused enough to surface the events that matter, and current enough to present with confidence.
Why Does This Tutorial Matter
A chronological view does what a pile of records cannot: it reveals the sequence the case turns on, exposes gaps where you'd expect continuity, and brings contradictions to the surface. Used well, the timeline is both your analytical tool while you work the case and the foundation of the chronology section when you build the report.
The timeline's strength is that it's generated directly from the events you've captured; its weakness is that it inherits every error in those events. A timeline shown in a deposition is only as credible as the entries behind it, so an incorrect date, an unexplained gap, or sequence mistaken for causation carries forward into exactly the moment it matters most.
Steps
Build the timeline from events you've already checked against their sources, so the sequence is accurate.
Use the chronological view to look for gaps and treat each one as something to explain rather than overlook.
Read the timeline for contradictions between events and for patterns the documents don't show on their own.
Update the timeline as new events and documents are added, so it always reflects the present state of the case.
Include only the events that bear on the case, so the important sequence isn't lost among minor ones.
Remember the timeline shows what happened when, not why — causation needs support from the record, not just order.
Use the timeline as the foundation of the chronology section, so the report rests on the same verified sequence you analyzed.
Note A gap in a timeline can be as important as anything in it. A break in treatment, an unexplained interval, a missing record — the chronological view is often what makes these visible when the documents alone do not. |
Tip Read the timeline forwards once for the story and backwards once for the gaps. The two passes catch different things — the narrative on the way down, the missing pieces on the way up. |
What to Do if Something Goes Wrong
The list below covers the most common problems when building and using the timeline. Each entry follows the same pattern: what you'll notice, why it likely happened, a real example, and how to fix it.
Problem: An incorrect or duplicate point appears on the timeline.
Likely cause: The timeline reflects its underlying events exactly, so an incorrect date or a duplicate event in the chronology shows up the same way on the timeline.
Example: A duplicate hospital admission entered twice in the chronology appears as two separate points on the timeline instead of one.
Fix:
Build the timeline only from events you've verified against their sources (see T-09).
When the timeline looks wrong, trace the issue back to the underlying event rather than adjusting the view.
Correct the event, and let the timeline update from the corrected data.
Problem: A gap or a cluster of events on the timeline is taken at face value without checking what's actually behind it.
Likely cause: A gap can reflect either a genuine break in treatment or simply missing records, and a cluster can be real or the product of duplicate entries — neither was confirmed before drawing a conclusion.
Example: A cluster of five events on the same date is read as an unusually active treatment day, when three of the five are actually duplicate entries of the same visit.
Fix:
Before drawing conclusions, confirm whether a gap reflects reality or absent documents.
Check that a cluster of events isn't the product of duplicate entries.
Annotate or explain significant gaps and clusters to prevent misinterpretation.
Problem: The events that actually decide the case are lost among everything else shown on the timeline.
Likely cause: Every event was displayed at once, without using filters or colour coding to focus the view on what matters for a particular issue.
Example: A timeline showing every routine visit alongside a pivotal surgical intervention makes the surgery easy to miss in the clutter.
Fix:
Use filters and colour coding to focus the timeline on the events relevant to a particular issue.
Build focused views, such as by provider, issue, or phase, rather than presenting everything at once.
Keep the full timeline available, but lead with the view that tells the relevant story.
Problem: A timeline presented in a deposition or at trial gets challenged because an entry doesn't hold up against the record.
Likely cause: The timeline was used as an exhibit without confirming beforehand that each entry links to its source document.
Example: Opposing counsel questions a date on the timeline, and the presenting team can't immediately point to the document that supports it.
Fix:
Before using the timeline as an exhibit, confirm that each entry links to its source document.
Check that the dates and sequence are defensible against the records.
Use the hyperlinks to evidence so any entry can be substantiated on the spot.
Problem: The timeline still shows an old sequence after new records have changed the underlying events.
Likely cause: The timeline wasn't refreshed after events were added or changed, so it no longer reflects the current state of the case.
Example: A new medical record shifts the date of a key procedure, but the timeline shown to the team still reflects the original, incorrect date.
Fix:
Refresh the timeline whenever events are added or changed.
Re-examine gaps, clusters, and the sequence after each update.
Confirm you're presenting the current version, not an earlier one.
Problem: The timeline shows a flat list of dates but doesn't make clear how an event changed the claimant's baseline condition.
Likely cause: The timeline wasn't organized to distinguish before, during, and after the event, so the change the case turns on stays implicit rather than visible.
Example: A timeline lists pre-injury and post-injury treatment dates in the same undifferentiated style, leaving a reader to work out for themselves what changed.
Fix:
Use the timeline to show the baseline before the event, the event itself, and the change that followed.
Apply colour coding to distinguish pre-event, event, and post-event entries.
Let the timeline demonstrate whether a change was temporary or permanent, rather than leaving it implicit.
Summary
Your timeline is now built entirely from verified events, with its gaps and clusters investigated rather than assumed, its view focused on what matters for the issue at hand, its entries kept current, and its story of baseline, event, and change made visible — a tool you can analyze with and present from with confidence.