How to organize evidence for any legal situation

Whatever your dispute is about — a business partner, a spouse, a landlord, an employer, a vendor — the record that decides it has the same anatomy. Most people learn this anatomy after they've already lost evidence they can't get back. You can learn it now.

This page is the general version. The situation-specific hubs (partnerships, family money, landlord-tenant, employment, contract disputes) describe what to document in each kind of case. This one describes how to do it well.

The five things every legal record needs

1. A chronology. A simple, dated list of every relevant event, in order.
2. A party map. Who's involved, in what role, with what authority.
3. Originals. The actual files — emails as .eml, texts as exported threads, PDFs as PDFs, photos with metadata intact. Not retyped, not summarized, not screenshotted-and-emailed.
4. A communications log. Every conversation between the parties, in order, by channel.
5. A short summary of what's in dispute and what you want.

If your case file has those five things — even in a basic spreadsheet — you're ahead of most people who walk into a lawyer's office.

Provenance is everything

The single most undervalued concept in evidence is provenance: the unbroken chain showing where a piece of evidence came from, when it was captured, and how it got from its source to your file.

Strong provenance:

• An email saved as a .eml file with original headers, including timestamps and authentication results.
• A PDF received by email and stored unchanged, with the receiving email message still in your inbox.
• A photo whose EXIF data (date, time, sometimes location) is intact because the file was never re-edited.
• A text thread exported from the phone or platform that sent it.

Weak provenance:

• A screenshot of an email pasted into a Word document.
• A photo that's been edited, cropped, or run through a filter.
• A text retyped into a notes app from memory.
• "I'm sure I had it somewhere."

You don't always need strong provenance for every piece of evidence — but the pieces of evidence with strong provenance are the ones that hold up under scrutiny. Whenever you have a choice, choose the version closer to the source.

How to capture, in practice

A few rules that consistently produce good records:

• Keep originals. When something arrives in a particular file format, store the original. Do all your annotating, highlighting, and commenting on a copy.
• Save before you forward. Forwarding an email to yourself can strip or alter headers depending on the client.
• Export chat threads where possible. Most messaging platforms offer an export feature. It produces a far stronger record than screenshots.
• For photos, turn off filters and editing apps. Save photos directly from the camera; back them up before opening them in editors.
• For phone calls and voicemails, save the audio file where you can. For calls where no recording exists, write notes within 24 hours: who, when, how long, and what was said.
• For in-person conversations, write contemporaneous notes — within the same day. Note who was present, where, when, and the substance of what was said. These notes are admissible in many contexts because they were made when memory was fresh.
• Back up in two places. A cloud drive plus an external disk, or two cloud providers. People lose entire case files to a single dead laptop more often than you'd guess.

Building a chronology

A chronology is the spine of every case file. It doesn't need to be fancy. A spreadsheet with these columns is sufficient:

• Date (and time, if known)
• Event (one sentence: who did what)
• Source (the file or message that proves it)
• People involved

Rules of thumb:

• One line per event. If two things happened at the same time, that's two lines.
• Use plain language. "Alex emailed me saying the Q2 distribution would be skipped." Not "Alex took adverse financial action against me."
• Tie every line to a source. If you can't, mark it as recollection and date the note.
• Keep it strictly chronological. Don't group by topic or party.

When this gets long enough, this is the work AitaraPilot does automatically — pulling structured events from your mixed pile of files and producing a verified, source-grounded chronology with one click. The point of doing it by hand first is that you'll understand exactly what the tool is producing.

Building a party map

A party map is a short document that lists:

• Every person and entity involved in the dispute.
• Their role (your spouse, the LLC's CFO, the landlord's property manager, the manager who fired you).
• Their authority (decision-maker, signatory, witness, advisor).
• The best contact information you have for them.
• A one-line note on their relationship to each other.

In partnership and family-money cases especially, the party map is what makes the chronology readable. A line that says "K. Marcus signed the amendment" only matters if a reader can see, in the party map, that K. Marcus is the bookkeeper rather than a member.

The communications log

Separate from the chronology, keep a single log of every communication between the parties:

• Date and time
• Channel (email, text, phone, in-person)
• From and to
• Subject or summary
• Source file (link or filename)

The point of keeping this separately is that communications are often the most-contested evidence ("we never agreed to that"; "I never said that"). Having every communication listed in one place, in order, kills entire categories of disputes before they start.

What to send to a lawyer

When you eventually hand a case file to an attorney, the highest-value first delivery is:

1. A one-page summary: what happened, who's involved, what you want.
2. The chronology.
3. The party map.
4. A folder of source documents, named with dates and a short description.
5. The communications log.

That's a fraction of the documents people typically arrive with, organized in a way that lets the lawyer be useful in the first meeting instead of the fifth.

What never to do

• Don't destroy anything, even if it's embarrassing. Spoliation of evidence is its own claim, and it tends to be a strong one against the destroyer.
• Don't access systems you don't have a clear right to access, even to gather "obviously true" evidence. It often creates worse liability than the dispute itself.
• Don't share your case file with people who don't need it. Discussions with friends are not privileged; emails to your therapist sometimes are; emails to a lawyer almost always are. Pick your audience carefully.
• Don't rely on memory. Memory is treated, fairly or not, as the weakest possible evidence. A contemporaneous note from the day it happened is stronger than your sworn recollection a year later.