Rights and contracts
AI use clauses in design and construction contracts
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
AI clauses in design and construction contracts usually require disclosure of AI tool use, require owner approval before use, bar training on project information, or widen owner data and deletion duties. Before reusing project records for licensing, review active and closed owner agreements for these clauses, because the strictest clause on a project governs that project's records.
Key takeaways
- Owner AI clauses range from simple disclosure of AI tools to outright bans on training with project information.
- AI clauses sit on top of ownership terms for instruments of service, which negotiated contracts often change from the AIA and EJCDC defaults.
- A master agreement can reach every task order under it, not just one project.
- Shared records such as RFI responses are affected differently from deliverables and firm-only records.
- A project-by-project register of ownership and AI terms is the basis for any licensing scope in a design or construction firm.
Which AI clauses are showing up in owner contracts?#
AI clauses in owner contracts fall into a handful of recognizable types. Some come from owners' legal teams reacting to public AI tools; others are copied from technology procurement templates and fit design and construction work poorly.
Read each clause for two separate effects: what it says about using AI tools on the project, and what it says about any later use of project information. Only the second limits licensing, but firms often discover both at once.
| Clause type | What it typically says | Effect on reusing records |
|---|---|---|
| Disclosure | The design professional must disclose AI tools used on the work | Little direct effect on licensing |
| Approval before use | AI tools need owner consent before use on the project | May be read to cover sharing project data with AI developers |
| No training or ingestion | Project information may not be used to train or improve AI | Directly blocks licensing records from that project |
| Expanded owner data definition | All information produced for the project is owner data | Can sweep in RFI logs, meeting minutes and emails |
| Deletion at closeout | Owner information must be returned or destroyed after the project | Records may not exist to license, or must not be kept |
| AI-assisted deliverables | Ownership and warranty of work produced with AI help | Usually affects deliverables, not internal records |
| Standard of care | Use of AI does not reduce the professional standard | No licensing effect, but signals owner attention |
How do AI clauses interact with instruments of service?#
AI clauses interact with instruments of service by narrowing what a firm may do even with documents it owns. The AIA B101-2017 owner-architect agreement deems the architect and its consultants the authors and owners of their instruments of service, and gives the owner a nonexclusive license to use them for the project. EJCDC owner-engineer forms take a similar approach, with the engineer keeping an ownership interest, including copyright.
Those are defaults. Negotiated owner contracts often change them, and some owners require a transfer of copyright in everything produced for the project. Read the signed agreement and its amendments, not the standard form.
A firm that owns its drawings can still be barred from sharing them with an AI developer if a no-training clause covers project information. A firm that does not own its drawings may still control internal records the owner never received, such as QA/QC comments, staffing plans and proposal history. So the review has two layers: who owns or controls each record family, and whether any AI or confidentiality clause limits use of records the firm does control.
How do ownership and AI terms combine on a project?#
Ownership and AI terms combine to decide each project's treatment, and the combination matters more than either clause alone. The matrix gives a starting view for a managing principal; the signed contract decides the real answer.
Shared records such as RFI responses, submittal reviews and meeting minutes are where the two layers collide most often, because they mix owner information with the firm's own professional judgment. Firm-only records such as estimating history and design standards are usually affected only by the strictest clauses.
| Ownership position | AI or confidentiality term | Likely treatment of the project's records |
|---|---|---|
| Firm owns instruments of service | Standard confidentiality only | Internal records often in scope after de-identification; deliverables reviewed for owner information |
| Firm owns instruments of service | No training or ingestion of project information | Project-derived records excluded, including firm-owned drawings |
| Owner owns all project documents | No AI term | Deliverables excluded; internal QA/QC, estimating and staffing records reviewed separately |
| Owner owns all project documents | Owner data defined as all information produced for the project | RFI logs, minutes and emails treated as owner data and usually excluded |
| Any | Return or destroy owner information at closeout | Confirm what may lawfully be kept before counting it as licensable |
| No signed contract can be found | Unknown | Excluded until the governing terms are confirmed |
How to review a contract portfolio for AI terms#
A contract review for AI terms should cover closed projects as well as active ones, because closed projects hold most of a firm's history. The output is a register that tags each project before anyone decides licensing scope.
Expect gaps in older files. Signed copies of closed agreements are sometimes missing or stored only with the owner, and a project with no findable contract should be tagged as unknown and kept out of scope until the governing terms are confirmed.
- Collect owner agreements, master service agreements, task orders and amendments for each project in the candidate date range.
- Search for terms such as artificial intelligence, machine learning, train, large language model, automated tools and owner data.
- Note the ownership clause for instruments of service and project documents.
- Check confidentiality, return and deletion obligations at closeout.
- Check subconsultant agreements for flow-downs that restrict the firm as well.
- Tag each project as clear, consent needed or excluded, and record the reason.
- Ask owners for written consent only where the records are worth the request.
Illustrative: an architecture firm builds its register#
Illustrative: a fictional 90-person architecture firm keeps proposals, fees and staffing in Deltek Vantagepoint and QA/QC checklists on its own file server. Its RFI responses and submittal reviews live mostly in contractors' Procore projects and Bluebeam Studio sessions. Its clients include private developers, a public university and several corporate campus owners.
The register shows that the university's master agreement bars any use of project information to train AI, two corporate owners require approval before AI tools touch their information, and most private developer contracts, based on amended AIA forms, say nothing about AI but define project documents broadly.
The managing principal excludes every university project, includes internal QA/QC notes and proposal history across the board after de-identification, and includes RFI responses only from private projects where the contract allows it and the firm kept its own copies at closeout. The firm also updates its proposal template so future contracts separate AI tool use from licensing of de-identified internal records.
What should firms propose in new contracts?#
Firms negotiating new contracts can propose AI terms that answer owner concerns without closing off every later use. Owners mostly worry about their confidential information reaching public tools and about AI lowering quality; few have a view on de-identified process records.
Practical positions include a carve-out for de-identified internal records that do not identify the owner or the project, a disclosure duty limited to tools that process owner information, and approval rights that apply to AI tools rather than to every downstream use. Mutual terms are easier to accept than one-sided ones, and counsel should fit them to each owner's paper.
How SourceX handles AEC contract restrictions#
SourceX reviews AEC contract restrictions in the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Scope is set project by project, and records from projects tagged as excluded never enter preparation.
The resulting scope, including which projects and record families are in and why, is recorded in the SourceX Evidence Packet under licensing rights and permitted use, next to provenance, the privacy record and release authorization.
Frequently asked questions
Does a no-AI clause in one contract taint all of a firm's records?
Usually not. Most clauses cover information from a specific project or owner. A master service agreement, however, can apply to every task order issued under it, so one signature may reach many projects. The register should track the agreement that governs each project, not just the project name.
Do subconsultant and subcontractor agreements matter?
Yes. Prime agreements often flow AI and confidentiality terms down to subconsultants, and a subconsultant's own records may be restricted by terms it agreed with the prime. Firms acting as prime should also check what their subconsultants are allowed to do with shared project records.
Are public owners different from private owners?
Often. Public owners may add records, procurement and security requirements, and some projects involve security-sensitive information that should be excluded entirely. Treat public-owner projects as a separate review category rather than applying private-owner assumptions.
Can using AI features in project software breach a no-training clause?
It can, depending on the software vendor's terms. Procore's AI FAQ, for example, says customer data is not used to train Microsoft's models but that Procore's internal models may use customer inputs and outputs to improve its AI accuracy. Check the settings and terms of any tool that holds owner information against each owner's clause.
Should firms tell owners they plan to license de-identified records?
Where the contract requires consent, yes. Where it does not, many firms still prefer transparency with long-standing clients, because a surprise can damage the relationship even when the license is permitted. The decision is commercial as well as legal.
Does an AI clause added by amendment reach records created before it?
It may. Amendments and renewals often restate definitions such as project information or owner data, and those definitions can reach records created earlier on the same project. Read the amendment's wording and effective-date language with counsel before treating older records as unaffected.
Sources
- Under AIA B101-2017 Section 7.2, the Architect and its consultants are deemed the authors and owners of their Instruments of Service. Source
- AIA B101 grants the Owner a nonexclusive license to use the Instruments of Service for the Project. Source
- EJCDC E-500 language states the Engineer retains an ownership and property interest in the Documents, including the copyright. Source
- Procore's AI FAQ says customer data is not used to train Microsoft products and that Procore's internal models may use customer inputs and outputs to improve Procore AI accuracy. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.