The other side’s production of text messages just arrived. It may be a tidy Bates-numbered log, or it may be forty screenshots in a ZIP file with a cover email. Either way, the first question is not what the messages say but whether you received everything you asked for, in the form you asked for it. That review is what turns a vague sense that “something is missing” into a deficiency letter specific enough to fix the problem.

This guide sets out a review workflow for the receiving side, from logging the delivery to the meet-and-confer. It pairs with our guide to drafting requests for production of text messages, which covers the request that sets the standard you are reviewing against. Rule references are to the Federal Rules of Civil Procedure; state rules often track these concepts with different numbering.

What should you check the moment a production arrives?

Treat the delivery as evidence before treating it as reading material. Log it, fingerprint it and check that it is internally whole:

  • Date received, delivery method, sender and the cover letter or email that came with it
  • The Bates range claimed in the cover letter, and the range actually present
  • No skipped numbers, repeated numbers or unnumbered pages inside the range
  • Every file listed in the cover letter or manifest is present and opens
  • A SHA-256 value recorded for each file on arrival, compared with any hash values the producing party listed
  • Confidentiality designations noted, so the production is stored and shared under the protective order

Store the delivery as received and work only from copies. If a later dispute turns on what was produced and when, the untouched delivery and its hash values are your answer.

Does the production match the written response?

Hold the production against the written response request by request. Under Rule 34(b)(2)(C), an objection must state whether responsive materials are being withheld on that basis, so the response tells you what to expect:

The response saysCheck in the productionRed flag
Messages with [Name] from [date] to [date]First and last message dates in each threadThreads start late or stop early
Produced as a PDF log with the source exportThe source file and its manifest entryLog only, with no source file
Nothing withheldContinuity of dates and conversation flowReplies to messages that are not there
Withheld on privilegeA privilege log describing each itemNo log, or entries too vague to assess
Redacted for privacyVisible, labeled redactions and a redaction logUnlabeled black boxes or cropped messages

Note every mismatch with the request number and Bates page. Those notes become the deficiency chart later, so write them in a form you can paste.

How do you run a gap analysis against your client’s side?

Your client was a participant in many of these threads, so their own export is the best map of what a complete production should contain. The comparison works in four steps:

  1. Collect your client’s side properly. Use a device or backup export with full dates, years and phone numbers, logged and hashed like any other evidence. Screenshots make a poor comparison source; see producing text messages in discovery for collection steps.
  2. Put both sides on one timeline. Normalize both sets to the same time zone, then merge them so each message appears once. Our guide to deduplication and threading explains how duplicate copies are matched.
  3. Sort into three groups. Messages in both sets, messages only on your client’s side and messages only in the production. The second group is your deficiency list; the third deserves a quiet look too, since it may show messages your client no longer has.
  4. Look for patterns, not just counts. Gaps of days or weeks, threads that begin mid-conversation, one side of an exchange missing, attachments referred to but not produced, group chats with participants dropped, and messages with no year or zone.

When the other side produced a source export, loading it next to your client’s export in Message Extractor, which auto-detects common formats and merges duplicates into one chronological thread model, gives reviewers a single timeline to compare instead of two stacks of pages.

Is the form of production what you asked for?

A complete set of messages can still be deficient if it arrives in a form that strips what you need. Check each item against the form your request specified:

  • Screenshots instead of an export. Cropped images usually lose years, phone numbers, attachments and per-message times.
  • Missing fields. A log without sender identifiers, a stated time zone or attachment references makes authentication and chronology harder.
  • Image-only PDFs. Pages that are not text-searchable slow review and may fall short of a reasonably usable form.
  • No objection to the form. Under Rule 34(b)(2)(D), a party objecting to a requested form must say so and state the form it intends to use. Producing a different form without saying so is itself a point for the letter.

How do you check the privilege log and redactions?

Withheld and redacted material needs its own pass. Confirm that each withheld message or thread appears on a privilege log with enough detail to assess the claim, that every redaction is visible and labeled with a reason, and that the redactions match what the parties agreed, for example unrelated third-party content only. Redactions that remove whole stretches of a conversation without a label, or a log that says only “privileged communications,” belong in the letter. See the privilege log guide for what a usable entry contains.

What belongs in a deficiency letter?

Specifics. A letter that says “your production is incomplete” invites a reply that says “it is not.” A letter that lists the request, the Bates pages, the dates and the missing count invites a supplement. Organize it by request number and include:

  • The request and response at issue, quoted or cited
  • Each gap, with dates, threads, message counts and Bates pages
  • The basis for knowing about the gap, such as your client’s records
  • Any form-of-production problem, privilege log or redaction issue
  • A question whether anything is being withheld, if the response is silent
  • The cure requested, a date to respond and proposed times to confer

Template: deficiency letter, one request

Request No. [number] asked for all Messages between [Party] and [Name] from [date] through [date], in the form described in Instruction [number]. Your production of [date] (Bates [PREFIX]-[number] through [PREFIX]-[number]) includes Messages in that Thread from [date] through [date] only. Our client’s records show [number] Messages in the Thread between [date] and [date], including Messages on [dates], none of which appear in the production. The production also omits the attachments referenced on [PREFIX]-[number] and [PREFIX]-[number], and consists of screenshots rather than the requested export, without an objection to the form. Please produce the missing Messages and attachments in the requested form, or confirm in writing whether any responsive Messages are being withheld and on what basis, by [date]. We are available to confer on [dates and times].

What happens after the letter?

Calendar the response date, then confer. Use the call to narrow the dispute: confirm what source the other side collected from, what filters it applied and whether a supplement is coming. Our ESI meet-and-confer checklist lists the technical questions worth asking. Confirm any agreement in writing, including the date for a supplemental production and its Bates range; the producing side’s obligations are covered in supplementing discovery responses.

If conferring does not resolve it, a federal motion to compel under Rule 37(a)(1) must include a statement that the movant conferred or tried to confer in good faith, and many local rules add their own steps. The deficiency letter, the conference notes and the gap analysis are the record that motion would rest on.

What mistakes weaken a deficiency review?

MistakeConsequenceFix
Reviewing the only copy of the deliveryNo clean record of what was producedHash on arrival; work from copies
Comparing against client screenshotsGaps that cannot be provenCompare against a dated, hashed export
A general “incomplete” letterA general denial in replyCite requests, Bates pages, dates and counts
Assuming deletion from a gapAn accusation the record does not supportAsk about sources and filters first
No follow-up dateThe dispute drifts past the cutoffCalendar the response and the conference

Whether to press a deficiency, seek a device examination or file a motion are strategic decisions for the supervising attorney; staff build the record that informs them. Family, housing and state trial courts often handle discovery disputes differently from the federal model, so confirm local practice with counsel licensed where the matter is pending.