APPROVED, DRAFT, CONFIDENTIAL: A Guide to Document Control Stamps

Somewhere in every office — physical or digital — there is a moment when someone looks at a document and asks: is this the final version? Or: has this been paid? Or: can I forward this to the client?

A signature answers who. A date answers when. But neither answers what stage is this document in right now. That is the job of the humble status stamp: APPROVED, DRAFT, CONFIDENTIAL, PAID, VOID, COPY. These are not glamorous. Nobody frames them. But they prevent more confusion per square centimeter than any other mark on a page.

This guide covers how to choose, design, and place document control stamps so they do their job without cluttering your files. If you are looking for company seals or signature-area stamps, see how to design a company seal and seal placement guide. Here, we are talking about the workhorses: the stamps that move a document through its lifecycle.

Why status stamps still matter in a digital world

You might think version control software, email timestamps, and approval buttons in project management tools have made status stamps obsolete. They have not — for the same reason that a "WET PAINT" sign has not been replaced by a database entry somewhere recording that the paint is wet. The stamp is visible on the thing itself. You do not need to check a separate system to know what you are looking at.

This matters especially when documents leave your system. A PDF attached to an email has no connection to your approval workflow. A printed contract sitting on a desk has no link to Jira. A scanned invoice in someone else's filing cabinet carries no metadata from your accounting software. The stamp travels with the document, and that is its entire value.

In East Asian business practice, status stamps are deeply embedded. Japanese offices use a rich vocabulary of stamps beyond the personal hanko: 承認 (approved), 検印 (inspected), 回覧 (circulated), 至急 (urgent), 親展 (confidential). Chinese companies stamp invoices with 已付 (paid) and receipts with 已收 (received) as a matter of routine bookkeeping, not ceremony. Korean offices use 결재 (approval) stamps in hierarchical sign-off chains. These are not relics — they are current practice, often alongside digital systems rather than replaced by them.

In Western offices, the equivalents are usually rubber stamps or, increasingly, digital stamp images placed on PDFs. The function is identical: mark the document's status so the next person who picks it up does not have to guess.

The stamps you actually need

Not every office needs every stamp. Here is a practical inventory, grouped by function. Pick the ones that match your workflow; ignore the rest.

Status stamps

DRAFT. The most important stamp you can own, and the one most people forget. A document marked DRAFT cannot be mistaken for a final version. This matters more than you think — drafts get forwarded, printed, filed, and sometimes acted on as if they were final. A clear DRAFT mark, ideally in a color that stands out against the document text, prevents that. Some people prefer "FOR REVIEW" or "NOT FINAL" — any of these work, as long as the message is unambiguous.

APPROVED. This stamp says: someone with authority has reviewed this document and accepted it. In a small business, that someone might be you. In a larger organization, it might go through multiple approvers. The stamp does not replace the approval signature — it supplements it by making the status visible at a glance, even on a thumbnail or across a room. Consider including a date line or a space for initials alongside the word.

REJECTED. Less common but useful when documents cycle through review. A REJECTED stamp with a date prevents the rejected version from being confused with a later approved version. If "REJECTED" feels too harsh for your culture, "RETURNED" or "REVISE AND RESUBMIT" accomplish the same thing with softer language.

Financial stamps

PAID. If you process invoices, a PAID stamp with a date field is one of the most practically useful marks you can have. It turns the invoice into its own receipt. When you look at it six months later in a filing cabinet or a PDF archive, you know instantly whether it was settled. Without it, you have to cross-reference your bank statements or accounting software every time.

RECEIVED. For incoming documents — invoices from vendors, deliveries, applications. The stamp records when the document arrived, which matters for payment terms, deadlines, and disputes. A RECEIVED stamp with a date is especially valuable when you deal with paper documents that do not have email timestamps.

VOID. For cancelled checks, superseded invoices, withdrawn documents. The VOID stamp needs to be large and obvious enough that nobody can miss it — a small, discreet VOID in the corner defeats the purpose. If you are voiding a financial document, the stamp should cross over the key fields (amount, payee) to make it visually clear that this document is no longer actionable.

Classification stamps

CONFIDENTIAL. This stamp signals that the document should not be shared freely. It does not enforce confidentiality — no stamp can do that — but it establishes that the sender intended the contents to be restricted. This can matter legally if a dispute arises about whether information was shared without authorization. A CONFIDENTIAL stamp on the first page of a document is a clear record of intent.

INTERNAL USE ONLY. A lighter version of CONFIDENTIAL. It says: this is fine to share within the organization, but do not send it outside. Useful for pricing sheets, internal memos, strategy documents, and anything that would be embarrassing rather than damaging if it leaked.

COPY. When you distribute copies of an original document, stamping them COPY prevents any single copy from being presented as the original. This is more relevant than it sounds — in legal and financial contexts, the distinction between an original and a copy can matter for enforceability.

ORIGINAL. The counterpart to COPY. Some organizations stamp originals to make the distinction explicit. This is common in notarial practice and in jurisdictions where original documents carry different legal weight than copies.

Workflow stamps

FOR REVIEW. Similar to DRAFT, but specifically flagging that the document is waiting for someone's attention. Useful in approval chains where a document might sit in a queue.

REVISED. Marks that this version incorporates changes from a previous review. Often paired with a date or version number. This is especially helpful when multiple rounds of revision happen and you need to know which version you are holding.

CANCELLED. For contracts, orders, or agreements that were valid but have been terminated. Different from VOID — a voided document was never valid; a cancelled document was valid and has been stopped.

