What defines reasonable scope?

Reasonable scope focuses on relevance and proportionality to the claims or defenses. Under modern discovery principles, requests should be tailored by topic, time frame, and custodian to balance burden and need.

How do I object to a request?

Object on specific grounds (overly broad, unduly burdensome, privileged, vague) and state the factual basis. Prompt and detailed objections preserve rights and frame any subsequent meet-and-confer discussions.

How is privilege asserted?

Withhold privileged materials and provide a privilege log describing document type, date, author, recipients, and privilege basis; consider a clawback agreement to protect inadvertent disclosures.

Can ESI be produced electronically?

Yes. Request native formats or searchable PDFs with metadata. Specify load files and naming conventions to facilitate review and authentication.

Are electronically signed certifications acceptable?

Electronically signed certifications are generally valid under ESIGN and state e-signature laws when intent and attribution are demonstrable; include a signed certification describing collection methods.

How to handle confidential information?

Propose a protective order with defined categories, handling instructions, and dispute-resolution procedures to permit production while protecting sensitive material.

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 a party to produce tangible evidence or electronically stored information. Typically served under the applicable rules of civil procedure (for federal courts, Rule 34), it describes categories of documents sought, the relevant time frame, and the form of production requested. Responses must state objections, identify responsive materials, and note any privilege claims. The request starts the practical exchange of evidence that supports motions, depositions, and trial preparation.

Why issuing a clear, well-scoped Request matters

A focused Request narrows disputes, speeds document exchange, and reduces motion practice. Clear scope and format instructions improve compliance and limit objections.

Which teams prepare and respond to Requests for Production

Law firms, corporate legal teams, and records custodians commonly draft and respond to production requests in litigation and regulatory matters.

Plaintiff and defense counsel preparing targeted discovery requests or objections to preserve issues for motion practice
In-house legal and compliance teams coordinating document collections and privilege logs across custodians
Records custodians or IT staff extracting ESI, metadata, and native files for review and production

Effective coordination among counsel, custodians, and vendors reduces delays and minimizes risk of sanctions or evidentiary loss.

Who may sign or certify production responses

Plaintiff's Attorney

An attorney of record typically signs objections and responses, certifying that a reasonable inquiry was made into the existence of responsive documents and that privilege assertions are supported.

Records Custodian

A designated custodian or corporate representative may sign certifications about search methods and the completeness of production when required by local rules or court order.

Essential fields and required metadata in a Request

Requesting Party: Name and counsel

Responding Party: Name and counsel

Document Description: Specific categories listed

Timeframe: Clear start/end dates

Production Format: Native, PDF, or TIFF

Date Served: MM/DD/YYYY

Common pitfalls that delay production

Overbroad requests that lack clear custodians or timeframes lead to disputes and burdensome collection processes that courts may narrow.
Failing to meet-and-confer before filing a motion to compel increases the risk of sanctions or denial of relief for premature litigation.
Producing privileged material without a proper privilege log or clawback agreement can waive protection and create additional motion practice.
Ignoring ESI issues—missing metadata or producing only printed copies—can omit key evidence and prompt discovery disputes.

Step-by-step: preparing and serving a Request for Production

Follow a consistent sequence: draft precise categories, identify custodians, specify format, and set realistic timelines that comply with procedural rules.

01

Draft categories: List specific document types and examples
02

Identify custodians: Name persons and custodial systems to be searched
03

Specify format: Request native ESI or searchable PDF with metadata
04

Serve and track: Serve per local rules and log the service date

How to configure an online production workflow

Set up a documented workflow for collection, review, redaction, and secure delivery to streamline ESI production and maintain defensible processes.

Field	Configuration
Collection scope	Custodians, date ranges, and file types
Authentication	Use MFA or verified email for access
Format settings	Native ESI or searchable PDF with metadata
Audit logging	Capture hashes, timestamps, and user actions

Where to send a Request and how it’s received

Service and delivery follow local rules; use documented channels and confirm receipt to maintain chain-of-custody and compliance.

Serve opposing counsel: Deliver by authorized court or party service methods
E-service acceptance: Confirm the court or local rule allows electronic service
Third-party vendors: Use eDiscovery vendors for large ESI collections
Court filings: File motions or certificates as required by local rules

