ESI discovery is the process of requesting electronically stored information from the other side in a lawsuit, and getting it right depends on three things you have to line up in order: preserving your own data the moment litigation is foreseeable, drafting a request narrow enough that a court will enforce it, and locking down the format and privilege protections before a single file changes hands. Federal Rule of Civil Procedure 34 gives you the right to request ESI in any medium from which it can be retrieved.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things The rule is broad. Your request should not be.
What Counts as ESI
Emails and attachments still make up the bulk of most productions, but the category is much wider. Text messages, Slack and Teams chats, and social media posts are all fair game, and they often show intent more plainly than a formal email does. Database exports from accounting, CRM, or ERP systems establish financial and operational facts. GPS and mobile location data can place someone at a specific time. Voicemail, surveillance video, and other audio and visual files also qualify.
These files live in more places than people expect. Corporate servers and work laptops are the obvious sources, but cloud services, external drives, backup tapes, tablets, and personal phones used for work all hold discoverable data. Rule 34 reaches any electronic medium from which information can be obtained, directly or after translation into a usable form.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things Missing a storage location at the start creates problems you cannot fix later.
Preserve Before You Request
Your duty to preserve ESI does not wait for a formal discovery request. It starts the moment litigation is reasonably anticipated. That trigger is deliberately flexible: a demand letter, word that a former employee is considering suit, or an incident of the kind that has produced lawsuits in the past can all activate it. You do not need certainty. Reasonable foreseeability is enough.
Once the duty attaches, issue a written litigation hold to everyone who might control relevant data. A workable hold identifies the dispute, describes the categories of information that must be kept, and tells recipients to suspend any automatic deletion, whether that is an email purge rule or a scheduled document destruction routine. Send it to every custodian, not just the records department. Update and reissue it as the case develops and new people or systems become relevant, and send periodic reminders so employees do not quietly resume cleaning out their inboxes.
If ESI that should have been preserved is lost because a party failed to take reasonable steps, and the data cannot be restored or replaced through other discovery, the court can impose sanctions under Rule 37(e).2Legal Information Institute. Federal Rules of Civil Procedure Rule 37 – Failure to Make Disclosures or to Cooperate in Discovery For negligent loss, the court can order measures no greater than necessary to cure the prejudice: monetary sanctions, fee-shifting, or a court-ordered forensic exam. If the court finds you acted with intent to deprive the other side of the information, the remedies escalate sharply. A jury can be told to presume the lost data was unfavorable, or the case can be dismissed or a default entered against you. A well-documented hold is your best defense if a spoliation fight ever comes.
Building a Request That Will Actually Work
A demand for everything on the other side’s servers will draw objections and go nowhere. Courts expect targeted requests, and the targeting happens before you draft. Four decisions do most of the work.
Name the Custodians
A custodian is the person who created, received, or managed the relevant data. In a contract dispute, that is often the project manager and the executives who approved the deal. In an employment case, it might be the supervisor, HR, and the employee’s direct reports. Listing custodians by name narrows the search, reduces the producing party’s burden, and gives you a defensible request.
Set the Date Range and Search Terms
A date window tied to the events at issue is far more defensible than an open-ended sweep. Combine it with keywords that actually distinguish relevant material: names of key people, project titles, product codes, or phrases specific to the dispute. Generic terms like “contract” or “meeting” return too much noise and hand the other side a ready-made objection. Test proposed terms by exchanging hit counts and sampling results before you finalize the list, and agree on a validation process so no one can argue later that the search was inadequate.
Specify the Metadata
Metadata is the background information embedded in every electronic file: who authored it, when it was created, when it was last modified, and so on. It is what lets you authenticate a document, build a timeline, and show that a file has not been altered. The SEC’s data delivery standards are a useful reference for the fields commonly requested, including author, date created, date last modified, file name, file extension, custodian, sender and recipient fields for email, and an MD5 hash value that acts as a digital fingerprint.3U.S. Securities and Exchange Commission. Data Delivery Standards Ask for the fields by name in the request. Silence about metadata invites disputes about what “complete” production means.
Map the Sources
Find out where the data actually lives before you draft. Does the opposing party use Google Workspace, Microsoft 365, or Dropbox? Are there local drives, network shares, backup tapes, or personal devices used for work? Identifying sources in advance lets you write a request that names them and puts you in a stronger position if the other side later claims certain data does not exist.
Keeping the Request Proportional
ESI discovery gets expensive fast, and courts will not let one side pile unlimited cost on the other. Rule 26(b)(1) requires all discovery to be proportional to the needs of the case, weighed against the importance of the issues, the amount in controversy, the parties’ relative access to information, their resources, the importance of the discovery to resolving the case, and whether the burden outweighs the likely benefit.4Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery A $50,000 dispute does not justify a $200,000 e-discovery bill. Keep the ratio realistic when you draft, because the other side will raise it in objections if you do not.
Some data is genuinely hard to reach: backup tapes, legacy systems, damaged media. Under Rule 26(b)(2)(B), a producing party does not have to produce ESI from sources it identifies as not reasonably accessible because of undue burden or cost.4Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery The producing party has to prove inaccessibility. If it does, you can still get the data by showing good cause, but the court may shift retrieval costs to you or attach other conditions. Cost-shifting disputes often turn on how tailored the request is, whether the information is available elsewhere, and the cost relative to the amount at stake. Some courts skip the inaccessibility analysis entirely and go straight to Rule 26(b)(1) proportionality.
Specifying the Form of Production
The format the data arrives in is one of the most consequential choices in the whole request. Rule 34(b)(2)(E) says that if you do not specify a form, the producing party can deliver ESI in the form it is ordinarily maintained or in any reasonably usable form.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things Leaving that choice to your opponent is almost always a mistake.
Native format means files delivered exactly as they were created: an Excel spreadsheet as an .xlsx, an email as a .msg or .eml. Native production preserves metadata, formulas, and embedded content, but Bates-stamping native files for use at trial is awkward. Image format, usually TIFF or PDF, delivers a static picture of each page that is easy to stamp and use in a courtroom but strips out interactivity. You cannot click through an Excel formula or see hidden columns in an image. Many productions use a hybrid: images for most documents and native files for spreadsheets, databases, or anything else where the static image loses too much.
When ESI is produced as images, a load file is what makes the production usable. It pairs each image with its metadata, Bates numbers, family relationships such as an email and its attachments, and extracted text. Without a load file, you receive a stack of images you cannot search or organize. Say in the request that the production must include load files compatible with standard review platforms.
A well-drafted request for production names the custodians, the date range, the categories of documents and ESI sought, the metadata fields, and the file format. Spell all of it out. Vague requests get vague productions, and cleaning up a bad production costs more than writing a good request in the first place.
Serving the Request and the Rule 26(f) Conference
Serving a request for production starts a 30-day clock for the other side’s written response.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things In federal court, service usually runs through the electronic filing system. Missing the 30-day window can waive objections, so both sides watch the calendar.
Before discovery gets going, the parties have to confer under Rule 26(f) and put together a proposed discovery plan. That plan has to address ESI issues, including the forms of production and any preservation concerns.4Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery The meet-and-confer is where the practical details actually get settled: which file formats each side can handle, how to deal with proprietary or legacy data, volume estimates, naming conventions, transmission methods, encryption, and delivery deadlines.5United States Courts. Recommendations for Electronically Stored Information Discovery Production in Federal Criminal Cases It is also the moment to raise a Rule 502(d) clawback order (covered below). The court’s Rule 16(b) scheduling order can then formally incorporate whatever the parties agreed to.6Legal Information Institute. Federal Rules of Civil Procedure Rule 16 – Pretrial Conferences; Scheduling; Management
The written response either agrees to produce or raises specific objections such as overbreadth, disproportionate cost, or privilege. If the parties cannot work it out, the requesting side can move to compel under Rule 37(a), and the losing side on the motion usually pays the winner’s reasonable expenses, including attorney’s fees.2Legal Information Institute. Federal Rules of Civil Procedure Rule 37 – Failure to Make Disclosures or to Cooperate in Discovery
Handling Large Document Volumes
When a collection runs into hundreds of thousands or millions of documents, manual review is not realistic. Two approaches narrow the pile.
Keyword searching is the simpler one. The parties agree on terms, run them, and review the hits. The weakness is that keywords are blunt. A term like “termination” pulls in every IT ticket about ending a software license along with the emails about firing an employee, and if the real communications used euphemisms or abbreviations, the search misses them. Test terms before locking them in. Exchange hit counts, review samples, and agree on a validation process so no one can attack the search after the fact.
Technology-assisted review, or predictive coding, uses machine learning instead. Attorneys code a sample set as responsive or not, the software scores every document against that sample, and the team reviews and corrects a second sample so the system retrains. The cycle repeats until results stabilize.7Federal Judicial Center. Technology-Assisted Review for Discovery Requests TAR works best on large collections where responsive documents share common features. It struggles when responsiveness turns on a unique identifier that a keyword would catch more reliably. Two metrics matter when you evaluate results: precision (of what the system flagged, how much was actually relevant) and recall (of everything relevant in the collection, how much the system found). Set acceptable rates during the Rule 26(f) conference along with quality-control procedures.
After Production: Privilege Logs and Clawback Orders
When the data arrives, verify it before you build a case on it. Check the formats, confirm the metadata fields are populated, and load the files into your review platform to make sure the load files actually work. Gaps are much easier to fix now than later.
If the producing party withholds documents for attorney-client privilege or work-product protection, it has to describe what it withheld in enough detail for you to evaluate the claim without revealing the privileged content.4Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery That means a privilege log: date, author, recipients, general subject, and the legal basis for withholding each document. Read the log carefully. Boilerplate entries sometimes hide improper withholding, and courts will order production when a log fails to justify the claim. If a privilege dispute cannot be settled, the court can review the documents in camera to decide whether the privilege applies, and losing parties can face sanctions or search-cost orders.2Legal Information Institute. Federal Rules of Civil Procedure Rule 37 – Failure to Make Disclosures or to Cooperate in Discovery
Privileged material sometimes slips into a large production no matter how careful the review. A clawback order under Federal Rule of Evidence 502(d) protects both sides from that risk. The rule lets a federal court order that a disclosure in connection with the litigation does not waive privilege, and that protection extends to other federal and state proceedings.8Legal Information Institute. Federal Rules of Evidence Rule 502 – Attorney-Client Privilege and Work Product; Limitations on Waiver Under a typical 502(d) order, if the producing party discovers it accidentally handed over privileged material, it notifies the receiving party, who has to return or destroy the material and all copies within a set time. The receiving party cannot argue that the accidental disclosure itself waived the privilege.
Negotiate the 502(d) order at the Rule 26(f) conference, before production starts. Both sides can then run privilege review more efficiently because a single missed document is not catastrophic. Skipping this step is one of the most preventable errors in ESI discovery. Without a 502(d) order in place, an inadvertent production of a single privileged email can be treated as a waiver, exposing attorney strategy and confidential communications for the rest of the case.