A sample electronic discovery request works only if its bones are right: named custodians, a defined date range, identified systems, and category descriptions specific enough that the other side cannot plausibly claim it did not understand what to search for. Federal Rule of Civil Procedure 34 requires each request to describe the items sought with “reasonable particularity,” and anything looser gets objected down before a file is produced.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes The language below is built to survive that first round of objections.
Why Particularity Decides Everything
Two rules do most of the work. Rule 34 sets the particularity standard. Rule 26(b)(1) requires that discovery be proportional to the needs of the case, weighing the stakes, the parties’ resources and relative access to information, and whether the burden of production outweighs the likely benefit.2Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery
Those two constraints push in the same direction. A request for “all documents related to the defendant’s business operations” fails both. A request for “all emails between John Smith and Jane Doe regarding the Acme project between January 1, 2024 and December 31, 2025” satisfies both. Every drafting choice described below is really a choice about moving from the first kind of language to the second.
Define Custodians, Dates, and Data Sources First
Before writing any category, lock down three definitions at the top of the request. These become defined terms you reference throughout, so each category stays short and specific.
Custodians
List the specific people whose files and communications you want searched, by name. These are the employees, executives, or agents directly involved in the events behind the lawsuit — the people making decisions, sending relevant communications, or handling the transactions at issue. Requesting ESI from every employee in a department is what triggers proportionality objections.
Relevant Period
Set a clear start and end date tied to the dispute’s timeline. If the contract was signed in March 2024 and the breach occurred in October 2025, the period might run from January 2024 (to capture pre-contract negotiations) through the present. Open-ended ranges like “from the inception of the company” invite narrowing unless you can justify why older data matters.
Relevant Systems
Identify the systems by name: email servers, shared network drives, cloud storage platforms, accounting software, CRM databases, collaboration tools like Slack or Microsoft Teams, and individual devices like laptops or mobile phones. Specificity here prevents the responding party from claiming confusion about scope and shows the court the request is targeted rather than a fishing expedition.
Sample Language by Category
With Custodians, Relevant Period, and Relevant Systems defined up front, each category below can stay focused on subject matter. Adapt the bracketed terms to the facts of your case.
“All emails and email attachments sent to or received by the Custodians during the Relevant Period that contain any of the following terms: [Project Orion], [merger], [due diligence], or that were sent to or received from any employee of Acme Corp.”
Keyword terms and specific sender/recipient addresses keep the request focused. Without them, you are asking for every email a custodian sent over a multi-year period, which courts routinely find disproportionate.
Slack, Teams, and Other Collaboration Tools
Threaded conversations, auto-deleting ephemeral messages, and inline file sharing make collaboration tools unlike email. Tailor the request to the platform and name the specific channels:
“All messages, shared files, and channel content from the [#project-orion] and [#finance-review] channels in [Defendant’s Slack workspace / Microsoft Teams environment] during the Relevant Period, including any direct messages between the Custodians concerning [Project Orion] or [the proposed acquisition].”
If you do not yet know the channel names, that is a question for the Rule 26(f) conference.
Structured Data and Databases
For data in databases, accounting systems, or large spreadsheets, precision matters more than anywhere else. Identify the system by name and specify which fields or records you need:
“All records from [Defendant’s SAP accounting system] for transactions coded to [cost center 4400] or [project code PO-2024] during the Relevant Period, including the following fields: transaction date, amount, vendor name, approving officer, and associated purchase order number.”
Requesting an entire database export when you only need certain fields or records is the fastest way to trigger a cost-shifting motion.
Documents and Files
For files on network drives, cloud storage, or local devices, describe categories by subject matter rather than file type:
“All documents, spreadsheets, presentations, and draft agreements stored on the Relevant Systems by the Custodians during the Relevant Period that relate to the negotiation, execution, or performance of the [Supply Agreement dated March 15, 2024].”
Specify the Production Format and Demand Metadata
Rule 34 lets you specify the form of production, and if you do not, the responding party can produce in whatever form it ordinarily keeps the data or in any “reasonably usable” form.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes That choice may not serve you. Always specify.
The two main options are native format and image format. Native files (the original .docx, .xlsx, .pptx, or .msg files) preserve full functionality: tracked changes stay visible, spreadsheet columns sort, and documents remain searchable. Image format (TIFF or PDF) creates a static picture of each page, which is easier to Bates-stamp and mark as exhibits but strips interactive features. Most practitioners request native files for spreadsheets and databases, and TIFF or PDF images with accompanying load files for everything else.
Whichever format you pick, require that metadata be preserved and produced. Metadata is the background information embedded in every file: author, creation date, last-modified date, file path, and for emails, the complete header fields including recipients, timestamps, and subject lines. Without it, you lose the ability to establish who created a document, when it was last edited, or whether it was forwarded to someone the opposing party claims never saw it. A production stripped of metadata is functionally incomplete.
One limit worth knowing: Rule 34 prohibits requiring the same ESI in more than one form. You can request native or imaged format for a given set of documents, not both.
Preservation Instruction
The duty to preserve ESI attaches under Rule 37(e) when a party reasonably anticipates litigation, which for a defendant can be as early as a demand letter or internal complaint.3Legal Information Institute. Federal Rules of Civil Procedure Rule 37 – Failure to Make Disclosures or to Cooperate in Discovery Your request does not create that duty, but a preservation instruction eliminates any argument that the other side did not know what categories of data you considered relevant.
Include language directing the responding party to suspend routine deletion of the Relevant Systems for the Custodians during the Relevant Period, and to preserve server backups, archived mailboxes, mobile device data, and any ephemeral messaging data within scope. Identify the specific data sources you expect preserved. If data is later lost, that written record matters: the most severe Rule 37(e) sanctions — including adverse inferences and case-ending orders — require a finding that the party acted with intent to deprive the other side of the evidence.3Legal Information Institute. Federal Rules of Civil Procedure Rule 37 – Failure to Make Disclosures or to Cooperate in Discovery
Privilege Log Instruction
Build a standing instruction into your request requiring a privilege log for anything withheld on attorney-client or work-product grounds. Rule 26(b)(5)(A) requires the withholding party to expressly claim the privilege and describe each document in enough detail that you can evaluate the claim without seeing the privileged content.2Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery
Specify what each entry must contain: document date, author, all recipients, general subject matter, and the specific privilege claimed. Courts routinely reject logs that offer only conclusory descriptions like “attorney-client communication.”
Pair the log instruction with a Rule 502(d) clawback order negotiated at the Rule 26(f) conference. Under Federal Rule of Evidence 502(d), a federal court can order that inadvertent disclosure of privileged material during the litigation does not waive the privilege, and that protection extends to other federal and state proceedings.4Legal Information Institute. Federal Rules of Evidence Rule 502 – Attorney-Client Privilege and Work Product; Limitations on Waiver If a privileged email slips through in a batch of 50,000 documents, the producing party can claw it back without permanent waiver. Both sides benefit: the producing party gets waiver protection, and the requesting party gets faster production because the pre-production privilege review does not have to be exhaustive.
Response Window and the Objection Standard
The responding party has 30 days after service to respond in writing, unless the parties agree otherwise or the court adjusts the timeline.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes The response must address each category individually. A blanket objection to the entire request is improper.
For every category, the responding party either agrees to produce or states specific grounds for objecting. Boilerplate language like “overly broad, unduly burdensome, and not proportional to the needs of the case” with no explanation does not satisfy the rule. The 2015 amendments also require an objection to state whether any responsive materials are being withheld on the basis of that objection, and partial objections do not excuse producing the non-objectionable portion.1Legal Information Institute. Federal Rules of Civil Procedure Rule 34 – Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes
When objections come back, meet and confer first; file a motion to compel if that fails. The more specific your original request, the stronger your position on the motion.
One Limit on Scope: Inaccessible Sources
Even when ESI is relevant, Rule 26(b)(2)(B) lets the responding party object to producing data from sources “not reasonably accessible because of undue burden or cost.” If that showing is made, the court can still order production on good cause — and can attach cost-sharing conditions.2Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery
In practice this comes up with backup tapes, legacy systems, and decommissioned databases. Data on an active email server or current cloud platform is presumed accessible. Draft to target accessible sources first. If you genuinely need data from backup tapes or retired systems, be ready to explain why the data matters enough to justify the cost, and consider offering to share expenses in a negotiated agreement.