FinchContext
Run with

Build Production Transmittal Letter

Skill: Convert production-volume metadata into an FRCP-compliant transmittal letter

Region: United States Category: Legal / eDiscovery Does: Takes the metadata for a document production volume and generates a production transmittal letter (cover letter) plus an optional per-volume inventory — the document that accompanies a discovery production and records what was produced, in what form, and under what terms. Authority: FRCP 34(b)(2)(E) · FRCP 26(a)(1)(A)(ii) · local-court ESI production orders · governing protective order

The transmittal letter is the official record of a production: it ties a Bates range to a set of responsive requests, states the production format, and preserves objections, confidentiality designations, and clawback rights. It is sent to opposing counsel with each volume (often rolling). Confirm the format and content against the case ESI protocol and protective order.


When this applies


Input data required

Group Fields
Parties producing party + counsel; receiving party + counsel; matter caption & case number
Volume volume name/number (e.g. VOL003), production date, Bates range (begin–end), document & page counts
Format form of production (native, single-/multi-page TIFF + text + load file), load-file type (DAT/OPT/EDRM), metadata fields produced, native file types
Scope the requests for production (RFPs) this volume responds to; date range; custodians covered
Designations confidentiality tiers applied (Confidential / Highly Confidential–AEO)
Exceptions redactions made (with basis), documents withheld for privilege (refer to privilege log), families
Delivery & terms delivery method (SFTP/encrypted media), FRE 502(d) clawback reservation, objections preserved

Letter structure

1. Caption & date — matter, case number, addressee counsel
2. Production statement — "Producing party hereby produces documents Bates ABC000001–ABC004500"
3. Responsive scope — the RFP numbers this volume responds to (and any continued/rolling note)
4. Form of production — native vs imaged; load-file format; metadata fields; text/OCR
5. Custodians & date range covered (if disclosed)
6. Confidentiality — designations applied under the protective order
7. Redactions & withholdings — categories redacted + basis; privileged docs withheld (see privilege log)
8. Clawback / reservation — FRE 502(d) order reference; reservation of objections; no waiver
9. Delivery — method, encryption, volume contents (load files, natives, images, text)
10. Inventory attachment (optional) — per-volume: Bates range, doc/page counts, designation breakdown

Drafting rules


Worked example (outline)

Re: Acme Corp v. Beta LLC, No. 25-cv-014 — Defendant's Third Production (VOL003)
Date: 2026-05-31
Produced: Bates BETA0008001–BETA0011200 (1,040 documents / 3,200 pages)
Responsive to: RFP Nos. 4, 7, 9–12
Format: Multi-page TIFF + extracted text + Concordance DAT/OPT load file; spreadsheets produced natively
        with slip-sheets; metadata fields per ESI Protocol §5
Custodians: J. Doe, R. Roe (Jan 2023–present)
Confidentiality: 212 documents designated "HIGHLY CONFIDENTIAL – AEO" per Protective Order ¶7
Redactions: PII redacted under FRCP 5.2; 14 documents withheld for privilege (see concurrently served Privilege Log P-0001–P-0014)
Clawback: Produced subject to the FRE 502(d) Order entered 2025-09-01; no waiver
Delivery: Encrypted SFTP, password under separate cover

Validation checklist


Last updated: 2026-05-31 — confirm production-format and content requirements against the case ESI protocol, the protective order, local rules, and current FRCP 34(b)(2)(E) before serving the production.