Establishing secure connection…Loading editor…Preparing document…

Legal Requests for Production

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

LEGAL REQUESTS FOR PRODUCTION

To: ; Responding Party Address:

From: ; Requesting Party Representative:

Court: Case Title: Case Number:

Date of Service:

RECITALS

WHEREAS, Requesting Party is a party to the litigation referenced above and seeks relevant documents, tangible things, and electronically stored information in order to prepare for pleadings, discovery, depositions, and trial; and

WHEREAS, Responding Party is believed to have possession, custody, or control of documents, communications, and electronically stored information that are relevant to the claims and defenses in this action; and

WHEREAS, the parties are obligated to preserve discoverable materials and to produce responsive information in a form that permits meaningful review and use;

NOW THEREFORE, pursuant to the applicable rules of civil procedure, Requesting Party hereby serves the following Requests for Production upon Responding Party. Responding Party shall produce documents and ESI in accordance with the definitions, instructions, and requests set forth below.

DEFINITIONS

1.1 "Document" and "documents" are used in the broadest sense and include all written, recorded, or graphic material, however produced or reproduced, including but not limited to correspondence, agreements, notes, memoranda, invoices, reports, photographs, audio and video recordings, calendars, diaries, drafts, metadata, and any electronically stored information.

1.2 "Electronically Stored Information" or "ESI" means all computer-based or other electronic data, including files, email, databases, system logs, text messages, social media content, slack or chat logs, documents stored on servers or cloud services, and metadata associated with such data.

1.3 "You" or "Responding Party" refers to the named responding party and any agents, attorneys, affiliates, employees, or other persons acting on its behalf.

INSTRUCTIONS

2.1 Time Period: Unless otherwise stated, the time period for these Requests is from through .

2.2 Responsive documents shall be produced as kept in the usual course of business and shall not be altered or destroyed. If documents are withheld on the ground of privilege or protection, Responding Party must provide a contemporaneous privilege log meeting the requirements below.

2.3 ESI Production Format: Unless otherwise agreed, produce native files for spreadsheets, databases, and multimedia files; produce single-page, searchable PDF images for text documents with accompanying load files or metadata fields sufficient to identify custodian, file path, filename, date created, date modified, author, recipients, and hashing where applicable.

2.4 Custodians and Search Methodology: Identify custodians searched and the search terms or other methodology applied. If automated filtering or de-duplication is used, describe the processes and provide relevant parameters.

REQUESTS FOR PRODUCTION

Request No. 1: All correspondence, including electronic mail and text messages, between Responding Party and any third party regarding the subject matter of this litigation, including attachments and embedded images.

Request No. 2: All agreements, contracts, amendments, statements of work, purchase orders, invoices, and receipts relating to the transactions or events alleged in the complaint or defenses.

Request No. 3: All internal documents, notes, memoranda, calendar entries, and investigation files prepared in connection with the matters at issue, including drafts and redacted versions.

Request No. 4: All documents reflecting communications with expert witnesses, consultants, or advisors retained in connection with the claims or defenses, excluding privileged communications protected by law, and identify the custodian for each produced document.

Request No. 5: All invoices, billing records, time entries, and correspondence reflecting charges, payments, or financial transactions relevant to the claims or defenses.

Request No. 6: All versions of policies, procedures, manuals, or guidelines in effect during the relevant time period that relate to the subject matter of the dispute.

Request No. 7: All backups, snapshots, archived files, and system images that may contain responsive ESI, together with a description sufficient to permit restoration and review.

Request No. 8: All draft and final versions of documents responsive to these requests, showing tracked changes, comments, or version history where available.

Request No. 9: All communications with regulatory bodies, governmental agencies, or insurers concerning the subject matter of this action.

Request No. 10: All statements, recorded interviews, transcripts, or summaries of oral statements by any witness identified in this litigation, including recordings and drafts.

Request No. 11: All documents evidencing or reflecting any insurance coverage that may be implicated by the claims, including reservation of rights letters and correspondence with carriers.

Request No. 12: A copy of any document retention, destruction, or litigation hold notices, and all materials implementing or responding to such notices for the relevant custodians.

OBJECTIONS, PRIVILEGE, AND PRIVILEGE LOG

If Responding Party objects to any Request, the objection must state with specificity the legal and factual grounds for the objection. Any objection that documents are overbroad, unduly burdensome, or not reasonably calculated to lead to admissible evidence shall include a description of the efforts and time required to comply and proposed means of narrowing the request.

For any document withheld on the basis of privilege, work product, or other protection, Responding Party shall produce a privilege log that identifies each withheld document by date, author, recipient, custodian, document type, and a brief description sufficient to assess the claim of privilege without disclosing privileged information.

PRESERVATION AND CUSTODIAL SEARCH

Responding Party is directed to preserve all potentially relevant documents and ESI. Preservation duties include, but are not limited to, retention of deleted, residual, or overwritten ESI and system metadata pending completion of discovery.

