The Paper Trail Gap Analysis¶

Why It Matters¶

Legitimate processes create paper trails. Contracts, approvals, audit trails, meeting minutes, and correspondence should exist at specific points. Their absence, suspicious timing, or unusual characteristics indicate either process violations or cover-ups. Fraudsters and rule-violators often create retroactive documentation but make detectable errors.

The Key Move¶

For the process you're investigating, map the required documentation: "If this contract was legitimate, there should be: RFP, bid submissions, evaluation committee notes, approval signatures, executed contract, payment records." Then check: Does each document exist? If documents are missing, why? If they exist, do they show signs of backdating (metadata, references to events that happened later, anachronistic language)? Are they consistent with each other (do they tell the same story, use the same figures)? Interview participants: "Standard process requires X - why is it missing?" Their explanations are often revealing.

Classic Application¶

Pentagon Papers investigation. The documents showed the government's internal assessments of the Vietnam War were far more pessimistic than public statements. But critical verification was checking the paper trail: were these authentic government documents or forgeries? Investigators verified: classification markings matched actual DOD standards, distribution lists matched known personnel, dates aligned with other historical events, and writing style matched other confirmed government analyses. The consistent paper trail authenticated the leak.

Surprising Application¶

M&A due diligence. When acquiring a company, check that expected documents exist and are genuine: board minutes approving major decisions, signed customer contracts (not just unsigned drafts), employee offer letters, IP assignment agreements. A surprising number of startups have incomplete paper trails - contracts that were never actually signed, IP that was never formally assigned, approvals that were casual conversations not documented. Missing documents reveal operational sloppiness or sometimes fraud (claimed contracts that don't exist).

Failure Modes¶

Assuming missing documents mean wrongdoing (sometimes legitimate processes have gaps, or records weren't required at the time). Not understanding document retention policies (absence might be routine destruction, not evidence destruction). Accepting document existence as sufficient (documents can exist but be fabricated). Not checking metadata (creation dates, author, edit history) on digital documents. Over-focusing on documents and ignoring that legitimate work sometimes happens informally, especially in fast-moving environments.

Go Deeper¶

Gup, "The Art of Business: Journalism After Watergate" Chapter 5 on document verification. Weinberg, "The Reporter's Handbook" on public records analysis. ICIJ, "Leak Investigation Methodology" (from Panama Papers) on document authentication at scale.