Text Message Exhibits: Formatting Best Practices for Hearings and Trial

The messages are collected, the foundation is planned, and now the exhibit has to work for a judge reading on the bench, a witness on the stand, and opposing counsel looking at a shared screen. Format decides whether the court understands a thread in thirty seconds or spends five minutes asking which gray bubble belongs to whom.

This guide covers the formatting decisions that make a text message exhibit readable and defensible: which overall format to use, the header block every log needs, how to lay out each message, time zones, attachments and reactions, omissions and highlighting, and the final checks for redaction and numbering. Templates are included for the header and the message lines.

Which format should a text message exhibit use?

Use the format that best fits the thread’s length and the dispute. Short exchanges often work as screenshots; long or contested threads usually work better as a log generated from an export.

Many teams combine them: a complete log as the evidentiary exhibit, with two or three screenshots to show how a key message actually appeared on the phone. If your team builds logs by hand today, a paralegal’s guide to text message logs covers the build process step by step.

What should the header block of a message exhibit include?

The first page should answer the foundation questions before anyone asks them: who is in the conversation, where the messages came from, what period is covered, and what time zone the times are in.

• Participants identified by number or handle, not only by saved contact name
• Channel stated, since one conversation can mix SMS, iMessage and RCS
• Source and collection method stated in one line
• Date range and time zone stated explicitly
• Whether the exhibit is complete or an excerpt

How should each message line be formatted?

One message per line or row, in chronological order, with the same fields every time: date, time, sender, and the verbatim text, plus any attachment or status marker.

Verbatim means verbatim

Reproduce the text exactly, including misspellings, capitalization, abbreviations and emoji. Do not correct spelling or add [sic] after every error; a header note that messages are reproduced as sent covers it. Emoji can render differently across platforms, so where meaning may be disputed some teams add the emoji’s standard name in brackets, without interpreting it.

Distinguish the participants

In a log, use consistent names with the number or handle. In a screenshot series, keep color, because bubble color and alignment are how a reader tells the participants apart. Group chats need every participant identified in the header.

Merging channels, devices and duplicates

Real conversations rarely stay on one channel. The same two people may text over SMS, switch to iMessage, and continue on WhatsApp, and the firm may hold screenshots from one phone and an export from another. Merge everything into one chronological sequence only if every line carries its channel label, and record each source in the header. Remove exact duplicates (the same message captured in both a screenshot and an export) but keep a list of what was merged, so anyone can trace a line back to every source that contains it.

How do you handle timestamps and time zones?

State one time zone in the header and present every message in it. Mixed time zones are one of the quietest and most damaging formatting errors in message exhibits.

Exports vary: some record times in UTC, others in the device’s local time, and screenshots show whatever time zone the capturing phone was set to at the moment of capture. When sources are combined, a message can appear to arrive before the one it answers. Convert everything to a single zone, note daylight saving transitions in the date range, and verify the conversion against at least one event whose time is independently known.

How should attachments, reactions, edits and deletions appear?

Show them as the source recorded them, labeled consistently, without reconstructing anything the data does not contain.

• Attachments. A thumbnail or reference in the message line, with a full-size copy in an appendix and a cross-reference both ways. Produce audio and video natively and reference them by file name.
• Reactions. Platforms record reactions differently, and between iPhone and Android users a reaction may arrive as a separate text message. Present it as recorded and add a note if it could confuse the reader.
• Edits and unsent messages. If the source shows an edited or unsent indicator, include it. Do not reconstruct earlier versions unless the data actually contains them.
• Voice notes. Label any transcript as a transcript, identify who prepared it, and keep the audio available.

How do you show excerpts without inviting a completeness fight?

Mark every omission in the exhibit itself and point to where the full thread can be found. Silent gaps invite a Rule 106 completeness argument; marked gaps show the excerpt was made openly.

Keep the admitted exhibit clean. Put highlighting, callouts and arrows on a separately labeled demonstrative copy, or note on the page that highlighting was added by counsel. For very long threads, a summary chart of key messages may be offered under Rule 1006, which requires that the underlying records be made available to other parties; Rule 107 addresses illustrative aids used only to help the factfinder understand evidence. For presenting all of this on screen, see presenting electronic exhibits in court and on video.

What final checks should every message exhibit pass?

Before an exhibit goes into the binder, check redaction, numbering and readability in one pass.

In federal court, Federal Rule of Civil Procedure 5.2 limits certain personal identifiers in filings: the last four digits of Social Security and financial account numbers, the year of birth, and a minor’s initials. States have their own privacy rules, and family courts often have additional ones for children’s information. The guide to redacting personal identifiers in exhibits covers technique.

• Exhibit label on the first page; Bates or page number on every page; page X of Y
• Header block complete, with time zone stated
• Body text legible when printed and when projected
• Omissions marked with references to the complete thread
• Attachments cross-referenced to the appendix
• Personal identifiers redacted with a true redaction tool
• Searchable PDF with bookmarks for electronic submission
• Clean exhibit and demonstrative copies clearly distinguished

Much of this can be generated rather than hand-built. A tool like Message Extractor produces a chronological, paginated PDF log with sender, timestamp and channel on every message, attachment thumbnails with a full-size appendix, Bates-style numbering and an automated index; see a sample of the log layout. For where the finished exhibit goes next, the hearing exhibit binder checklist picks up from here, and the responsible attorney, licensed where the matter is pending, should confirm format requirements against local rules and the judge’s standing orders.