Establishing secure connection…Loading editor…Preparing document…

Legal Production Request

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

LEGAL PRODUCTION REQUEST

This Legal Production Request (the Request) is made on Date: by Requesting Party: and is directed to Producing Party: for documents and electronically stored information related to Matter/Cause: filed with Tribunal/Court/File No.: .

RECITALS

WHEREAS, Requesting Party reasonably believes that Producing Party has in its possession, custody or control certain Documents and Electronically Stored Information that are relevant to the claims and defenses in the matter identified above; and

WHEREAS, Requesting Party seeks the production of those Documents and Electronically Stored Information in a form and manner that preserves source metadata and facilitates review and, where appropriate, the protection of privileged or confidential information; and

WHEREAS, the parties desire to set forth agreed terms, timelines and protocols governing the scope, format and logistics of production to minimize disputes and preserve rights.

NOW, THEREFORE, in consideration of the mutual promises and covenants set forth herein, the parties agree as follows:

1. DEFINITIONS

For the purposes of this Request: (a) "Document(s)" shall mean all writings, recordings, photographs, files, emails, attachments, databases, logs, metadata, and other tangible or electronic records within the custody or control of Producing Party; (b) "Electronically Stored Information" or "ESI" includes email, databases, files, metadata, server logs, backups, and any other material stored in electronic form; and (c) "Confidential Information" means information entitled to protection from public disclosure under applicable law or by agreement of the parties.

2. SCOPE OF REQUEST

Producing Party is requested to produce all non-privileged Documents and ESI responsive to the categories described below that are in its possession, custody, or control, including Documents in the possession of its agents, contractors, and third-party service providers, for the date range From: To: .

3. CUSTODIANS, SOURCES, AND SEARCH PROTOCOL

4. PRODUCTION FORMAT AND TECHNICAL REQUIREMENTS

Unless otherwise agreed, Producing Party shall produce Documents in the following formats and with the following metadata fields:

Native/Original electronic format    Text-searchable PDF    Single-page TIFF    Accompanying extracted text/utility files

Producing Party shall preserve and produce metadata fields including but not limited to: file name, original path, custodian, creation/modification dates, author/sender, recipients, and hash values. Bates numbering, load files, and cross-reference files shall be provided with productions where applicable.

5. PRIVILEGE, REDACTION AND PRIVILEGE LOG

Producing Party may redact or withhold only those portions of Documents that are privileged or otherwise protected. Any withheld or redacted Documents shall be logged in a privilege log that identifies, at a minimum, document identifier, date, author/sender, recipient(s), a brief description of the nature of the withheld material, and the asserted privilege or protection.

Assertion of privilege shall be governed by the applicable rules of procedure and any court order. The parties agree to a clawback protocol under which the inadvertent production of privileged material will not constitute a waiver if produced in error and notice is promptly provided.

6. TIMELINE, MEET AND CONFER, AND COSTS

Prior to any motion practice, the parties shall meet and confer in good faith to resolve disputes arising from this Request. The parties shall hold an initial meet-and-confer conference on or before Date: to address scope, search methodology, and production logistics.

Unless otherwise agreed, each party shall bear its own costs of collection and review. If Producing Party seeks cost-shifting, it shall provide a written proposal identifying specific costs and reasonable justification for shifting.

7. OBJECTIONS AND RESERVATION OF RIGHTS

Producing Party shall state any objections to specified categories of Documents within Number of Days: days of service of this Request. An objection must identify the specific category objected to and the factual or legal basis for the objection. Failure to object timely shall be deemed a waiver of such objection.

Nothing in this Request waives any party's right to seek protective orders, to contest relevance, to assert privileges, or to seek under-seal treatment for confidential materials.

8. CERTIFICATION

The undersigned Requesting Party certifies that the information provided in this Request is complete and accurate to the best of its knowledge, that the Request is reasonable in scope and directed to relevant sources, and that prior to serving this Request the undersigned attempted to meet and confer in good faith with Producing Party regarding scope and procedures.

9. NOTICES

All notices required or permitted under this Request shall be in writing and delivered to the addresses and contacts set forth below, and shall be effective upon receipt.

10. MISCELLANEOUS

Governing Law: This Request shall be governed by and construed in accordance with the laws of the jurisdiction in which the tribunal or court identified above sits, without regard to conflict of law principles.

Entire Agreement: This Request constitutes the entire agreement between the parties with respect to the subject matter herein and supersedes all prior oral or written communications on the same subject.

Severability: If any provision of this Request is held to be invalid or unenforceable, the remainder shall continue in full force and effect.

Amendments; Waiver: No amendment to this Request shall be effective unless made in writing and signed by both parties. No waiver of any provision hereof shall be effective unless in writing and signed by the party granting such waiver.

Counterparts: 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.

Requesting Party:

By:

Date:

Producing Party:

By:

Date:

Enter text✕

What a Legal Production Request Is and When it Applies

A Legal Production Request is a formal written demand used in litigation, administrative proceedings, or investigations to obtain documents, electronically stored information (ESI), and tangible items from another party or third party custodian. It identifies the requesting party, the responding party, specific custodians or repositories, defined document categories, date ranges, and the preferred production format. The request may require a signed certification of completeness or privilege logs for withheld materials. Proper drafting clarifies scope, reduces disputes, and sets expectations for format and delivery.

