Production, Load Files, Redaction and Privilege Log Validation

Productions That Load Cleanly the First Time

The review is finished, the deadline is close and the receiving side has sent a specification full of field names, image formats and load file encodings. Global Digital Forensics builds the production to that specification on software we own, verifies every redaction in the image, the text and the log, and keeps families and Bates ranges intact. Wherever the receiving side allows it, we test a sample import before the full set ships, and we stand behind the package if a question comes back.

Get a Free Consultation Call (800) 868-8189

Bagged hard drive beside a forensic write blocker.

Agree on the Specification Before the First Document Is Exported

A production is judged by the receiving system, not by the sending one. Before any export runs we sit with counsel and the stipulation or ESI protocol and settle the native and image formats, the text layer, the metadata fields and their order, the load file type and encoding, how families stay together, how Bates numbers and confidentiality designations are applied, how redactions are burned in and how the package travels. Where a regulator or a receiving platform has published its own instructions, we read them line by line, because a format that is close is a format that fails.

The specification becomes the test plan. The handoff includes the production manifest, the field and format mapping, the validation and exception record and whatever privilege log and redaction materials counsel has approved. Wherever the receiving side will allow it, we run a sample import into their system first and resolve missing files, broken parent and attachment links or invalid field values before the full set ships.

Where a Rule 502(d) order is in place, we keep the records that make a clawback fast to execute: which documents were flagged, when, what was corrected in the package and when the recipient confirmed return or deletion.

Primary references: Current Federal Rules of Evidence.

If the ESI protocol is still being negotiated, send us the draft and a senior examiner will flag the fields and formats that cause import failures before you sign it.

Get a Free Consultation

Technical methods and scope

Catch Format, Numbering and Metadata Problems Before the Other Side Does

The problems that stall a production are rarely dramatic. A date field exported in the wrong format, a Bates range that skips, an attachment separated from its parent email, a text file that still holds the words beneath a redacted image. Any one of them gives the receiving side a reason to reject the set or to ask pointed questions about the care taken with everything else. We treat production as its own technical phase after review decisions are final, and we validate the package against the specification and against the source records before counsel authorizes release.

Global Digital Forensics has served clients since 1992, from AmLaw 100 firms to small practices producing their first electronic set, and from Fortune 1000 companies to the midsize business that has never seen a load file. We own the software we use to process and produce, which lets us build productions around the matter and its budget rather than around a platform minimum. The validation and exception record we hand over gives the producing party a clear, documented basis for saying the production is complete and in the agreed form.

Choose the Format and Prove It Imports

We agree on the native, image, text and load file requirements with the legal team and confirm what the receiving system actually accepts before assembly begins. A TIFF production typically carries extracted or OCR text alongside a Concordance, Summation or EDRM XML load structure, while a native production carries the metadata load file that ties each delivered item to its fields. PDF delivery can include searchable text and document metadata when the specification allows it.

Most modern productions are hybrids: images for the bulk of the documents and native files for spreadsheets, audio, video or anything else that loses its meaning when flattened. Relativity deliveries use the .dat and .opt pairing with the agreed fields and image links. Packages for the SEC, the DOJ, the FTC or a state attorney general are built only after their current instructions and any custom format are confirmed, because regulator specifications change and an outdated template is an avoidable failure. In every case a sample import against the real receiving environment is the test we trust and the one we document.

Call (800) 868-8189 or send the discovery schedule to plan the work around it.

Build the Privilege Log Alongside the Review, Not After It

Where counsel wants a privilege log, we develop the entries and the exceptions while coding is under way and reconcile them against the withheld set and the production record before delivery. That ties the approved log to the documents actually held back and to the Bates ranges actually produced, which is where privilege logs usually fall apart.

The log follows the fields, categories and any governing order set in the protocol. The technical record can include the document or Bates identifier, date, document type, custodian, author, recipients, the approved privilege ground and a factual description written to describe the document without disclosing its protected content. We apply that specification consistently and route anything unresolved to the responsible legal reviewer. Where categorical logging is approved, the workflow applies the agreed categories, reconciles the counts and prepares whatever supporting record counsel directs.

Verify Every Redaction in Image, Text and Log

A redaction has to hold in three places at once: the image the reader sees, the text layer a search engine reads and the log that explains why. We check placement on the page, confirm the permanent image output, confirm the redacted words are gone from the extracted text and reconcile each redaction with its log entry before the package is released.

The redaction log records the document identifier, the affected Bates pages, the reason code and the application date, which supports protected health information, personal data and confidential business information under one consistent record. Original unredacted material stays under the matter's access, retention and custody controls, so it is available if a redaction is challenged and is never part of the delivered set.

