How Do Architects Engage an Engineer of Record for Review-and-Seal?

The first model is the EOR as design partner: the architect engages the structural or MEP engineer at project inception, the engineer designs the systems through the phases, and the seal at permit time covers work the PE authored. This is the smoothest path — responsible charge is natural because the PE did the work, coordination is continuous, and there are no surprises at the end. Most established architect-engineer teams work this way, and the fees reflect a full design scope. The second model is the EOR as reviewing engineer: the design exists — produced by the architect's staff, a design-build entity, or a previous engineer — and the PE is engaged to review it, verify the calculations, require revisions, and seal. This is the true review-and-seal engagement, and it is where the discipline matters most: the PE must actually review, not just read. I take these engagements seriously and price them for the review effort they require, because a reviewing EOR who finds real problems is doing exactly what the owner paid for. Architects should expect the review to produce revision comments — a review that finds nothing on a complex set was not a review.

The coordination rhythm I recommend: the EOR reviews the structural system selection and MEP concept at schematic design, when the architect is choosing between systems and the engineer's input actually changes the building. At design development, the EOR verifies preliminary sizing and the coordination assumptions — floor-to-floor heights against duct depths, structural bays against the program grid — because DD is where coordination failures get cast in concrete. At construction documents, the EOR performs the full review-and-seal: detailed code compliance check, verified calculations, marked revisions, re-review of corrections, then the seal. The architect's role in this rhythm is to feed the EOR reviewable packages at each milestone — not a Friday-afternoon PDF dump, but backgrounds, narratives, and decisions in a form the engineer can actually review. I also ask architects to include the EOR in the AHJ pre-submittal meeting or at least share the notes; the EOR who hears the reviewer's concerns firsthand seals a set that anticipates them. Coordination is not overhead — it is the mechanism by which the review stays ahead of the drawing set instead of chasing it.

Put these in place at contracting and the engineering scope stays clean through permit. • Written scope: phases, disciplines, deliverables, revision protocol, correction rounds included • Name the individual PE in responsible charge and verify the license (and Texas F-number) in the project state • Engage at schematic design — the EOR's early input on system selection is the highest-value engineering on the project • Deliver reviewable packages at each milestone: backgrounds, narratives, geotechnical report, AHJ checklist • Define who revises and who re-reviews, so plan-check corrections do not trigger a scope argument mid-permit