Evidence guide
Evidence moves from a client to a lawyer, from a device to a review system, from a preserved source to an exhibit, and sometimes from one party to another. The right transfer method depends on the source, the context and metadata that matter, and how much unrelated private information surrounds the evidence.
“Transfer” can mean making an evidentiary copy, giving material to counsel, moving a collection into an eDiscovery platform, producing data to another party, or presenting a readable exhibit. Those jobs do not always require the same format.
Evidence may originate in phones, computers, cloud services, messaging platforms, email, social media, files or personal AI accounts. Collection methods range from simple user captures to specialist forensic workflows.
Preservation is about maintaining information that may matter later. Depending on the matter, that can include original files, account exports, metadata, surrounding messages, collection notes or a forensic image.
A lawyer may need a readable screenshot for quick review, a native file for metadata, a structured export for analysis, or a selected production that maps back to a broader preserved source.
The practical trade-off is usually between simplicity, source detail, reproducibility, privacy and cost. The table describes general characteristics, not legal requirements for every case.
| Method | Useful for | What it can preserve | What may be missing |
|---|---|---|---|
| Screenshots | Fast review, visually readable messages or posts, initial client intake | Visible content, interface context, timestamps or identifiers shown on screen | Hidden metadata, material outside the crop, complete thread/account context |
| PDF / copied text | Readable packets, notes, correspondence, selected excerpts | The text and layout included in the created document | Native metadata and direct linkage to the underlying source may be reduced |
| Email / secure upload / cloud link | Transporting files already collected | Depends on the files being transferred | The transfer channel itself does not fix a weak collection method |
| Native files | Documents, spreadsheets, media and other file-based evidence | File contents and available native metadata | May not capture account-level or application context around the file |
| Account exports | Cloud services, messaging history, AI chat history and platform data | Provider-supplied structured data and broader account context, depending on the service | Can include substantial unrelated private data; formats vary by provider and over time |
| Forensic collection | Matters where source integrity, deleted data, device state or detailed metadata matters | Potentially extensive source information using documented technical processes | Cost, scope and privacy impact can be higher; not automatically necessary for every dispute |
| eDiscovery workflow | Larger litigation collections and controlled review/production | Structured processing, review decisions, production metadata and auditability | Quality still depends on what was collected and how source data was preserved |
For a closer look at the most familiar format, see screenshots as evidence.
If a source may matter later, consider preserving it before repeatedly editing, converting, cropping or forwarding the only available copy. A working copy or readable exhibit can be created after the source is stabilized.
Determine the account, device, file or data source that may contain relevant information.
Keep an appropriate source or source-level copy before unnecessary transformations.
Record enough about how and when material was collected to explain the process later.
Separate what is potentially responsive from what is irrelevant, private or potentially privileged.
Share the format and scope appropriate to the receiving lawyer, expert, party or tribunal.
Emerging evidence source
A personal AI account can hold work drafts, medical questions, financial concerns, relationship discussions, legal research and ordinary day-to-day thinking in the same history. A dispute may concern one conversation while the account contains hundreds of unrelated ones.
That creates two different questions: how to preserve enough source information to support later review, and how to avoid transferring an entire private history when only a narrow subset is actually needed. Screenshots, selected text, official provider exports and specialist collection each solve different parts of that problem.
It is the movement of digital material between stages or people in an evidence workflow—for example, from a source device or account into a preserved copy, from a client to counsel, into an eDiscovery system, to an expert, or into a production or exhibit. The transfer method should match the purpose and the type of source.
Ask the lawyer or firm what intake method and format they want. For potentially important source material, preserve the original or an appropriate source-level copy where reasonably possible before converting it. Do not assume that emailing a screenshot, deleting the original, or sending an entire private account export is always the right choice.
Screenshots are commonly used and can be admissible, but admissibility is not automatic. Authentication, relevance, hearsay and other rules can still apply. A screenshot also may preserve less metadata or context than an underlying source. See our screenshots as evidence guide.
No universal rule requires that every digital item be collected forensically. The appropriate method depends on the evidence source, the dispute, likely authenticity challenges, preservation needs, cost, proportionality and applicable legal rules. Specialist collection becomes more important when those technical issues are likely to matter.
At a high level, it means producing selected responsive material from a broader preserved source rather than automatically handing over the entire source. In a sound workflow, the selected material can still be traced back to what was preserved. The precise legal review and production process belongs with counsel.