Context is King: Court Rejects "Isolated" Teams Messages Production as Unusable

Why This Alert Is Important

This ruling underscores that producing ESI is not merely about providing a readable file format; it is about maintaining the integrity and usability of the information. As workplace communication shifts toward collaboration platforms like Microsoft Teams, courts are increasingly skeptical of "keyword-only" productions that strip away the surrounding conversation. Failing to provide sufficient context can render a production "incomplete" under Rule 34.

Overview Text

In Soqui v. England Logistics, Inc., a former employee alleged he was terminated after requesting a work-from-home accommodation for a disability. During discovery, plaintiff issued Requests for Production (RFPs) seeking "all documents [and] communications" concerning his accommodation request and the basis for his eventual termination. In response, defendant England Logistics produced more than 100 individual Teams messages that apparently hit on specific keywords. However, defendant produced these messages in chronological order as isolated snippets, omitting the surrounding conversation threads.Plaintiff moved to compel production of the surrounding messages, arguing the production was incomplete and unusable. Defendant opposed the motion on proportionality grounds, claiming that it would take its current IT director “at least fifty or sixty hours” to recreate the searches and export the full conversations in a different format. The court was not persuaded by defendant’s "burden" argument, noting that the difficulty was a "problem of England’s own making" by choosing an inadequate production method initially. It ordered defendant to produce “the entirety of any Teams conversation containing twenty or fewer total messages that ha[d] at least one responsive message,” and, for longer conversations, “the ten messages preceding or following any responsive Teams message,” but denied plaintiff’s request for attorney’s fees.

Ruling Summary

• Usability not a “file format” issue The court determined that producing only Teams messages containing search terms, without surrounding context, was "not fully responsive" to the RFPs at issue. Magistrate Judge Oberg noted that "responsive documents include messages containing the entire conversation regarding these topics—not just isolated, individual messages". By stripping away the thread, defendant failed to fulfill its obligation to provide a complete response under Rule 34.
• Usability Requires Contextual Relevance Regardless of whether the file format (MSG) was standard, the court found the production "entirely unusable" because the lack of context made it "impossible to determine what the messages are about". The court emphasized that, under Rule 34, ESI must be produced in a "reasonably usable form". When messages are presented without their surrounding dialogue, they lose their evidentiary value and fail to meet this procedural threshold.
• Self-Imposed Burdens Do Not Excuse Compliance The court rejected defendant's proportionality argument, reasoning that the 60-hour labor estimate was not "unduly burdensome" given the central importance of the communications. Magistrate Judge Oberg remarked that the burden was "largely a problem of England’s own making" because defendant chose to produce "isolated messages in the first place". Furthermore, a change in IT personnel does not "excuse the need for a fulsome response."

Expert Analysis

Patricia Antezana, Counsel, Reed Smith

Parties should discuss reasonable parameters for the collection of text or collaborative platform messages if relevant to the parties’ claims or defenses early in the case. As the Committee Notes to the 2006 Amendments to Rule 34 recognize, “the option to produce in a reasonably usable form does not mean that a responding party is free to convert [ESI] from the form in which it is ordinarily maintained to a different form that makes it more difficult or burdensome for the requesting party to use the information efficiently in the litigation.”

‍

Tip Text

To avoid the re-do costs seen in this case, parties should reach a consensus on the unit of production (e.g., full threads vs. a specific message buffer) during the Rule 26(f) meet-and-confer. For more practical tips on navigating these requirements, download Exterro’s Guide to the FRCP to ensure your production protocols meet judicial standards for usability and completeness.

‍