Technical options for producing documents electronically

Electronic production commonly uses PDF, native file formats, secure file transfer, or e-discovery platforms with audit trails.

File formats: PDF, DOCX, XLSX, native
Authentication: Email, SMS OTP, or KBA
Integrations: Supports Salesforce, NetSuite, Box

Choose a platform that preserves metadata, provides tamper-evident logs, and supports secure, auditable delivery to opposing counsel.

Typical timelines and response deadlines to expect

Deadlines vary by jurisdiction, but most rules set a specific number of days to respond after service; track all dates carefully to avoid waiver.

Service date recorded:

Day zero for response timing

Standard response period:

Typically 30 days to respond to production requests

Meet-and-confer window:

Allow time for dispute resolution before motion practice

Production schedule:

Staggered productions may be negotiated

Motion timing:

File compel motions after meet-and-confer efforts

Consequences of deficient production or missed deadlines

Court sanctions: Monetary penalties or case-specific sanctions

Evidentiary exclusion: Late evidence may be barred at trial

Adverse inference: Jury instruction for spoliation risk

Waiver of privilege: Unprotected disclosure can waive privilege

Motion costs: Order to pay opposing counsel’s fees

Contempt risks: Possible contempt for willful noncompliance

Practical examples of Request for Production usage

These two scenarios illustrate typical drafting choices and production workflows in civil disputes.

Commercial Contract Dispute

A plaintiff requested emails and invoices for a two-year period relating to the contract

The point was to establish chronology and conduct
The defendant produced native emails with metadata and a privilege log, then negotiated a rolling production schedule to reduce burden and avoid motion practice.

Healthcare Records Matter

A defendant sought medical billing and claims data for a patient over one year

The point was to verify billed services and payments
The provider produced redacted records under HIPAA protocols, provided a written certification, and used secure transfer to preserve PHI protections.

Practical tips for accurate, efficient Requests and production

Apply consistent drafting and collection standards to reduce disputes, preserve evidence integrity, and control costs.

Be specific in requests

Define document categories with examples and narrow time ranges; specificity reduces burden, speeds collection, and limits objections.

Preserve metadata

Request native files or searchable PDFs with metadata and hashing to maintain forensic integrity and simplify authentication.

Use meet-and-confer

Engage opposing counsel early to resolve scope, format, and schedule issues and to limit motion practice and sanction risk.

Document collection methods

Maintain defensible collection logs describing search terms, custodian interviews, and tools used for ESI retrieval.

eSignature vendor comparison for document certification and secure production delivery

Comparing common eSignature vendors can help select a platform that preserves audit trails, supports HIPAA where required, and fits budget constraints.

	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	Yes, 7-day trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about Requests for Production

Answers to common questions about scope, objections, format, privilege, and e-delivery to help practitioners avoid routine mistakes.

Need help? Contact support

What defines reasonable scope?
Reasonable scope focuses on relevance and proportionality to the claims or defenses. Under modern discovery principles, requests should be tailored by topic, time frame, and custodian to balance burden and need.
How do I object to a request?
Object on specific grounds (overly broad, unduly burdensome, privileged, vague) and state the factual basis. Prompt and detailed objections preserve rights and frame any subsequent meet-and-confer discussions.
How is privilege asserted?
Withhold privileged materials and provide a privilege log describing document type, date, author, recipients, and privilege basis; consider a clawback agreement to protect inadvertent disclosures.
Can ESI be produced electronically?
Yes. Request native formats or searchable PDFs with metadata. Specify load files and naming conventions to facilitate review and authentication.
Are electronically signed certifications acceptable?
Electronically signed certifications are generally valid under ESIGN and state e-signature laws when intent and attribution are demonstrable; include a signed certification describing collection methods.
How to handle confidential information?
Propose a protective order with defined categories, handling instructions, and dispute-resolution procedures to permit production while protecting sensitive material.

Explore Templates

California Warranty Deed Grant Deed Joint Grant Deed Trust Deed of Severance California Joint Tenants Agreement CA Condominium Form

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now