Timeline Construction¶

Why It Matters¶

Humans are poor at lying consistently about sequences and timing. Memory distorts chronology. Coordinated deception rarely accounts for all timing details. A sufficiently detailed timeline makes lies and errors visible through logical impossibilities ("you couldn't have been in both places"), contradictions between sources ("three people give three different dates for the same meeting"), and suspicious patterns ("every document dated just after the legal deadline").

The Key Move¶

From all available sources and documents, extract every dated fact: when was each meeting, email, transaction, phone call, public statement, or decision. Build a master timeline. Note: where do sources disagree on dates? Where are there suspicious gaps (no documentation for weeks when you'd expect activity)? Where do events happen in convenient order (contract signed one day before damaging audit)? Impossible sequences (email discussing meeting that allegedly happened before the email was sent)? Use timeline contradictions as interview leverage: "You said the meeting was in March, but this email from February already references decisions from that meeting. Which is correct?"

Classic Application¶

Theranos investigation. Elizabeth Holmes claimed the blood-testing technology was developed over years with extensive validation. Journalists built a timeline from: patent filings (when technology claims were made), employee hiring dates (when expertise was brought in), partnership announcements (when claims about capabilities were made externally), and lab inspection reports (when actual capabilities were assessed). The timeline revealed the technology didn't exist when partnerships were announced, testing was done on commercial analyzers when Holmes claimed proprietary technology was used, and validation studies cited in presentations hadn't yet been completed when the presentations occurred.

Surprising Application¶

Debugging distributed systems. When investigating production incidents involving multiple services, build a timeline from: service logs (with normalized timestamps), deployment history, database transaction logs, and monitoring alerts. The timeline often reveals: impossible orderings (service B processed a request before service A sent it - clock skew), suspicious coincidences (deployment at exactly when errors started), and contradictions (logs claim success but monitoring shows failures). The timeline makes causal relationships visible.

Failure Modes¶

Trusting timestamps without verification (logs can have wrong time zones, people backdate documents, memory about timing is unreliable). Not accounting for normal variance in chronology (people misremember whether something was Tuesday or Wednesday without being deceptive). Seeing patterns in randomness (suspicious coincidences happen by chance). Not marking certainty levels (treat all timeline entries as equal when some are "confirmed by multiple documents" and others are "source recalled"). Building timeline to confirm pre-existing narrative rather than testing it.

Go Deeper¶

Weinberg, "The Reporter's Handbook" Chapter 6 on chronology construction. Spark, "Investigative Reporting: A Study in Technique" on timeline analysis. Meyer, "Precision Journalism" on timeline cross-verification.

Deception - Military Strategy & Strategic Thinking: A Map of the Territory