Establishing secure connection…Loading editor…Preparing document…

Legal Response to Production

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

LEGAL RESPONSE TO PRODUCTION

Court:    Case No.:

Plaintiff(s):

Defendant(s):

Responding Party:    Counsel for Responding Party:

Requesting Party:    Counsel for Requesting Party:

Recitals

WHEREAS, on or about the Requesting Party served Requests for Production of Documents and Things on the Responding Party; and

WHEREAS, the Responding Party has reviewed the requests and, subject to the objections and reservations set forth below, has undertaken a reasonable search and is prepared to produce responsive documents as described in this Response; and

WHEREAS, the parties desire to set forth the Responding Party's objections, responses, and the procedures governing production and claims of privilege or confidentiality.

NOW, THEREFORE

In consideration of the foregoing recitals and the mutual covenants herein, Responding Party responds to the Requests for Production as follows.

1. Definitions

For purposes of this Response, the following terms have the meanings set forth below: "Document" or "Documents" means all written, recorded, printed, electronic, magnetic, or other tangible items that are within the scope of Federal Rules of Civil Procedure governing production; "Communications" include any correspondence, emails, notes, reports, or other transmissions between persons; and "You" and "Your" refer to the Requesting Party, collectively.

2. General Objections

Responding Party makes the following general objections to each Request for Production. These objections are incorporated by reference into each specific response and are not waived by failure to repeat them verbatim in any particular response.

a) Relevance and Proportionality: Responding Party objects to any request to the extent it seeks information that is not relevant to the subject matter of this action or not proportional to the needs of the case under governing procedural rules.

b) Overbroad and Unduly Burdensome: Responding Party objects to requests that are overbroad in scope, unduly burdensome, or seek unrelated or cumulative materials beyond a reasonable search.

c) Privilege and Protection: Responding Party objects to requests to the extent they call for production of materials protected by the attorney‑client privilege, attorney work product doctrine, common interest doctrine, or any other applicable privilege or protection. Such materials will be withheld and logged in a privilege log.

3. Specific Responses to Requests for Production

The Responding Party provides the following specific responses. Each response states objections (if any), identifies whether documents will be produced, and describes any claim of privilege or other protection.

Request No.:

Relevance    Overbroad    Privilege/Protected    Unduly Burdensome

Production Status:    Produced    No Responsive Documents Found    Withheld (see privilege log)

Date(s) of Production (if produced):

Request No.:

Relevance    Overbroad    Privilege/Protected    Unduly Burdensome

Production Status:    Produced    No Responsive Documents Found    Withheld (see privilege log)

Date(s) of Production (if produced):

Request No.:

Relevance    Overbroad    Privilege/Protected    Unduly Burdensome

Production Status:    Produced    No Responsive Documents Found    Withheld (see privilege log)

Date(s) of Production (if produced):

4. Privilege Log and Withheld Documents

Documents withheld on the basis of privilege or protection are described sufficiently in a privilege log, which identifies for each withheld document: (a) a unique log identifier; (b) document date; (c) author(s); (d) recipient(s); (e) document type; and (f) privilege or protection asserted. The privilege log will be served contemporaneously with or promptly following this Response unless otherwise agreed.

5. Form of Production and Preservation

Unless otherwise stipulated, responsive electronically stored information will be produced in reasonably usable native or image format with associated metadata where available. Paper documents will be produced as single‑sided, legible images. The Responding Party will preserve potentially relevant documents in its possession, custody, or control to the extent required by applicable preservation obligations.

6. Supplementation

Responding Party acknowledges a continuing duty to supplement or amend its responses and production in accordance with applicable procedural rules upon discovery of additional responsive information or documents.

7. Reservation of Rights

By making these responses and producing documents, Responding Party does not waive, and expressly reserves, all objections as to admissibility, relevance, materiality, confidentiality, authenticity, or privilege. No response constitutes an admission of fact, liability, or that any document is relevant or admissible at trial.

8. Notice and Contacts

