How does Bates numbering work for natively produced files that have no fixed pages?

Bates numbering is a sequential labeling system used in litigation to give every produced item a unique, traceable identifier. It originated with paper, where a stamp printed an incrementing number on each physical page. That model assumes a document has fixed pages you can mark. Many electronic files do not.

The problem with “no fixed pages”

When you produce a file in its native format (a spreadsheet, a database export, a chat thread, an audio or video file, or a dynamic document), there is no fixed page on which to burn a number. A spreadsheet may have thousands of rows and many tabs; how it “paginates” depends on the software, the print settings, and the screen. Stamping a Bates number directly onto such a file would either alter it or be impossible without first converting it to a static image.

How practitioners solve it

Two common approaches keep native files identifiable without destroying their integrity:

• File-level Bates identifiers. The entire native file is assigned a single Bates number (sometimes a beginning and ending range) recorded in the production’s load file and metadata, rather than printed on the file itself. The number, the original filename, and a hash value travel together so the item stays uniquely referenced.
• Bates-stamped placeholders (slip sheets). The production includes a single image page that bears the Bates number and a note such as “Document produced in native format,” pointing to the corresponding native file. This preserves a sequential paper-style index while the usable evidence remains native.

Why this matters

Under the Federal Rules of Civil Procedure, parties generally may specify the form of production for electronically stored information, and produced ESI should be reasonably usable. A file-level identifier plus accurate metadata satisfies the goal of Bates numbering — unique, defensible identification — without forcing a lossy conversion that strips formulas, comments, or hidden data.

Agree on numbering conventions early, ideally in a meet-and-confer or an ESI protocol, and document the scheme so identifiers remain consistent across the production. Requirements vary by jurisdiction, so confirm local court rules and any governing protective order. For broader context, see our e-discovery topic hub.