Design-build: who owns the design when the A/E works for the builder?

Who owns the design in a design-build project?#

Ownership of the design in a design-build project usually depends on two contracts read together. The owner's agreement with the design-builder decides what the owner gets, whether ownership of the design documents or a license to use them. The design-builder's agreement with the architect or engineer then has to deliver those rights, often by passing the owner's terms down.

That is why the A/E's own subcontract rarely answers the question alone. An A/E can sign a subcontract that says it keeps its instruments of service, while a flow-down clause binds it to a prime contract that promised the owner ownership on payment. Which term controls depends on the drafting and, in a dispute, on how a court reads the documents together.

For a general counsel or risk manager at an A/E firm, the practical result is simple: no design-build project can be cleared for reuse or licensing from the subcontract file alone.

How rights move through the contract chain#

Rights in design documents move through the design-build chain in a predictable shape. Picture three tiers: the owner at the top, the design-builder in the middle, and the A/E with its sub-consultants at the bottom. Obligations flow down; rights in the design flow up.

If the owner is to own the design on payment, the design-builder needs the A/E to assign or license enough rights for that to happen. If the owner instead takes a license, the A/E may keep copyright and license upward. The answer for any project sits in the actual wording at each link.

AIA, ConsensusDocs and DBIA design-build forms#

Standard design-build forms come in families from three main publishers. The AIA design-build family includes B143, written for the agreement between a design-builder and its architect. ConsensusDocs publishes a design-build family that includes its 410 agreement between owner and design-builder and a separate agreement between the design-builder and its design professional. The Design-Build Institute of America publishes its own forms as well.

Each family addresses ownership and use of design documents, but the allocation differs between publishers and has changed between editions. Projects also modify standard forms heavily through riders and owner exhibits. Treat the form name as a starting point for review, not as an answer, and read the version and amendments actually signed.

Checklist for reading pass-through and ownership clauses#

A checklist keeps the review of design-build subcontracts consistent from one project to the next. Work through each point for every project before any reuse or licensing decision, and record the answer next to the project number.

Missing prime contracts are common in older archives, because subcontracts often incorporated the prime by reference instead of attaching it. Request copies through the design-builder before treating those projects as anything other than restricted.

• 1Get both contracts: the A/E subcontract and the owner and design-builder agreement, with all amendments.
• 2Find the flow-down clause and note whether it incorporates the whole prime contract or only listed obligations.
• 3Confirm whether the A/E received the prime contract at signing; incorporation of an unseen document is a review flag.
• 4Read the prime contract ownership clause: ownership on payment, a license, or something else.
• 5Read the subcontract ownership clause and check whether it conflicts with the prime.
• 6Check payment conditions, including whether rights pass only once the A/E is paid.
• 7Check termination terms: who may use an incomplete design, and on what conditions.
• 8Look for retained rights covering standard details, pre-existing material, software and know-how.
• 9Note confidentiality terms at both levels and any clause on data, AI or publicity.
• 10Confirm that sub-consultant agreements pass through matching rights.

What the A/E usually keeps, and what usually goes#

What the A/E keeps after a design-build project depends on the clauses above, but some patterns recur often enough to guide a first pass through the archive.

Internal working records deserve particular attention. Even where the owner ends up owning the drawings, QA/QC comments, RFI responses and calculations created inside the A/E are often not listed as deliverables, which can leave them with the A/E, still subject to confidentiality terms flowing down from the prime.

Illustrative: an A/E sorts its design-build projects before a licensing review#

Illustrative: a fictional architecture and engineering firm has served as designer of record for several design-builders on schools, warehouses and municipal facilities. Its risk manager reviews these projects before the firm considers licensing internal QA/QC comments and RFI responses.

Some subcontracts incorporate prime agreements the firm never received, so those projects are marked unknown until the design-builders supply copies. Warehouse projects for a private developer used a prime contract that left copyright with the designers and gave the owner a license, and the subcontract matched, so they move forward. Municipal projects, where the prime gave the owner ownership and added public records terms, are excluded.

The firm also adds a retained rights clause and a short data use clause to its standard design-build subcontract markup for future pursuits.

How SourceX handles design-build projects in a rights review#

SourceX handles design-build projects in the Rights step of the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, by documenting both contract levels for each project proposed. Projects whose chain cannot be traced stay out of the package.

The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, including which contracts were reviewed for each project. Counsel for the A/E makes the legal calls; SourceX keeps the record consistent across projects.