9. Governing Law; Miscellaneous

This Response shall be governed by the substantive and procedural law of the jurisdiction in which the action is pending. The headings in this Response are for convenience only and shall not affect its interpretation. If any provision of this Response is determined to be invalid or unenforceable, that determination shall not affect the remaining provisions, which shall remain in full force and effect.

Entire Agreement: This Response, together with any privilege log and any stipulated agreements regarding production, contains the entire understanding of the parties with respect to the subject matter hereof and supersedes any prior written or oral understandings related to the Requests for Production.

Amendments and Waiver: Any amendment or waiver of any provision of this Response must be in writing and signed by the party against whom enforcement is sought. No failure or delay in exercising any right shall operate as a waiver.

10. Verification

I declare under penalty of perjury under the laws of the jurisdiction in which this action is pending that I have read the foregoing responses and that the statements contained herein are true and correct to the best of my knowledge, information, and belief, based upon a reasonable inquiry.

Responding Party:

By:

Date:

Requesting Party (Acknowledgment):

By:

Date:

Enter text✕

What a Legal Response to Production Is and When it Applies

A Legal Response to Production is a formal written reply to a discovery request seeking documents or electronically stored information in civil litigation. It identifies responsive documents, asserts any objections, and states whether documents are being produced, withheld, or produced subject to conditions. Federal cases follow the Federal Rules of Civil Procedure (see Rule 34) while state practice may vary. Well‑prepared responses protect privilege, preserve objections, and create a clear record for meet‑and‑confer efforts or motions to compel.

Why a Clear Response Protects Your Case Position

A complete, timely response documents compliance, preserves objections and privilege, and reduces exposure to sanctions or spoliation claims. It clarifies scope, format, and custodians for produced records and sets expectations for any follow‑up discovery.

Why a Clear Response Protects Your Case Position

Who Prepares and Reviews a Response to Production

Final approval should come from counsel to ensure privilege claims, objections, and production specifications are legally defensible.

  • Plaintiff or defense counsel reviewing demands and coordinating custodial searches and redactions.
  • In‑house legal or compliance teams gathering corporate records and assembling privilege logs.
  • eDiscovery vendors or litigation support teams executing ESI collection, filtering, and production tasks.

Core Components That Make a Professional Response

A professional response to production blends formal legal language with operational detail so recipients can identify produced items and understand asserted protections.

Cover Statement

A formal captioned response referencing each request, identifying the responding party, and noting the date and method of service; provides the document’s procedural context.

Response Entries

Line‑by‑line answers: admit responsive materials exist, state whether documents are produced, and specify limitations or scope narrowed by date, custodian, or subject.

Objections

Clear, specific objections (overbreadth, undue burden, relevance, confidentiality) that articulate the basis for refusal or partial compliance.

Privilege Assertions

Privilege claims identifying withheld documents and referencing a privilege log when required, with a description of the privilege type and factual basis.

Production Format

Detail format and media for production (native files, TIFF/PDF, load files, metadata fields) and any redaction or Bates‑numbering protocol.

Privilege Log

A separate, indexed log describing withheld items by identifier, date, authors, recipients, and privilege basis when privilege is asserted.

Essential Fields and Metadata to Include

Requesting Party: Name of party who served the request
Request Identifier: Number or text of the specific production request
Response Date: Date the response was served
Scope Limitations: Temporal, custodian, or subject restrictions
Privilege Basis: Type of privilege asserted, e.g., attorney‑client
Production Format: Native, PDF, or load file specification

Step‑by‑Step: Preparing a Legally Sound Production Response

Follow a disciplined workflow from review to production to reduce risk and speed compliance.

  • 01
    Review Requests: Read each request and identify scope, timing, and custodians.
  • 02
    Search Records: Run targeted custodian and keyword searches across systems.
  • 03
    Assert Objections: Draft specific objections and identify privileged items for log inclusion.
  • 04
    Produce and Certify: Assemble produced files, add load files/Bates numbers, and serve with a written certification if required.