Identify the custodians searched and provide a brief description of the search protocol within the response. If any custodian is not searched, state the legal and factual basis for exclusion.

RESPONSE DEADLINE AND MEET AND CONFER

Responding Party shall serve written responses and produce non-privileged documents within 30 days of service of these Requests, unless otherwise ordered by the court or agreed in writing by the parties. Responses must state whether documents will be produced in whole, produced in redacted form, or withheld.

If disputes arise regarding scope, form of production, or asserted privileges, the parties shall meet and confer in good faith prior to seeking judicial intervention and shall make reasonable efforts to narrow disputes.

GOVERNING LAW; OTHER PROVISIONS

Governing Law: This instrument shall be governed by the substantive and procedural laws of the jurisdiction in which the action is pending, without regard to conflicts of law principles.

Entire Agreement: These Requests for Production, together with any written agreements between the parties concerning discovery, constitute the entire understanding of the parties with respect to the production of documents at this stage of the litigation.

Severability: If any provision of these Requests is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect to the extent consistent with the court's order.

CERTIFICATION

By signing below, the signatory certifies that, to the best of their knowledge after a reasonable inquiry, the information set forth in these Requests and any accompanying cover letter is consistent with governing rules of civil procedure and is not interposed for any improper purpose, such as to cause unnecessary delay or needlessly increase the cost of litigation.

Requesting Party Contact for Production

CERTIFICATE OF SERVICE

I declare under penalty of perjury that on the date below I served a true and correct copy of these Requests for Production on the parties identified herein by the method indicated and to the addresses provided.

Method of Service: Service Date:

Requesting Party:

By:

Date:

Responding Party:

By:

Date:

Enter text✕

What a Legal Request for Production Is

A Legal Request for Production is a formal written discovery tool used in civil litigation to compel another party to produce documents, electronically stored information (ESI), or tangible items relevant to claims or defenses. Under the Federal Rules of Civil Procedure, Rule 34 governs production requests, requiring specificity in the items sought and allowing requests for ESI subject to proportionality and relevance limits. Requests for Production may be served between parties after initial disclosures, and responses typically must state whether responsive materials will be produced, withheld, or produced subject to objections or a protective order.

Why Requests for Production Matter in Litigation

Requests for Production focus fact-finding, let parties obtain documentary evidence, and shape case strategy by revealing records, communications, and ESI that support claims or defenses. They formalize document exchange, preserve admissible evidence, and create a record for motions and trial.

Why Requests for Production Matter in Litigation

Who prepares, serves, and responds to production requests

Typical participants include litigators who draft and serve requests, opposing counsel who respond, and client personnel or records custodians who locate and produce materials.

  • Plaintiffs and defense counsel who draft targeted requests and manage meet-and-confer communications to resolve scope disputes.
  • Records custodians and corporate litigation teams who collect ESI, run searches, and prepare privilege logs.
  • Third-party vendors and eDiscovery providers who process, host, and deliver productions in court‑acceptable formats.

Coordination among attorneys, custodians, and vendors is essential to meet deadlines, preserve privilege, and ensure an auditable production process.

Key signers and contacts

Litigation Attorney

Experienced counsel who drafts requests, evaluates proportionality and privilege, conducts meet-and-confer negotiations, and submits motions to compel or protective orders when necessary.

Records Custodian

Corporate or organizational custodian responsible for searching custodial sources, preserving ESI, running targeted collections, and certifying that searches were performed as described in discovery responses.

Essential parts of a professional production request

A clear, defensible Request for Production includes a concise caption, defined terms, precise requests, a defined time range, production instructions, and explicit objection and privilege procedures.

Case Caption

Court name, case number, and party names must match the pleadings so the request is properly served and docketed.

Definitions Section

Define key terms (e.g., 'document', 'communication', custodian names, and time frame) to reduce ambiguity and limit scope disputes.

Specific Requests

Numbered items that describe documents or ESI with reasonable particularity, avoiding overly broad or vague language that invites objections.

Time Period

State exact start and end dates for requested materials; open-ended ranges often trigger proportionality objections.

Production Instructions

Specify format (native, TIFF, searchable PDF), metadata fields, and delivery method to simplify review and meet court expectations.

Objections & Privilege

Include a process for asserting privilege and producing a privilege log, plus proposals for clawback or protective orders.

Step-by-step path to prepare and serve production requests

Follow these steps to prepare, serve, and manage production requests effectively while preserving privilege and meeting court rules.

  • 01
    Identify custodians: List relevant individuals and systems to scope collections.
  • 02
    Draft specific requests: Use precise language and defined terms to limit objections.
  • 03
    Serve with certificate: Serve under local rules and include proof of service.
  • 04
    Track and review: Log responses, privilege claims, and produced Bates ranges.

Typical production workflow from request to review

