Scope
Define documents sought with specificity, avoiding vague phrases; list topics, subject matter, or transaction identifiers to limit disputes and disputes over breadth.
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.
Various roles handle production requests depending on context — litigation teams, compliance groups, and records custodians commonly participate.
Coordination among legal, IT, and records teams reduces risk and speeds review while ensuring defensible collection and production.
Define documents sought with specificity, avoiding vague phrases; list topics, subject matter, or transaction identifiers to limit disputes and disputes over breadth.
Name specific individuals, groups, servers, or third-party providers responsible for relevant data to direct collection and reduce overbroad searches.
Provide clear start and end dates and explain any rolling or continuing obligations so parties know the temporal limits of the request.
Specify formats such as emails, attachments, drafts, metadata, databases, or physical documents and whether native files or images are required.
State preferred delivery (PDF/A, native files, load files, metadata fields) and technical specifications for Bates numbering, OCR, and metadata exports.
Require privilege logs identifying withheld items and specify procedures for clawback, reviewer notes, and confidentiality designations under protective orders.
| 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 |
Choose platforms that support required file formats, metadata exports, secure transfers, and integrations with case management and eDiscovery tools.
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.
Serve under local rules; allow reasonable time for response.
Standard practice is 30 days to respond absent different rule.
File promptly after meet-and-confer, following local court timing.
Preserve ESI upon reasonably anticipated litigation.
Agree on phased or rolling production timelines where needed.
| 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 |