Who owns the BIM model: the owner, architect or contractor?

Who owns the BIM model?#

The BIM model is usually not owned by one party: each contributor typically keeps rights in the elements it authored, and the project owner receives a license to use the model for the project. The owner-architect agreement, its BIM or digital data exhibit, and the BIM execution plan set the actual terms.

That default reflects how design documents have long been treated. Architects and engineers have traditionally treated drawings as instruments of service in which they retain rights, and BIM extends that logic to model content. Owners with strong bargaining power, including many public and institutional owners, often rewrite the clause so that ownership transfers on payment or on creation.

Why model ownership splits across parties#

Model ownership splits because a modern BIM model is really several models. The architect authors the architectural model, consultants author the structural and MEP models, and trade contractors may author fabrication models. A federated coordination model links them without merging their authorship.

Ownership also differs from permission. A contractor may be allowed to use the architect's model for coordination without owning it, and a project owner may receive the right to use the model for facility management without the right to reuse it on another building. Read the grant of rights and the reliance language together.

Reliance is the quiet third issue. Many agreements let other parties use a model while stating that the printed or sealed documents govern, so permission to use a model is not a promise that it is accurate.

Matrix: model content, typical owner and internal history#

The matrix shows typical positions in negotiated agreements. Your contracts may differ, so treat it as a set of questions to check rather than an answer.

Documents that decide BIM ownership#

BIM ownership on a specific project is decided by a stack of documents, and the agreement's order of precedence clause usually says which one controls when they differ. Collect all of them before answering an ownership question for a project.

Where no precedence clause resolves a conflict, or where the documents are silent, the answer is a legal question for counsel, not a default to assume in either direction.

• 1Owner-architect or owner-engineer agreement, especially the instruments of service and ownership clauses.
• 2BIM or digital data exhibit or addendum, whether a standard form from AIA or ConsensusDocs or the owner's own.
• 3BIM execution plan: model authors, levels of development, exchange protocols and permitted uses.
• 4Consultant agreements that pass rights up or down the contracting chain.
• 5Common data environment and platform terms where the model was hosted.
• 6Software license terms, which can affect how files created with the tools may be used.

What the project owner gets at handover#

At handover, the project owner usually receives model files and a license to use them for operating and maintaining the building, often with disclaimers that the model may not match field conditions. Some contracts transfer ownership of the record model outright, and some facility owners ask for that so they can maintain the model for operations.

Handover does not normally transfer the firm's internal working history: superseded versions, internal markups, review comments and coordination notes that were never deliverables. Those records generally stay with the firm, though confidentiality obligations about the client's project still apply to them.

The practical step for a digital practice leader is to make this split visible from the start of each project: name model authors in the BIM execution plan, keep internal review files apart from deliverables, and record what was handed over and when.

What this means for licensing internal model records#

Licensing internal model records starts by separating what the firm authored and retained from what belongs to the project. Families, templates, modeling standards, QA logs and coordination decisions are often separable. Client-specific design content and anything handed over as a deliverable are usually excluded.

Even firm-owned history needs de-identification. Model metadata can carry project addresses, client names, user names of staff and file paths that reveal clients, so preparation goes beyond the visible geometry.

• 1Pull the executed agreement, BIM exhibit and execution plan for each project in scope.
• 2Mark each record family as firm-authored, client-owned, third-party or unclear.
• 3Exclude unclear projects until counsel has reviewed them.
• 4Strip model metadata, staff user names and file paths from anything retained.
• 5Record the basis for each inclusion so the decision can be explained later.

Illustrative: mapping a Revit archive against contracts#

Illustrative: a fictional architecture firm's digital practice leader maps its Revit archive against the agreements behind each project. Projects signed on the firm's preferred agreement form, with a standard license to the project owner, have internal QA logs and coordination notes that counsel clears for a de-identified package.

Projects for owners whose contracts vest all project data in the owner are excluded entirely, including their internal history, because the confidentiality language reaches working files. The firm's office template and family library, which it authored and never assigned, are considered separately. The result is a smaller scope that every partner can explain.

How SourceX approaches model ownership#

SourceX checks model records project by project in the Rights step of the SourceX five-step transaction, against the executed agreement, the BIM exhibit and the execution plan. Projects with unclear or owner-vested rights are left out rather than argued, and client design content stays out unless the rights review clears it.

In Preparation, model-derived records such as QA logs and coordination notes are stripped of file paths, staff user names and project metadata. The SourceX Evidence Packet records the licensing rights relied on and the permitted use, the firm keeps ownership of its records, and the firm approves the final scope.