Caption and Parties
Include full court caption, docket number, and names of requesting and responding parties so the request is an enforceable court document and easily tied to the case file.
A well-drafted Request for Production narrows disputes, speeds evidence exchange, and reduces the likelihood of objections or sanctions. Clarity about formats, date ranges, custodians, and privilege logs helps parties meet discovery obligations while protecting confidential information under protective orders.
Litigation counsel, corporate litigation teams, paralegals, and records custodians commonly draft and respond to Requests for Production in civil cases; courts also review disputes and motions related to responses.
Clear role assignments and documented chain-of-custody reduce inadvertent omissions and strengthen responses to motions to compel under FRCP 37.
Include full court caption, docket number, and names of requesting and responding parties so the request is an enforceable court document and easily tied to the case file.
Define terms (e.g., 'document', 'communication', 'you', 'custodian') and provide controlled meanings to avoid ambiguity and limit scope disputes during meet-and-confer sessions.
List discrete categories (e.g., emails to or from specific custodians, contracts, invoices) rather than open-ended phrasing to increase proportionality and reduce objections.
Specify a clear date range and identify custodians or systems (e.g., custodian names, shared drives, cloud services) to focus collection and preservation efforts.
State acceptable formats (native, searchable PDF, load files), metadata fields to include, and whether OCR or Bates numbering is required for consistency with e-discovery protocols.
Require a privilege log with entries for withheld documents and define the redaction standard; include instructions for clawback agreements or provisional privilege assertions.
| Field | Configuration |
|---|---|
| Production Format | Searchable PDF with text layer, or agreed native files |
| Metadata To Include | Date, author, recipients, file path, hashing |
| Pagination/Bates | Sequential Bates stamping required |
| Privilege Log Format | CSV or PDF with required columns |
Identify platform capabilities and integrations needed to collect, process, and deliver ESI in the requested formats.
Confirm that the chosen vendor or in-house tooling can produce metadata, load files, and chain-of-custody reports to meet court or opposing counsel expectations.
Commonly 30 days after service under FRCP 34(b)(2)(A)
Often required within 14–21 days to narrow disputes
Agreed rolling productions frequently set 7–30 day intervals
File after meet-and-confer; local rules vary
Preserve relevant ESI from the date of litigation hold
| 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 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 |