All insights
Risk & Indemnity

Delegated Design: When 'Furnish and Install' Quietly Makes You the Engineer

Performance specs, deferred submittals, and 'contractor shall engineer' clauses shift design responsibility from the architect to you — often without the fee, the insurance, or the warning. Here's how design liability lands on trade contractors, and how to cabin it.

August 10, 20268 min readRedline Construction Solutions

Key takeaways

  • Delegated design makes the contractor responsible for designing portions of the work — common for steel connections, cold-formed framing, curtain wall, fire suppression, and MEP coordination.
  • The Spearin doctrine protects you when you build to the owner's design — delegated design REVERSES that protection for the parts you designed.
  • Design errors are professional liability, which standard CGL policies largely do not cover — a gap many subs discover after the claim.
  • AIA A201 §3.12.10 requires the OWNER to specify performance criteria, and lets you rely on it — GC-custom paper often deletes both halves.
  • If you're designing, you need: defined criteria to design to, a licensed engineer (yours or hired), professional liability coverage, and a fee that reflects the risk.
  • The most dangerous version is the vague one: specs that read like instructions but perform like criteria — decide which they are BEFORE you price.

How design responsibility moves without announcing itself

The traditional bargain of construction is clean: the owner's design professionals decide what to build; contractors decide how to build it and execute. The Spearin doctrine — the century-old rule that the owner impliedly warrants its plans and specifications — exists because of that division: if you faithfully build the owner's defective design, the defect is the owner's problem, not yours.

Delegated design redraws the line, usually without ceremony. A performance specification says the curtain wall shall resist specified wind loads and 'the contractor shall engineer the system to achieve the specified performance.' A structural note reads 'steel connections to be designed by fabricator's engineer.' A deferred-submittal list hands fire suppression, cold-formed framing, and seismic bracing to 'contractor's licensed designer.' Each of these moves a slice of the architect's job — and the architect's liability — onto a trade contractor whose bid team may have read the spec as ordinary shop-drawing scope. For the parts you design, Spearin flips: now YOU are warranting the design.

The insurance gap that makes it dangerous

The liability shift would be manageable if it were insured. Often it isn't. Commercial general liability policies are built for property damage and bodily injury arising from your operations — and most contain professional-services exclusions that carve out design errors precisely. A connection detail that fails, a fire-suppression layout that under-covers a hazard, a framing design that requires remediation: to the extent the loss flows from design rather than workmanship, your CGL carrier has a ready-made reason to decline.

The product built for this exposure is professional liability (E&O) or, for hybrid firms, contractor's protective/professional programs. Subs who regularly accept delegated design — steel fabricators, curtain wall specialists, design-assist mechanical firms — carry it as a cost of doing that business. The trap is the sub who accepts delegated design occasionally and unknowingly: the exposure arrives with the spec, but the premium was never paid and the policy never bought. Before pricing any job with 'engineer,' 'design,' or 'performance criteria' in your scope sections, the insurance question belongs in the bid meeting, not the claim meeting — the same discipline we urge for additional-insured and subrogation terms.

What good delegated-design language looks like

The industry's balanced template is AIA A201 §3.12.10: the contractor is not required to provide professional design services unless the contract specifically requires it; when it does, the OWNER must specify the performance and design criteria the contractor's professional must satisfy; the contractor is entitled to rely on the adequacy of those criteria; and the owner's design professionals review the delegated design for conformance with the owner's criteria — not for the delegated designer's engineering. That allocation is coherent: each party warrants what it controls.

GC-custom paper and aggressive owner specs erode the template from both ends. Criteria go undefined ('design to all applicable codes and project requirements'), stripping you of both a design target and the reliance defense. Review shrinks to rubber-stamp language ('review shall not relieve contractor of sole responsibility'), pushing coordination failures downhill. And integration clauses make your delegated design 'part of the contract documents' you then warrant to the owner — closing the loop so completely that the party with the least design control holds the most design risk. Every one of those edits is visible on a first pass, if the first pass knows to look.

