Five Ways to Bates Stamp a Production, Compared Honestly
Manual editing, in-house scripts, dedicated batch tools, review-platform numbering, and outside vendors each solve the same problem at different scales. Here is where each one fits and where it breaks.
Every legal team that produces documents ends up choosing a stamping approach, usually by accident. Someone opens a PDF editor, adds a footer, and the firm is now a manual-stamping shop until the first five-thousand-page production makes that impossible. This comparison lays out the five approaches we see most often, judged on the criteria that actually matter when a production is due: how much volume the approach handles comfortably, whether it keeps numbering consistent across multiple productions, how it copes with scanned and mixed PDFs, what kind of verification and audit trail it leaves behind, and what it costs in money and setup time. We build a dedicated batch stamping tool, so read our assessment of that category with appropriate skepticism. The other four are described as fairly as we can manage, and for many teams one of them is the right answer.
| Option | Volume handled comfortably | Consistency across productions | Scanned and mixed PDF handling | Verification and audit trail | Cost and setup effort |
|---|---|---|---|---|---|
| Manual stamping in a general-purpose PDF editorBest for: Small exhibit sets, occasional productions under a few hundred pages, and firms that produce documents a few times a year. | Fine for dozens of files. Becomes a full-day task somewhere in the low hundreds of files and impractical beyond that, because each file is opened and configured individually. | Weak. The starting number, position, and font are re-entered by hand each time, so drift between productions is common unless someone keeps careful notes. | Adequate per file, since you can see each page and adjust. Painful at scale because every odd page size or rotated scan needs its own attention. | Almost entirely manual. There is usually no generated Bates map, so the map has to be built by hand and checked by eye. | Lowest setup. Most firms already own a PDF editor, and no training beyond the header and footer dialog is needed. |
| In-house scripts or command-line toolingBest for: Teams with a technically comfortable staff member and a stable, repeatable production format that does not change much between matters. | Very high. A script does not care whether the folder holds fifty files or fifty thousand, as long as the machine has time to run. | Strong if the script reads its starting number from a ledger file and writes back the ending number. Weak if those values are typed in by hand at each run. | Depends entirely on what the author anticipated. Mixed page sizes, rotated pages, and image-only files often need special cases that get discovered the hard way. | Can be excellent, because generating a Bates map and a hash manifest is easy to add. In practice it is only as good as the person who maintains the script. | No license cost, but real staff time to build, document, and maintain. The hidden cost is the day the author leaves and nobody else can modify it. |
| Dedicated batch stamping applicationBest for: Small and mid-sized litigation teams that produce regularly, handle mixed native and scanned PDFs, and want a repeatable process without writing code. | High. Built to process whole folders in one run, typically with progress reporting and exception handling for files that fail to open. | Strong when the tool saves stamp profiles per matter and tracks the last number used. Check that this is actually a feature and not a manual field. | Usually the strongest of the five, because handling odd page sizes, rotation, and image-only files is the core use case rather than an afterthought. | Good tools export a Bates map and logs automatically. Independent verification still requires a separate check, since the tool grading its own work proves little. | A subscription or license fee, plus an hour or two to define profiles. Far less setup than scripting, more than a PDF editor. |
| Numbering inside a hosted review platformBest for: Matters already loaded into an e-discovery platform for review, especially large productions with families, redactions, and multiple designation tiers. | Very high. Platforms are designed for large collections and apply numbering as part of the production export, alongside load files. | Strong within a single matter on the same platform, since the system tracks ranges. Weaker across matters or if the case moves to another platform. | Generally good, because pages are often imaged to a standard format during processing. Placement control can be less flexible than a dedicated tool. | Typically strong, with production logs and load files generated automatically. The tradeoff is that the underlying files are harder to inspect outside the platform. | Usually the most expensive option, priced per gigabyte or per user, and only sensible when the platform is needed for review anyway. |
| Outsourcing to a litigation support vendorBest for: One-time large productions, firms without litigation support staff, and matters with tight deadlines where internal capacity is the constraint. | Effectively unlimited, since the vendor scales staff and infrastructure to the job. | Depends on the vendor keeping the matter's ledger and profile on file. Switching vendors mid-case is where consistency problems appear. | Handled, but the firm loses visibility into how odd pages were treated unless it asks for exception reports. | Vendors usually provide a production log and Bates map. The firm still owns the obligation to verify before serving, which is easy to forget when the work is outsourced. | Per-page or per-project pricing that can be significant, but almost no internal setup and no software to maintain. |
- Manual stamping in a general-purpose PDF editor: This is the right choice more often than software vendors like to admit, but only until volume or frequency crosses a threshold that every firm eventually feels.
- In-house scripts or command-line tooling: Scripts are powerful and brittle in equal measure; the risk is not the code but the single person who understands it.
- Dedicated batch stamping application: This is our category, so weigh our view accordingly; the honest caveat is that it is overkill for a firm that produces twice a year.
- Numbering inside a hosted review platform: If the documents are already in a platform for review, stamping them there is usually the path of least resistance; if they are not, loading them just to stamp is rarely worth it.
- Outsourcing to a litigation support vendor: Outsourcing moves the labor but not the responsibility; the firm still signs the production letter.
Our verdict
For a firm that produces documents rarely and in small volumes, a general-purpose PDF editor is genuinely enough, and adding software or vendors on top of it would be spending money to solve a problem that does not exist yet. The moment to move on is when someone spends a full day stamping, when a production has to be re-served because of a numbering error, or when two people cannot agree on what the last Bates number was. Those are the symptoms of a process that has outgrown manual work, and they show up in roughly that order.
Past that point, the choice depends on what else the firm already has. Teams with documents in a review platform should number there. Teams with a capable technical staffer and stable formats can do well with scripts, provided the ledger and the script are documented so they survive turnover. Teams that want repeatability without code, and that regularly handle scanned or mixed sets, are the natural fit for a dedicated batch tool. Vendors are the release valve for the occasional oversized production. Whatever you pick, the criteria in this comparison matter more than the category: separate output from originals, a saved profile per matter, a generated Bates map, and a verification step that does not depend on the tool that did the stamping.
Frequently asked questions
Can a firm mix approaches, for example using a PDF editor for exhibits and a batch tool for productions?
Yes, and many do. The important thing is that the ledger for each matter lives in one place regardless of which tool applied the numbers, so the next production starts at the right number no matter who runs it or how. Mixing tools without a shared ledger is how ranges overlap.
Does a more expensive approach mean fewer numbering errors?
Not by itself. Errors come from skipped verification, an unmaintained ledger, and stamping originals in place, and every one of the five approaches can suffer from all three. Cost buys speed and convenience; correctness comes from the process around the tool.
Read the complete guide for the full reasoning behind this comparison.