What You’ll Produce in This Module

• A Fact-to-Evidence Map that ties each chronology event to its support
• A Missing Evidence Gap List you can send to the client (exact requests)

In Module 1, you built a clean chronology. In this lesson, you take the professional next step: you connect events to proof. AI can help organize quickly, but humans verify. Strong files map facts to evidence conservatively and defensibly.

Core Training Video

Video coming next.
This lesson will walk through how to turn a chronology into a defensible Evidence Map and Gap List.

You’ll use: M2-01 Fact-to-Evidence Mapping Table + M2-06 Evidence Map Builder Prompt (from Module 2 Downloads).

Key Concepts Covered

• Stories without proof fail. Strong files connect facts to evidence.
• Evidence categories: messages, emails, photos/videos, financials, medical, reports, witnesses.
• Basis matters: personal knowledge vs witness basis vs information-and-belief.
• AI organizes; humans verify. AI cannot confirm what you actually possess.
• Three statuses: Verified / Needs Request / Unknown.
• Gap List: precise follow-up requests tied to exact chronology events.

Professional Standard (Non-Negotiable)

• Do not state something as a fact without a basis.
• If it is witness-based, identify it as witness-based.
• If it is information-and-belief, label it clearly and conservatively.
• If evidence is missing, don’t “patch it” — request it.

Next step: Watch the Implementation lesson to build a Fact-to-Evidence Map in real time, then download the Module 2 templates.