Nobody went to law school to run Bates stamps at 9pm.
You don't need a primer on Bates numbering. You need to stop spending an evening driving Acrobat across a production, document by document, watching for the one mistake that breaks every citation downstream. DilloLex applies a clean, consistent Bates sequence across the whole set and builds the index automatically, on hardware your firm owns, so your staff never runs it document by document again.
General information for legal professionals. This is educational material rather than legal advice. Read the full disclaimer.
Bates numbering is the quiet infrastructure of every production: the unique address on each page that lets a lawyer, an adjuster, and a judge point to the same piece of paper and mean the same thing. You know that. You also know it has to be flawless: one continuous sequence, consistent padding, a stamp that never covers text, an index that maps every range to its document. Flawless and mechanical is a brutal combination, a job with no intellectual reward and no tolerance for error, done one production at a time, usually late at night.
Acrobat and the e-discovery suites can apply Bates numbers. That's not the problem. The problem is that someone still has to drive them: open each production, set the prefix and padding, run the stamp, confirm it didn't cover text, get the redact-then-stamp order right, and babysit the machine while it grinds through, all as a separate chore disconnected from naming, redacting, and assembling the same set. The software stamps; a person still does the work.
Why the manual grind hurts
The pain isn't conceptual. It's operational, and it's always the same handful of things:
- It's slow at scale. A few hundred pages is an evening; a real production is a slog spanning multiple days of running and checking sets one at a time.
- One error cascades. A reset counter, a duplicate number, or a gap doesn't just look careless; it breaks every citation that relied on the old numbers.
- Redaction makes it worse. Stamp and redact in the wrong order and you either cover the number or, far worse, place a stamp on top of a redaction and risk re-exposing what you meant to hide.
- It leaves no audit trail. A number dropped on with a basic PDF editor records nothing about who applied it, when, or to which source file. If the integrity of a set is ever questioned, there's no clean way to show the production was numbered once, in order, and never altered.
- Small inconsistencies break the other side's database. A hyphen where the last set used an underscore, or three leading zeros where the convention is six, and the receiving firm's load fails. A formatting slip turns your production into their objection.
- It's unforgiving after the fact. Once a set is produced, you can't renumber it without breaking every prior reference, so the pressure to get it right the first time is total.
The reward for all that care is a number in the corner of a page. Necessary, yes. Worth your paralegal's evening? No.
What it costs your firm
The cost is your people's time on work no client should be billed to think about, plus the quiet risk that rides along with manual stamping: the duplicate range that surfaces in a deposition, the gap that reads as a missing document, the stamp-over-redaction that becomes a disclosure problem. Multiply that by every production your firm sends, and Bates numbering is a standing tax on your capacity and your evenings.
How DilloLex stamps the production for you
DilloLex applies the numbering and builds the index automatically, so the defensible version is also the fast version:
- Drop the production in the matter folder. The appliance picks up the set and OCRs it.
- It flags the identifiers first. PII and PHI are detected and queued for the redaction your staff authorizes, so the page is final before it's stamped, the safe order, every time.
- It applies a consistent Bates sequence. One continuous run, properly zero padded, in the margin in the lower right, on every page, with confidentiality endorsements where you need them.
- It builds the index. A production log mapping every Bates range to its document, ready to cite and authenticate.
- Your staff reviews the finished set. Clean numbers, no gaps, nothing covering text.
The evening of stamping becomes a few minutes of review, and the numbering stays consistent across every production your firm sends because a machine applied it instead of a tired paralegal at 9pm.
Because a machine applied it, the production is reproducible. Each stamped file carries a content hash, and the appliance keeps a production log of what was assembled, in what order. If the numbering is ever challenged, you can show exactly what went out and that nothing changed after the fact. A stamp dropped on in a PDF editor leaves no such record.
The same engine across your filings
Because the appliance does this for any document set, the same clean numbering and indexing serves the rest of your work: the financial production behind an NRCP 16.2 disclosure, the records and bills in a PI demand package, your responses to requests for production, and your trial exhibits and appellate appendices. One stamping-and-indexing step your team never has to run document by document again.
A note on native files and e-discovery
Some files (spreadsheets, audio, video) are produced natively and can't carry a visible stamp on a page. The appliance handles them the standard way: a single-page Bates numbered placeholder stands in for the native file in the sequence, paired with the file's own identifier and an index entry recording what it is and where it sits in the production. A large electronic production that has to ship with industry-standard load files (DAT, OPT) still belongs in your e-discovery platform; DilloLex owns the paper-and-PDF side and the production index, while the load-file generation stays in your e-discovery platform. The principle still holds: every item has a unique, citable address, and you didn't stitch it together yourself.
Common questions
What is a Bates number?
A unique identifier stamped on each page of a document production, applied in one continuous sequence, so any page can be cited unambiguously and the integrity of the set is verifiable.
What is the standard Bates number format?
A prefix identifying the producing party or matter plus a zero padded sequence number, for example SMITH000001, often with a confidentiality endorsement such as CONFIDENTIAL or ATTORNEYS' EYES ONLY where a protective order applies. Reserve enough digits to cover the whole production.
How do you Bates stamp a PDF?
Apply the number in a consistent corner, conventionally the lower right, in the margin so it never covers text, on every page, without resetting the counter. Redact first, then stamp, so the number lands on the final page and never sits over a redaction.
What is the difference between Bates numbers and exhibit numbers?
Bates numbers uniquely identify every produced page in sequence; exhibit numbers label specific documents offered as exhibits. A single exhibit can span a Bates range, and the two systems coexist.
What are the most common Bates numbering mistakes?
Resetting the counter (which creates duplicate numbers), gaps that read as missing documents, inconsistent padding or prefixes, stamps that cover text, renumbering a set that was already produced, and a stamp interacting badly with a redaction.
A note on accuracy
This guide is general information for legal professionals. It is not legal advice, it does not create an attorney-client relationship, and it does not address the requirements of any specific case, protective order, or court. Production format, confidentiality designations, and e-discovery protocols are governed by the applicable rules, any operative protective or ESI order, and the parties' agreements; confirm those before relying on anything described here.