What must a request include

A request should identify the case, the requesting and responding parties, each numbered category of documents, an explicit time range, and the required production format. Clear specificity reduces objections and supports enforceability.

How to object properly

State specific grounds for each objection (overbroad, undue burden, privileged) and whether any responsive, non-privileged documents will be produced. General boilerplate objections are often disfavored by courts.

Follow any agreed ESI protocol: produce searchable PDF or native files as specified, include requested metadata fields, and provide a load file when required for review platforms.

What to include in a privilege log

List withheld documents by unique identifier with sufficient detail (date, author, recipient, general description, privilege asserted) to allow meaningful challenge without disclosing privileged content.

What happens for late or incomplete production

Responding parties risk motions to compel, sanctions, fee shifting, or adverse inferences; remedial supplementation and immediate meet-and-confer reduce exposure.

Can discovery and production be done electronically

Yes. Electronic service and eSubmission are common where allowed by local rules. Ensure chosen platform meets court and regulatory security requirements and supports audit trails and reproducible outputs.

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 (commonly called a Request for Production or RFP/RPD in litigation) is a formal discovery demand used to obtain documents, electronically stored information (ESI), and other tangible items from an opposing party. In federal practice it is governed by Federal Rule of Civil Procedure 34; state courts have parallel rules or local procedures. Requests identify categories of documents, a time frame, format for production, and specify whether originals, copies, or ESI outputs are required. Properly drafted requests enable focused discovery, reduce disputes, and support case preparation.

Why the Request for Production of Documents matters in litigation

A clear Request for Production narrows issues, compels relevant evidence disclosure, and builds the factual record efficiently. It forces the responding party to locate, preserve, and produce evidence that supports or rebuts claims.

Who prepares and responds to Requests for Production

Requests are prepared by counsel or parties; responses are produced by the party who controls the requested records.

Plaintiff counsel seeking admission of documents or ESI in support of claims
Defense counsel identifying exculpatory evidence and drafting proportional requests
Corporate records custodians and IT teams responsible for locating and producing ESI

Core elements every professional Request for Production should include

A professional request is concise, numbered, and organized so each category is discrete, time-bounded, and tied to relevance. Use plain language and specify formats for ESI.

Case Caption

Full court name, docket number, and party names. This anchors the request to the pending action and prevents ambiguity in multi-matter custody.

Specific Categories

Numbered requests describing documents or ESI categories precisely (e.g., 'all contracts between X and Y from 01/01/2019–12/31/2020') to avoid overbreadth objections.

Time Frame

Clear start and end dates for the search scope. Time bounds reduce disputes and narrow custodial searches in ESI collections.

ESI Format

Specify production format (native, searchable PDF, load files, metadata fields). Include required metadata fields and Bates-numbering expectations.

Custodian Identification

List custodians or systems to search (email boxes, servers, cloud accounts, mobile devices). This guides targeted collections and reduces burden.

Certification Clause

Require a discovery response certification attesting to reasonable inquiry and search methods used to locate responsive materials.

Required information to include in every Request for Production

Requesting Party: Name and counsel

Responding Party: Name and counsel

Document Categories: Numbered and specific

Time Period: Start and end dates

Production Format: Native or PDF

Certifications: Signature and date

Step-by-step: draft, serve, and manage a Request for Production

Follow a consistent sequence to reduce objections and preserve proof of service: identify needs, draft specific requests, specify format, coordinate custodian searches, and document service.

01

Identify issues: Map documents required to support claims or defenses.
02

Draft requests: Number items, set dates, and specify formats.
03

Serve request: Serve per court rules and proof-of-service requirements.
04

Manage production: Track responses, privilege logs, and supplementation.

How to configure an online workflow for serving and collecting productions

When using a secure platform, set document upload, authentication, retention, and audit settings before sending discovery requests.

Field	Configuration
Document Uploads	Allow native uploads and PDF conversion
Field Placement	Add signature and certification fields
Signer Authentication	Use email + SMS or stronger multi-factor
Audit Trail	Capture timestamps, IP, and download events

Where to send and how productions are delivered

Deliver productions according to the service rules in the jurisdiction and the agreed ESI protocol; track transmission and receipt carefully.

