Definitions and comparisons
Owner-furnished vs firm-produced documents: what can an AEC firm license?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
An AEC firm can usually license only what it produced and controls, such as internal review comments, RFI responses, QA/QC checklists and project management records, prepared to remove client details. Owner-furnished documents like surveys and geotechnical reports belong to others and stay out. Sort every project file by who produced it before asking whether it is licensable.
Key takeaways
- Provenance, meaning who produced a document, is the first sort for any AEC project archive.
- Owner-furnished documents such as surveys, geotechnical reports and existing drawings generally stay out of a license.
- Firm-produced drawings and models are instruments of service whose use depends on the signed agreement and its confidentiality terms.
- The firm's own process records, such as review comments and RFI responses, are usually the most licensable material.
- Consultant and contractor documents need those parties' rights checked, even when they sit in the firm's own systems.
What are owner-furnished and firm-produced documents?#
Owner-furnished documents are materials the client supplies for a project: site surveys, geotechnical reports, the building program, existing drawings from earlier designers, owner design standards and hazardous materials surveys. Firm-produced documents are what the firm's own staff create, from drawings, specifications and models to internal review notes, RFI responses, meeting minutes and fee proposals.
Between those two sit documents from consultants the firm hires, such as structural, MEP or civil engineers, and documents from contractors, such as shop drawings, submittals and contractor RFIs. Every project archive mixes all four, often in the same folder or the same project platform, which is why sorting by source comes before any licensing decision.
What can an AEC firm license, by document source?#
An AEC firm can usually license material it produced and controls, after client details are removed, and very little of what others produced. The table gives the usual starting position for each source; the signed agreements decide the final answer. Even firm-produced records can be caught by a confidentiality clause that treats all project information as the client's, so check that clause for each contract family.
The firm's process records are the strongest category for a reason beyond rights. They capture judgment: why a detail was changed, how a conflict was resolved, what a reviewer caught. That reasoning is what makes project records useful to AI developers working on design review and project delivery tools.
| Source | Examples | Usual ownership | Licensability |
|---|---|---|---|
| Owner-furnished | Surveys, geotechnical reports, program, existing drawings, owner standards | The owner or its consultants | Exclude unless the owner consents in writing |
| Firm-produced instruments of service | Drawings, specifications, BIM models, calculations | Often the firm under standard forms; varies by contract | Review: owner license, confidentiality and project type decide |
| Firm-produced process records | QA/QC checklists, review comments, RFI responses, change logs, minutes | The firm | Often licensable once client and project details are removed |
| Consultant-produced | Structural, MEP, civil and specialty drawings and reports | The consultant, under its own agreement | Exclude unless the consultant agrees |
| Contractor-produced | Shop drawings, submittals, contractor RFIs, pay applications | The contractor or its suppliers | Exclude originals; the firm's review responses may remain |
| Correspondence | Email and meeting threads among all parties | Mixed | Split by author; keep firm-authored reasoning only |
Instruments of service: ownership is not the whole answer#
Instruments of service are the drawings, specifications and models a design firm produces. Standard industry forms, such as the AIA B101 owner-architect agreement, generally treat the architect and its consultants as the owners of their instruments of service, including copyright, and grant the owner a nonexclusive license to use them for the project. Owner-drafted contracts often change that allocation, sometimes transferring ownership to the client outright.
Even where the firm keeps copyright, licensing drawings for AI raises further questions: confidentiality clauses, security-sensitive building types, the owner's proprietary layouts and consultant work embedded in the sheets. That is why it usually makes sense to start with the process records around the drawings rather than the drawings themselves, and to treat drawing sets as a later, project-by-project decision.
Mixed records: RFIs, submittals and email#
Mixed records are documents in which several parties wrote different parts, and they are both the most valuable and the most delicate part of an AEC archive. An RFI log holds the contractor's question, the firm's answer and sometimes a consultant's input, all in one record.
The practical approach is to split by author. The firm's response, reasoning and decision are firm-produced and can often be licensed once project and client identifiers are removed. The contractor's question can sometimes be paraphrased into a neutral prompt, but original attachments such as shop drawings stay out.
Document the split. A short note for each record family saying which parts were kept, paraphrased or dropped lets a reviewer check the work and makes the next export repeatable.
- RFIs: keep the firm's response and reasoning; drop contractor attachments and proprietary product data.
- Submittal reviews: keep review comments and dispositions; exclude the submitted shop drawings and product data.
- Change logs: keep the firm's evaluation of scope and design impact; remove fee and pricing details tied to the client.
- Email threads: keep firm-authored technical discussion; drop owner and consultant attachments.
- Meeting minutes: keep decisions and action items; remove names and owner business information.
How to tag documents by source in your systems#
Tagging documents by source is easiest where systems already record who authored or uploaded each item. Project platforms and markup tools usually track authors and companies; shared drives and email archives usually do not, so they need folder conventions, sender domains and sampling.
Start with the system that holds the most firm-authored reasoning, which for many firms is the project platform's RFI and submittal logs, and work outward to the less structured stores.
| System | What it usually holds | How to tag provenance |
|---|---|---|
| Procore or a similar project platform | RFIs, submittals, drawing logs, meeting minutes | Use the author or company recorded on each item to separate firm, owner, consultant and contractor |
| Bluebeam sessions and markups | Review comments and redlines on drawing sets | Sort or filter markups by author; the firm's reviewers' comments are firm-produced |
| Revit and other BIM models | Firm models plus linked consultant and owner files | Separate linked consultant models from the firm's own model |
| Deltek or BQE project records | Budgets, staffing, time entries, project notes | Firm-produced; remove client fee terms and personal data |
| Shared drives and email | Everything, often unlabeled | Sort by folder conventions and sender domain, then sample |
Illustrative: an engineering firm sorts its project archive#
Illustrative: a fictional structural and civil engineering firm wants to know which parts of its project archive could be licensed. Its projects live in Deltek, Procore and a shared drive, with Bluebeam sessions used for internal checking.
The team tags documents by source. Geotechnical reports, owner surveys and architect backgrounds are owner-furnished or consultant-produced, so they are excluded. Contractor shop drawings are excluded while the firm's submittal review comments remain. Calculation check records, internal peer review comments and RFI responses are firm-produced.
Projects whose contracts bar any disclosure of project information come out entirely, as does all work on security-sensitive facilities. The firm proceeds with a package of review comments, RFI responses and calculation check notes, with client names, site addresses and project identifiers removed.
How SourceX handles provenance in AEC archives#
SourceX sorts AEC records by provenance in the Rights step of the SourceX five-step transaction. The fit check asks which systems hold project records and which contract forms the firm uses, without collecting any files.
Provenance is the first element of the SourceX Evidence Packet, alongside licensing rights, permitted use, the privacy record and release authorization, so the buyer receives a clear statement of which parties produced the licensed material and which sources were left out.
Frequently asked questions
Does a signed AIA agreement settle what we can license?
It settles part of the question. The agreement allocates ownership and use of instruments of service, but modifications, owner riders, confidentiality clauses and project-specific terms can change the picture. Read the signed version with its amendments rather than relying on the standard form.
Who owns a BIM model with several authors?
Usually each author keeps rights in its own contribution, subject to the contracts. A federated model can combine the firm's model with linked consultant and owner files. Separate those layers before considering any license, and keep consultant and owner content out unless they agree.
What about projects for public agencies?
Public-agency contracts often carry their own ownership, confidentiality and records clauses, and some facilities raise security concerns. It is usually simpler to leave public-sector and security-sensitive projects out of a first license and focus on private-sector work with simpler terms.
Can we license documents inherited from a firm we acquired?
Possibly, if the acquisition transferred the contracts and records and the original agreements permit it. Asset deals and stock deals transfer rights differently, so confirm what came across under the purchase agreement before treating an acquired archive as your own.
Are fee proposals and staffing plans licensable?
They are firm-produced, and they show how the firm scopes and resources work, which some AI developers value. They also reveal pricing and client relationships. Firms that include them usually remove client names, fee amounts and personal details about staff, keeping the scoping logic.
Are our standard details and office master specifications licensable?
They are often the firm's most reusable work, because they are not tied to one client. Check their origins first: office masters are frequently built on subscription master guide specifications whose terms may restrict redistribution, and some details were adapted from manufacturers' published content. License only the parts the firm authored itself.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.