Before a dispute starts, preserve the evidence you will wish you had.
Once a dispute begins, every record is viewed under pressure. This checklist helps you prepare a cleaner evidence position before the facts are contested.
Dispute-ready evidence11 minEssential18 checks
Primary question
If this were challenged later, could you show what happened without relying on memory, screenshots, or platform trust?
Use this checklist before there is a dispute, complaint, challenge, takedown, authorship conflict, customer claim, regulatory question, or evidence request.
Dispute evidence is usually weakest when it is assembled after the problem appears. This checklist helps preserve the source, timing, custody, context, communications, and claim boundary before pressure begins.
Evidence goal
Prepare a cleaner evidence trail before disagreement, challenge, investigation, or formal dispute.
This checklist helps prepare dispute-ready records. It does not prove legal liability, ownership, infringement, truth, compliance, negligence, breach, authorship, or entitlement by itself.
Working principles
What this checklist is trying to protect.
The best dispute evidence is created before the dispute.
Evidence prepared before pressure begins is usually cleaner than evidence assembled after accusations, edits, deletions, or defensive reconstruction.
Preserve facts, not arguments.
Strong evidence shows what existed, when it existed, who had access, what changed, and what was communicated. It does not need to start as a legal argument.
Keep original records intact.
Editing, renaming, overwriting, deleting, or reorganising important files after a problem appears can damage the evidence trail.
Make the record understandable.
Evidence is weaker when only the original creator can explain it. A future reviewer should be able to follow the sequence.
Section 1
Evidence object
Identify the exact file, record, work, transaction, decision, publication, claim, or event that may later matter.
0%complete
Name the file, work, record, decision, delivery, publication, claim, or transaction.
Why this matters and what to do
Why this matters
Disputes become messy when the parties are not even talking about the same object or event. The evidence trail needs a defined centre.
What good looks like
The relevant object or event is named clearly.
The version, file, record, decision, claim, or transaction is identifiable.
The record does not blur several different events together.
Common mistake
Treating a general project, relationship, account, or platform history as the evidence object.
Next action
Write one plain sentence identifying the object or event that may later matter.
Preserve the state before later edits, uploads, responses, or changes.
Why this matters and what to do
Why this matters
The version at the time of an event may be different from the version available later. Dispute evidence needs to preserve the relevant state, not only the current state.
What good looks like
The relevant file version is retained.
The relevant webpage, record, submission, decision, or output is captured.
Later changes are distinguishable from the earlier state.
Common mistake
Updating the file or page and losing the version that would have shown what existed at the relevant time.
Next action
Save the relevant state now and keep it separate from later working copies.
Use a project ID, file hash, receipt ID, case ID, transaction ID, release ID, or folder reference.
Why this matters and what to do
Why this matters
Evidence gets weaker when source files, receipts, emails, platform records, and notes cannot be connected. A stable identifier helps join the record.
What good looks like
The source file, receipt, communication, and public record can be linked.
The identifier is used consistently.
The identifier survives file moves or folder changes.
Common mistake
Relying on memory to connect several scattered records later.
Next action
Assign a simple stable identifier and use it across the evidence folder.
Section 2
Timing and sequence
Preserve when key things happened and in what order.
0%complete
Create or preserve evidence of when the relevant object or event existed.
Why this matters and what to do
Why this matters
Timing becomes central in many disputes. Evidence created before the dispute is harder to dismiss as defensive reconstruction.
What good looks like
A receipt, hash, timestamp, log, submission record, publication record, or independent timing record exists.
The timing record is connected to the exact object or event.
The record can be checked later.
Common mistake
Creating the first timing evidence only after the other party challenges the claim.
Next action
Create or preserve a timing record before there is pressure.
Record what happened before, during, and after the relevant event.
Why this matters and what to do
Why this matters
Disputes often turn on sequence. A clean timeline can prevent later confusion about who had access, when something was changed, when something was submitted, or what was said first.
What good looks like
Key dates and events are listed.
The timeline distinguishes creation, sharing, publication, delivery, approval, rejection, complaint, and change events.
The timeline links to supporting evidence.
Common mistake
Trying to reconstruct the timeline from memory months later.
Next action
Add a short timeline note to the evidence folder.
Avoid ambiguous dates when events cross platforms, regions, or systems.
Why this matters and what to do
Why this matters
Platform dates, server logs, emails, messages, and blockchain records may use different time zones or date formats. Ambiguity can create unnecessary disputes.
What good looks like
Important times include time zone where needed.
System, platform, and local times are not confused.
The sequence still makes sense across records.
Common mistake
Treating all displayed dates as if they use the same time zone.
Next action
Add time zone notes for important events if the context could later be ambiguous.
Section 3
Custody and control
Preserve who controlled the files, accounts, records, systems, or access points.
0%complete
Show who held, accessed, uploaded, approved, changed, or transmitted the relevant object.
Why this matters and what to do
Why this matters
Dispute evidence is stronger when it can show where the object was, who controlled it, who received it, and how it moved.
What good looks like
The relevant account, folder, device, system, repository, platform, or owner is identified.
Access or transfer points are recorded.
The chain from source to shared or published version is understandable.
Common mistake
Keeping the file but losing the evidence of who had access and when.
Next action
Record the custody path from creation or source to current location.
Preserve who could see, edit, download, receive, or act on the material.
Why this matters and what to do
Why this matters
Many disputes depend on access. If you cannot show who could access the material, it becomes harder to explain exposure, responsibility, or opportunity.
What good looks like
Recipients are recorded.
Shared-link settings are captured where relevant.
Platform access logs, permission lists, or collaborator records are saved where available.
Common mistake
Sending or sharing through temporary links without retaining recipient or access records.
Next action
Save the access list, recipient list, or permission state before it changes.
Avoid altering the record that may later need to be examined.
Why this matters and what to do
Why this matters
Editing, overwriting, re-exporting, renaming, compressing, or replacing key files can make the evidence trail harder to trust.
What good looks like
Original files are copied before further work.
Later edits happen in separate working copies.
The preserved version remains available for review.
Common mistake
Fixing, cleaning, or reorganising files after a problem appears and damaging the original evidence trail.
Next action
Freeze a copy of the relevant record before making further changes.
Section 4
Communications
Preserve the messages and surrounding context that explain what happened.
0%complete
Save emails, messages, submission confirmations, approvals, comments, tickets, calls notes, or platform notices.
Why this matters and what to do
Why this matters
Communications often explain context, permission, delivery, expectations, warnings, approval, rejection, disagreement, and reliance. Without them, the file record may be incomplete.
What good looks like
Relevant sent and received messages are retained.
Attachments or links are preserved with the message context.
Submission confirmations, approvals, receipts, or notices are saved.
Common mistake
Keeping the work but losing the communications that explain how it was shared or used.
Next action
Save the key communication thread or export it into the evidence folder.
After calls or meetings, record what was agreed, requested, approved, rejected, or disputed.
Why this matters and what to do
Why this matters
Verbal discussions are fragile. A short contemporaneous note can help preserve context before memories diverge.
What good looks like
Meeting or call notes are dated.
The note identifies participants.
The note separates facts, requests, approvals, and opinions.
Common mistake
Relying on memory for important verbal instructions or approvals.
Next action
Write a short dated note after important calls or meetings.
Do not mix what happened with what you believe it means.
Why this matters and what to do
Why this matters
Evidence becomes less persuasive when factual records are mixed with accusations, assumptions, conclusions, or emotional commentary. Keep the record clean.
What good looks like
The evidence folder contains factual records.
Interpretation or argument is kept separate.
Claims are linked to the records that support them.
Common mistake
Writing angry notes into the evidence record and making the file look defensive rather than factual.
Next action
Keep a factual evidence note separate from any argument or complaint draft.
Section 5
Preservation and recovery
Make sure the evidence survives ordinary loss, deletion, account changes, and platform dependency.
0%complete
Keep source, timing, custody, communications, public records, and notes together.
Why this matters and what to do
Why this matters
Evidence that exists but cannot be found is weak. A structured folder helps preserve the record before pressure, deletion, or platform change.
What good looks like
Source files are retained.
Receipts or timing records are retained.
Communications are retained.
Access or custody records are retained.
A short timeline or verification note is retained.
Common mistake
Leaving evidence scattered across inboxes, downloads, devices, cloud folders, dashboards, screenshots, and memory.
Next action
Create a dispute-ready evidence folder and move or copy key records into it.
Do not rely on one device, account, dashboard, or platform.
Why this matters and what to do
Why this matters
Accounts close, links expire, dashboards change, platforms remove content, cloud sync fails, devices break, and logs roll over. Export and backup protect the evidence from ordinary loss.
What good looks like
Key files and records are backed up.
Platform records are exported where possible.
Receipts and identifiers are stored outside temporary locations.
Common mistake
Assuming that a platform, cloud drive, or message app will preserve everything exactly as needed.
Next action
Export or back up key evidence now, especially records held inside platforms.
Identify records that may expire, be deleted, be overwritten, or become inaccessible.
Why this matters and what to do
Why this matters
Many useful records disappear automatically. Logs rotate, links expire, edits overwrite previous versions, subscriptions lapse, and message histories get cleared.
What good looks like
Expiring links are saved.
Logs or platform records are exported before they disappear.
Auto-delete or retention settings are known.
Common mistake
Discovering after a dispute starts that the relevant logs or messages have already expired.
Next action
Check what evidence could disappear and export it before it does.
Section 6
Claim boundary and review
Keep claims accurate and make the evidence reviewable.
0%complete
State what the evidence supports and what it does not support.
Why this matters and what to do
Why this matters
Overclaiming weakens credibility. A receipt, timestamp, email, log, screenshot, file, or public page may support one claim but not another.
What good looks like
The record states whether it supports existence, timing, custody, access, delivery, publication, approval, or sequence.
The record does not overstate ownership, infringement, breach, compliance, truth, or liability.
Unproven assumptions are kept separate.
Common mistake
Treating evidence of timing or access as proof of legal fault or ownership.
Next action
Add a short claim boundary note to the evidence folder.
Identify material, data, assets, licences, approvals, or dependencies that are not solely yours.
Why this matters and what to do
Why this matters
Many disputes are complicated by third-party materials or permissions. Evidence that a record existed does not prove all included material was owned, licensed, approved, or lawful to use.
What good looks like
Third-party assets or data are listed.
Licences, approvals, permissions, or source notes are retained where relevant.
Your contribution is distinguishable from external material.
Common mistake
Using a dispute-ready record to imply rights over everything inside the file.
Next action
Add a rights and dependencies note for relevant external material.
The record should be understandable without your memory.
Why this matters and what to do
Why this matters
Evidence is stronger when a reviewer can follow the path from source, to timing, to sharing, to publication or decision, to communications, to claim boundary.
What good looks like
The evidence folder has clear file names.
The timeline note explains the sequence.
Receipts, identifiers, files, and communications are linked.
The claim boundary is clear.
Common mistake
Building an evidence folder that only makes sense to the person who created it.
Next action
Add a short read-me note explaining how the evidence should be reviewed.
Completion
What stronger dispute readiness looks like
You are in a stronger position when the relevant object or event is defined, the version is preserved, timing is recorded, custody and access are understandable, communications are retained, evidence is backed up, and claim boundaries are clear before any formal dispute begins.
Stronger position
The exact object or event is defined.
The relevant version or state is preserved.
A timing record exists before pressure begins.
The sequence of events is recorded.
Custody, access, and recipient records are retained.
Original records are not overwritten.
Key communications and confirmations are preserved.
Platform-held records are exported where possible.
Evidence is backed up outside one fragile location.
The claim boundary is accurate and restrained.
A future reviewer could understand the evidence path.
Weak position
The record depends on memory.
Only screenshots or platform dates exist.
The relevant version was overwritten or lost.
Timing evidence was created only after the challenge.
Recipients, access, custody, or communications are unclear.
Evidence is scattered across inboxes, downloads, dashboards, cloud folders, and devices.
Claims exceed what the records actually prove.
A reviewer would need the original creator to explain everything.
Next steps
What to do from here.
If there is no dispute yet
Preserve the record now. Define the object, save the relevant version, create timing evidence, retain communications, export platform records, and write a short claim boundary.
If a dispute may be emerging
Stop casual edits to relevant files. Freeze copies, preserve messages, export logs, save access records, and avoid rewriting the evidence trail while under pressure.
If a dispute has already started
Preserve originals immediately. Do not delete, overwrite, selectively edit, or reconstruct records casually. Consider legal, forensic, compliance, or expert support before making firm conclusions.
This checklist prepares evidence. It does not decide legal outcomes, certify ownership, prove infringement, prove compliance, or replace professional advice.