Serve Requests: Send via court-approved e-service or hand/service per local rules.
Receive Production: Accept files via secure portal or encrypted transfer.
Acknowledge Receipt: Confirm receipt in writing with Bates ranges and file list.
Preserve Originals: Keep originals and maintain chain-of-custody records.

Technical and platform requirements for eSubmission and secure exchange

Use platforms that support secure upload, audit trails, standard file formats, and integrations with case management systems.

Integrations: Salesforce, NetSuite, Microsoft 365 supported
File Formats: PDF, DOCX, XLSX, native files accepted
Security Standards: TLS 1.2/1.3 and AES-256 encryption

Key deadlines and timing expectations for producing documents

Timelines are jurisdiction-specific but federal practice provides a baseline. Track service dates, response deadlines, supplementation duties, and motion windows carefully.

Response Deadline:

Typically 30 days after service (Federal Rule 34(b)(2)(A))

Supplemental Production:

Duty to supplement arises upon later discovery of new responsive materials

Privilege Log Timing:

Provide privilege logs with the response or in the timeframe ordered by the court

Motion to Compel:

File after meet-and-confer; follow local stay/meet rules

ESI Protocol Agreement:

Negotiate early to avoid late-format disputes

Common drafting and production mistakes to avoid

Overbroad or vague categories prompting objections and motion practice
Failing to specify ESI formats and required metadata increases rework
Not identifying custodians or relevant systems leads to incomplete searches
Omitting a privilege log requirement risks waiver or sanctions

Consequences of improper production or noncompliance

Sanctions: Court-ordered penalties possible

Compelled Production: Court may order disclosure

Adverse Inference: Limitations or jury instruction risk

Fee Shifting: Responding party may pay costs

Contempt: Repeated defiance may lead to contempt

Privilege Waiver: Inadvertent disclosures can waive protections

Typical eSignature vendor pricing and feature snapshot for producing and exchanging discovery materials

Secure eSignature platforms reduce turnaround time and provide audit trails; below is a concise vendor pricing and capability comparison with signNow listed first.

	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	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes (bulk send available)	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA available)	Varies by plan	Varies by plan	Varies by plan	Varies by plan

Practical tips to make Requests for Production effective and defensible

Adopt clear drafting, early coordination, and agreed ESI protocols to reduce disputes and discovery costs.

Limit scope strategically

Define precise date ranges, custodians, and document types. Narrow requests to what is necessary to prove or disprove elements of claims or defenses and to honor proportionality under Rule 26(b)(1).

Specify formats and metadata

Identify preferred production formats and required metadata fields (e.g., date, author, custodian, file path) to avoid later reformatting disputes and ensure usable productions.

Agree on ESI protocol early

Negotiate search terms, de-duplication, and load file requirements at the outset to prevent costly reprocessing and meet court scheduling needs.

Document searches and preservation

Record search terms, custodians, and steps taken. Preservation holds and a written litigation hold notice reduce spoliation risk.

Frequently asked questions about Requests for Production and common solutions

Answers to frequent questions about drafting, responding, objections, ESI formats, privilege logs, and platform use during production.

Need help? Contact support

What must a request include
A request should identify the case, the requesting and responding parties, each numbered category of documents, an explicit time range, and the required production format. Clear specificity reduces objections and supports enforceability.
How to object properly
State specific grounds for each objection (overbroad, undue burden, privileged) and whether any responsive, non-privileged documents will be produced. General boilerplate objections are often disfavored by courts.
How to produce ESI
Follow any agreed ESI protocol: produce searchable PDF or native files as specified, include requested metadata fields, and provide a load file when required for review platforms.
What to include in a privilege log
List withheld documents by unique identifier with sufficient detail (date, author, recipient, general description, privilege asserted) to allow meaningful challenge without disclosing privileged content.
What happens for late or incomplete production
Responding parties risk motions to compel, sanctions, fee shifting, or adverse inferences; remedial supplementation and immediate meet-and-confer reduce exposure.
Can discovery and production be done electronically
Yes. Electronic service and eSubmission are common where allowed by local rules. Ensure chosen platform meets court and regulatory security requirements and supports audit trails and reproducible outputs.

Explore Templates

Letter Requesting Notification of Estate Creditors Wedding Planner Letter Requesting Execution of Affidavit of Subscribing Witness Letter Requesting Payment for Gift Share Invitation Letter to Visit USA Letter Requesting Execution of Withdrawal of Probated Claim

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now