Every construction project produces records made by several parties: the owner, the general contractor, a dozen subcontractors, the architect and engineers. When an AI training-data buyer asks a contractor about licensing its records, the first question is not price. It is whether those records are the contractor’s to license at all.
This is general information, not legal advice. Your contracts decide, and your own lawyer should read them.
The default position
Without a contract term saying otherwise, the party that creates a record for its own business generally holds the rights to it. In practice that gives a pattern most contractors will recognize:
| Record | Usually belongs to |
|---|---|
| GC estimates, bid files, job cost | The GC |
| Sub estimates, labor tracking, shop drawings | The sub |
| Daily logs | Whoever wrote them, for their own crews |
| Master schedule | Prepared by the GC; the owner often has rights in it |
| Change orders | A contract document both sides signed |
| Drawings and specifications | The design professional |
Design documents are the clear exception for contractors. Standard design agreements commonly keep ownership with the architect or engineer and give the owner a license to use them for the project. A contractor holding copies in its project platform has no right to license them on.
What the owner contract can change
The owner’s agreement with the GC is where the default most often changes. Three kinds of clause matter:
Ownership of project documents
Some owner contracts say that everything “prepared for the project” belongs to the owner. Read literally, that could cover your daily logs and schedules. If your contract says this, leave that project out of any license or ask the owner in writing.
Confidentiality
Many contracts make project information confidential, sometimes with no end date. Whether de-identified records still fall under the clause depends on its wording. That is a question for your lawyer with the clause in front of them, not a judgment to make from a summary.
Records and audit rights
A clause giving the owner the right to inspect your records for a number of years is about access, not ownership. It does not by itself stop you licensing your own records, but read it alongside the confidentiality clause.
The subcontractor’s position
Subcontractors have two extra things to check. First, flow-down: most subcontracts pass the prime contract’s terms down, so an owner’s confidentiality clause can bind the sub even though the sub never signed the owner’s agreement. Second, the platform: if your RFIs and logs were entered in the GC’s Procore project, find out what the GC’s terms say about records made there.
A sub’s own estimates, labor tracking and internal logs kept on its own systems are usually the cleanest records in the whole industry to license.
Records made by two parties
RFIs and change orders are joint. You wrote the question; the architect wrote the answer. You priced the change; the owner signed it. Options for joint records:
- License only your side: the question, the dates, the cost and time impact, without the design response text.
- Include the full record only where the contract and the other party allow it.
- Leave joint records out of a first license and start with records that are clearly yours.
A worked example
A 60-person mechanical subcontractor reviews three past jobs:
| Project | Contract terms found | Decision |
|---|---|---|
| Private office fit-out | No ownership clause; confidentiality ends at completion | Include own records |
| Data center for a private owner | Owner owns all project documents, confidentiality survives | Leave out |
| Public school | Public records rules plus a flow-down confidentiality clause | Leave out pending legal review |
The firm’s estimates, labor tracking and SOPs from the first project go into scope. Everything from the second is excluded. The third waits for counsel.
Before you talk to a buyer
On their own sites, buyers take a position on ownership after a license. In micro1’s wording the seller retains the underlying data. Nyne leaves it to the signed agreement. Labelbox Prism leaves rights with the seller but makes its licenses exclusive by default. (Each of the three runs or may run a referral arrangement that could pay this site after a GC or sub we introduced signs; their positions are reported as written.)
None of that answers the earlier question: whether the records were yours to begin with. Settle that first, project by project, using the clause table in our ownership reference, and the rest of the conversation to sell construction data gets much simpler.
A clean list of projects you can license, and the reason each is on it, is the document your lawyer will thank you for.