A production follows a predictable path: drafting, serving, collection, delivery, and review. Each stage has distinct tasks and responsibilities.

  • Prepare request: Draft precise numbered requests and definitions.
  • Serve request: Deliver per court and local rules; include deadlines.
  • Collect & process: Collect ESI, filter, and process for review.
  • Produce & certify: Deliver in agreed format with privilege logs.

Configuring an online workflow for production requests

When using an e-signature or document platform, configure fields and routing to support service, recordkeeping, and reproducible audit trails.

Field Configuration
Case Caption Field Auto-fill from case metadata to prevent transcription errors
Request Number Field Sequential numbering and validation to avoid duplicates
Service Confirmation Capture signature, timestamp, and IP for proof of service
Production File Upload Accept native files and required metadata fields

Digital delivery, signing, and security basics

Ensure the platform evidences intent and retention consistent with ESIGN and UETA and that HIPAA or other industry rules are observed when applicable.

  • Supported Formats: PDF, DOCX, native ESI
  • Authentication Options: Email link, SMS code, or higher-proof KBA
  • Integrations: Link to eDiscovery and case management

Key timing rules and expected deadlines

Timelines for Requests for Production are governed by court rules and local practice; missing deadlines can prompt motions to compel or sanctions.

Standard federal response:

30 days to respond per FRCP 34(b)(2)(A).

Meet-and-confer period:

Local rules vary; commence promptly after objections to avoid court intervention.

Extension by agreement:

Parties may agree to reasonable extensions in writing.

Production schedules:

Large ESI collections often use phased rolling productions.

Motions to compel:

File after meet-and-confer if disputes remain unresolved.

Milestones from request to usable production

Track these sequential milestones to manage workload, vendor timelines, and court obligations during discovery.

01

Draft and serve request

Prepare precise requests and serve with proof.

02

Preservation and collection

Issue litigation hold and collect ESI.

03

Processing and review

Deduplicate, OCR, and review for responsiveness.

04

Deliver production

Produce files, metadata, and privilege log.

Common mistakes that create disputes

  • Drafting overly broad requests that lack reasonable particularity and trigger proportionality objections.
  • Failing to identify custodians and data sources, which leads to incomplete or inconsistent productions.
  • Neglecting to specify formats and metadata, causing unusable productions and meet-and-confer disputes.
  • Insufficient privilege logging or improper redaction practices that prompt motions to compel or sanctions.

Consequences of improper or late production

Sanctions: Court may impose monetary or evidentiary sanctions.
Adverse inference: Juries may be instructed to infer missing evidence.
Motion fees: Loser may pay moving party's legal costs.
Waiver: Failure to timely assert objections can forfeit them.
Spoliation risk: Destruction of ESI can lead to serious penalties.
Case delay: Incomplete production prolongs motion practice and trial preparation.

Security and compliance considerations for productions

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Audit Trail: Maintain timestamps, IPs, and action logs
HIPAA: Execute BAA when PHI appears in production
Privilege Logs: List withheld documents and bases
Access Controls: Role-based access for sensitive datasets
Retention: Preserve originals until litigation concludes

eSignature vendor comparison for preparing and serving discovery

Platforms differ on price, HIPAA support, bulk send, and envelope caps. signNow appears first for easy comparison; evaluate audit trails and retention features for discovery 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, no card required Free trial varies Free trial varies Free trial available Free trial available
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Typical production scenarios and outcomes

Two example scenarios show common discovery paths and practical resolution approaches.

Document-heavy commercial dispute

A plaintiff served broad requests for communications about billing.

  • Parties met and narrowed requests to contract- and invoice-related ESI.
  • The phased production and agreed metadata format reduced review time and avoided court motion practice by resolving scope early.

Healthcare record production

Defense counsel sought patient files across multiple clinics.

  • Custodians and vendor mapped PHI and applied redaction protocols.
  • A signed BAA and secure delivery preserved confidentiality while meeting production deadlines and avoiding sanctions.

Practical tips to prepare defensible, efficient productions

Follow these best practices to reduce disputes, control costs, and preserve admissibility.

Draft narrowly tailored, fact-specific requests
Limit requests to documents reasonably calculated to lead to admissible evidence and tie each item to an element of a claim or defense to reduce proportionality objections and motion practice.
Use defined terms and precise time ranges
Clear definitions and specific date ranges reduce ambiguity, minimize over-collection, and make meet-and-confer negotiations more productive.
Agree on production formats and metadata early
Specifying native vs PDF, required metadata fields, and delivery method in a protocol prevents rework and helps expert review and e-discovery processing.
Document custodian searches and preservation steps
Keep a defensible record of litigation holds, search terms, and collection steps to respond to challenges about completeness or spoliation.

Frequently asked questions about Requests for Production

Answers to common questions about scope, timing, format, privilege, and electronic production to help parties avoid common discovery pitfalls.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users