Establishing secure connection…Loading editor…Preparing document…

Legal RPD Document

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

LEGAL RPD DOCUMENT

This Request for Production of Documents (the "Request") is made as of by and between Requesting Party: and Responding Party: . This Request is issued in connection with the action captioned: , Case No. .

Recitals

WHEREAS, the Requesting Party seeks the production of documents and tangible things relevant to the claims and defenses in the action identified above; and

WHEREAS, the Responding Party is in possession, custody, or control of certain documents, electronically stored information, and tangible items that may be responsive to the Request; and

WHEREAS, the parties desire to set forth the definitions, instructions and specific requests governing production of documents to avoid disputes and to preserve relevant materials.

NOW THEREFORE

NOW THEREFORE, in consideration of the mutual covenants contained herein and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. Definitions

1.1 "Document" or "Documents" means all writings, drawings, graphs, charts, photographs, sound recordings, images, electronic mail, databases, metadata, instant messages, text messages, other electronically stored information and other tangible items within the meaning of the applicable rules of civil procedure, whether produced or stored in hard copy, electronic form, or other media.

1.2 "You" and "Your" mean the Responding Party and any of its agents, representatives, affiliates, predecessors, successors, custodians, and any person acting on its behalf.

2. Instructions

2.1 These Requests call for the production of Documents in Your possession, custody, or control, including Documents within the possession of Your attorneys, accountants, agents, or other representatives.

2.2 Unless otherwise stated, the time period covered by these Requests is from through .

2.3 If any Document responsive to a Request has been destroyed, lost, or disposed of, identify the Document, state the date and manner of destruction, and identify the person who authorized or performed the destruction.

3. Requests for Production

The Responding Party is requested to produce the following Documents. For each numbered request, produce all responsive Documents in full and as kept in the ordinary course of business, including all non-identical copies and drafts.

Request No. 1 — All communications, including emails and messages, between the Responding Party and any third party concerning the subject matter of the action.

Request No. 2 — All contracts, agreements, amendments, and related correspondence referenced in or relating to the claims or defenses.

Request No. 3 — All internal policies, procedures, training materials, and audit reports relevant to the subject matter.

Request No. 4 — All documents sufficient to show the identity of persons with knowledge of facts material to the claims or defenses, including resumes and correspondence.

Request No. 5 — All billing records, invoices, receipts and expense reports related to the matters at issue.

Request No. 6 — All drafts, notes, or analyses prepared for internal use that memorialize decisions or actions relevant to the claims.

Request No. 7 — All documents reflecting communications with regulators, governmental agencies, or auditors concerning the subject matter.

Request No. 8 — All electronically stored information in original file format, including metadata, for documents otherwise produced in redacted or printed form.

Request No. 9 — All pictorial or audiovisual materials, including photographs, video recordings, and audio recordings, relevant to the claims or defenses.

Request No. 10 — All documents sufficient to identify any reinsurance, insurance coverage, or indemnity agreements applicable to the claims.

4. Production Format and Confidentiality

4.1 Documents maintained in electronic form shall be produced in a reasonably usable electronic format that preserves native file metadata. The producing party shall identify for each significant file the file format and any applicable password or access instructions.

4.2 If Documents contain Confidential or Highly Confidential information, the producing party may designate such Documents as Confidential and the parties shall treat such designated Documents in accordance with any protective order entered in the action or, absent such an order, the following terms: confidentiality designations shall be made in writing at the time of production, and designated materials shall be used only for prosecution, defense, or settlement of this action.

5. Objections and Preservation

5.1 The Responding Party must serve written objections to specific Requests within the time permitted by the applicable rules of civil procedure, stating with specificity the grounds for objection. Objections that are not timely asserted are deemed waived except as required by governing procedural rules.

5.2 Nothing in this Request shall be construed as permitting destruction, alteration, or concealment of Documents that are or may be relevant to the subject matter of the litigation. The Responding Party shall preserve all Documents reasonably likely to be relevant to the claims or defenses.

6. Responses and Certification

