Workflow · 10 min read
How to Prepare a Text Message Exhibit Packet for Review
A source-review checklist for source files, key excerpts, context windows, redactions, and report manifests.
The short answer
An exhibit packet is not a highlight reel, and the difference shows under questioning. A packet assembled only from the strongest messages invites a single reply: what did you leave out? A packet that states its own scope is much harder to dismiss. In practice that means five parts. The source material, or a clear statement of where it is held. The excerpts themselves, each traceable to a specific message. A context window around every excerpt, so a reader can see what was being answered. A participant map recording how each identifier was attributed and on what basis. And a short manifest describing how the packet was produced — what the source was, what was filtered out, what was redacted and why. None of that makes an exhibit persuasive by itself. It makes it checkable, which is the property that survives someone trying to take it apart. Textimony produces automatic or reviewer-curated reports from a completed run while keeping the parsed messages available for contextual review.
Packet components
Source export or source-file reference. Hash values for source uploads and generated reports. Participant map with phone numbers, handles, or account identifiers. Timeline of key events with context before and after each excerpt. Redaction log for review copies. Review note distinguishing evidence organization from argument drafting.
Context windows
For each highlighted message, include nearby messages that help explain the exchange. Context windows reduce the risk that a reviewer sees a message without the conversation around it. The right window size depends on the matter. Textimony’s timeline and candidate context views help reviewers inspect nearby parsed messages; any external packet should still cite the preserved source.
Review before sharing
Before sharing a packet, check for unrelated private data, third-party names, children, addresses, financial details, and privileged communications. Keep the owner original separate from redacted review copies.
Start with review scope, not formatting
An exhibit packet should not begin as a design project. It should begin with scope: what source files were reviewed, what date range was included, which participants were mapped, what filters were applied, and what material remained outside the packet. Formatting matters later because reviewers need readability. But a clean PDF with no source path can create more risk than a plain packet with message IDs, hashes, context windows, and source notes. The packet should explain where each excerpt came from and how to inspect the underlying messages.
Packet components to include
Cover index naming the case workspace, source files, date range, participants, and generated export date. Evidence manifest with filenames, hashes when available, message counts, attachment counts, and known gaps. Participant map explaining display names, numbers, aliases, account handles, and uncertain identities. Timeline or issue sections with message IDs, timestamps, nearby context, and source-file references. Redaction log that separates owner-controlled originals from privacy-safe review copies. Summary chart only when each row can be traced to underlying messages and source files. Source notes page for missing media, unsupported files, deleted-message claims, and legal-review boundaries.
Use source links to reduce challenge points
The most useful exhibit packet anticipates basic objections: Who sent the message? Is the screenshot complete? What came before and after? Which file was analyzed? Was the copy changed? Which messages were omitted? Source-linked reports keep the factual workflow inspectable. Textimony generates automatic or reviewer-curated reports from a completed run. Those reports can support packet preparation, but the source manifest, redaction log, exhibit selection, and final filing packet must be assembled and approved separately.
Before you share the record
The final packet should preserve a reviewer path in both directions: from each summary row back to the original message, and from each source file forward to the excerpts or charts that used it. That bidirectional trail is what keeps the packet useful after it leaves the software.
What belongs on the first page of a text message exhibit packet?
A cover page that lets the packet identify itself without anyone asking. Name the source files it derives from, the date range covered, the participants, when the export was made and by whom, and what the packet is for. State plainly that it is a review aid compiled from a preserved source rather than the original record — that single sentence prevents the packet from being mistaken for the evidence itself.
Should screenshots go in the packet?
They can, particularly where they capture something an export omitted — a reaction, a disappearing message, or media that did not survive. Include them as labeled artifacts tied to the source record and the surrounding context window rather than dropping them in as loose images. A packet built only from screenshots is much harder to defend than one where each screenshot has a stated role.
What is a redaction log?
It is a record of every redaction applied to a review copy: what was removed or masked, which category it fell into, the reason, and which copy it affected, with confirmation that the unredacted original remains preserved. Its purpose is to let you show that redactions were principled rather than selective, which is precisely what an opposing party will test if the packet matters.
Can Textimony decide what is admissible?
No. Admissibility is a ruling a court makes, applying rules of evidence to a specific record in a specific proceeding — it is not a property of a file that software could detect. Textimony produces reports from a completed run. Which of that material becomes an exhibit, what gets redacted, and how it is filed are legal judgments requiring qualified review.
Published by
Textimony. Editorial status: Source-linked informational guide. Updated: 2026-07-10.
Sources
Federal Rule of Evidence 901; NIST: Digital Evidence Preservation; FTC: Protecting Personal Information