EngineeringID Staff
Who Actually Presses Your Stamp?
In a lot of firms, the person applying the seal is not the person whose name is on it. Every board treats sealing as a personal act. Any process where your credential can be used without you is broken by design.
Ask a mid-sized design firm on a deadline day who applied the seal to the drawings that went out this morning. The honest answer, more often than anyone wants to admit, is not the person whose name is inside the circle.
The stamp file lives on a shared drive, in a folder called seals, or stamps, or somebody's initials. A project manager pulls the PNG into the title block. An admin who has done this a thousand times places it, sizes it, and sends the set out. The licensee sees it later, maybe, when the plans come back marked up. Sometimes the licensee asked for exactly that. Sometimes nobody asked at all.
Boards — the 69 member licensing boards NCEES represents across the 50 states and the US territories — treat sealing as a personal act by a specific human being. Not a firm act, not a delegable clerical step. The seal is the licensee saying, in their own name, that they prepared this work or directly supervised its preparation and that they take responsibility for it. There is no version of that statement a coworker can make on someone else's behalf.
Why it happens
This is not a story about bad people. The practice is common because the mechanics of a stamp file make it feel administrative.
Start with the artifact. For most firms the seal is a raster image or a vector file — a circle with a name, a number, and a state. It sits next to the logo and the CAD title block template. Files in that folder get used by whoever needs them. Nothing about a PNG communicates "legal instrument." It looks like a graphic because it is a graphic. Separating the image from the act is most of the distance between a broken process and a sound one, which is why the distinction between a seal and a stamp as terms of art keeps mattering long after people assume it is settled.
Then the calendar. A bid closes at two. The engineer of record is in a truck between site visits, or on a plane, or in a plan review across town. The set is done. The only thing between finished work and a missed deadline is a two-inch circle, and someone in the office knows where the file is. The math, in the moment, is not close.
And habit. The wet-stamp era had its own version of this — a rubber stamp in a desk drawer a junior staffer could reach. The drawer was at least in the office, which imposed a kind of accidental proximity control. A network share has no drawer. It replicates. It syncs to laptops. It gets emailed to a sub. The shift from wet stamps to electronic ones removed friction that was doing quiet security work nobody had budgeted for.
What boards actually regulate
Read enough board rules and a pattern emerges. They regulate two different things, and firms conflate them.
The first is the appearance of the seal: shape, size, required text. This gets attention because it is checkable. Colorado requires a circular seal between 1.5 and 2 inches under Colo. Rev. Stat. § 12-25-217. California specifies 1.5 inches under Cal. Code Regs. tit. 16, § 411. New York calls for 1.75 inches under 8 NYCRR § 68.13. Texas lands at 1.5 to 2 inches under 22 TAC § 137.31. Across the 51 US jurisdictions there are ten distinct diameter specifications, which is why a firm working in five states cannot use one image everywhere, and why the dimension requirements by jurisdiction and the no-signup stamp preview tool exist at all.
The second is control — who may apply the seal, and under what circumstances. This gets ignored, because it is not checkable by looking at the drawing. A perfectly compliant 1.5-inch circle applied by the wrong person is still a violation. The plan set does not carry a watermark saying who moved the mouse.
That asymmetry is the whole problem. Firms optimize hard for the visible requirement and run essentially no process on the invisible one. To see how uneven the rules get once you leave appearance behind and start reading responsibility language, the state-by-state requirements comparison is a useful tour, as is the general stamp requirements guide.
The exposure lands on one person
When a sealed document becomes a problem — a failure, a claim, a complaint to the board, a discovery request — the board's counterparty is the licensee. Not the PM. Not the admin. Not the firm's principal, unless the principal is also the one who sealed.
The person who clicked has no standing in that conversation. And "I did not apply that" is not a defense. It converts the story from "I made an engineering judgment you disagree with" into "my credential was in use without me," which is a worse story and a separate exposure stacked on the original one.
So the delegation is not shared risk. It is a full transfer of convenience to the office and a full retention of consequence by one individual. Anyone who has thought about how professional seals get misused on documents recognizes the shape: the mechanism that makes casual delegation easy makes deliberate forgery easy, and from the outside the two produce identical artifacts.
There is a related trap. Many clients, and some jurisdictions, expect both a seal and a signature — the Washington board's stamp and seal requirements direct the licensee to sign in permanent ink across the face of the seal — and a stamp image with a signature baked into it is a signature the licensee did not make on that document. If your seal graphic contains a reproduced signature, every use of it is an assertion. Settle whether you need a stamp, a signature, or both before deciding what belongs inside the circle.
The strongest objection
The best counter-argument: you are confusing the ministerial act with the professional one. The professional act is the engineering — the analysis, the judgment, the review of the set. The licensee did all of that. Placing an image in a title block is typing. We do not demand engineers do their own plotting or their own file naming. If the licensee reviewed the set and said "issue it," insisting they personally drag the graphic is fetishism about a mouse click.
That argument is not stupid. It is the correct way to think about most of the production chain. If sealing worked the way signing a paper document works — where the physical act and the authorization are the same event, unavoidably — the objection would be decisive.
It fails on one point. The delegation is not per-document. Handing someone your stamp file does not authorize one drawing set. It authorizes every use of that file, forever, by everyone who can reach it, including uses you will never see. You cannot delegate the ministerial act without also delegating unbounded future capability, because the file does not know which document it was borrowed for.
Compare a signature. When you sign a page, your hand is present for that page and no other. Your capacity to sign does not detach and stay on the table. A stamp file detaches by default. The objection is right that the click is trivial. It is wrong about what you are giving away.
Which is why the meaningful line is not electronic versus paper but bound versus unbound. A seal cryptographically bound to a specific document by a specific person at a specific moment is closer to a wet signature than a PNG ever was. That is the substance behind the difference between electronic and digital signatures, and the mechanics of how digital signatures work are worth an hour of any licensee's time, because this vocabulary is used loosely by vendors and precisely by boards.
What a sound process looks like
Three properties. Lacking any one of them, the process is broken by design, whether or not it has yet produced a bad outcome.
Sole control
The credential must be usable only by the licensee. Not "usable by the licensee and the two people who know where the folder is." Sole control means that if the licensee is unreachable, the seal cannot be applied. That will be inconvenient a handful of times a year, and those are precisely the moments the control exists for.
Practically: sealing capability is tied to an authenticated identity, not to possession of a file. Anyone who can copy the artifact can use the credential, so the artifact cannot be the credential.
Per-document authorization
Each sealing event is its own decision. Not a standing grant, not a folder permission — an act the licensee performs against one identified document. This is what answers the ministerial-act objection. Once authorization is scoped to a document, whether the licensee personally positioned the graphic stops mattering, because the authorization did not leak past the thing being authorized.
An audit trail
A record of what was sealed, by whom, and when — one the firm did not author and cannot quietly revise. The value runs both directions. It protects the licensee who did everything right and needs to demonstrate it years later, and it deters the shortcut, because the shortcut stops being invisible.
This is where independent verification earns its keep: a sealed document anyone can check against the underlying license record is a much harder thing to fake than an image cropped out of a PDF. The state-by-state license lookup guide covers where to verify, and jurisdiction pages handle the common ones directly — Ohio PE license lookup, Texas PE license lookup.
Multi-state practice makes it worse
A licensee registered in six states has six seals, six sets of appearance rules, and six boards with independent authority to act — NCEES's Records program can expedite the comity applications that got them there, but it does nothing about the six seals afterward. Ohio wants a circular seal of 1.5 to 2 inches under Ohio Rev. Code § 4733.14 and 30 PDH every two years. Texas wants 15 PDH annually. New York wants 36 PDH per three years. Colorado imposes no continuing-education requirement on engineers at all. Different obligations, different renewal clocks, different failure modes.
Six files in a folder is not six times the risk. It is six times the surface area, multiplied by the odds that whoever grabs one grabs the wrong one — and a seal applied under the wrong state's credential is a control failure and a jurisdictional one at once. State-specific tooling helps: a Texas stamp builder, an Ohio stamp builder, or a California stamp builder renders to that jurisdiction's spec instead of leaving you to remember which folder holds which diameter. The California engineer stamp requirements and Colorado engineer stamp requirements pages cover the rules behind the file.
None of this is engineer-specific. The same control logic governs an architect's seal, a land surveyor's seal, and a landscape architect's seal — and the differences between architect and engineer stamps are mostly about scope of practice, not about who is permitted to press them. All 51 US jurisdictions permit digital or electronic seals in some form, so nobody is defending a paper-only workflow on legal grounds.
What to do this week
Four moves, in order of how quickly they pay.
Search your file server for your own name. Not the seals folder — everywhere. Project directories, old CAD templates, email attachments, whatever your firm uses for file transfer. You are looking for copies you did not know existed, in places you never authorized, sometimes on projects you left years ago. You cannot reason about your exposure until you know the count.
Ask, directly, who has applied your seal in the last year. Ask the PM. Ask the CAD lead. Ask the admin. Not as an accusation — as an inventory. The answer is information you are entitled to and probably do not have.
Pick one project and seal it yourself, end to end. Take the finished set through applying a stamp to PDF drawings personally, and time it. You will find out how much of the friction is real and how much is folklore. Discovering it takes a couple of minutes kills the delegation habit faster than any policy memo.
Write down what happens when you are unreachable. One paragraph. If the honest answer is "someone uses my file," you have found the thing to fix — and the fix is a process where the credential cannot be exercised without you, which also means having a real answer for the bid closing while you are on a plane. That answer is usually "it goes out unsealed and gets sealed on landing." That is a fine answer. It is a much better one than what you are running now.
Your license took years. The seal is the only part of it anyone outside the profession ever sees, and in a lot of offices it is a file anyone can copy. Treat it like the credential it is, not the graphic it resembles.