Who owns construction documents: what a contractor can license, and what stays with the architect, owner and subs

Why ownership of construction documents decides what you can license

A project platform puts every participant's documents in one place. Procore's annual report says customers can “invite all project participants, including owners, general contractors, specialty contractors, architects, and engineers” (source: Procore Technologies, Form 10-K for 2025). That is convenient for running a job and messy for a data license, because a buyer needs you to warrant that you have the right to license every record you deliver. One buyer program, for example, excludes what you hold on behalf of your own clients, and a data lab says data held for clients is out of scope unless you have the right to license it (source: program terms, Regulr buyer directory). Each is the program's own published term; our buyer directory lists the programs and links to their published terms.

So the first job in scoping is sorting documents by author. The rest of this page goes through the usual categories on a commercial project. Your own prime contracts and subcontracts control, and they often edit the standard forms. For what buyers want from the records that pass, see our construction contractors guide.

Ownership of drawings and specifications under AIA A201

A201-2017 defines Instruments of Service as representations, in any medium, of the creative work performed by the architect and its consultants, including studies, surveys, models, sketches, drawings and specifications (§1.1.7). Section 1.5.1 of the standard form says the architect and its consultants are “deemed the authors and owners” of their Instruments of Service, and that the contractor, subs and suppliers shall not own or claim a copyright in them (source: AIA A201-2017 with AIA's additions and deletions report (University of Wisconsin System copy)).

Section 1.5.2 then gives the contractor, subs and suppliers a narrow permission: they may use and reproduce the Instruments of Service provided to them “solely and exclusively for execution of the Work,” and may not use them on other projects or for additions outside the scope of the Work without written consent of the owner, the architect and, if needed, the architect's consultants (source: AIA A201-2017 with AIA's additions and deletions report (University of Wisconsin System copy)). Licensing drawing sets to an AI buyer is a use outside the Work, which is why buyers typically exclude them.

Owners do not get ownership by default either. AIA's owner-architect agreement keeps the architect as author and owner and gives the owner a license to use the Instruments of Service for constructing, using and maintaining the project (source: AIA Contract Documents, The Rights of an Architect's Instruments of Service). Owners often edit that, though. The public copy we read, adopted by the University of Wisconsin System, replaces the architect-ownership sentence with one that makes the drawings, models and approved shop drawings the owner's property on completion (source: AIA A201-2017 with AIA's additions and deletions report (University of Wisconsin System copy)). Under either version the drawings are not the contractor's. For the designer's side of this question, see our guide on who owns architectural drawings.

Copyright in construction drawings and photos of buildings

Federal copyright law lists architectural works among protected works (source: 17 U.S.C. § 102(a)(8), architectural works (Cornell LII)), and defines an architectural work as the design of a building as embodied in any tangible medium of expression, “including a building, architectural plans, or drawings” (source: 17 U.S.C. § 101, definition of architectural work (Cornell LII)). So copyright in construction drawings sits with the designer, on top of whatever the contracts say.

Photos are different. Section 120(a) says the copyright in a constructed building does not include the right to prevent photographs of it if the building is located in or ordinarily visible from a public place (source: 17 U.S.C. § 120, scope of architectural works (Cornell LII)). That is why dated job-site photos, progress video and 360 captures usually pass once faces, plates, badges and documents in frame are blurred. Two cautions: photos of secure sites go to review, and a photo that mostly shows a drawing on a table is really a picture of the architect's work.

Shop drawings, product data and submittals

A201 defines shop drawings as drawings, diagrams, schedules and other data specially prepared for the Work “by the Contractor or a Subcontractor, Sub-subcontractor, manufacturer, supplier, or distributor” (§3.12.1), and product data as illustrations, schedules, performance charts, instructions and brochures furnished to illustrate materials or equipment (§3.12.2). It also says shop drawings, product data and samples are not Contract Documents (§3.12.4) (source: AIA A201-2017 with AIA's additions and deletions report (University of Wisconsin System copy)).

In practice almost every submittal on a GC's project was prepared by a sub, a fabricator or a manufacturer, and the review stamps and comments come from the architect or engineer. That content usually stays out. What may pass review is your own submittal log: dates, status, number of resubmittals and turnaround, with names removed. For a self-performing specialty contractor that draws its own shop drawings, those drawings are the company's own work, subject to what your subcontract says.

Construction documents the contractor creates

These are the records that usually belong to the contractor and form the core of a license:

• Estimates, takeoffs and bid results. Quantities, unit prices, crew assumptions and the won or lost outcome. Keep the numbers; drop takeoff images drawn on the architect's sheets.
• RFIs your team wrote. The question and its context are yours. The architect's answer and any sketch are the architect's, so buyers typically take the question plus a short factual note of the outcome.
• Change orders and change events. Your pricing, cause and schedule impact are your work. Because they quote the prime contract and name the owner and subs, they are reviewed rather than shipped as is.
• Daily logs, schedules and job cost. Weather, manpower, delays, baselines and updates, budgets, commitments and actuals. These are the contractor's own records, subject to the software terms covered in our guide to Procore, Sage and Vista data export.
• Pay applications. The schedule of values, billed to date and retainage are your numbers. In our view the AIA form layout itself is AIA's, so buyers take the figures, not images of the forms.
• Safety, quality and punch records. Inspections, JHAs, toolbox talks, punch lists and warranty calls, with worker and occupant names removed.

Owner contracts, confidentiality and platform accounts

Your prime contracts are the next filter. Many owner contracts include confidentiality clauses that cover project information, pricing or the owner's identity, and some owners add clauses about data and publicity. Even the standard A201 requires the contractor to keep information the owner furnishes about its financing and designates as confidential, confidential (§2.2.4) (source: AIA A201-2017 with AIA's additions and deletions report (University of Wisconsin System copy)). Read the confidentiality and publicity sections of your largest contracts before you scope a license; that is usually where a project moves from “in” to “review.”

