Do You Need to Combine PDFs Before Bates Numbering?

When a document production contains dozens or hundreds of PDFs, one of the first instincts may be to combine everything into a single enormous PDF before Bates numbering begins.

That workflow is understandable. Some production tools have historically worked best with one file. Other systems have made document ordering cumbersome enough that combining everything beforehand felt safer. And once a process works a few times, it can easily become the way every production is prepared.

But combining the files first is not inherently part of Bates numbering. In many cases, it is an extra preparation step you can simply skip.

Bates numbering does not require one giant PDF

A Bates sequence needs an intentional document order and a consistent numbering setup. It does not require every source document to be merged into one physical PDF beforehand.

With BatesNumbers, multiple individual documents can be uploaded as part of the same production. The numbering can continue across those documents while the files themselves remain separate.

If the documents are already organized the way you want them, combining them first may create work without adding much value.

Why people combine productions in the first place

There are perfectly reasonable reasons this habit developed. A legal team may have used software that expected a single input PDF. Someone may have experienced a production where files appeared in the wrong order. A vendor may have requested one consolidated document. Or a team may simply have inherited a workflow that has been used for years.

None of that means the workflow is wrong. It just means it is worth asking whether the combining step is still solving a problem.

• Does your current Bates-numbering workflow actually require one PDF?
• Are you combining files only because that is how the last system worked?
• Are the documents already organized into a useful folder structure?
• Will you want the produced documents to remain separate afterward?
• Are you spending time merging files only to recreate their organization later?

Keeping documents separate can preserve useful organization

A production is often more than a stack of interchangeable pages. The individual documents may already represent correspondence, reports, exhibits, records, photographs, drawings, or other logical groups.

Keeping those documents separate can make the production easier to understand and manage. It also avoids turning a collection of reasonably sized source files into one massive PDF that has to be opened, transferred, checked, and potentially rebuilt if something changes.

If the documents are already arranged in folders, another option is to place the production into a ZIP file and upload the ZIP. BatesNumbers can preserve the folder structure so the organization does not have to be flattened simply to apply a continuous Bates sequence.

Document order still matters

Skipping the merge step does not mean ignoring document order. Continuous Bates numbering will follow the production order you establish, so that order should still be reviewed before final processing.

Individual uploaded files can be reviewed and reordered before finalizing the job. Files contained within a ZIP are initially discovered in filename order and can also be reviewed as part of the production setup.

This is also why a short production review is worth doing before the numbering run. The five-minute production check covers document order, final versions, unusual pages, and Bates settings before the production is finalized.

When combining PDFs still makes sense

There is nothing wrong with combining a production when that is the format you actually want. Some teams prefer one consolidated PDF. A recipient may request one file. A particular production protocol may call for it. Or the source material may already exist as a single combined document.

BatesNumbers can work with that too. The point is not that combining files is a mistake. The point is that it should be a choice rather than an assumed prerequisite.

Large combined PDFs can create their own headaches

Combining a large production can also create a much larger working file than any of the original documents. That may mean more time spent merging, transferring, reopening, checking, or rebuilding the file if one source document needs to change.

Productions containing scans, photographs, oversized drawings, or other unusual pages can make that effect even more noticeable. Keeping the original documents separate may make it easier to identify and manage the unusual pieces of the production.

This does not mean a large combined PDF is inherently a problem. It simply means there is little reason to create one solely because you assume Bates numbering requires it.

Sometimes the fastest preparation step is the one you skip

If you already have twenty, fifty, or two hundred documents ready for production, you may not need to spend additional time turning them into one file before Bates numbering begins.

Upload the individual documents, or package an organized folder structure into a ZIP. Review the document order, configure the Bates sequence once, preview representative pages, and finalize when the production looks right.

If you prefer one combined PDF, use one. If you do not, do not create extra work simply because an older workflow taught you that you had to.

Sometimes improving a production workflow is not about adding another step. It is about realizing you can remove one.