Designing a status stamp that works

Status stamps have different design priorities than company seals. A company seal needs to look official and carry identity information. A status stamp needs to be instantly readable — often at small sizes, at odd angles, partially overlapping text, or in a low-quality scan.

Shape: rectangle, not circle. Most status stamps are rectangular because text reads more naturally in a horizontal line. Round seals work well for names and company identities, but "APPROVED" in a circle wastes space and is harder to read. The seal shapes guide covers when each shape makes sense — for status stamps, the answer is almost always a rectangle with slightly rounded corners.

Font: bold, simple, large. Use a heavy sans-serif typeface. The word needs to be legible at thumbnail size and after a bad photocopy. Avoid decorative fonts, thin strokes, or condensed faces. If your stamp includes a date line, that can be in a lighter weight, but the status word itself should be bold enough to read from across a desk.

Color: not black. The whole point of a status stamp is to stand out from the document text, which is almost always black. Red is the classic choice — it is visually distinct and carries cultural associations with urgency and authority. Blue works too, especially in Western contexts where blue reads as "official." Green is sometimes used for APPROVED stamps specifically, borrowing the traffic-light metaphor. Pick one color and stick with it; your stamps do not need to be a rainbow.

For more on choosing colors that stay readable on screen, in print, and in scans, see the seal color and contrast guide.

Size: big enough to see, small enough to not cover content. A status stamp is typically smaller than a company seal — roughly 40–60mm wide by 15–25mm tall for a rectangular stamp. It needs to be large enough that the word is immediately readable, but not so large that it obscures the text underneath. If you are placing it on a PDF digitally, use a semi-transparent version so underlying text remains legible.

The size and resolution guide covers the technical details of pixels and DPI. For status stamps specifically, export at least 600 pixels wide so the text stays sharp when the document is printed or zoomed.

Include a date field. A stamp that says APPROVED is useful. A stamp that says APPROVED with today's date is much more useful. If you are creating a digital stamp, consider adding a thin line or box below the status word where the date can be typed or handwritten. For fully digital workflows, you can generate a new stamp image with the date baked in each time.

Placing status stamps on documents

Where you put a status stamp is almost as important as the stamp itself. The rules are different from company seal placement because the purpose is different — you are not authenticating identity, you are communicating status.

First page, upper right corner. This is the most common placement for stamps like DRAFT, CONFIDENTIAL, and FOR REVIEW. The upper right corner is where the eye naturally goes after reading the title, and it does not compete with letterheads or logos in the upper left. A stamp here is visible even in a document thumbnail.

Diagonal across the page. For DRAFT and VOID stamps specifically, a large diagonal placement — light gray or faded red text running from lower-left to upper-right — works like a watermark. It is impossible to miss and does not obscure the content if you use a low opacity. This is the nuclear option: use it when you really, truly need to make sure nobody treats this as a final document.

Near the relevant field. PAID stamps go near the total amount. RECEIVED stamps go near the date or the sender information. APPROVED stamps go near the signature block. Placing the stamp close to the information it modifies makes the relationship clear.

On every page or just page one? For classification stamps (CONFIDENTIAL, INTERNAL USE ONLY), stamping every page is best practice — any single page might be separated from the rest. For status stamps (APPROVED, DRAFT), the first page is usually sufficient unless the document is a multi-page contract where individual pages might be referenced independently.

Building your stamps

You can create document control stamps in the seal generator — switch to a rectangular layout, type your status word, choose a bold font and your preferred color, and export as a transparent PNG. The transparent PNG guide walks through making sure the background is truly transparent so the stamp overlays cleanly on any document.

For placing the stamp on existing PDFs without Acrobat, the PDF stamping tool lets you position an image directly. If you work primarily in Word, the guide to adding seals to documents covers inserting transparent images with text wrapping set to "In front of text" so the stamp floats over your content.

A few practical tips for maintaining your stamp library:

Keep a folder of ready-to-use stamps. Export each stamp as a transparent PNG at a consistent size. Name them descriptively: stamp-approved-red-600px.png, stamp-draft-gray-600px.png. The file management guide has a naming system that works well for this.

Create date-stamped versions when you need them. For PAID and RECEIVED stamps, generate a new version with the date embedded whenever you use it. This takes thirty seconds and produces a more professional result than handwriting the date on a digital stamp.

Match your company seal's visual language. If your company seal uses a particular red, use the same red for your status stamps. If it uses a specific border style, echo that style in your stamp borders. Visual consistency signals that these marks come from the same organization. You do not need to overthink this — just enough similarity that they look like they belong together.

When a stamp is not enough

Status stamps are visual markers. They are not access controls, they are not audit trails, and they are not legal instruments. A CONFIDENTIAL stamp does not encrypt the document. An APPROVED stamp does not prove who approved it or when, unless you add a signature and date alongside it.

For documents where you need a verifiable chain of approval — regulated industries, legal filings, financial audits — a stamp image is a complement to your approval system, not a substitute for it. The distinction between a visual mark and a legally binding electronic signature is covered in electronic seal vs. electronic signature.

But for everyday office work — invoices that need to be marked paid, drafts that must not be mistaken for finals, copies that should not be confused with originals — a well-designed status stamp does its job quietly and cheaply. It asks nothing of the recipient except a glance. And in a world where documents travel through email chains, shared drives, and chat apps — losing their metadata, their context, and their audit trail along the way — a stamp that travels with the document is worth more than a status field that stayed behind in the system where the document was born.