6.1 The Responding Party shall produce responsive Documents and provide written responses indicating whether Documents will be produced, withheld, or produced subject to a claim of privilege or protection. For any withheld Document claimed to be privileged, provide a privilege log describing the nature of the Document sufficient to assess the claim without disclosing privileged content.

6.2 All written responses shall be signed by the Responding Party or an authorized representative certifying under penalty of perjury that the responses are complete and correct to the best of their knowledge after a reasonable inquiry.

Response due by:

7. Governing Law

This Request shall be governed by and construed in accordance with the laws of the jurisdiction in which the underlying action is pending, without regard to conflict of laws principles.

8. Entire Agreement

This Request, together with any agreements or orders referenced herein, constitutes the entire understanding between the parties with respect to the subject matter and supersedes all prior proposals, negotiations, and communications on the same subject.

9. Severability

If any provision of this Request is held to be invalid or unenforceable, the remainder of this Request shall remain in full force and effect and such provision shall be reformed only to the extent necessary to make it enforceable.

10. Notices

11. Amendments; Waiver; Counterparts

11.1 This Request may be amended or supplemented only by written agreement of the parties. No waiver of any provision shall be effective unless in writing and signed by the waiving party.

11.2 This Request may be executed in counterparts, each of which shall be deemed an original, and all of which together shall constitute one and the same instrument.

12. Certification of Service

The undersigned certifies that a copy of this Request was served on the Responding Party in accordance with applicable rules of civil procedure on .

Requesting Party:

Printed Name:

By:

Date:

Responding Party:

Printed Name:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the Legal RPD Document Is and when it’s used

A Legal RPD Document (Request for Production of Documents) is a formal discovery request used in civil litigation to compel another party to produce documents, electronically stored information (ESI), or tangible items relevant to the case. It typically appears under the case caption, lists numbered requests with clear definitions and date ranges, and requires responses that either produce documents, state that documents are not in the responding party’s possession, or assert privilege with a privilege log. Federal practice follows Federal Rules of Civil Procedure, Rule 34; many states have parallel discovery rules.

Why a clear Legal RPD Document matters

A precise RPD reduces disputes, narrows issues, and preserves admissible evidence; it clarifies scope, format, and date ranges, making responses easier to review and reducing the risk of sanctions under discovery rules.

Why a clear Legal RPD Document matters

Who prepares and responds to an RPD

The RPD is used by litigators and parties engaged in discovery; it requires coordination across legal, records, and IT teams.

  • Plaintiff and defense counsel coordinating requests and responses during discovery proceedings.
  • Corporate records custodians responsible for collecting and producing ESI and physical documents.
  • Third-party vendors such as e-discovery providers and process servers assisting with collection and service.

Accurate routing and early preservation reduce friction; involve records custodians, IT, and counsel before serving or responding to requests.

Core sections to include in a professional Legal RPD Document

A professionally drafted RPD is structured logically, defines terms, and specifies formats and date ranges so responding parties can locate and produce materials without ambiguity.

Case Caption

Complete court caption, case number, and party names so the request is properly directed and docketed in court filings.

Instruction Section

Clear instructions on production format, electronic metadata to include, Bates numbering, and whether privilege logs are required.

Definitions

Defined terms (e.g., 'document', 'communication', named systems) to limit ambiguity and guide custodians and e-discovery searches.

Individual Requests

Numbered requests that specify the document or ESI sought, including date ranges and custodian or system where possible.

Date Range

Explicit start and end dates for each request or global date range to avoid disputes about scope and relevance.

Signature Block

Name, bar number, address, counsel signature and date; include service method and certificate of service when required.

Essential data fields to include in every RPD

Case Caption: Court, parties, case number
Request Number: Sequential request ID
Date Range: MM/DD/YYYY to MM/DD/YYYY
Custodian: Named custodian or system
Format: Native, PDF, or load file
Privilege Log: Required if asserting privilege

Step-by-step: drafting and serving an RPD

