Rights and contracts
Who owns BIM models and shared project data on construction projects?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
On most construction projects, no single party owns the BIM model or the shared project record. Each author usually keeps rights in what it created, the owner receives a project-use license, and contracts and platform terms set the rest. For licensing, a design firm's strongest position is its own internal records, not shared deliverables.
Key takeaways
- A federated BIM model is a stack of separately authored models, and rights usually follow each author unless the contract assigns them.
- Ownership, licensed use and confidentiality are three separate questions, and a project record can be restricted even where the firm holds copyright.
- Hosting a common data environment controls access and retention, not ownership of the documents inside it.
- Owner-drafted agreements often shift ownership of drawings and models to the owner, so read the signed version, not the standard form.
- Internal review notes, QA/QC checklists, staffing and scheduling records are usually the most licensable part of a design firm's archive.
Who owns the BIM model and the shared project record?#
The BIM model on a typical project is owned in pieces, not as one asset. The architect's design model, the structural and MEP engineers' models, and the contractor's coordination and fabrication models are each authored by a different party, and copyright in each part usually starts with its author.
Contracts then move rights around. Many owner-design agreements leave the design professional holding copyright in its instruments of service and grant the owner a license to use them to build, operate, maintain and later alter the project. Owner-drafted agreements often go further and require an assignment, so the owner holds title to drawings and models outright.
Shared records such as RFIs, submittals, meeting minutes and change documents add a third layer. Each document has an author, but the contract usually treats the collection as project records that are confidential and must be delivered to the owner at closeout. A managing principal therefore has to answer three separate questions for every record: who owns it, who may use it, and who must keep it confidential.
Ownership matrix by record type#
Record type is the quickest way to sort a project archive, because the author and the contract position tend to repeat across projects. The matrix below shows the usual starting point, which any signed agreement can change.
| Record type | Usually created by | Typical rights position | Licensing outlook for the design firm |
|---|---|---|---|
| Design model and construction drawings | Architect or prime engineer | Author keeps copyright and licenses the owner, unless the agreement assigns it | Usually carved out: client-specific and often confidential |
| Consultant models (structural, MEP, civil) | Each subconsultant | Consultant keeps rights, flowed through the prime agreement | Needs the consultant's consent as well as the client's |
| Coordination and fabrication models | General contractor and trades | Contractor or subcontractor keeps rights | Not the design firm's to license |
| RFIs and responses | Contractor asks, design team answers | Mixed authorship; project confidentiality applies | Possible for the firm's own responses, de-identified and contract-checked |
| Submittals and shop drawings | Subcontractors and manufacturers | Supplier content; reviewer adds stamps and comments | Review comments may qualify; supplier documents usually do not |
| Internal design reviews, redlines and QA/QC checklists | Design firm | Firm-owned internal records | Strongest candidate, after removing client identifiers |
| Staffing, scheduling and fee tracking in Deltek or BQE | Design firm | Firm-owned operating records | Strong candidate, with commercial terms masked |
How contract forms change the default#
The contract form decides which column of the matrix applies on a given project. AIA's standard owner-architect agreement, B101-2017, deems the architect and its consultants the authors and owners of their instruments of service, with copyright reserved, and gives the owner a nonexclusive license to use them for constructing, using, maintaining, altering and adding to the project, provided the owner performs its obligations, including payment. EJCDC's owner-engineer agreement takes a similar position for engineers, who keep copyright and the right of reuse.
Other standard families, including ConsensusDocs, handle ownership in their own ways, and most families also publish BIM or digital data exhibits that set how models may be used and relied on. Editions differ and forms are routinely modified, so the signed document controls. Owner-drafted agreements are where most surprises sit: institutional, developer and public owners often replace the license with an assignment, add broad confidentiality, and require the return or destruction of project information at the end of the job.
| Contract form | Usual starting point | What to look for |
|---|---|---|
| AIA B101 owner-architect agreement | Architect and consultants own their instruments of service; owner gets a nonexclusive project-use license | Modified ownership language, BIM or digital data exhibits, confidentiality |
| EJCDC owner-engineer agreement | Engineer keeps copyright and the right of reuse | Edits to the reuse wording and any owner confidentiality rider |
| AIA A201 general conditions | Contractor and its subcontractors may use the design documents only to perform the Work | Contractor's own coordination models and shop drawings stay separate content |
| Owner-drafted agreement | Owner often takes title to drawings, models and project data | Assignment wording, survival of confidentiality, return or destruction duties |
| Design-build | Designer often contracts with the design-builder, not the owner | Flow-down clauses that pass owner terms through to the designer |
| Public agency contract | Public owner frequently claims ownership | Security restrictions on facility information and public records duties |
| Subconsultant agreement | Mirrors the prime agreement | Whether the prime may use or license the consultant's work |
Hosting a common data environment is not ownership#
A common data environment controls access to project information, not title to it. Whoever holds the Procore, Autodesk Construction Cloud or Bluebeam Studio account, usually the owner or the general contractor, decides who can see, export and keep records, and the platform's terms govern that account.
Design firms often lose access to the shared environment at closeout. The copies they exported along the way, such as RFI logs, submittal registers and marked-up PDFs stored in their own project folders, remain their copies, but holding a copy does not change who owns the content or lift any confidentiality duty.
When building an inventory, record where each copy lives and how it got there. A firm that can show its RFI responses came from its own document management system has a cleaner provenance story than one relying on a bulk export from a contractor's account.
What a design firm can usually license#
A design firm can usually license records that capture how it works rather than what it delivered to a particular client. Those records hold the professional judgment AI developers look for, and they carry fewer client restrictions than models and drawings.
- Internal design review comments, redlines and QA/QC checklists, with project names and addresses removed.
- The firm's drafted RFI responses and the internal discussion behind them, where the agreement does not forbid reuse.
- Staffing, scheduling and utilization histories from Deltek or BQE, with client names and fees masked.
- Office standards, Revit templates and content families the firm built itself, not ones licensed from manufacturers.
- Lessons-learned reports and post-occupancy reviews written for internal use.
- Carve-outs to keep out: owner-assigned deliverables, public agency projects with security limits, and any record a client has asked to be destroyed.
Illustrative: a structural engineering firm sorts its archive#
Illustrative: a fictional structural engineering firm keeps Revit models, Bluebeam markups, RFI logs exported from Procore and project financials in Deltek Vantagepoint. Its managing principal wants to know what could be licensed without asking every past client.
The firm's counsel sorts projects by agreement. Projects signed on the firm's standard terms, which kept ownership with the firm and limited confidentiality to information the owner marked as confidential, move forward after a check for any such markings. Owner-drafted agreements with assignments, and every public agency project, are excluded. Contractor coordination models are excluded everywhere.
The package that proceeds contains internal review markups, RFI responses and staffing records, de-identified so that no building can be recognized. It is smaller than the full archive but every record has a documented rights basis. The firm also updates its standard agreement so future projects state clearly what it may reuse.
How SourceX approaches project record ownership#
Project agreements are the main rights input SourceX works from with a design firm. In Rights, the second stage of the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery), each record family is tied to the agreements that govern it, and anything with an unresolved owner or consultant claim waits until the firm and its counsel decide.
Nothing is shared during the initial fit check, which asks only about systems, years of history and record families. When a package proceeds, the licensing rights section of its SourceX Evidence Packet names the governing agreement for every included project, and the release authorization shows the firm's own sign-off.
Frequently asked questions
Who owns the record model handed over at closeout?
The owner usually receives the record model and as-built documents as a contract deliverable, with use rights the agreement defines. The design firm may still hold copyright in its content unless it assigned it, and contractor updates add the contractor's own material. Receiving the file and owning every part of it are different things.
Can an architect reuse standard details from past projects?
Firms routinely reuse their own standard details, specifications language and know-how, and most agreements expect that. Elements designed specifically for one owner, or information the owner marked confidential, are treated differently. Licensing reuse to an outside party is a separate question from reuse on the next project, so check the agreement for both.
Are RFIs confidential project information?
Often they are. Many agreements define project information broadly enough to cover RFIs, submittals and meeting minutes, and require the design team to keep it confidential. De-identification may help, but it does not override a confidentiality clause, so the agreement has to permit the use or the owner has to consent.
Does removing names make a building model safe to license?
Usually not on its own. Building geometry, structural grids and site features can identify a specific building even without a project name or address. That is why most firms license internal reviews and text records rather than models, and why security-sensitive facilities are typically excluded altogether.
Do subconsultants have to agree?
If the records include a subconsultant's models, drawings or calculations, the subconsultant's rights usually need to be addressed. Subconsultant agreements often mirror the prime agreement, so the prime firm may hold a license to use the work on the project but not to license it to anyone else.
Sources
- Under AIA B101-2017 Section 7.2, the Architect and the Architect's consultants are deemed the authors and owners of their respective Instruments of Service and reserve all common law, statutory and other rights, including copyrights. Source
- AIA B101 grants the Owner a nonexclusive license to use the Architect's Instruments of Service solely and exclusively for constructing, using, maintaining, altering and adding to the Project, provided the Owner substantially performs its obligations, including prompt payment of all sums due. Source
- EJCDC E-500 Owner-Engineer agreement language (2014 edition excerpt) states that all Documents are instruments of service and the Engineer retains an ownership and property interest therein, including the copyright and the right of reuse at the Engineer's discretion. Source
- AIA A201-2017 Section 1.5.2 authorizes the Contractor and its subcontractors and suppliers to use and reproduce the Instruments of Service only for performing the Work. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.