What is proper service timing?

Timing follows local and federal rules; serve requests early enough to allow reasonable response time and to avoid prejudice. Many courts expect meet-and-confer before filing a motion to compel.

How specific must categories be?

Categories should be specific and proportional. Avoid blanket or vague terms like 'all documents'; instead describe subject matter, custodians, and date ranges.

What if privileged documents are found?

Withhold privileged items, produce a privilege log with sufficient detail, and follow any court-ordered procedures for in-camera review or clawback agreements.

Can ESI metadata be requested?

Yes. Specify required metadata fields and production format. Be prepared to negotiate what metadata is reasonably accessible or burdensome to produce.

What happens if production is incomplete?

Opposing counsel may file a motion to compel; courts can order supplementation, award fees, or impose sanctions if production was unreasonable or wilfully incomplete.

How to handle large datasets?

Use targeted search terms, sampling, phased productions, and vendor-assisted processing. Consider predictive coding or review platforms to manage volume efficiently.

Electronic Signature
Templates
Other
Request for Production of Documents

Request for Production of Documents

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

What a Request for Production of Documents Is and When It’s Used

A Request for Production of Documents is a formal discovery tool used in civil litigation to compel an opposing party to produce non-privileged documents, electronically stored information (ESI), and tangible things relevant to claims or defenses. Under the Federal Rules of Civil Procedure (Rule 34) and analogous state rules, parties specify categories, time frames, custodians, and preferred formats. Responses must state objections, produce responsive materials, and, when asserting privilege, provide a privilege log. Proper drafting balances scope, proportionality, and preservation obligations to avoid motions to compel or sanctions.

Why a Carefully Drafted Request Matters

A clear Request for Production organizes evidence, reduces disputes over scope, preserves discoverable records, and supports dispositive motions or settlement. Precise requests limit surprise, lower litigation costs, and make responses easier to review and use at trial.

Who Prepares and Responds to Production Requests

Typical users draft, serve, and respond to production requests as part of litigation workflows.

Litigators and law firms: Draft targeted categories, negotiate scope, and move to compel when necessary.
In-house counsel and corporate eDiscovery teams: Coordinate custodian searches, preserve ESI, and manage rolling productions.
Paralegals and litigation support: Collect metadata, run searches, process native files and assemble privilege logs.

Step-by-Step: Preparing and Serving a Production Request

Follow a consistent sequence to create a defensible request and reduce discovery disputes.

01

Identify custodians: List people and systems likely to hold relevant documents for targeted searches.
02

Define scope: Draft specific categories, date ranges, and key search terms to meet proportionality.
03

Specify format: State native, PDF, or extracted text and include metadata fields required.
04

Serve and track: Serve per rules, record service details, and schedule rolling productions as needed.

Essential Elements to Include in Every Production Request

A professional Request for Production has defined scope, clear instructions, and production protocols to ensure defensible, usable results.

Scope Definition

Describe categories of documents with specificity, including subject matter, document types, and any exclusions to avoid overbreadth and meet proportionality requirements.

Date Range

State a precise start and end date for the request. Narrow ranges reduce search costs and make relevance disputes easier to resolve.

Custodians

List custodians or custodial systems explicitly to direct collection efforts and to document reasonable efforts to preserve relevant information.

Format Instructions

Specify whether documents must be produced in native format, searchable PDF, or with extracted text and which metadata fields must accompany each file.

Privilege Procedure

Include instructions on objections, privilege assertions, and the required form of a privilege log with sufficient detail to support withheld items.

Certification

Require a signed certification that the responding party performed a reasonable search and produced all responsive, non-privileged materials.

Required Identification and Case Data

Case Number: Court docket number for accurate filing.

Party Names: Full legal names for clarity.

Service Date: Date request was served on opposing party.

Custodial List: Named custodians for targeted searches.

Date Range: MM/DD/YYYY start and end dates.

Production Format: Native, PDF, and metadata specifications.

Configuring an Electronic Production Workflow

Map delivery, authentication, and processing settings before collection to ensure consistent, defensible output.

Field	Configuration
Delivery Method	Secure file share or vendor-hosted review platform.
Authentication	Email plus access code or platform SSO for recipient access.
File Naming	Standardized convention: Custodian_Date_DocID.
Privilege Log	CSV or PDF with privilege basis and document identifiers.

