A spreadsheet with formulas, a presentation with speaker notes, or an email stored in its original container can tell a materially different story than a static image. That is why the decision to produce native files is not a formatting preference. It is a production protocol that can affect usability, confidentiality, privilege review, and the defensibility of discovery.
For litigation teams, native production should be planned before collection, review, and production deadlines begin to collide. The right workflow preserves what makes a file useful while giving the producing party control over exceptions, redactions, naming, Bates references, and delivery.
What It Means to Produce Native Files
A native file is produced in the format in which it was created or ordinarily maintained. Common examples include Microsoft Excel workbooks, PowerPoint presentations, Word documents, PDFs, audio and video files, databases, and email files such as MSG or EML. Unlike TIFF or PDF images, native files may retain formulas, hidden worksheets, embedded content, comments, tracked changes, metadata, and other functional characteristics.
A native production does not necessarily mean sending every source file without processing. In a typical legal production, the native is paired with a production image or placeholder, a Bates number, and load files that identify custodians, document families, dates, and other agreed metadata. This structure allows the receiving party to review the native document while preserving a coherent production record.
The protocol matters because native files can expose information that is not visible on the face of a document. A workbook may contain hidden columns. A presentation may include speaker notes. A Word document may carry tracked changes or prior author information. Producing a native without examining its contents and metadata can create an avoidable disclosure problem.
When Native Production Is the Right Choice
Native format is often appropriate when functionality is central to the evidence. Excel files are the clearest example. Rendering an Excel workbook to TIFF or a static PDF can obscure formulas, cell relationships, pivot tables, filters, hidden tabs, and calculations. Financial models, damages analyses, transaction schedules, and operational reports are frequently more meaningful in their native form.
Presentations, multimedia files, design files, and data exports may also lose context when converted. If an animation, embedded video, audio recording, or interactive feature bears on the issues in dispute, a static image may not be an adequate substitute.
That said, native production is not automatically the right approach for every document type. Email and word-processing documents are often produced as images or searchable PDFs because those formats are easier to review, redact, stamp, and cite. The appropriate method depends on the governing order, party agreement, document population, review needs, and sensitivity of the information.
Start With a Written Production Protocol
The most costly native-production issues arise when the parties use the phrase “native format” without defining the operational details. A clear ESI protocol should specify which file types will be produced natively, whether certain categories will be imaged, how redactions will be handled, and what metadata fields will accompany the production.
The protocol should also address file naming and Bates treatment. Native files cannot be physically Bates stamped in the same way as TIFF images. A common approach is to provide a Bates-numbered slip sheet or placeholder image identifying the corresponding native file. The native file name may include the production Bates number, and the load file should map that identifier to the document record.
Family relationships require equal attention. If a produced Excel attachment belongs to an email family, the production data should preserve the relationship between the parent email and its attachment. Without family integrity, reviewers may struggle to understand context, and counsel may face unnecessary questions about completeness.
Review Before You Produce Native Files
A defensible workflow separates the decision to produce a native from the act of releasing it. During review, attorneys and litigation support personnel should identify documents designated for native production and flag any issues that require an exception.
For spreadsheets, reviewers should inspect hidden worksheets, hidden rows and columns, formulas, comments, external links, named ranges, and embedded objects. For presentations, check speaker notes, hidden slides, embedded media, and document properties. For other file types, the focus may include metadata, revision history, geolocation, embedded attachments, or information created by third-party applications.
This is also where privilege and confidentiality decisions must be final. A native file may contain privileged content that does not appear in a rendered image. If review reveals protected information that cannot be safely removed, the producing party may need to withhold the document, negotiate an alternative format, or produce a redacted image in place of the native. The production log should clearly identify the exception where required by the protocol.
Handle Redactions and Exceptions Deliberately
Redacting a native file is not as simple as drawing a black box over text. Redaction must remove the underlying information, not merely hide it from view. For many native formats, a secure redacted version may be impossible or impractical to create without changing the file’s functionality.
In those circumstances, teams commonly produce a redacted TIFF or PDF with the correct Bates designation and a slip sheet stating that the original was withheld or replaced due to redaction. The receiving party still receives a reviewable document, while the producing party avoids releasing concealed data through formulas, document properties, layers, or recoverable content.
Exceptions should be consistent and documented. If a protocol calls for native production of spreadsheets but a particular workbook contains privileged formulas or personal information, record the reason for the image-only treatment. Consistency is what turns an exception from an apparent production gap into a defensible decision.
Build Quality Control Into the Delivery Process
Quality control should verify more than whether the production folder opens. Before delivery, validate that every native file is present, opens as expected, and corresponds to the correct Bates number and database record. Confirm that load files populate properly, text and metadata fields align with the agreed specifications, and document family links remain intact.
Teams should also test the production in the same review environment the receiving party is likely to use. A file that appears correct in a staging folder may fail to map correctly when loaded into a review platform. Production validation should identify duplicate filenames, zero-byte files, password-protected documents, corrupted files, unsupported formats, and discrepancies between the native count and the load-file count.
Chain of custody remains essential throughout this process. Sensitive source files should move through controlled storage, access permissions, documented transfers, and verified delivery channels. This is especially important for matters involving regulated records, employee data, trade secrets, government information, or forensic collections from mobile devices and email accounts.
Production Capacity Matters Under Deadline
Native production requires coordination across legal review, eDiscovery processing, production specialists, and sometimes trial support teams. When a court deadline is approaching, the risk is rarely one large failure. It is a series of small omissions: an unreviewed hidden worksheet, a mismatched Bates number, a missing attachment, or a native file released without its corresponding placeholder.
A qualified legal document services partner can help establish production specifications, process and validate complex file sets, generate Bates-numbered slip sheets, manage secure transfers, and prepare replacement images for exceptions. For high-stakes matters, it is practical to use a provider with both electronic discovery capability and production-floor capacity. Concord Document Technologies supports these connected workflows for law firms, corporations, and government agencies handling sensitive, deadline-driven matters.
The best native production is one the receiving party can use immediately and the producing party can explain without hesitation. Establish the protocol early, review the files for what static images cannot show, and make every exception traceable before the production leaves your control.
