Client-owned drawings vs firm records in A&E roll-ups: what can be licensed

Who owns architectural drawings?#

Who owns architectural drawings is set by the contract for each project, with copyright law as the default behind it. Under US copyright law, work an employee creates as part of regular duties is a work made for hire owned by the employer, so drawings prepared by a firm's staff generally belong to the firm unless a written agreement transfers them.

Standard professional forms keep that position. AIA B101-2017, Section 7.2, deems the architect and its consultants the authors and owners of their instruments of service and reserves their rights, including copyrights, while B101 gives the owner a nonexclusive license to use them for constructing, using, maintaining, altering and adding to the project. EJCDC E-500 owner-engineer language (2014 edition) similarly treats documents as instruments of service in which the engineer keeps an ownership interest, including the copyright and the right of reuse.

Many clients do not sign those forms. Developers, institutions, corporate owners and public agencies often use their own contracts, which may assign ownership of design documents to the client. A work-made-for-hire label alone may not do that for an outside firm, because commissioned work qualifies only in certain statutory categories, so owner contracts often add an express assignment.

Ownership is only one gate. A firm can own a drawing set outright and still be bound by confidentiality terms, client security requirements or limits on information the client supplied. And a project-limited license to the owner does not, by itself, let the owner license the drawings to anyone else.

Firm records vs client deliverables: an ownership table#

Firm records and client deliverables sit in different ownership positions, and sorting an archive by record class is the fastest way to see what a roll-up might license. The table shows typical starting positions; the project contract can move any of them.

Why roll-ups make the question harder#

Roll-ups make the ownership question harder because each acquired firm brings its own contract forms, client mix and file habits. A platform that bought one firm with mostly private developer work and another with mostly public agency work may hold similar-looking Revit and Bluebeam archives with opposite ownership positions.

Deal structure adds a layer. In a stock acquisition the acquired firm keeps its contracts and copyrights; in an asset acquisition they move only to the extent the purchase agreement assigns them. After integration, merged file servers and a shared Procore or Autodesk Construction Cloud account can blur which firm, and which contract, a project came from.

Some projects stay out whatever the contract says: critical infrastructure, secure facilities, export-controlled work, and projects where the client's design is the substance of the record. SourceX excludes customer-owned designs from licensing.

A project-level screen across acquired firms#

A project-level screen gives every project in the archive a rights tag before any record class is considered for licensing. Run it from the project accounting system, because Deltek, BQE or a similar system usually holds the cleanest list of projects, clients and contract references.

Start with the projects that carry the most licensing value: larger, longer engagements with complete RFI, submittal and review histories from each firm's more recent years. Clearing a focused group of well-documented projects is more useful than a partial pass over the whole archive, and it quickly shows counsel which contract forms recur across the acquired firms.

• 1Pull the project list for each acquired firm, with client, client type, years active and contract reference.
• 2Locate the signed agreement and identify the form: standard professional form, owner-drafted or agency form.
• 3Record the ownership outcome: firm owns, client owns, or joint or unclear.
• 4Record confidentiality terms, security requirements and any limit on reuse of project information.
• 5Flag subconsultant sheets and client-supplied documents inside the project folders.
• 6Tag each record class for the project as candidate, candidate after preparation, or excluded.
• 7Treat projects with no locatable contract as excluded until counsel decides otherwise.

Mixed records: RFIs and markups that quote the drawings#

Mixed records such as RFI logs, submittal comments and Bluebeam markups are the hardest class, because they are firm-created reasoning wrapped around client documents. An RFI asks a question about a sheet, the response cites a detail, and the attachment is often a cropped drawing.

The usual approach keeps the question, the reasoning and the resolution text while removing attached sheets, embedded images, project names, addresses, client and contractor names, and anything that reveals a building's security features. What remains shows how architects and engineers resolve coordination problems, which is the part developers of document and project tools tend to want.

Check whether the project contract treats project communications as confidential information. If it does, removing identities may not be enough, and the project stays excluded.

Illustrative: an engineering platform with four acquired firms#

Illustrative: a fictional engineering platform has acquired four regional firms: two MEP practices, a civil firm and a small structural practice. Each kept its own Deltek database and file server until integration, and two now share an Autodesk Construction Cloud account.

The project screen shows that the civil firm worked mostly for public agencies under agency forms that give the client ownership and impose strict confidentiality, so its archive is excluded. The MEP firms worked mostly for private developers on standard professional forms, and their RFI logs, submittal review comments and QA checklists become candidates once attachments and identities are removed.

Drawings and models stay out across all four firms. The platform's general counsel also adopts one contract template for new projects that addresses reuse of de-identified project records, knowing it will not change the inherited archive.

How SourceX reviews design records from a roll-up#

SourceX reviews design records from a roll-up one acquired firm at a time within the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check uses metadata such as firms, systems, years of projects and contract forms, and nothing is shared during the initial assessment.

Under the SourceX Enterprise Data Value Framework, firm workflow records tend to rate well on domain expertise and human-generated signal, while privacy burden and preparation cost reduce net value where records are tangled with client documents. Provenance by acquired firm and the rights basis for each project group are recorded in the SourceX Evidence Packet.