If “Junk” Is Responsive to Your Request, You Can’t Complaint About Getting “Junk”

If “Junk” Is Responsive to Your Request, You Can’t Complaint About Getting “Junk”

EDRM (Electronic Discovery Reference Model)
EDRM (Electronic Discovery Reference Model)Jun 1, 2026

Companies Mentioned

Why It Matters

The ruling clarifies that courts will enforce the form and scope outlined in the request, placing the onus on litigants to draft focused discovery demands and to raise objections promptly, which reshapes e‑discovery strategy across federal cases.

Key Takeaways

  • Court affirmed PDF production met Fed.R.Civ.P. 34(e) requirements.
  • Plaintiffs failed to request native format in their RFP.
  • “Junk” documents deemed responsive when request is overly broad.
  • Late objections dismissed; production timing upheld by court.

Pulse Analysis

The Ann Arbor case highlights a growing tension between high‑volume e‑discovery and the practical limits of document production. While parties often seek native files for seamless review, the court emphasized that the discovery request itself must specify that format. By interpreting the request’s language strictly, the judge upheld the City’s choice to deliver searchable, bookmarked PDFs, a common industry practice that balances accessibility with cost control. This outcome signals that discovery plans alone cannot override the precise wording of a request.

Equally pivotal is the court’s treatment of “junk” documents. The plaintiffs argued that thousands of blank pages and third‑party newsletters were irrelevant, yet the court ruled that responsiveness hinges on the request’s breadth, not the usefulness of the output. When a request asks for all communications containing a keyword over a multi‑year span, the producing party is not obligated to filter out every non‑pertinent item. This reinforces the “legal right” test: producers meet their duty if the documents fall within the literal scope of the request, even if many are of limited evidentiary value.

For practitioners, the decision underscores two actionable best practices. First, draft discovery requests with explicit form specifications—such as “native format” or “PDF only”—to avoid ambiguity. Second, anticipate the inclusion of peripheral material by narrowing temporal or custodial parameters, thereby limiting the volume of “junk.” Promptly raising objections, ideally within the production window, remains essential; delayed challenges are unlikely to succeed. As courts continue to prioritize request language over post‑production grievances, meticulous request design will become a cornerstone of cost‑effective e‑discovery.

If “Junk” is Responsive to Your Request, You Can’t Complaint About Getting “Junk”

Comments

Want to join the conversation?

Loading comments...