Preparing email PDFs for Bates numbering

What a numbering tool actually needs

A Bates stamp is a unique, sequential identifier burned onto each page, so that every page in a production has a name that both sides can use. Applying it is mechanical. Getting a reliable result depends entirely on the input being uniform, and email is the least uniform input in a typical production.

Three properties matter:

• Consistent pagination. Every message rendered by the same pipeline with the same layout, so the page count is a function of the content and not of who printed it from which client.
• A stable order. The sequence the numbers run in is a decision, and it should be made deliberately at conversion rather than inherited from whatever order the file browser happened to hand the stamping tool.
• Predictable filenames. So that after stamping, a file can still be traced back to the message it came from.

Why printing from a mail client fails here

Printing emails to PDF one at a time from Outlook or a webmail client produces none of the three. Page layout varies with the print dialog and the browser. Header presentation differs between clients. Filenames come out as the subject line, which means punctuation, duplicates, and truncation. And the header block is often reduced to a browser print header rather than the From / To / CC / Date / Subject block a produced email is expected to carry.

The result is a set that has to be manually reconciled after stamping, which is precisely the work the numbering was meant to eliminate.

The combined-PDF shortcut

The single most useful thing you can do before stamping a batch of email is to combine it. One PDF, messages in date order, stamped in one pass:

• The sequence cannot break, because there is only one file.
• The order is the order you chose, not the order a tool inferred.
• Reconciling the produced range against your log is reading two numbers, not auditing four hundred filenames.

Keep the individual message PDFs too. When one email becomes Exhibit C, you want that message on its own, not a range extracted out of a combined file.

Where the numbers come from

Nothing here assigns numbers. The starting number, the prefix format, the zero-padding, and the register of which ranges have been used are your firm’s to hold — they have to be, because they span matters and productions and long outlive any single batch of email. This step’s job is to hand your numbering tool a set it cannot mis-stamp.

How to do it in EML Exhibit

1. Convert the batch to PDF

   Render every .eml message to PDF in one pass so pagination and layout are consistent across the whole set. Mixed-source PDFs — some printed from Outlook, some converted, some scanned — are the usual reason a numbered set does not line up.

2. Sort by the date on the email

   Choose the date sort rather than filename order. A chronological set numbers into a sequence that reads as a narrative, which is what makes a thread comprehensible to someone seeing it once.

3. Set the matter prefix

   Enter a prefix such as JONES_001. It lands on every output filename, so files from different matters cannot silently intermingle in a shared document store.

4. Turn on combine

   The combine option produces one continuous PDF of every message in the sorted order. Stamping one file in a single pass is both faster and far less error-prone than stamping four hundred files and hoping the tool kept the order.

5. Stamp in your numbering tool

   Open the combined PDF in Acrobat or your firm's numbering software, set the prefix and starting number, and apply. Because pagination was fixed at conversion, the page count the tool sees is the page count on the exhibit.