High-Level Production Process from Request to Delivery

A predictable four-step flow helps manage expectations and creates audit evidence for the litigation record.

Draft Request: Define categories, formats, custodians, and date ranges.
Serve Request: Serve per local rules and document the date and method of service.
Collect and Review: Search custodial sources, apply filters, and review for privilege.
Produce: Deliver responsive, non-privileged materials with metadata and certify the production.

Common Pitfalls to Avoid When Drafting or Responding

Overbroad categories that ignore proportionality invite motions to compel and increased costs for the responding party.
Failing to specify production format leads to rework, lost metadata, and unusable PDFs or native files.
Incomplete custodian lists or failing to preserve ESI can trigger spoliation disputes and sanctions.
Poor privilege logging or blanket objections often result in court-ordered disclosure and credibility harms.

Consequences of Incorrect or Deficient Productions

Motion to Compel: Court may order further production and costs for the non-complying party.

Sanctions: Monetary fines, adverse inference instructions, or case-dispositive remedies.

Waiver: Failure to timely object may waive rights to contest scope or privilege.

Spoliation Risk: Sanctions or evidentiary penalties for deleted or altered ESI.

Cost Shifting: Court may require requesting party to bear extraordinary collection costs.

Reputational Harm: Judicial criticism or loss of credibility in court filings.

Common eSignature Vendor Pricing and Feature Snapshot for Production Workflows

Compare basic pricing and features relevant to document signing, bulk workflows, audit trails, and HIPAA support when selecting an eSignature vendor.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Free trial available	Free trial available	Free trial available	Free trial available
Bulk Send	Yes	Yes	Yes	Yes	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Practical Tips for Accurate, Efficient Productions

Adopt defensible, repeatable practices that reduce disputes and lower review costs.

Narrow and Specific

Limit requests to relevant issues using clear terms, custodians, and date ranges; overly broad requests increase costs and invite objections.

Preserve Early

Issue litigation holds and suspend routine deletion policies promptly to prevent spoliation and to document preservation steps.

Specify Format

Require consistent production formats and metadata fields; specifying native versus searchable PDF avoids later conversion disputes.

Use Privilege Logs

Provide detailed privilege logs with sufficient information to allow meaningful judicial review while protecting privileged material.

Representative Use Cases from Litigation Practice

Real-world examples show how Requests for Production resolve fact issues and streamline case preparation.

Corporate Contract Dispute

A plaintiff served narrowly tailored requests for emails and contracts

focused date range reduced review volume
targeted production enabled prompt motion practice and focused depositions, lowering discovery expense.

Employment Litigation

Defense counsel requested personnel files and contemporaneous performance reviews

used custodian-specific categories to limit scope
the approach reduced privilege disputes and shortened meet-and-confer time.

Frequently Asked Questions About Requests for Production

Answers to common practical and procedural questions encountered when drafting, serving, or responding to production requests.

Need help? Contact support

What is proper service timing?
Timing follows local and federal rules; serve requests early enough to allow reasonable response time and to avoid prejudice. Many courts expect meet-and-confer before filing a motion to compel.
How specific must categories be?
Categories should be specific and proportional. Avoid blanket or vague terms like 'all documents'; instead describe subject matter, custodians, and date ranges.
What if privileged documents are found?
Withhold privileged items, produce a privilege log with sufficient detail, and follow any court-ordered procedures for in-camera review or clawback agreements.
Can ESI metadata be requested?
Yes. Specify required metadata fields and production format. Be prepared to negotiate what metadata is reasonably accessible or burdensome to produce.
What happens if production is incomplete?
Opposing counsel may file a motion to compel; courts can order supplementation, award fees, or impose sanctions if production was unreasonable or wilfully incomplete.
How to handle large datasets?
Use targeted search terms, sampling, phased productions, and vendor-assisted processing. Consider predictive coding or review platforms to manage volume efficiently.

Explore Templates

Complaint Regarding Negligence Sales Letter Using Referral Limited Liability Partnership Agreement Letter Requesting Information from a Government Agency Letter Requesting Retraction of Obituary Partnership Agreement with Covenant Not to Compete

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now