Establishing secure connection…Loading editor…Preparing document…

Notice of Compliance with Request for Production

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

IN THE UNITED STATES DISTRICT COURT
DISTRICT OF CONNECTICUT

V.

PLAINTIFF

DEFENDANT

CAUSE NO.

NOTICE OF PLAINTIFF'S RESPONSE TO DEFENDANT'S SECOND REQUEST FOR PRODUCTION OF DOCUMENTS

Pursuant to Rule 9(d)3 of the Rules for the United States District Court for the District of Connecticut, Plaintiff hereby files notice with the Court that it has responded to Defendant's Second Request for Production of Documents. Plaintiff has responded, in whole or in part, to Document Request Nos. . Plaintiff has objected, in whole or in part, to Document Request Nos. .

By:



State Bar No.

Attorney for Plaintiff

CERTIFICATE OF SERVICE

This is to certify that I, , attorney for Plaintiff , have this date served a true and correct copy of the above and foregoing Certificate and Notice by U.S. Mail, postage fully prepaid, to the following counsel of record for the Defendant:



This the day of , 20

Respectfully Submitted,



Plaintiff's Attorney

State Bar No.

OF COUNSEL:




Telephone:

Enter text

What the Notice of Compliance with Request for Production Is

A Notice of Compliance with Request for Production is a formal written statement filed or served in litigation that informs the requesting party that the responding party has produced documents or provided access in response to a Rule 34 request. The notice identifies the documents produced, the form of production (paper, electronic, native files), any limitations or redactions based on privilege or confidentiality, and the method and date of delivery. It creates a record of compliance and supports meet-and-confer efforts if disputes arise over completeness or format.

Why a Clear Notice Matters in Discovery

A clean, accurate notice reduces procedural disputes, documents chain of custody, and helps preserve privilege assertions. It also creates a clear audit trail for the court and opposing counsel if objections or motions to compel follow.

Why a Clear Notice Matters in Discovery

Who Prepares and Receives This Notice

Use the notice to document format, production date, custodians searched, and any privilege log references so recordkeeping and meet-and-confer steps proceed efficiently.

  • Requesting counsel — confirms receipt and begins review of produced materials.
  • Responding counsel or records custodian — documents what was produced and when.
  • E-discovery vendors or court clerks — involved when electronic delivery, RON, or filing protocols apply.

Signatory Authority and Typical Preparers

Lead Counsel

Lead counsel signs or certifies the notice when they control discovery for a party; this person is responsible for accuracy and meet-and-confer communications with opposing counsel.

Records Custodian

A records custodian or litigation support manager completes technical details such as file formats, metadata exports, custodian searches, and storage location information recorded in the notice.

Essential Elements to Include in the Notice

A professional notice plainly identifies the case, the request being satisfied, the items produced, the format, any limitations, and the person certifying the production to avoid later disputes about scope or timing.

Case Caption

Full court name, case number, and party names so the notice is unambiguously tied to the litigation and easily filed or attached to the record.

Request Reference

Cite the specific request numbers or document categories from the original Request for Production to show which requests were addressed.

Produced Items

List produced documents by Bates range, file name, or unique ID and include counts or totals when large document sets are involved.

Format of Production

State whether documents were produced in native format, searchable PDF, TIFF, or another format and whether metadata fields were included.

Redactions & Privilege

Identify any redactions or withheld documents and reference an accompanying privilege log or privilege assertion basis.

Certification

Include signature, printed name, title, date, and contact information for the person certifying compliance with the production.

Required Data Points to Record

Case Number: Full docket number
Production Date: MM/DD/YYYY format
Produced Range: Bates or file IDs
Production Format: PDF, native, etc.
Privilege Log: Reference provided
Certifier: Name and contact

Step-by-Step: Preparing and Sending the Notice

Follow these sequential steps to prepare a defensible, auditable notice and avoid common discovery disputes.

  • 01
    Gather Records: Collect files and verify Bates ranges.
  • 02
    Review Privilege: Identify redactions and prepare privilege log.
  • 03
    Document Format: Confirm production file types and metadata.
  • 04
    Serve Notice: Send certified notice and retain proof.

