A Paralegal’s Guide to Text Message Logs Courts Can Actually Use

When the attorney asks for “a log of the texts,” they want something better than a stack of screenshots: a document that shows every relevant message in order, identifies who sent what and when, can be cited by page number, and can be tied back to the phone or account it came from. That is a text message log for court, and building one is mostly a paralegal job.

This guide walks through the build from source to finished PDF. It covers what to collect, the steps in order, how to handle the messy parts (group chats, reactions, attachments, deleted messages, time zones), how the log fits authentication and redaction rules, and the QC pass that catches errors before opposing counsel does. Rule references are to the Federal Rules of Evidence and Civil Procedure; state versions often track them but vary, so the attorney confirms what applies in your forum.

What makes a message log different from screenshots?

Completeness, structure and traceability. Screenshots show what someone chose to capture; a log shows the conversation as the data records it.

Screenshots still have a role as a map: they show which conversations the client thinks matter. But a log built from the export is what the attorney will want to rely on.

Where does the data for a message log come from?

From an export of the device or account. Each platform has its own route, and each produces a different format.

• iPhone messages: desktop tools such as iMazing can export iMessage and SMS conversations to CSV or Excel. See exporting iMessages for litigation for the options.
• Android messages: apps such as SMS Backup & Restore produce an XML file of text and multimedia messages.
• WhatsApp: the app’s built-in export chat feature, with or without media.
• Facebook and Instagram: the platforms’ download-your-information tools.
• Google Voice: Google Takeout.
• Email: native message files rather than printouts.

Record the export details as soon as the file arrives: who made it, when, from which device or account, with which tool and settings, and the date range covered. Hash the export file on receipt so you can later show the log was built from that exact file.

How do you build a text message log, step by step?

Confirm scope, ingest and fingerprint, normalize, then paginate and document. The order matters because each step depends on the one before it.

1. Confirm scope with the attorney. Which participants, which threads, which date range. Build an unfiltered master even if the working version will be filtered.
2. Ingest and hash the sources. Keep the export files untouched and record a SHA-256 hash for each.
3. Normalize into one thread model. Map every phone number or account to a name in a participant table, and label each message’s channel (SMS, iMessage, WhatsApp and so on).
4. Merge duplicates. The same message can appear in two exports, for example from two backups of the same phone. Merge them without dropping either source from the manifest.
5. Set the time zone basis. Decide whether times display in local time or UTC and state it on the cover page.
6. Handle attachments. Reference each attachment in line, with a thumbnail where useful, and place full-size images in an appendix.
7. Paginate and Bates number. Use the matter’s numbering convention; see the Bates numbering guide.
8. Index and document. Add an index by date and participant, a source manifest listing every input file and its hash, and a hash of the finished PDF.

Software does most of this mechanically. A tool like Message Extractor auto-detects common export formats, merges duplicates into one thread model, and produces a chronological, paginated PDF log with sender, timestamp and channel, attachment thumbnails with a full-size appendix, Bates-style numbering, an index and a SHA-256 digest. The paralegal’s value is in scoping it correctly and checking the result.

Whatever tool builds the log, the cover page should let a reader understand it without asking anyone.

How should tricky message types be handled?

Label them; never silently drop or “clean up” anything. Every editorial choice should be visible in the log or in a note to the attorney.

Group chats

List every participant on the cover page and identify the sender on every line. Note when participants joined or left, if the data shows it.

Reactions and cross-platform artifacts

Reactions sent between different platforms can arrive as standalone text lines, such as the word “Liked” followed by the quoted message. Leave them in and label them, because the reaction itself may matter.

Deleted, edited and unsent messages

An export reflects the data at the moment it was made. Messages deleted earlier may simply be absent, and edits may not appear the way they did on screen. Do not fill gaps from memory or screenshots inside the log; flag them for the attorney.

Conversations that move between apps

People often switch between SMS, iMessage and WhatsApp with the same person, sometimes on the same day. If the attorney wants the whole conversation, export each channel, merge the results into one chronological log, and keep the channel label on every line. A gap that lines up with a channel switch may mean a missing export rather than missing messages, so check before reporting it as a gap.

Contact names

The name on the phone is the owner’s label, not proof of identity. The participant table should show the underlying number or account for every name.

How is a message log authenticated and certified?

The paralegal prepares the materials; the attorney chooses the route. The common paths in federal court are:

• Testimony under Rule 901. A witness with knowledge, such as a participant in the conversation or the person who made the export, plus distinctive characteristics of the messages themselves. See authenticating text messages under Rule 901.
• Certification under Rule 902(14). Data copied from an electronic device or file, authenticated by a process of digital identification such as a hash and certified by a qualified person. Rule 902(13) covers records generated by an electronic process. Both require the reasonable written notice described in Rule 902(11).
• Completeness under Rule 106. If the log is filtered, the unfiltered master answers the inevitable request for the rest of the conversation.

Whether individual messages are hearsay, party admissions or offered for a non-hearsay purpose is a separate question for the attorney. A declaration template can speed up a certification, but counsel completes it and decides whether to use it.

What needs redacting before a message log is filed?

Whatever the court’s privacy rules require, plus anything a protective order covers. In federal filings, Rule 5.2 generally limits filings to the last four digits of Social Security and financial account numbers, the year of a person’s birth, and a minor’s initials. State courts have their own rules, and family courts often have additional protections for children.

• Keep the unredacted master; redact a copy.
• Use true redaction that removes the underlying text, not a black box drawn over selectable text.
• Log every redaction with its page and reason.
• Distinguish what is filed with the court from what is produced in discovery; the rules differ.

What should the QC pass check before the log goes to the attorney?

Counts, boundaries, numbering and anything that was transformed.

• The message count in the log matches the source for the stated scope.
• The first and last messages match the device or export.
• A random sample of messages matches the source word for word.
• Bates numbers run in sequence with no gaps or duplicates.
• Index page references land on the right pages.
• The time zone basis is stated and consistent.
• Every participant name maps to a number or account.
• The attachment appendix is complete and cross-referenced.
• The source manifest lists every input file and hash.
• Any filtered version states its filters on the cover page.
• Redactions cannot be selected, copied or searched.

Authentication, hearsay and disclosure decisions belong to the supervising attorney licensed where the matter is pending. A clean, complete, well-documented log means those decisions are made on solid ground.