Production and Defensible Delivery

What This Solves

Production is where discovery disputes most often crystallize. A format that does not match the agreed production protocol, a Bates numbering error, a missing load file field, or an over-redacted document can generate objections, motion practice, or court-ordered re-production. None of those outcomes are acceptable when a matter is already under deadline pressure.

GDF treats production as its own quality-controlled workflow, separate from the review phase. Documents cleared for production go through a dedicated production preparation and verification process before delivery. The result is a production set that matches the agreed specification, includes required documentation, and is verified against the source data before it ships.

FRCP Rule 34 and Production Format Requirements

Federal Rule of Civil Procedure 34 requires a producing party to produce documents as they are kept in the usual course of business or to organize and label them to correspond to the categories in the request. Rule 34 also requires specificity about objections and whether responsive materials are being withheld, and the 2015 amendments specifically require parties to state whether any objection pertains to part of a request and to produce the non-objectionable portion. Courts have increasingly scrutinized productions where the format makes the data difficult to use or where metadata has been stripped without disclosure.

GDF's production workflow is designed to satisfy Rule 34's usability standard. Format is agreed before production begins, and the production set is built to that specification. Metadata fields are preserved and mapped to the load file. If the parties have agreed on a specific Concordance, Relativity, or EDRM XML format, GDF builds to that format and validates the output against it before delivery.

Supported Production Formats

GDF produces in every standard litigation format. The format is agreed during production specification review, and GDF confirms that the receiving party's review platform can ingest the selected format before the production set is assembled.

• TIFF images with extracted text and standard load file (Concordance, Summation, EDRM XML)
• Native format production with metadata load file
• PDF with optical character recognition text and document-level metadata
• Hybrid productions: TIFF for most documents, native for select file types such as Excel spreadsheets and audio files
• Relativity load files (.dat and .opt format)
• Custom formats for regulatory productions to the SEC, DOJ, FTC, or state attorneys general

Privilege Log Support

A privilege log that does not satisfy the receiving party's specificity expectations delays the matter and can generate motion practice. GDF builds privilege logs during review, not after, so the log reflects real-time coding decisions and is complete when production is ready.

Standard privilege log fields include: document identifier (Bates number or control number), document date, document type, custodian, author, all recipients, privilege ground, and a factual description that identifies the nature of the communication without revealing the privileged content. Courts in several circuits have specific requirements for privilege log format and content. GDF can tailor the log to those requirements based on the jurisdiction and any applicable court orders or standing orders from the assigned judge.

For categorical privilege logs, which some courts permit for large volumes of similar documents, GDF can build the category definitions, populate document counts per category, and provide sample documents for each category if the court requires them for in camera review.

Redaction and Redaction Logs

Redactions applied during review are verified during production preparation. GDF checks that every redaction appears on the produced image correctly, that the redaction layer does not allow the underlying text to be extracted from the PDF or TIFF, and that every redacted document appears in the redaction log.

The redaction log records: document identifier, Bates range for the redacted page or pages, redaction reason code, and the date the redaction was applied. For productions involving personal health information, personally identifiable information, or confidential business information, the redaction log provides the documentation that supports the producing party's position if the redactions are challenged. GDF retains the pre-redaction version of every document under the same chain-of-custody protocols as the original collected data.

Rule 502(d) Clawback Support

Rule 502(d) of the Federal Rules of Evidence allows parties to obtain a court order specifying that disclosure of privileged material does not constitute a waiver, which enables faster pre-production privilege review and establishes a clear process for recovering inadvertently produced documents. When counsel has secured a Rule 502(d) order for a matter, GDF's production workflow is configured to track every document that was reviewed for privilege but cleared with less than full certainty, flag those documents for an additional check before production, and generate clawback notices promptly if a privileged document is identified after production.

The clawback log records: document identifier, date identified as potentially privileged, date notice was sent to receiving party, receiving party confirmation of return or deletion, and any subsequent court proceedings related to the clawback. That documentation becomes part of the matter record and is available to support any privilege dispute that arises after production.

Bates Stamping and Numbering

Bates numbers are applied to every page of every produced document during the production preparation phase. The numbering scheme is agreed before production begins and follows the format specified in the discovery agreement or court order. GDF applies Bates stamps to produced images, not to the original collected files, so the originals are preserved without modification.

For matters with multiple productions, GDF maintains a Bates number log that tracks the range assigned to each production volume, the date of each production, and the recipient. Supplemental productions receive the next sequential range so the full Bates universe remains contiguous across the life of the matter.

Our Production Process

What Every Production Includes

Every production delivered by GDF includes a standard package of materials that document what was produced and support any subsequent dispute about completeness, privilege, or format.

Defensibility and Chain of Custody

GDF maintains chain of custody from the point of collection through production delivery. Every step is documented: who collected the data, where it was stored, which workspace it was processed and reviewed in, who handled the production preparation, and how delivery was confirmed. That chain supports any challenge to the integrity or completeness of the production.

For productions subject to court-ordered verification or opposing party challenges, GDF can produce a declaration covering the production methodology, format compliance, Bates numbering accuracy, privilege log completeness, and any other aspects of the production process that are at issue. The declaration addresses technical and operational facts; legal conclusions about responsiveness or privilege remain within counsel's purview.

GDF retains production logs and matter documentation for the period specified by counsel or applicable law. Supplemental productions reference prior Bates ranges, so the complete production history of a matter remains accessible for the life of the litigation.