Where to File, Serve, and Submit the Notice

The notice is served on opposing counsel and retained in the producing party's case file; if required, a copy may be filed with the court according to local rules.

  • Opposing Counsel: Primary recipient for service.
  • Court Clerk: File only if local rule requires.
  • E-discovery Platform: Attach notice in production portal.
  • Internal File: Retain in litigation records.

How to Configure an Online Production Workflow

Set simple, verifiable settings before exporting produced files to preserve chain of custody and metadata.

Field Configuration
Authentication Method Email link | SMS code | KBA as needed
Retention Settings Enable archival PDF/A and store originals
Audit Trail Capture IP, timestamp, and user actions
Notifications Auto-email recipients with delivery receipts

Digital Signing and Submission Requirements

Preserve audit logs, select secure file formats, and verify recipient access before finalizing production to reduce follow-up disputes.

  • Supported Formats: PDF, DOCX, TXT
  • Integrations: Salesforce, NetSuite, Google Workspace
  • Authentication: Email, SMS, KBA options

Key Timing Rules and Response Deadlines

Discovery deadlines and production timing are critical. Follow the Federal Rules and local civil rules and document any agreed or court-ordered extensions in writing.

Standard Response Time:

Generally 30 days per Federal Rules of Civil Procedure, Rule 34.

Extension by Agreement:

Parties may extend deadlines by written stipulation.

Court-ordered Schedule:

Comply with dates set in scheduling orders.

ESI Preservation:

Preserve ESI immediately upon notice of litigation.

Sanction Exposure:

Late or incomplete production risks case sanctions.

Milestones from Request to Certification

Track milestones in order so each stage has a clear owner and deadline to reduce disputes and support privileged assertions.

01

Request Served

Date opposing counsel served the original request.

02

Internal Review

Search custodians, collect, and review responsive records.

03

Production Delivered

Transmit files and confirm delivery to requestor.

04

Certification Filed

Certify compliance and retain supporting logs.

Common Preparation Errors to Avoid

  • Incomplete Bates ranges or inconsistent identifiers that make it impossible to match produced files to requests, increasing dispute risk and review time.
  • Failing to disclose format and metadata decisions, such as producing TIFF without load files, which can lead to meet-and-confer disputes over ESI form.
  • Over-redaction or vague privilege descriptions that prompt motions to compel and may require in camera review to resolve.
  • Not preserving ESI promptly after notice of litigation, which can create spoliation allegations and sanctions exposure under court rules.

Consequences of Inaccurate or Late Notices

Motion to Compel: Court may order further production
Monetary Sanctions: Fines or cost-shifting
Adverse Inference: Evidence lost may be presumed unfavorable
Exclusion: Documents may be excluded at trial
Default Judgment: Severe sanction in extreme cases
Ethics Complaint: Misrepresentations risk bar discipline

Real-World Examples of Electronic Production Workflows

These brief examples illustrate how organizations used digital workflows and signed notices to document production and preserve audit trails.

Martin Properties

A small real-estate firm centralized production using online signing and delivery

  • Reduced turnaround time for tenant and lease records
  • Tim Martin: "I can process and execute all of these documents online with 100% compliance and built-in security."

Fertility Centers

A healthcare provider digitized records delivery with strict audit logs

  • Ensured HIPAA controls and traceability
  • John Butler: "The airSlate SignNow team has been exceptional, responsive, the API has been great, and we're extremely happy that we chose airSlate SignNow as a company."

eSignature Vendor Comparison for Preparing and Signing Notices

Compare common feature criteria and starting prices for platform selection; signNow is shown first per vendor comparison standards.

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 by plan Varies by plan Varies by plan Varies by plan
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 by plan Varies by plan Varies by plan

Frequently Asked Questions and Troubleshooting

Answers to common questions about electronic notices, validity, late corrections, confidentiality, and signature methods encountered during discovery.


Need help? Contact support

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