Native Files in Litigation: What Every Lawyer Needs to Know

Native Files in Ediscovery

Native Files in Litigation: What Every Lawyer Needs to Know

Native Files in Litigation: What Every Lawyer Needs to Know 1000 744 Rakesh Madhava

What is a native file?

It’s one question we hear time and again from many clients, or “Do I really need natives in litigation?” Most litigators have heard that native files are important in modern litigation. However, many eDiscovery reviewers never even see or use a native file in their work.

The short answer is that a native file is the true document or file. That is the original Word document, spreadsheet, or Outlook email as it was found on a computer or device in its native format. An imaged document, as you may have guessed is merely a rendered image of that native file. An image is an exact copy of the original.

Get to Know Your Native Files in Litigation

  • Native files are the actual files from a custodian’s computer, such Microsoft Word or Excel files, or emails taken directly from an email server.
  • Image files are the visual representation of these files, usually in PDF, TIFF or JPEG format.
  • If there are paper copies of documents, they are usually scanned to one of these formats as well.

Now, Nextpoint’s processing engine can handle a variety of file types, including native and imaged files. However, we tell our clients to make sure they are requesting a loadfile when accepting evidence from another party regardless of the format.

A loadfile is the file used to import data and identifiers of that data (coded, captured or extracted data from ESI processing) into a database. These load files carry all of the essential information about your data – where it came from, where it resides, and pointers to associated metadata.

While it is common to receive productions with images of files, it is important to request a loadfile with those images so that you can match imaged files to the original, native version. Because you cannot stamp a native file without altering the data, Nextpoint creates a separate XML or CSV file showing a unique document ID to identify and track natives files in litigation.

Best Practices for Handling Native Files

The existing caselaw and Federal Rules of evidence demand that evidence in litigation must be kept in a “reasonably usable” format.  It is reasonable to expect non-native files in many matters. However, if evidence is challenged or needs to be authenticated, native or “native-like” copies will be necessary.

A reasonably usable format (other than native) should include full metadata for all relevant fields and full text, along with an image showing all hidden information, such as comments and tracked changes. But native files remain the most useful and complete record of your evidence available.

If you have any questions or comments about the role of native files in litigation, you can download our free ediscovery guide: eDiscovery Collection Best Practices.

Want to know about native file exports and productions in ediscovery? Here’s a great post about how to do it correctly.