Why One Company Ends Up With Five Seals (And How to Design Them as a Set)

The first seal is easy. Somebody registers the company, orders or generates a round red seal with the full legal name around the ring, and that is the company's mark. Done.

Then the finance team asks for something to put on payment vouchers. Then a sales manager wants a seal for a stack of routine contracts, because carrying the main one around makes everybody nervous. Then someone in operations makes a rectangular "RECEIVED" stamp in a design tool over lunch. Eighteen months later there are five images in five folders, two of them look almost identical at thumbnail size, and nobody can say with confidence which one is supposed to go on a purchase order.

This is not a design failure. It is what happens when a single mark has to serve a growing number of unrelated jobs. The fix is to treat these seals as a set — designed together, distinguishable at a glance, and matched to a decision about who is allowed to use what. This guide covers how those sets usually break down, what actually drives the split, and how to make them look like family members rather than strangers.

Splitting a seal is a control decision, not an aesthetic one

Here is the part most design articles skip: the reason companies carry several seals has very little to do with graphics. It is about limiting blast radius.

A seal that can bind the company to anything is a dangerous thing to hand around. If the same mark approves a five-year lease, a bank instruction, and a courier receipt, then anyone who can reach it can do all three. Splitting the mark into purpose-specific seals means the person stamping delivery notes all day is not holding the thing that can sign a lease.

That is the logic behind almost every seal set you will encounter. In mainland Chinese practice, for instance, an organization commonly keeps a company seal alongside separate seals for contracts, finance, and invoices, each held by a different function. Japanese companies typically distinguish a registered seal from a bank seal and from the everyday square seal used on quotations and invoices. Korean practice separates the registered corporate seal from a "use seal" for routine paperwork. The vocabulary differs; the instinct is identical.

The practical takeaway: before you design anything, write down who will hold each seal and what they are allowed to stamp with it. If two seals would live in the same hands and cover the same documents, you do not need two seals. If one seal would be handled by six people with different authority, you probably need more than one.

For what is legally expected in a specific jurisdiction, read the country-specific pieces rather than trusting a generic rulebook — electronic seals in China, hanko and electronic seals in Japan, and dojang and electronic seals in Korea each cover a different set of expectations. Requirements change, and they change by entity type as much as by country.

The four roles most seal sets cover

Strip away regional naming and nearly every seal set fills some combination of four roles.

The identity seal. The company's primary mark, carrying the full registered name. Used sparingly, held tightly, usually reserved for anything consequential. This is the one to design first and design well, because everything else in the set will borrow its shape and typography. If you are starting from zero, how to design a company seal walks through the anatomy.

Transaction seals. Marks scoped to one category of paperwork — contracts, finance vouchers, invoices, bank instructions. They usually repeat the company name but add a purpose line, so a reader can tell in one second that the mark belongs on this kind of document and not another. The contract seal, finance seal, and invoice seal templates show how that purpose line typically sits inside the ring.

Personal or role seals. The mark of a named individual acting for the company — a legal representative, a director, a licensed professional. These are usually small, often square, and carry a person's name rather than an organization's.

Workflow stamps. APPROVED, PAID, RECEIVED, VOID, CONFIDENTIAL, a date stamp, a department stamp. These make no claim about identity at all. They record that a step happened. They are the most abused category, because they are easy to make and easy to mistake for something more official than they are.

Not every company needs all four. A three-person consultancy issuing ten invoices a month has one seal and no honest use for a second. Building a seal set for an organization that does not have separate functions yet just produces files nobody uses.

Make them siblings, not twins

Once you know what the set contains, the design problem is specific: each seal must be recognizable as belonging to the same organization, while being impossible to confuse with its siblings — including at thumbnail size, in grayscale, in a bad scan, and by someone who does not read the language on the ring.

The levers worth using:

• Shape. The strongest signal available. A round identity seal beside square or rectangular sub-seals separates at a glance without anyone reading a word. Round, oval, or square covers what each shape tends to imply.
• The purpose line. Text inside the ring or across the center, naming the seal's job. Keep it short and keep it in the same position on every seal in the set, so the eye learns where to look.
• Size. A consistent hierarchy — identity seal largest, transaction seals a step smaller, workflow stamps smaller still — is a quiet but effective cue. Keep sizes deliberate, not accidental; the seal size and resolution guide explains how to think in pixels and millimeters at the same time.
• Center element. A star, an emblem, a registration number, or nothing at all. Vary it between the identity seal and the rest, not between every seal.

And the levers to be careful with:

• Color alone. Coding sub-seals by color is tempting and fails often. Documents get printed in monochrome, scanned badly, faxed, or photocopied, and the difference vanishes. Use color as reinforcement, never as the only distinction. The seal color and contrast guide has more on how colors survive real document handling.
• Typography drift. Different fonts across the set is the fastest way to make a seal family look like a collection of unrelated files. Change the words, not the typeface.
• Near-identical text. Two seals whose ring text differs by one character are a filing error waiting to happen. If the purpose lines are that close, ask whether both seals need to exist.

A test I would apply before signing off on a set: shrink every seal to about the size it will occupy on a page, print the sheet in black and white, and hand it to a colleague who has never seen them. If they cannot sort them apart, neither will the counterparty's accounts payable clerk at 5pm on a Friday.

Keep workflow stamps visually distant

Of everything in a seal set, the workflow stamps deserve the most separation. An APPROVED stamp is an internal note. It says a step in a process happened. It does not identify the company, it does not indicate authorization to bind anyone, and it should not look like it does.

Give them a different shape from the identity seal, plain readable type instead of decorative seal script, and often a different color entirely. The approved stamp and other process-stamp templates lean deliberately plain for exactly this reason. When an internal routing stamp is designed to look like a corporate seal, it invites a reader outside the company to draw a conclusion that was never intended.

The set is only as good as the files behind it

Five well-designed seals stored as five ambiguously named PNGs in a shared drive will still get misused. Once the designs are settled, the discipline moves to file handling: one master per seal, exports named for their purpose, and a short note telling people which file goes where. That is a whole topic on its own — the seal file management guide covers naming, versioning, and who gets edit access versus download access.

Two habits pay off immediately. Name files by seal purpose and destination, not by date or by who made them. And when a seal is retired, archive it somewhere that is clearly not the active folder — old seals resurfacing on current documents is a common and avoidable mess.

It is also worth stating plainly, in that same usage note, what these images are and are not. A seal image makes a document look stamped; it does not verify identity, prevent tampering, or leave an audit trail. Are image seals legally valid? and electronic seal vs. electronic signature cover that distinction, and it is worth reading before you decide which workflows a set of image seals belongs in.

A short checklist before you build the set

• Each seal has a named holder and a written scope of use.
• No two seals cover the same documents in the same hands.
• The set shares one typeface and one visual language.
• Every seal is distinguishable in grayscale at real page size.
• Workflow stamps look clearly different from identity seals.
• Sizes follow a deliberate hierarchy.
• Files are named by purpose, with one master per seal.
• Retired seals are archived out of the active folder.

Start with the identity seal, get it right, and derive the rest from it — that is far easier than reconciling five seals designed by five people over two years. You can build the whole set in the online seal generator, or start from a purpose-specific layout in the template gallery and adjust the text to match your organization.