Ask a discovery specialist how this fits your matter; the first consultation is free.

Track Rule 502(d) Clawbacks So Counsel Can Act Quickly

When counsel supplies an applicable Rule 502(d) order and a written clawback protocol, we track the designated items, implement the approved technical corrections to the package and preserve the records counsel needs for the notice process.

The clawback record identifies the document, the date it was flagged, the date counsel sent notice, the recipient's confirmation of return or deletion and any related proceedings. Those records stay with the matter file so the disclosure and the response can be assessed without reconstructing the sequence from email.

Bring the specification and the deadline to a free initial consultation and we will test the import before the export runs.

Methodology

From Reviewed Set to Validated Production in Four Steps

Map the sources to the specification

We map the selected sources, data types and review decisions to the agreed production specification and the deadline, so every field the receiving side expects has a source.
Preserve the approved source record

We retain the approved source record, custodians, dates and exceptions so each delivered document can be traced back to the material selected for production.
Assemble and test the package

We build the images, natives, text and load files, run a sample import against the receiving environment where possible and resolve exceptions before the full set is finalized.
Validate, deliver and document

We validate the package against the agreed fields, formats and receiving requirements, deliver it through the agreed secure channel and retain the manifest and audit record.

Get a Free Consultation Call (800) 868-8189

Evidence commonly examined

Production data and specifications we review

Custodian and source inventories define the material selected for production and let us account for every item that was or was not included. Microsoft 365 and Google Workspace supply the business suite records in the set, collaboration and messaging sources bring conversations whose relationships must survive in the load file, and computers, phones and file shares contribute the endpoint records. Database and structured exports need field and format mapping for the receiving workflow, and the collection, processing and exception logs provide the technical history behind the package.

What you can expect

Your production package and validation record

The package manifest accompanies the approved production specification and records what was delivered, in what form and in what quantity. Method logs retain the collection and processing details assigned to us, the reconciliation report accounts for exceptions, missing items and required corrections, and the delivered set follows the agreed format with the validation record that answers questions about it months later.

Want to know who would explain this validation record if the production is challenged? Meet the examiners who have described their methods in federal and state courts.

Plan the Production With the Examiner Who Will Build It

Bring the production specification, the receiving platform and the deadline to a free initial consultation. We will walk through field mapping, redaction handling, the sample import and the checks that have to pass before release, and we will tell you where the specification is likely to cause trouble.

Review the data discovery case study, in which raw financial data, email and legacy mainframe source code supplied without access to the live system were made usable for a New York firm, then meet the forensic team and their qualifications to match our experience to your production.

Get a Free Consultation

Frequently asked

Load Files, Bates Ranges and the Production Deadline

What should we define before the production begins?

Settle the production specification with the receiving side: native, image and text formats, the metadata fields and their order, the load file type and encoding, family handling, Bates and confidentiality conventions, redaction treatment and the delivery method. Then agree how validation and exceptions will be handled before anything is exported.

What determines the price of a production?

The size of the reviewed set, the formats required, the number of redactions and privilege entries, whether a sample import is possible and how quickly the set must ship. Ask for an itemized scope with any recurring hosting charges and a change approval process. Because GDF owns its software, we can scale the work to the matter rather than to a platform minimum.

Can you produce from or into our existing review platform?

Yes. Tell us the platform, the export it can generate and the tasks your team will keep. We confirm compatibility, the transfer method and who is responsible for each step before the work starts, and we test the handoff with a sample before the full production.

What if the production deadline is days away?

Call with the deadline, the specification and where the set stands. We will tell you plainly what can be validated in the time available and what the priorities should be, so the schedule is set with the facts in hand.

Can you repair a production after a deficiency letter?

Yes. Send the letter with the original specification and the delivered package, and we trace each complaint to its cause, whether a field mapping, a broken family, a Bates gap or a text layer, then rebuild and revalidate the affected volumes with a record of what changed.

Talk with an examiner

Prepare the Production Before the Deadline Does

Share the formats, metadata fields and family relationships the receiving side expects. We will work through the delivery specification and the outstanding exceptions with you before the export is finalized.

Global Digital Forensics brings court tested forensic expertise and software it owns to every production, with a practice dating to 1992.

Talk with an examiner

Send the Specification to the Examiner Who Will Build It

Send the specification or the deficiency letter before a free first call, and a senior examiner will flag the fields and formats most likely to fail import and set out the validation steps and timing for the set.

Call (800) 868-8189 Get a Free Consultation

For discovery production support, call (800) 868-8189.

Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed November 3, 2026.