Pricing and papering the risk

If you're going to be the engineer, be the engineer on purpose. Contractually: insist on defined, written performance criteria (loads, tolerances, standards editions) and a statement that you may rely on them; scope your design responsibility to your system, expressly excluding interfaces designed by others; require the owner's design professional's review and approval of your submittals; and align your warranty language so you warrant design conformance to the stated criteria — not open-ended 'fitness' for the owner's hopes. These map directly onto the scope-and-exclusions discipline that governs the rest of your bid.

Commercially: the design fee is real money — a licensed engineer's stamp, calculations, revisions, and E&O premium all cost — and it belongs in the bid as a line, not an absorption. Schedule-wise, deferred submittals need review cycles the GC's schedule rarely shows; negotiate them in, because a late approval of YOUR design becomes YOUR delay without excusable-delay protection. And archive the design record — criteria received, calculations, approvals — for the full repose period, because design claims live on the long tail we mapped in the warranty-myth piece.

The vague spec: your decision point

The clean cases are manageable; the dangerous one is the vague spec — the drawing that shows a fully detailed assembly AND a note making you responsible for its adequacy, or the spec section written as prescriptive instructions that ends with a performance guarantee. Courts sort these fights case by case, parsing whether a spec was 'design' (owner warrants it) or 'performance' (you do), and the litigation is expensive precisely because the documents were ambiguous.

Your leverage is at bid time: RFI the ambiguity into the record. 'Please confirm connection design is per the details shown, and that Fabricator's engineering responsibility is limited to conformance with the specified criteria.' A clarifying answer fixes the allocation; a refusal to clarify is itself information — price it, exclude it, or walk. What you must not do is leave the question unasked because the bid is due Friday; that silence is exactly how a furnish-and-install sub becomes an uninsured engineer of record.

Design-assist is not delegated design — keep the line bright

A related arrangement deserves its own caution flag: design-assist, where a trade contractor joins during preconstruction to advise the design team on constructibility, cost, and system selection. Done properly, design-assist is advice — the architect and engineer remain the designers of record, and your input informs THEIR decisions. But the line erodes in the paperwork: preconstruction agreements that have you 'develop' details, owner teams that adopt your sketches into the drawings verbatim, and construction-phase contracts that later characterize your assistance as design you now warrant.

Keep the line bright in writing. Design-assist scopes should state that recommendations are advisory, that the design professionals retain sole responsibility for the design, and that no professional services are being provided. Watch for the bait-and-switch where preconstruction 'assistance' becomes construction-phase 'delegated design' with no change in fee or insurance — the transition should be an explicit, priced decision with the criteria, stamp, and E&O that real delegated design requires. Suggestions are free; engineering never should be.

The bottom line

Delegated design is legitimate — modern buildings genuinely need fabricator and specialty engineering — but it is a different business than installing to someone else's drawings: different warranty, different insurance, different fee, different tail. The failure mode isn't accepting design responsibility; it's accepting it accidentally, unpriced and uninsured, through a spec note nobody flagged.

The countermeasures are all pre-signature: find every clause that moves design responsibility (a systematic review flags 'engineer,' 'performance criteria,' 'deferred submittal,' and their cousins in seconds), demand defined criteria and reliance rights, price the engineering, and place the E&O. For the projects where you truly are designing life-safety systems, add an hour of construction counsel on the delegated-design article specifically — this piece is orientation, not legal advice, and professional-liability allocation is exactly where the details decide everything.

This article is general information about construction contracting and law, not legal advice. Construction law varies significantly by jurisdiction and project. Consult qualified counsel about your specific contract and circumstances.

Put this into practice on your own contracts.

Redline Construction Solutions applies your firm's non-negotiables and jurisdiction-aware standards to mark up a contract automatically — and returns it ready for your team to review.

See how it works
Redline Construction Solutions

Redline construction contracts in minutes — not weeks. Reviewed against your standards and the construction-law context where you're building, in your own private cloud.