Chronological Gap Analysis¶

Why It Matters¶

Human memory and narrative construction are notoriously unreliable about timing. People compress timeframes, reverse causation, and insert events that "must have happened" even if they didn't. Chronological gaps expose these problems. A timeline that requires physically impossible sequences, contradicts documented timestamps, or depends on implausible coincidences is probably wrong. Conversely, a timeline that aligns perfectly with independent timestamps and requires no improbable conjunctions is more likely accurate.

The Key Move¶

Create a timeline of all claimed events, using the most specific timestamps available (documents, phone records, security footage, etc.). Mark events with known times in one color and estimated times in another. Identify gaps: periods where something important allegedly happened but there's no record. Identify inconsistencies: events that would require people to be in two places simultaneously, or causes that come after effects, or actions that leave no trace despite ordinarily doing so. Test your opponent's narrative the same way - often they haven't done this analysis and their timeline contains contradictions they haven't noticed.

Classic Application¶

Alibi defense in criminal cases. Defendant claims they were at Location A when crime occurred at Location B. Prosecution timeline: crime occurred at 9:15pm (per surveillance footage), defendant's cell phone pinged tower near Location B at 9:12pm. Defense timeline: defendant was at restaurant at Location A from 8:00-10:00pm (per receipt timestamped 9:47pm and server testimony). Gap analysis: travel time from Location B to Location A is minimum 25 minutes in traffic. Defendant cannot be at crime scene at 9:12 and generate restaurant receipt at 9:47 unless timeline is wrong. Either phone ping is misidentified, or crime time is wrong, or server testimony is inaccurate. Forces prosecution to address this gap.

Surprising Application¶

Project failure post-mortems. Team claims project failed because "requirements changed midstream." Timeline analysis: Requirements document finalized January 15. First code commit January 12 (before requirements finalized). Architecture decisions locked in December 20 (before requirements even drafted). First "requirements change" email February 3 (three weeks after development started, requesting feature explicitly listed in January 15 requirements doc). Gap analysis reveals narrative is backwards: development started before requirements were complete, then requirements were labeled "changes" when they contradicted already-written code. The real failure was premature development, not changing requirements.

Failure Modes¶

Over-precision - treating estimated times as exact creates false precision and false contradictions. Ignoring timezone issues, clock discrepancies, timestamp tampering - documented times aren't always accurate. Assuming gaps are evidence of lying rather than memory failure or irrelevance - not every moment has documentary evidence. Focusing on timeline to exclusion of causation - events can be correctly sequenced but misattributed. Building timeline from interested party recollections rather than neutral records - contaminated source data produces contaminated analysis.

Go Deeper¶

Hastings, Reed. "Timeline Analysis in Complex Litigation," ATLA Annual Convention Reference Materials, 2003; Schum, David A. "The Evidential Foundations of Probabilistic Reasoning." Northwestern University Press, 1994, Chapter 7 on temporal evidence.