Every page, numbered once — and it stays that way through every sort, merge, and export.
Bates numbering and stamping software from Medrecords AI applies sequential Bates numbers and confidentiality legends across the full production in one automatic pass. The numbering holds stable through deduplication, re-sorting, and packet-building, so a page keeps the same number for the life of the file — and citations speak Bates.
One pass across the whole production.
Set the prefix, starting number, and padding once, and every page in the production is stamped sequentially — no page-by-page work, no export to a separate stamping tool. Confidentiality and AEO legends go on in the same pass, per page or per document range.
Numbering that survives the life of the file.
A Bates number belongs to the page, not to its position in a list. Deduplicate the file, re-sort it by provider, rebuild the packet: the order changes, the numbers do not. A removed duplicate's number is retired, never reassigned, and a re-production continues the sequence instead of renumbering.
Citations that speak Bates.
Once a production is stamped, every citation in the chronology, summaries, and Q&A answers can carry the Bates reference alongside the page reference. The platform's p.140 and the court file's ADAMS-000140 are the same page, so your work product reads in the register opposing counsel and the court actually use.
A number you can defend, on a page you can trace.
Every stamped page stays linked to the source document it came from, and every stamping run is recorded: range, legends, and retired numbers. When opposing counsel asks why ADAMS-000141 follows a gap, the answer is in the production record — not in someone's memory.
See Hyperlinked ExportsFrom raw packet to numbered production.
Three steps — the stamping happens inside the same platform that sorted and deduplicated the file.
Drop the production set. Pages are read, sorted, and deduplicated; anything questionable is flagged for review first.
Choose the prefix, starting number, and any confidentiality or AEO legends — per case, per client, per packet.
The full range is stamped in one pass and exported production-ready, with the run recorded for later reference.
Who stamps productions with it.
Anyone who produces a file and then has to live with the numbering.
Discovery productions numbered and legended in one pass — and citations that already speak Bates.
For law firmsExam files referenced by stable page numbers, so the report and the record never drift apart.
For IME orgsClaim files produced to counsel with numbering that survives every later re-sort and re-production.
For TPAsBates numbering, answered.
Yes. Set the prefix, starting number, and legend once, and every page in the production is stamped in a single pass — hundreds or thousands of pages, across multiple packets. No page-by-page stamping, and no separate tool between review and production.
Yes. Prefixes, number padding, and starting values are configured per case, so each client or matter keeps its own convention — ADAMS-000001 for one file, a different prefix for the next. The platform remembers the convention for re-productions in the same matter.
Nothing. A Bates number is assigned to the page itself, not to its position in a list. Deduplication, re-sorting, and packet-building change the order you see, never the number a page carries — and a re-production picks up the sequence where the last one ended instead of renumbering.
Yes. Confidentiality and Attorneys'-Eyes-Only legends are stamped alongside the Bates number in one pass, per page or per document range, so a protective-order production goes out numbered and legended together rather than through two tools.
Yes. Once a production is stamped, every citation in the chronology, summaries, and Q&A answers can display the Bates number next to the page reference — p.140 and ADAMS-000140 point to the same page — so work product reads in the register the court file uses.
Related capabilities.
Stamping is the last step of a pipeline — these are the steps around it.
Suggested redactions, human-approved, on a logged production copy.
ExploreRule-based sorting and packet assembly before the stamp goes on.
ExploreOne canonical copy of every page — numbering held stable through removal.
ExploreWord and HTML exports with live links back to every stamped source page.
ExploreNumber your next production automatically.
Upload a file and get it back sorted, deduplicated, and Bates-stamped — with every citation pointing at a page that keeps its number. Handled under our BAA; never used to train a model.