Two Recent Rulings Show Exactly Why
TL;DR
While metadata is vital in ESI production, it is not automatic. Under Rule 34, courts treat stripped metadata as unusable—yet recent federal decisions confirm judges won’t compel its production unless you specifically request it by name. Always explicitly demand metadata upfront to avoid waiving your right to it.
A judge compared a PDF production without metadata to a car without an engine. Another judge, ruling the opposite way weeks later. Both rulings are correct on their own facts, and that is exactly what makes them worth reading together. Metadata disputes are one of the more common, and more avoidable, fights in discovery right now, and two recent federal decisions map out both sides of the problem with unusual clarity. One shows what happens when a producing party strips metadata from a production the underlying documents needed to be usable at all. The other shows what happens when a requesting party never asked for metadata in the first place.
What Happened in Blevins-Clark v. Beacon Communities?
In Blevins-Clark v. Beacon Communities, LLC, No. 5:22-CV-00281-GFVT-MAS, 2025 U.S. Dist. LEXIS 189822 (E.D. Ky. Sept. 26, 2025), Magistrate Judge Matthew A. Stinnett ordered a defendant to redo a production after it turned over documents as PDFs with no accompanying metadata.
So what was the problem? Rule 34 of the Federal Rules of Civil Procedure requires that electronically stored information be produced “in a form or forms in which it is ordinarily maintained or in a reasonably usable form.” Judge Stinnett found the PDF-only production failed that standard outright, calling it “not a reasonably usable form” given current technology. The comparison he drew is important because producing documents without metadata is like manufacturing a car without an engine, a shell without much use.
Metadata is what tells a reviewer who created a document, when, what changes were made, and who touched it along the way. Strip that out and a PDF becomes a flat image of text, useful for reading but nearly useless for the kind of authentication and search work discovery requires. The court ordered the documents reproduced in a format that included the metadata Rule 34 calls reasonably usable.
What Happened in EEOC v. Alto Ingredients?
Four months later though, in EEOC v. Alto Ingredients, Inc., No. 1:24-cv-01269-JEH-RLH (C.D. Ill. Jan. 9, 2026), Magistrate Judge Ronald L. Hanna ruled that, on the surface, the outcome was the opposite.
In that case, the EEOC sought personnel files and documents related to a terminated employee, but its request for production never mentioned metadata. Judge Hanna held that Alto satisfied its obligation under FRCP Rule 34(b)(2)(E) by producing the documents in native form. Nothing in the rule required Alto to go further and preserve or produce metadata the EEOC never asked for.
The reasoning traces back to a principle that predates both cases: courts presume a producing party has no special obligation to preserve or produce metadata. A request has to call for it by name.
Requesting “all electronic documents” is not the same as requesting the metadata attached to them, and a court will not read that obligation into a request that does not contain it.
How Do These Two Rulings Fit Together?
They are not really in tension, even though they point in opposite directions on their facts. Blevins-Clark addressed what “reasonably usable” means once a production happens. Alto Ingredients addressed what a party must produce in the first place.
When you put the two side by side, the rule becomes clear. How? If a request calls for metadata, or if metadata is necessary to make the production usable at all, a court will require it under Rule 34’s reasonably usable form standard. If a request never mentions metadata, a court will not impose that obligation on a party.
That distinction puts the burden squarely on the requesting party to be specific.
A generic request for “all documents” or “all electronically stored information” leaves room for a producing party to hand over PDFs and point to Alto Ingredients as cover. A request that names metadata directly, and states what fields matter for the matter at hand forces the issue before production happens rather than after.
Why Does This Keep Coming Up as a Dispute Instead of Getting Resolved Upfront?
Part of the answer is cost. Producing full metadata across a large document population takes more processing time and more platform capability than a bare PDF export, and a producing party facing a tight budget has an incentive to produce the minimum the rule technically requires.
A requesting party that has not named its metadata needs gives that incentive room to run. Neither Blevins-Clark nor Alto Ingredients turned on bad faith. Both turned on the language the request itself used, which is exactly why the fix is so straightforward once a party knows to look for it.
The other part of the answer is habit. Plenty of requests for production still get drafted from templates built years before native-format review platforms became standard, and those templates often ask for “all documents” without ever mentioning metadata. A template built for paper discovery, or for early email-only discovery, does not anticipate a dispute over Slack export formats or system metadata on a modified spreadsheet.
Updating the template once solves the problem for every matter that follows, rather than relitigating the same gap case by case.
What Should a Request for Production Say?
- Name metadata explicitly, not by implication. “Produce all responsive ESI in native format, including all associated metadata” removes the ambiguity that let the producing party in Alto Ingredients limit its production to native files without metadata attached.
- Specify which metadata fields matter. Author, creation date, modification date, and recipient information cover the basics for most email and document disputes. A matter involving forensic questions about when a file was altered may need system metadata that goes well beyond those basics, and naming those fields upfront avoids a second fight later.
- State the production format directly. Native format, load files, or a specific document management platform export format all carry different metadata behavior. A request that leaves format unstated invites the kind of PDF-only production Blevins-Clark had to correct after the fact.
- Raise the issue at the meet and confer, not after production lands. Both cases show courts weighing what happened before a dispute reached a motion. A party that flagged its metadata needs early and got a clear answer is in a far stronger position than one raising the issue for the first time after an incomplete production already arrived.
What Does This Look Like Done Well?
On a recent matter involving a wrongful termination claim, the request for production specified native-format production for all email and document custodians, named the exact metadata fields needed for the authentication questions at issue, including sender, recipient, and modification history, and set that expectation in writing before the first custodian’s data was collected. When the production arrived, there was no dispute to litigate over format. The request had already answered the question a court would otherwise have had to answer for the parties.
That is the practical value in reading Blevins-Clark and Alto Ingredients together. Neither case is really about metadata in the abstract. Both are about what happens when a request does, or does not, say exactly what it needs.
Key Takeaways
- A PDF production without metadata can fail Rule 34’s reasonably usable form requirement, as Blevins-Clark v. Beacon Communities, LLC, 2025 U.S. Dist. LEXIS 189822 (E.D. Ky. Sept. 26, 2025), shows when metadata is necessary to make the production usable.
- Courts will not infer a metadata obligation from a generic request, as EEOC v. Alto Ingredients, Inc., No. 1:24-cv-01269-JEH-RLH (C.D. Ill. Jan. 9, 2026), shows. A request that never mentions metadata leaves a producing party free to withhold it.
- The fix sits entirely in how the request for production is drafted. Naming metadata, specifying fields, and setting format expectations before collection starts avoids a fight that both recent rulings show is entirely preventable.
Drafting a request for production and want to make sure it covers what your matter needs? Contact Complete Legal at info@completelegal.us or 888-885-9909. We can help you specify the metadata and format requirements that hold up if the other side pushes back.
📧 info@completelegal.us | 📞 888-885-9909
Related Articles: