Valcrum, LLC v. Dexter Axle Co. (N.D. Ind. July 15, 2026)

‍

Why This Case Is Important

This ruling highlights the unique challenges of producing short-form messages like Microsoft Teams. It demonstrates that when parties fail to negotiate a specific ESI (Electronically Stored Information) protocol for chat context, courts will independently impose solutions, penalizing boilerplate objections and inadequate, standalone search techniques.

Overview Text

In Valcrum, LLC v. Dexter Axle Co., the parties engaged in a trademark dispute over a hubcap design. Valcrum sought discovery of Dexter Axle’s Microsoft Teams messages. Initially, the defendant produced standalone Teams messages based on search-term hits, completely disconnected from their surrounding conversations. Later, a supplemental production revealed fully threaded chronological chats, exposing the missing context from earlier productions. Valcrum moved to compel the entirety of the Teams messages organized into full threads, plus unredacted copies of previously assembled threads.

Unlike the agreed-upon message-count formula seen in Lubrizol Corp. v. IBM Corp., neither party here provided a workable protocol for short-form messages. Although Valcrum filed a defective meet-and-confer certification, the court excused the procedural defect, finding further conferral futile. The court then tackled the complexities of chat context and the ongoing duty to supplement under the Federal Rules.

Ruling Summary

• Duty to Supplement Enforced
  The defendant argued Valcrum's motion to compel was untimely, but the court firmly rejected this attempt to shift blame. The court noted this argument "improperly shifts the burden onto Plaintiff for requesting supplemental discovery material while ignoring its own duty to supplement." Because "Rule 26(e) imposes a duty to supplement on a responding party in a timely manner," the court officially excused the plaintiff's delay in filing the motion.
• Keyword Searches Inadequate for Teams
  Addressing the scattered production, the court held that "Keyword searches alone, without more advanced and thoughtful search techniques, will be inadequate for Teams data—a medium where conversations are shorter, more informal, and less likely to include full names than email." Borrowing from Deal Genius, LLC v. O2Cool, LLC, the court ordered the production of messages "three days before and after the single communications already produced in order to provide context."
• Boilerplate Redactions Waived
  When challenging the unredacted production of the threaded chats, the defendant claimed the requests were overly broad, vague, and not proportional. The court struck this defense down, echoing the precedent in McGrath v. Everest National Insurance Company. Because the defendant "does not elaborate further on its objections," the court determined that "they are deemed waived." Consequently, the court ordered that "the threaded Teams conversations must be produced in their entirety."

Expert Analysis

What stands out is the court's emphasis on its own discretion. The court noted it holds broad latitude to shape discovery rulings, saying it "behooves [it] ‘to independently determine the proper course of discovery based on the arguments of the parties’” rather than simply granting or denying what either side requested. Here, that meant ordering a three-day window around each responsive message, a remedy neither party proposed. Practitioners should note that leading review platforms should be able to render Teams data in near-native, threaded chat bubbles. Resisting that format to avoid making review easier for opposing counsel isn't a viable strategy; cooperative discovery practice and the courts expect parties to meet their disclosure obligations proactively, not just when compelled.

‍

Tip Text

Ensure your internal technical understanding of modern chat platforms aligns with your preservation strategy to avoid relying on inadequate, standalone keyword searches. Negotiate context mechanisms accordingly, such as specific message-count or time-based windows, in your initial ESI protocol. Failing to propose a tailored solution leaves you vulnerable to a court importing an ill-fitting formula from unrelated cases. To master how the Federal Rules apply to modern, short-form data, download Exterro’s Layman’s Guide to the FRCP.