Why a Clear Production Request Matters

A well-drafted production request focuses discovery, preserves rights, sets technical production standards, and reduces motion practice. It establishes what must be produced, the acceptable formats, and the timeline for response while limiting disputes over scope and privilege.

Why a Clear Production Request Matters

Who Typically Prepares and Responds to These Requests

Various roles handle production requests depending on context — litigation teams, compliance groups, and records custodians commonly participate.

  • Litigation counsel and paralegals: Draft scope, serve requests, and manage objections and privilege logs.
  • Compliance and privacy officers: Ensure regulatory protections, HIPAA considerations, and internal policy adherence.
  • Records custodians and IT staff: Locate ESI, run searches, and produce files in agreed formats.

Coordination among legal, IT, and records teams reduces risk and speeds review while ensuring defensible collection and production.

Key Elements to Include in a Professional Request

Include concise scope language, explicit custodians, date ranges, file types, production format, and instructions for privilege logs and confidentiality handling.

Scope

Define documents sought with specificity, avoiding vague phrases; list topics, subject matter, or transaction identifiers to limit disputes and disputes over breadth.

Custodians

Name specific individuals, groups, servers, or third-party providers responsible for relevant data to direct collection and reduce overbroad searches.

Date Range

Provide clear start and end dates and explain any rolling or continuing obligations so parties know the temporal limits of the request.

Document Types

Specify formats such as emails, attachments, drafts, metadata, databases, or physical documents and whether native files or images are required.

Production Format

State preferred delivery (PDF/A, native files, load files, metadata fields) and technical specifications for Bates numbering, OCR, and metadata exports.

Privilege Handling

Require privilege logs identifying withheld items and specify procedures for clawback, reviewer notes, and confidentiality designations under protective orders.

Required Case and Contact Information

Case Caption: Full case title and court
Case Number: Docket or file number
Requesting Party: Name and counsel contact
Responding Party: Name and records custodian
Response Deadline: Date for production or objection
Signature: Authorized counsel signature

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

Follow a clear sequence to draft, serve, and manage responses to a production request to preserve rights and meet obligations.

  • 01
    Prepare: Identify issues, custodians, date ranges, and specific document categories.
  • 02
    Serve: Deliver the request under applicable service rules and confirm receipt.
  • 03
    Collect: Custodians and IT run searches and export ESI per specs.
  • 04
    Review: Privileged items logged; responsive materials produced or objections served.

Configuring an Electronic Production Workflow

Set clear technical settings for eDiscovery collections and e-submissions to ensure consistent production and defensible handling of ESI.

Field Configuration
Signature Method eSign or wet signature as required
File Format PDF/A preferred; preserve native for spreadsheets/databases
Delivery Method Secure upload to shared repository or encrypted email
Authentication Email confirmation; optional SMS or two-factor

Typical Routing for a Production Request

Production requests move between counsel, custodians, and service providers; each step should be documented and time-stamped for the record.

  • Serve Counsel: Send request to opposing counsel for processing and objections.
  • Notify Custodians: Inform named custodians and IT for targeted collection.
  • Process ESI: IT or eDiscovery vendor collects, deduplicates, and prepares load files.
  • Deliver Production: Produce via secure transfer, e-filing, or agreed repository with audit logs.

Technical Requirements and Integrations for e-Production

Choose platforms that support required file formats, metadata exports, secure transfers, and integrations with case management and eDiscovery tools.

  • File Formats: PDF, PDF/A, DOCX, XLSX, native
  • Integrations: Connectors for cloud storage and CMS
  • Authentication: Email links, SMS codes, or SSO

Ensure the chosen stack provides an audit trail, supports required metadata fields, and integrates with systems such as case management, cloud storage, and eDiscovery vendors for defensible production.

Typical Timelines and Response Expectations

Timelines vary by jurisdiction and court order; many rules provide a standard response period, but local rules or agreements may shorten or extend deadlines.

Service Deadline:

Serve under local rules; allow reasonable time for response.

Response Period:

Standard practice is 30 days to respond absent different rule.

Motion to Compel:

File promptly after meet-and-confer, following local court timing.

Preservation Duty:

Preserve ESI upon reasonably anticipated litigation.

Production Window:

Agree on phased or rolling production timelines where needed.

Common Drafting and Production Errors to Avoid

  • Overbroad scope that requests irrelevant materials and triggers disputes and expense.
  • Omitting custodians or repositories, causing incomplete collection and follow-up requests.
  • Ambiguous date ranges that lead to inconsistent search hits and motion practice.
  • Failing to specify production format, resulting in unusable file deliveries and extra conversion work.

Consequences of Inadequate or Incorrect Responses

Sanctions: Court-ordered penalties possible
Monetary Fines: Costs or fines against noncompliant party
Adverse Inference: Instruction to jury or factfinder
Evidence Exclusion: Preclusion of late or withheld documents
Contempt: Civil contempt adjudication risk
Reputational Harm: Credibility loss with court or opposing party

eSignature Platform Comparison for Document Collection and Production

Compare common vendor criteria for electronic signing and secure delivery when collecting signed production certifications or consent documents. signNow is listed first per comparison convention.

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 Varies Varies Varies
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Common Questions and Practical Answers

Answers to frequently asked questions about serving, responding, and producing documents electronically in the United States.


Need help? Contact support

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