Setting Up an Online Production Workflow

Configure your digital workflow to track collections, redactions, and signoffs while preserving metadata and audit trails.

Field Configuration
Authentication Method Email links or SMS codes for signers and approvers
Document Format PDF with extracted text plus native file backup
Metadata Fields Include custodian, file path, date, and bates range
Audit Trail Capture timestamps, user ID, and IP for each action

Where to Send Your Response and Productions

Deliver responses according to the service rules and any court e‑filing requirements; document the method and proof of service.

  • Opposing Counsel: Serve the response and production in the agreed format
  • Court Clerk: File summaries or certificates when local rules require
  • eDiscovery Platform: Upload native files and load files to shared review platforms
  • Third‑Party Custodian: Deliver subpoenaed materials through secure channels

Technical Requirements for eSubmission and eSigning

Confirm encryption in transit (TLS) and at rest (AES‑256), maintain audit trails, and retain original native files per agreed protocol.

  • File Formats: PDF, native Office files, and ESI load files
  • Authentication: Email/SMS codes, optional KBA, or SSO
  • Integrations: Salesforce, NetSuite, Microsoft 365, Box supported

Key Deadlines and Timing Considerations

Observe court rules and local practice; federal cases commonly follow FRCP timing but courts set local variations and extensions.

Initial Response Window:

Often 30 days after service under FRCP 34; local rules may shorten or extend

Privilege Log Timing:

Provide concurrently or within the timeline set by the court or meet‑and‑confer

Meet‑and‑Confer:

Initiate promptly to resolve scope and format disputes

Motions to Compel:

File after meet‑and‑confer if disputes remain; timely filings vary by jurisdiction

Preservation Duties:

Begin preservation when litigation is reasonably anticipated

Common Risks and Potential Sanctions for Deficient Responses

Waiver of Objections: Risk of losing unasserted objections
Privilege Waiver: Overbroad disclosure may waive privilege
Court Sanctions: Monetary or evidentiary sanctions possible
Spoliation Claims: Failure to preserve can trigger severe remedies
Contempt Risk: Noncompliance with court orders may incur contempt
Reputational Harm: Repeated discovery failures harm credibility

How a Formal Response Differs from a Privilege Log

Compare the role and contents of a response to production with a separate privilege log to reduce confusion during discovery.

Criteria Response Privilege Log
Primary Purpose answer scope describe withheld items
Timing served timely often contemporaneous
Required Content responsive status document metadata
Sanctions Risk

Practical Tips for Accurate and Efficient Responses

Adopt repeatable processes that combine legal review with technical collection to minimize errors and speed production.

Centralize Custodial Searches
Assign custodians and run coordinated searches to avoid duplication and ensure consistent search terms across systems.
Use Consistent IDs
Bates‑number produced files and use matching IDs in privilege logs to enable easy cross reference during review.
Document Decisions
Record search terms, custodians, and redaction rationales to support meet‑and‑confer and protect against sanctions.
Preserve Native Files
Keep native copies of ESI when possible to preserve metadata and support forensic validation if contested.

Illustrative Use Cases for a Response to Production

These concise examples show how responses streamline discovery and reduce disputes in common scenarios.

Employment Dispute

A company identifies custodial emails responsive to termination claims

  • Filters reduce non‑responsive data by 60%
  • The response documents searches and asserts privilege where applicable, avoiding a motion to compel.

Contract Litigation

Counsel coordinates production of contract drafts and redacted pricing schedules

  • Metadata maintained for key documents
  • A clear privilege log narrowed the dispute and preserved settlement options.

eSignature Provider Comparison for Document Execution and eSubmission

Comparing common eSignature providers on price and core capabilities relevant to producing signed discovery certifications or executed agreements.

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 credit card Varies by vendor Varies by vendor Varies by vendor Varies by vendor
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 Responses to Production

Common practical and legal questions about preparing responses, asserting privilege, and producing ESI with defensible procedures.


Need help? Contact support

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