Then check whose platform account each project lives on. Procore's agreement says customer data is “owned exclusively by Customer” (§5.1) (source: Procore Subscription Services Agreement v.2025.01.24), and the customer is whoever holds the subscription. If an owner or developer bought the account and invited you, that owner is the customer for that project's data, and your export rights come from your contract with the owner. Projects on your own account are the cleaner starting point.

Subcontracts, purchase orders and sub quotes

Your subcontract and purchase order templates are your own drafting, and the patterns in them (scope language, exclusions, risk allocation) are what buyers find useful. Signed subcontracts also carry the sub's pricing and sometimes confidentiality terms, so they are reviewed and de-identified.

Bid-day quotes from subs and suppliers are the most sensitive third-party pricing a GC holds. Bid instructions and quote terms sometimes impose confidentiality, and even when they don't, the pricing was given to you for a specific bid. Buyers typically exclude raw sub quotes or take only aggregates by trade and region that cannot be traced to a sub.

Federal, defense and secure projects

Some project records carry handling rules that override any ownership question. Controlled unclassified information is information a law, regulation or government-wide policy requires or permits an agency to safeguard or limit (source: 32 CFR 2002.4, controlled unclassified information (Cornell LII)). Airport and transit security projects can involve sensitive security information (source: 49 CFR 1520.5, sensitive security information (Cornell LII)), and utility work can involve critical energy infrastructure information (source: 18 CFR 388.113, critical energy infrastructure information (Cornell LII)). Records from those projects usually stay out entirely, and at least one buyer program does not accept defense and export-controlled work at all (source: program terms, Regulr buyer directory). Commercial work at the same company can still qualify.

How buyers handle records with mixed authorship

Most construction records are not cleanly one party's. An RFI log has your question, the architect's answer and a sub's follow-up. A change order quotes the prime contract, prices a sub's work and carries your markup. Buyers and their de-identification teams typically handle that mix in a few consistent ways:

• Keep your text, summarize theirs. Your question, your pricing and your reasoning stay in. Another party's answer becomes a short factual note of the outcome, such as approved, revised or rejected, rather than its full text.
• Strip identity marks. Professional stamps, signatures, license numbers, title blocks and logos come off, along with names, phone numbers and email addresses of everyone outside your company.
• Replace names with tokens. The owner, the architect and each sub get a consistent placeholder, so a job still reads end to end without naming anyone.
• Drop attachments by default. Drawing sheets, spec sections, cut sheets and shop drawing PDFs attached to RFIs and submittals are left out unless you confirm the company authored them.
• Leave out what cannot be cleaned. A record that only makes sense with the designer's drawing attached, or that names a client the contract keeps confidential, is excluded rather than forced in.

You review a sample of the cleaned records before anything leaves your systems, and the exclusions are named in the contract. Getting this sorting right early is also what makes a buyer's warranty questions easy to answer.

Summary: who usually owns each construction document

If you are preparing a sale, a buyer of your company will ask the same authorship questions in diligence; our guide to selling a construction company covers how a license fits that process. To see what your company-authored records could be worth, try the data value checker or see which of your construction records could qualify.

Frequently asked questions

Sources

AIA A201-2017 text, the AIA Contract Documents article, 17 U.S.C., the CFR sections, and Procore and Bluebeam terms read on October 18, 2026. Program terms checked against each program's pages on October 15, 2026; our buyer directory lists them.

1. AIA A201-2017 with AIA's additions and deletions report (University of Wisconsin System copy)
2. AIA Contract Documents, The Rights of an Architect's Instruments of Service
3. 17 U.S.C. § 101, definition of architectural work (Cornell LII)
4. 17 U.S.C. § 102(a)(8), architectural works (Cornell LII)
5. 17 U.S.C. § 120, scope of architectural works (Cornell LII)
6. Procore Subscription Services Agreement v.2025.01.24
7. Procore Technologies, Form 10-K for 2025
8. Bluebeam General Terms and Conditions (Mar 7, 2026)
9. 32 CFR 2002.4, controlled unclassified information (Cornell LII)
10. 49 CFR 1520.5, sensitive security information (Cornell LII)
11. 18 CFR 388.113, critical energy infrastructure information (Cornell LII)
12. program terms, Regulr buyer directory