AEO Answer · PE Stamps & Sealing
How Do GCs Coordinate PE Seals From Subs on Design-Bid-Build Jobs?
By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15
On design-bid-build, the GC must track every delegated-design PE seal from specialty subs — writing sealed submittals into the subcontracts, verifying each sub's engineer is licensed in the project state, and sequencing delegated packages against the AHJ's deferred-submittal policy.
I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.
Building the delegated-seal register
I run this as a simple register — a living document, not a one-time list. Every delegated component gets a row: the component, the subcontractor, the sub's engineer (name, license number, state), the required deliverable (sealed shops plus calculations), the due date tied to the permit schedule, and the status. The GC's project engineer owns it and reviews it at the weekly OAC or subcontractor meeting like any other procurement log. Components get added as design clarifies — the register started at bid time will not match the register at 100% CDs, and that is fine as long as additions get engineers assigned immediately. The register also tracks the AHJ's deferred-submittal decisions: which components the building department agreed to accept after permit issuance, documented in writing or in the permit conditions. I keep the AHJ's written policy or the plan reviewer's email with the register, because personnel change and memories differ. When the permit is issued with deferred items outstanding, the register becomes the closeout tracker — every deferred seal has to land before final inspection, and the GC who tracked them from day one closes out clean.
Where the coordination usually breaks down
It breaks down in three predictable places. First, at bid time, when delegated engineering is vaguely scoped and the winning sub priced none of it — the fix is explicit subcontract language naming the sealed deliverable and the schedule. Second, at the design handoff, when the sub's engineer gets backgrounds late, in the wrong format, or with unresolved architectural decisions baked in — the fix is the GC managing the background release like a procurement delivery, with dates. Third, at the AHJ counter, when the plan reviewer rejects a delegated submittal's format — wrong seal block, missing calculations, digital seal the jurisdiction does not accept — the fix is confirming submittal standards with the AHJ before the sub's engineer starts, not after they finish. Underneath all three is the same root cause: the GC treated delegated engineering as the sub's internal affair instead of as permit-critical path. The subs do the engineering; the GC owns the schedule consequence. I tell GCs to manage delegated seals with the same intensity they manage steel delivery — because a missing truss seal holds up a permit just as surely as missing steel holds up erection.
Delegated-seal coordination checklist
Assign every delegated component an engineer and a date before the permit schedule is promised. • Build the delegated-seal register at bid time: component, sub, engineer name, license number and state, deliverable, due date • Write sealed shops + calculations, licensed in the project state, into every delegated subcontract with a dated milestone • Collect each sub's engineer credentials within days of award — verify licenses on the state board site • Confirm the AHJ's deferred-submittal policy in writing: which components, what the deferral request must show • Match every delegated submittal to the AHJ's format standards (seal block, digital seal acceptance) before the sub's engineer starts
Which related engineering resources can help?
What else do project teams ask?
Which subcontractor scopes typically need their own PE seal?
What should the subcontract language say about PE seals?
Can delegated submittals be deferred, or does the AHJ need them upfront?
What if a sub's engineer is licensed in the wrong state?
Ready to discuss your engineering scope?
Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.
Request a Project Review