Mythic Engineering

Delegated Design vs. Structural Engineer of Record (SEOR)

Engineering responsibilities on a project are often shared between multiple parties. This page explains the difference between Delegated Design and the Structural Engineer of Record (SEOR), and why some engineering services require separate contracts.

Understanding these roles helps avoid confusion during design, permitting, and construction.

What Is the Structural Engineer of Record (SEOR)?

The Structural Engineer of Record is the licensed professional engineer responsible for the overall design intent and code compliance of a specific engineering discipline for the project.

The SEOR typically:

Establishes the design criteria and load assumptions

Defines the overall structural or system approach

Coordinates with the architect and other design disciplines

Reviews delegated designs for general conformance to the design intent

The SEOR is not responsible for designing every component in detail, especially components that are commonly delegated to specialty engineers or manufacturers.

What Is Delegated Design?

Delegated design occurs when specific components or systems are engineered by a specialty engineer, manufacturer, or supplier rather than by the SEOR.

Common examples include:

Prefabricated structural systems

Specialty framing, trusses, or panelized systems

Connections or components requiring manufacturer-specific design

Systems governed by proprietary methods or installation requirements

In delegated design, the specialty engineer is responsible for:

Designing their assigned component

Providing calculations and details for that component

Sealing documents within their defined scope

How Delegated Design and SEOR Work Together

In a typical project:

The SEOR defines what is required

The delegated engineer designs how their specific system meets those requirements

The SEOR may review delegated designs for coordination and compatibility, but does not assume responsibility for the detailed design of delegated components unless explicitly contracted to do so.

Why Some Items Require Separate Contracts

Delegated engineering often requires:

Specialized analysis

Manufacturer-specific knowledge

Separate professional liability

Additional coordination beyond the base engineering scope

For this reason, delegated engineering services are frequently provided under separate agreements, either directly with the specialty engineer or as an additional service.

This ensures that:

Responsibility is clearly assigned

Liability is properly managed

Engineering effort is matched to project needs

Common Questions

"Aren't you responsible for all of it?"

No. Engineering responsibility is divided by scope. The SEOR is responsible for the overall design intent, while delegated engineers are responsible for the detailed design of their assigned systems.

"Can the SEOR just stamp the delegated design?"

No. An engineer can only seal work they are directly responsible for and have prepared or thoroughly controlled.

"Why does the manufacturer need their own engineer?"

Manufacturers often design proprietary systems that require specialized analysis and engineering beyond the SEOR's scope.

"The building department asked for this—who does it?"

AHJ requests are addressed by the engineer responsible for that portion of the design. Delegated items are handled by the delegated engineer; overall coordination remains with the SEOR.

Why This Structure Exists

Separating SEOR and delegated design:

Improves technical accuracy

Clarifies responsibility

Reduces delays during review

Aligns engineering effort with expertise

It also helps projects move through permitting and construction with fewer misunderstandings.

Final Note

If you're unsure whether a system is part of the SEOR scope or requires delegated engineering, it's best to clarify early. Clear roles upfront lead to faster reviews, smoother permitting, and fewer surprises later.