Follow a clear sequence: define scope, identify custodians, draft requests, preserve evidence, serve, and track responses to ensure compliance with procedure rules.

  • 01
    Define Scope: Identify relevant issues and reasonable date ranges
  • 02
    Identify Custodians: List persons and systems likely to hold responsive material
  • 03
    Preserve Evidence: Issue litigation hold to prevent spoliation
  • 04
    Serve Request: Serve per court and local rules; record service

Where to send or file the RPD and typical routing

RPDs are served on opposing counsel and, when required, filed or lodged with the court according to local rules; electronic service is increasingly accepted.

  • Serve Counsel: Deliver to opposing counsel by agreed method
  • File With Court: File if local rules require or when attached to motion
  • E-File Systems: Upload via court e-filing where permitted
  • Document Repository: Share produced files via secure repository

Technical considerations for electronic production and signatures

Use tools that preserve metadata and produce load files; confirm encryption and access controls for production repositories.

  • File Formats: PDF, native files, load files
  • Security: TLS in transit, AES-256 at rest
  • Integrations: E-discovery, cloud storage, case management

Ensure the chosen platform supports audit trails, metadata export, role-based access, and integration with document review and court e-filing systems.

Common deadlines and response timing for RPDs

Observe the governing procedural rule for response time and preservation duties; local rules or court orders may shorten or extend deadlines.

Federal Response Time:

Typically 30 days under FRCP 34(b)(2)(B)

Preservation Duty:

Preserve relevant ESI immediately upon reasonable anticipation

Extensions:

Parties may agree or seek court extensions

Privilege Log Timing:

Provide privilege logs with or shortly after responses

Court Deadlines:

Follow case-specific scheduling orders

Penalties and risks from inadequate or late production

Sanctions: Court may impose sanctions (FRCP 37)
Adverse Inference: Spoliation can lead to adverse-inference rulings
Monetary Fines: Fines or fee-shifting may be ordered
Evidence Exclusion: Late materials may be excluded at trial
Default Judgment: Refusal to comply can lead to default
Contempt: Severe noncompliance can yield contempt findings

Practical tips for accurate, defensible RPD drafting and production

Adopt consistent processes to improve defensibility and reduce dispute: be specific, preserve promptly, document collection, and maintain an audit trail.

Be Specific
Draft requests narrowly and with precise dates to avoid overbreadth objections and reduce collection burden.
Preserve Early
Issue litigation holds and collect ESI promptly to avoid spoliation and sanctions.
Document Collection
Log custodians, searches, and export parameters to support search methodology in meet-and-confer or motion practice.
Use Metadata
Include key metadata fields and Bates numbering to streamline review and production validation.

How organizations handle RPDs in practice

These real-world examples illustrate operational approaches to preparing and producing documents in litigation.

Martin Properties (Real Estate)

The firm centralized collection workflows to reduce delays and ensure compliance.

  • They used coordinated custodian lists and standardized date ranges.
  • As a result, the team delivered consistent productions that reduced follow-up motions and preserved chain-of-custody documentation for trial use.

Fertility Centers of Illinois (Healthcare)

Healthcare provider required strict PHI handling and audit logs during production.

  • They paired legal counsel with IT to export redacted records and audit trails.
  • The coordinated approach helped satisfy HIPAA concerns while meeting court-ordered production and privilege-log obligations.

Configuring an online workflow for RPD drafting and e-production

Set up a repeatable template and collection workflow to standardize requests, preserve metadata, and secure produced files.

Field Configuration
Authentication Email link, SSO, or two-factor for reviewer access
Field Types Text, date, checkbox for tracked request elements
Audit Trail Capture actions, timestamps, and user IDs
Storage Secure repository with role-based access

eSignature vendor comparison for supporting RPD workflows

Basic vendor cost and capability comparison for document signing, secure delivery, and compliance features relevant to discovery production workflows.

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 (premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA) Yes (BAA) Yes (BAA) No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently asked questions about Legal RPD Documents

Answers to common questions about formality, electronic signatures, preservation, and typical discovery disputes involving RPDs.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.