AI for architecture firms: what your project archive is good for

What is an architecture firm's project archive good for?#

An architecture firm's project archive is good for two things AI depends on: examples of how designs develop, and examples of how professionals review, question and resolve them. Finished drawings show the outcome. Working records show the reasoning.

Internally, the archive can feed tools that draft specifications from the office master, find precedent details, or help newer staff answer code questions against past projects. Externally, de-identified records can be licensed to AI developers building plan-review, document understanding and design-assist tools. The firm keeps ownership in both cases; a license grants defined use, not the records themselves.

Which archive records serve which AI uses#

Archive records differ in how useful they are and in how restricted they are, so sort them before anyone talks to a tool vendor or a developer. The table covers the record families most firms hold in Revit, Bluebeam, Newforma, Deltek and their project drives.

Two patterns stand out. Records that capture the firm's own judgment, such as internal design review notes and QA/QC markups, help internal tools, draw developer interest and carry the lightest rights flags. Records that mix in other parties' material, such as submittal reviews and RFIs, are just as useful but need the contractor's content separated out, while proposals and owner correspondence help internal tools and rarely belong in a license.

Client deliverables and internal records are not the same#

The distinction between client deliverables and internal records decides most of what an architecture firm can do with its archive. Deliverables are what the owner paid for and received. Internal records are what the firm created along the way to produce them.

Internal records are usually under the firm's control, subject to confidentiality terms about the project. Deliverables come with owner licenses, confidentiality obligations and sometimes ownership transfers. Material from clients, consultants and contractors belongs to them and should be left out or cleared separately.

• 1Internal records: QA/QC markups, design review notes, internal meeting minutes, staffing plans, proposal drafts, lessons learned.
• 2Deliverables: issued drawing sets, specifications, models and reports transmitted to the owner.
• 3Client-furnished information: surveys, geotechnical reports, owner design standards, existing-building drawings.
• 4Consultant work: structural, MEP, civil and specialty drawings and models prepared by others.
• 5Contractor material: shop drawings, product data and the questions contractors raise in RFIs.

What the instruments-of-service position means for licensing#

The instruments-of-service position means the architect usually starts from ownership. Under Section 7.2 of AIA B101-2017, the architect and its consultants are deemed the authors and owners of their respective instruments of service and reserve their rights, including copyrights, while the owner receives a nonexclusive license to use them for the project. That is a strong starting point for licensing, but it is not permission by itself.

Owners often edit standard forms or use their own. Some transfer ownership of documents to the owner, add work-made-for-hire language, broaden confidentiality, or attach riders that bar training third-party models on project data. Each project's executed contract, including exhibits and amendments, decides the answer, and unclear cases go to counsel.

Consultant agreements follow similar logic. Consultants usually keep ownership of their own instruments of service, so their sheets and models need separate clearance even when they are bound into the architect's set.

Where to start: records ranked by control and effort#

The place to start is with records the firm wrote for itself, because they need the least clearing and the least preparation. The order below follows the line between internal records and deliverables: the more a record is the firm's own working material, the earlier it can move into internal tools or a licensing review.

The same order suits both uses. An internal specification or review assistant built on the first group shows quickly whether the archive is organized well enough, and the cleanup it requires prepares those records for any later rights review.

Illustrative: a mid-size practice starts with its specifications#

Illustrative: a fictional architecture practice designs multifamily housing and workplace interiors. Its managing principal wanted an internal specification assistant and asked whether any of the archive might also interest AI developers.

Operations found the office master specification and years of project edits in Word files on the project drive, QA/QC markups in Bluebeam, and submittal and RFI logs in Newforma. The specification assistant started with the master and the project edits, which the firm had written itself, and the team cleaned up file naming so each edit could be traced to its project.

For the licensing question, the team kept internal markups and the firm's own submittal review comments, and stripped contractor product data and client-furnished surveys from those records. One corporate client's agreement had assigned document ownership to the client, so its projects were excluded. The principal approved a metadata-only fit check before any records were shared.

How SourceX approaches architecture archives#

SourceX approaches an architecture archive project by project through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check needs only metadata, such as systems, record families, years covered and known contract restrictions.

Rights review separates internal records, deliverables and third-party material before anything is prepared. Large model archives stay in the firm's own storage or ship on encrypted drives, and the SourceX Evidence Packet documents what was approved, on what basis, and who authorized release.