Which comes first, redaction or Bates stamping, when you prepare a document production?

The usual order and why it works

The conventional sequence is review, then redact, then stamp, then produce. Redactions come before stamping because redaction, done properly, permanently alters the page content: text is removed, the underlying image is burned, and metadata is scrubbed. If you stamp first and then redact, the redaction tool has to work on a page that already carries a stamp, and any process that re-renders the page (which is what burning a redaction does) risks changing the stamp's rendering, flattening it into the image, or, in the worst case, redacting over it if the redaction box drifts. Related: Why is it critical to preserve original files when stamping PDFs for a case?

Stamping after redaction also gives you a clean checkpoint. The redacted set is the final content; stamping it produces the final production images; nothing about the content changes after that point. That makes verification simpler, because the only difference between the redacted set and the produced set should be the stamp itself. Any other difference is a defect you can catch by comparing page counts and hashes. Related: How can a small legal team batch-stamp thousands of pages without losing a whole day?

Keep reading: What exactly is Bates numbering and why do law firms rely on it for documents?, How do you keep Bates numbering consistent across multiple separate document productions?, When should you apply confidential or privileged watermarks to a batch of documents?. See how PdfStampr helps you bulk pdf stamping and bates numbering.

When stamping before redaction makes sense

There is a legitimate reason to apply a number before redaction: review teams often need a stable page identifier during review, long before the final production set exists. The answer is to apply a control number or a provisional identifier at ingestion, use it throughout review and redaction logging, and then apply the production Bates number to the final redacted images. The control number may be stamped or may live only in the review platform; if stamped, it goes in a different position or is removed before production stamping.

A second scenario is a rolling production where documents were already produced and now need additional redactions, perhaps because a privilege call changed or a protective order was modified. In that case the original Bates number must be preserved, so the redaction is applied to the already-stamped page and the page is re-produced with the same number, usually with a notation in the production letter. The rule of thumb: for new productions, redact then stamp; for re-productions of already-numbered pages, redact the numbered page and keep the number. Related: What exactly is Bates numbering and why do law firms rely on it for documents?

Managing the redaction log alongside the stamp

Every redaction should be tied to a page identifier and a reason. If the log references control numbers during review, add a column for the final Bates number once stamping is complete, so the privilege log and redaction log can be cited in production correspondence using the numbers the other side will see. Doing this mapping once, with a spreadsheet join or a load file export, is far easier than reconstructing it during a motion to compel.

Redaction labels also interact with stamping. Many teams mark redaction boxes with a short reason such as a privilege basis. That label sits inside the content area, while the Bates stamp sits in the margin, and they should not collide. If your redaction tool and stamping tool are separate products, check that the redaction label fonts and the Bates stamp fonts are both embedded so the final PDF renders identically on the recipient's machine. Related: How do you keep Bates numbering consistent across multiple separate document productions?

Verification steps specific to redacted productions

After stamping a redacted set, verify two things beyond the usual number sequence. First, confirm that redactions are actually burned in by searching the text layer for terms you know were redacted; if the term is found, the redaction was a visual overlay rather than a true removal and the production is not safe to send. Second, compare the stamped set against the redacted set page by page, checking that no page was re-rendered in a way that reintroduced hidden content, which can happen when a tool rebuilds a page from an older cached version.

Finally, keep three distinct sets: the original unredacted files, the redacted but unstamped set, and the stamped production. Store them separately and label them clearly. The middle set is the one people forget, but it is the set you will need if a redaction has to be lifted later, because you can re-stamp from it without starting over. Deleting it to save space is a false economy.