Delegated design submittals: whose work product is it?

Whose work product is a delegated design submittal?#

A delegated design submittal is the specialty engineer's work product. When a contract delegates the design of a component, such as precast connections or a curtain wall anchorage system, the contractor's specialty engineer prepares and seals the calculations and drawings, and that engineer is their author.

The engineer of record reviews the submittal for conformance with the performance criteria and design intent. The EOR's review stamp, comments and correspondence are the EOR firm's own records, created in its role on the project. That split is the starting point for every ownership and licensing question that follows.

Which items are commonly delegated?#

Commonly delegated items are components whose design depends on a particular manufacturer's or fabricator's system. The specification sets performance criteria, loads and constraints, and the specialty engineer designs within them, often with the fabricator's detailers producing the shop drawings.

Deferred submittals are the permitting counterpart. Building departments may let certain delegated items be submitted for approval after the main permit is issued, which adds a building official's review, and its correspondence, to the record trail. Track those approvals in the same log as the EOR review so the sequence stays complete.

The specification language that sets up delegation is itself a strong EOR record. Well-written delegated design sections state design criteria, loads, serviceability limits, submittal content and the specialty engineer's qualifications, and firms refine that language project after project as problems surface in review.

• 1Steel connections designed by the fabricator's engineer.
• 2Precast and post-tensioned concrete elements.
• 3Cold-formed steel framing systems.
• 4Wood and metal plate-connected trusses.
• 5Curtain wall, storefront and cladding attachment systems.
• 6Metal stairs, railings and canopies.
• 7Seismic bracing and anchorage for MEP equipment.

How the ownership splits, record by record#

Ownership splits record by record, and the table shows the usual position for a structural EOR firm. Contracts and project requirements can change any row, so treat it as a sorting guide for a rights review rather than a conclusion.

What do the contract forms say?#

The AIA general conditions protect the design team's documents from contractor ownership claims. AIA A201-2017 Section 1.5.1 states that the architect and its consultants are the authors and owners of their instruments of service, and that the contractor, subcontractors, sub-subcontractors and suppliers shall not own or claim a copyright in them. Section 1.5.2 lets them use and reproduce the instruments only for performing the work.

The specialty engineer's own design is a different matter. It is usually commissioned by a subcontractor or fabricator, not prepared by the EOR's employees, so it is not the EOR's work. Under US copyright law, a commissioned work is a work made for hire only within listed statutory categories and with a signed written agreement, so absent an assignment the specialty engineer generally keeps authorship.

Under the common AIA general conditions, shop drawings and similar submittals are not contract documents. They show how the contractor proposes to meet the design, which reinforces that the EOR's role in delegated design is review, not authorship.

Why EOR review records are worth separating#

EOR review records are worth separating because they capture expert judgment in a clean sequence: a submittal arrives, the engineer compares it with the criteria, returns comments, and a revised submittal closes the loop. That chain is human-generated, specific to structural practice and hard to reproduce, which are value drivers in the SourceX Enterprise Data Value Framework.

The difficulty is that review comments quote the specialty engineer's numbers, sketches and assumptions. A comment asking for a revised weld or a different anchor embedment refers directly to someone else's design. Preparation should keep the EOR's reasoning and disposition while removing copied calculations, markups drawn on the specialty engineer's sheets, seals and the fabricator's identity.

Submittal metadata can carry value on its own. The number of review cycles per delegated item, the time between submission and approval, and the recurring reasons for rejection describe how delegation works in practice, and they can be shared without quoting anyone's design.

Illustrative: a structural firm licenses its review history, not the shop drawings#

Illustrative: a fictional structural engineering firm keeps many years of submittal reviews in Bluebeam sessions, in Procore submittal logs on contractor-hosted projects and in its own project folders. Its CEO asks whether the review history can be licensed.

Counsel concludes that the specialty engineers' calculations and shop drawings are out, as are submittal logs on contractor-owned Procore projects, apart from the firm's own exported comments. The candidate package contains the firm's review comments and dispositions, its performance criteria language and its RFI responses on delegated items, with project names, fabricators, seals and quoted calculations removed. The firm approves the package scope before anything moves.

How SourceX handles delegated design records#

SourceX handles delegated design records by tracing authorship first. In the SourceX five-step transaction, the Rights step separates EOR-authored records from specialty engineer and contractor material, and the Preparation step removes quoted design content, seals and identifiers.

Every approved package carries a SourceX Evidence Packet documenting provenance, licensing rights, permitted use, the privacy record and release authorization. The EOR firm decides what is included, and nothing is shared during the initial fit check.