Who owns architectural drawings and engineering documents, and which ones a firm can license

Instruments of service: what AIA B101 says about ownership

“Instruments of service” is the contract term for what a design professional produces to deliver its services: drawings, specifications, models and the other documents behind a building. The term exists to separate two things a client might assume are the same, the building it paid for and the documents used to design it.

AIA Contract Documents' own summary of B101-2017 says the architect and its consultants are deemed the authors and owners of their instruments of service and retain “all common law and statutory rights, including copyright.” The owner receives a license to use the instruments of service “solely and exclusively” for the project, which continues after completion or termination unless the architect rightfully terminates for the owner's default. If the owner reuses the work without the architect, it must release and indemnify the architect (source: AIA Contract Documents, The Rights of an Architect's Instruments of Service).

The same article contrasts B105, the short-form residential agreement, where the architect grants the owner a more limited license (source: AIA Contract Documents, The Rights of an Architect's Instruments of Service). Either way, under an unmodified AIA form the copyright stays with the design firm, and that is the starting point for any license of the firm's drawings.

Who owns engineering drawings under EJCDC E-500

Engineers on public works and infrastructure often sign EJCDC E-500, the owner-engineer agreement published by the Engineers Joint Contract Documents Committee. Public copies of the 2014 form say at paragraph 6.03 that all documents are instruments of service and that the engineer keeps an ownership and property interest in them, including the copyright and the right of reuse, whether or not the project is completed (source: EJCDC E-500 (2014) public copy adapted by the City of Durham, NC).

Public owners often issue their own edited version of E-500; the City of Durham's working template cited here is one public example (source: EJCDC E-500 (2014) public copy adapted by the City of Durham, NC). An owner can rewrite the use-of-documents paragraph so it takes ownership of final documents, or so the engineer may not disclose project information. Those edits are why the signed agreement, not the standard form, decides whether an engineering project belongs in a license.

Calculations deserve their own note. They are often filed with the drawings, but they show the most reusable reasoning a firm has: loads, member checks, hydraulics, energy models. Treat them as instruments of service under the same agreement as the drawings they support.

Copyright of architectural drawings: what the statute says

Four provisions of the Copyright Act frame the question:

• Architectural works are protected. Section 102(a)(8) lists “architectural works” among the categories of protected works (source: 17 U.S.C. § 102, subject matter of copyright (Cornell LII)). Section 101 defines an architectural work as the design of a building as embodied in any tangible medium, including plans and drawings, and excludes individual standard features (source: 17 U.S.C. § 101, definitions (Cornell LII)).
• Technical drawings are protected too. Section 101 includes “technical drawings, including architectural plans” in pictorial, graphic and sculptural works (source: 17 U.S.C. § 101, definitions (Cornell LII)), which is how engineering drawings are usually protected.
• Ideas are not. Section 102(b) says copyright never extends to any idea, procedure, process, system or method of operation (source: 17 U.S.C. § 102, subject matter of copyright (Cornell LII)). A structural approach or a code interpretation is not owned by anyone; the specific drawings and text expressing it are.
• Building owners have limits on the architect's rights. Section 120 lets anyone photograph a constructed building visible from a public place, and lets the building's owner alter or destroy it without the architect's consent (source: 17 U.S.C. § 120, scope of rights in architectural works (Cornell LII)). It gives the owner no rights in the drawings themselves.

The practical point for a license: the firm's copyright in its drawings is what it licenses, and a buyer cannot get more rights than the firm holds. Where a client holds the copyright, or a joint interest, the project stays out.

Work for hire, owner-modified forms and client NDAs

“Work made for hire” means two different things, and A/E firms meet both:

• Your employees' work. A work prepared by an employee within the scope of employment is a work made for hire, and the employer is the author (source: 17 U.S.C. § 101, definitions (Cornell LII)). Drawings your staff produce are the firm's, which is why a license is signed by the firm, not the individual designers.
• Commissioned work. The statute's second category covers specially commissioned works in a short list of types (such as contributions to collective works, compilations and supplementary works) when both parties sign a written work-for-hire agreement (source: 17 U.S.C. § 101, definitions (Cornell LII)). Building design is not on that list, so client agreements that want the documents usually add an express assignment of copyright as well. Either clause, if present, takes the project out of a license.

Other clauses to look for in each agreement:

• An assignment of copyright or “ownership of documents” to the owner on payment.
• Confidentiality terms covering project information, which can bar disclosure even of de-identified files.
• Restrictions on publicity or on using the project in marketing, which signal a client that cares.
• Owner-supplied standards or templates, whose content is the owner's even if your drawings are yours.

As a rough rule (our estimate, not a survey), private clients on standard AIA or EJCDC terms leave the firm the most room, and public agencies and large corporate owners with their own forms leave the least. The mix of your client base largely decides how much of your drawing archive is licensable.

Federal, CUI and security-sensitive projects

These projects usually stay out of any license, whatever the copyright position:

• FAR 52.227-17 contracts. The clause says the contractor “shall not use, release, reproduce, distribute, or publish any data first produced” under the contract, or let others do so, without the Contracting Officer's written permission (source: 48 CFR 52.227-17, Rights in Data, Special Works (Cornell LII)).
• Controlled Unclassified Information. CUI covers information an entity creates or possesses for or on behalf of the government that a law, regulation or policy requires safeguarding or dissemination controls for (source: 32 CFR 2002.4(h), definition of CUI (Cornell LII)). Design files for federal facilities often carry CUI markings.
• ITAR technical data. Defense-related technical data is controlled under the ITAR definitions (source: 22 CFR 120.33, technical data (Cornell LII)).
• Sensitive security information. Airport, transit and other transportation security drawings can be SSI under 49 CFR 1520.5 (source: 49 CFR 1520.5, sensitive security information (Cornell LII)).

Buyers screen for this too: at least one buyer program lists defense and export-controlled work as excluded (source: program terms, Regulr buyer directory). Firms with a federal practice usually keep those projects on segregated servers already, which makes them easy to leave out.

Consultants, prime agreements and joint ventures

Many A/E projects have more than one design firm, and each firm's ownership runs through its own agreement. The AIA summary of B101 says the architect and its consultants are each the owners of their “respective” instruments of service (source: AIA Contract Documents, The Rights of an Architect's Instruments of Service), which means a structural or MEP engineer working under an architect owns its own sheets and calcs, not the architect's, and the reverse is true too.

• If you are the prime. Your consultants' drawings and calcs in your project folder are theirs. Leave them out, or ask the consultant to join the license for that project.
• If you are the consultant. Your rights flow from your agreement with the prime, often an AIA consultant form or the prime's own subconsultant agreement. Many pass the owner agreement's terms down to you, so a restriction in the prime's contract with the owner can reach your documents as well.
• Joint ventures and associated firms. Where two firms share authorship, the joint venture agreement decides who may license what. Treat shared sheets as out unless both firms agree in writing.
• Design-build. When the contractor hired you, your agreement is with the design-builder, not the owner, and design-build forms often move more rights to the owner or the design-builder. Read the chain from owner to you.

The practical effect is that one project can split: your firm's sheets and calcs may qualify while the consultants' sheets in the same folder do not. Buyers are used to that, as long as the split is recorded in the scope.

Other people's content inside your project files

Even on a project you own, the folder holds material by other authors. Buyers typically ask for it to be removed or reduced to your own comments and metadata:

Two software terms can also limit what you can offer, even on projects you own. Firms still on Newforma Konekt's 2023 terms granted Newforma a perpetual, irrevocable, sublicensable license to customer data, including to train machine learning and large language models (source: Newforma Konekt terms (updated June 26, 2023), §9.3), so a buyer cannot get those records exclusively. Bluebeam's addendum gives Bluebeam a perpetual right to use content from AI trials and betas for training (source: Bluebeam Product and Services Addendum (March 7, 2026), §2.3.2). Our guide to Deltek, Autodesk, Newforma and Bluebeam data terms covers each clause.

A project-level screen: how firms sort drawings for a license

Firms that license drawings usually build a simple project list and sort it into three groups:

1. Candidates. Private clients on unmodified B101 or E-500 use-of-documents terms, no NDA beyond the standard form, no federal funding clauses, no open claim.
2. Needs a closer read. Modified forms, confidentiality addenda, public owners, projects with publicity restrictions. Some can be cleared by asking the client; most firms simply leave them out.
3. Out. Work for hire or assigned copyright, FAR 52.227-17, CUI, ITAR or SSI, client-owned site data, and anything under a legal hold.

The firm's own records sit outside this screen entirely. Proposals, fee estimates, project financials, QA/QC checklists, firm standards and code responses are about how the firm runs, and they are where many A/E licenses start. The engineering and architecture firms guide lists which records buyers value most, and our page for A/E firms shows how Regulr reviews a firm's project archive.

If a sale of the firm is on the horizon, the screen does double duty: acquirers ask the same ownership questions in diligence. See selling an engineering or architecture firm with a data license in place.

What buyers ask a design firm to warrant

A license agreement turns the screen into promises. Expect to be asked for:

• A warranty that the firm owns or has the right to license the records in scope.
• A list of excluded projects and categories, named in the contract.
• Confirmation that federal, CUI, ITAR and SSI material is excluded.
• De-identification of client names, site addresses, title blocks, seals and license numbers.

And ask for these in return:

• A promise not to use the designs to reproduce any specific building or to identify a client.
• Deletion of raw files after processing, with written confirmation.
• Clear exclusivity terms, since one program licenses on an exclusive basis by default (source: program terms, Regulr buyer directory).

Programs describe their de-identification in their own terms; one says a specialist PII partner strips identifying fields before it or any lab sees the records (source: program terms, Regulr buyer directory). Our directory of programs and their published terms links to each, and the data value checker shows which factors move the price once you know which projects are in.

Frequently asked questions

Sources

AIA Contract Documents' article, the statutes, the FAR clause, the CUI definition and the Newforma and Bluebeam terms read on their own pages on October 18, 2026. The E-500 public copy could not be loaded that day; its wording is described from public copies of the form. Program terms checked October 15, 2026; our buyer directory lists the programs and links to their published terms.

1. AIA Contract Documents, The Rights of an Architect's Instruments of Service
2. EJCDC E-500 (2014) public copy adapted by the City of Durham, NC
3. 17 U.S.C. § 101, definitions (Cornell LII)
4. 17 U.S.C. § 102, subject matter of copyright (Cornell LII)
5. 17 U.S.C. § 120, scope of rights in architectural works (Cornell LII)
6. 48 CFR 52.227-17, Rights in Data, Special Works (Cornell LII)
7. 32 CFR 2002.4(h), definition of CUI (Cornell LII)
8. 22 CFR 120.33, technical data (Cornell LII)
9. 49 CFR 1520.5, sensitive security information (Cornell LII)
10. Newforma Konekt terms (updated June 26, 2023), §9.3
11. Bluebeam Product and Services Addendum (March 7, 2026), §2.3.2
12. program terms, Regulr buyer directory