Who owns your construction job cost data?

This guide is general information, not legal, tax or accounting advice. Laws, contract terms and exceptions vary by state, by claim and by contract, so confirm how any of this applies to you with an attorney or CPA licensed where you work.

An MEP subcontractor generally owns the job cost data, estimates, change order pricing and correspondence it creates to run its own jobs. Three things limit that ownership. The architect's drawings and specs belong to the design team, the prime contract can make owner information confidential, and your software agreement decides how much history you can pull out. As McNees Wallace & Nurick wrote in May 2026, "Job cost data is a critical business asset that supports forecasting, claims, and disputes."

Who owns the job cost data, estimates and project records a subcontractor creates?

The subcontractor that creates job cost data, estimates and its own project correspondence generally owns them as its business records. The standard ownership clauses in AIA A201-2017 Section 1.5 and ConsensusDocs 200 Section 2.3 deal with the design team's documents. Neither one claims a subcontractor's cost ledger or estimating files. Your specific contracts can still change that, so ownership turns on what you signed.

Records an MEP sub creates on its own account usually include:

• Estimates and bid files, including jobs you didn't win
• Job cost by cost code, labor hours and labor units
• Change order requests and the pricing backup behind them
• RFIs your team wrote and the project email it sent and received
• Shop drawings and submittals your team prepared

Ownership gets mixed when a record contains someone else's material. A submittal package can reproduce the architect's design. A project email thread can carry the owner's budget or the GC's schedule.

Owners also rewrite the standard forms. Vanderbilt University's standard A201-2017 general conditions (March 2026) say any building information model content generated by the contractor or its subs "shall be Instruments of Service," which that version makes the property of the owner, architect or their consultants. A clause like that reaches material your own detailers produced. Treat the standard forms as the starting point and read the version you actually signed, including the supplementary conditions.

What do the AIA contract documents say about ownership of project documents?

AIA A201-2017 Section 1.5.1 makes the architect and the architect's consultants the authors and owners of their Instruments of Service, including the drawings and specifications. Section 1.5.2 lets the contractor, subcontractors, sub-subcontractors and suppliers use and copy those documents solely for execution of the Work. Neither section addresses the contractor's own estimates, cost records or correspondence.

Section 1.1.7 defines Instruments of Service as representations of the creative work performed by the architect and its consultants under their professional services agreements. That definition covers design work. It doesn't describe a subcontractor's job cost ledger.

Section 1.5.1 also says the contractor and its subs "shall not own or claim a copyright" in the Instruments of Service.

Section 1.5.2 bars using the Instruments of Service on other projects without the written consent of the owner, the architect and the architect's consultants.

Section 3.12.4 says shop drawings, product data, samples and similar submittals aren't Contract Documents.

AIA A401-2017, the standard contractor-subcontractor agreement, adopts A201-2017 by reference. AIA's own summary says the contractor's duties under the prime contract pass to the subcontractor for its portion of the work. That's how Section 1.5 reaches an MEP sub that never signed the A201.

A401-2017 Section 14.7 also requires the parties to set protocols for sending Instruments of Service and other data in digital form.

What does ConsensusDocs say about ownership and use of project documents?

ConsensusDocs 200 Section 2.3.1 requires the owner to get from the design professional either a license for the constructor and subcontractors to use the design documents or ownership of the copyrights in them. The owner also indemnifies the constructor against infringement claims from using those documents on the project. Like the AIA forms, the ownership language addresses design documents.

The ConsensusDocs 200 Guidebook notes that when the owner owns the final construction documents, Section 2.3.1 should be rewritten so the owner grants the license. Either way, the subject is the designer's work.

ConsensusDocs 750, the standard constructor-subcontractor agreement, flows the prime contract down. Section 3.1 says the subcontractor assumes toward the constructor the same obligations the constructor assumes toward the owner and design professional, to the extent the prime agreement applies to the subcontract work.

ConsensusDocs 750 Section 2.4.1 calls for a written protocol before parties exchange documents and data electronically. The protocol covers privacy and security requirements along with storage and retrieval.

What do GC subcontract confidentiality clauses usually restrict?

In the standard forms, subcontract confidentiality starts with the owner's information and flows down to you. In the October 2018 revision, ConsensusDocs 750 Section 3.28 says that if the prime agreement protects the owner's proprietary or confidential information, the subcontractor "is equally bound." The clause in your subcontract can be one sentence long and still carry every confidentiality term in a prime contract you've never read.

AIA A201-2017 Section 2.2.4 covers information about the owner's financial arrangements that the owner designates confidential. The contractor may share it with subcontractors who need it for the project and agree to keep it confidential.

Owner-written terms can go much further. Louisiana's construction-manager-at-risk general conditions, built on A201, bar disclosure of "any information in connection with the Work or the Project" without the owner's written consent. The exceptions cover public information, legal requirements and what's needed to perform the Work.

The same Louisiana clause requires the contractor to bind subcontractors at every tier to those terms, and it survives completion of the Work.

That language is broad enough to reach records you created yourself, such as your cost reports on that job. Whether it does is a question for your attorney, job by job.

Does copyright protect your job cost data?

Copyright doesn't protect raw facts like labor hours, quantities and unit costs. In Feist Publications v. Rural Telephone Service (1991), the U.S. Supreme Court held that "there can be no valid copyright in facts." A compilation gets protection only for its original selection and arrangement, and the facts inside it "may be copied at will." Trade secret law and contracts do most of the protecting.

McNees Wallace & Nurick apply Feist to construction directly. Raw job cost entries generally aren't protected, and the vendor often owns the report formats and dashboards it designed.

Trade secret law can cover job cost data. The federal Defend Trade Secrets Act definition in 18 U.S.C. 1839(3) includes financial, business and engineering information. It applies when the owner has taken reasonable measures to keep the information secret and the information has value from not being generally known.

Your unit costs, labor productivity and bid history can meet that test. Proving it means showing you protected them, with access controls, confidentiality agreements and limits on who sees what.

McNees calls trade secret claims fact-intensive and expensive to pursue.

That leaves contracts. In McNees's words, "Contract language provides the strongest protection, particularly in SaaS agreements."

What do Procore, Trimble Viewpoint, Autodesk and ServiceTitan say about customer data?

All four vendors' published terms say the customer owns its data. They differ on what the vendor may do with it and how long you get to retrieve it after the subscription ends. The published windows run from no guaranteed access to 60 days. Your signed order form and agreement control, and they may differ from the terms posted online.

McNees describes a contractor that switched platforms after 5 years and was told only limited raw entries could be exported, with compiled reports available for an additional fee. Months later it needed 2-year-old records for a subcontractor dispute and couldn't get them from the old system. The records you'll need for that kind of dispute are covered in how long a contractor should keep project records.

What should you look for in your contracts and software agreements?

Start with the prime contract on each job, because subcontracts flow it down. Then read your subcontract, then every software agreement that holds project data. The goal is a list of which records you can share freely, which need someone's consent, and which have to stay inside the company.

1. Section 1.5 changes. Check whether the owner rewrote A201 Section 1.5 to claim BIM, as-builts or other material your team creates.
2. Confidentiality scope. Check whether the clause covers only the owner's information or "any information" about the project.
3. Flow-down language. A401 and ConsensusDocs 750 Section 3.1 pull in prime contract terms. Get a copy of the prime contract.
4. Survival. Check whether confidentiality ends at completion or survives it.
5. Return-of-documents clauses. Some owners require you to return or destroy owner and designer documents on request.
6. Software ownership clause. Confirm the agreement says you own your data.
7. Vendor use rights. Look for language on anonymized, aggregated or usage data and on AI model training.
8. Exit terms. Note the retrieval window, the export format and any fees for exports or compiled reports.
9. Parent or franchise ownership. Confirm no franchisor or parent company holds title to the data.

Before any subscription renewal, export your full history while you still have access. Statutes of repose can keep a job open to claims for a decade or more, as the construction statute of repose by state shows.

How does data ownership apply to licensing your project records?

You can license only the records you have the right to share. Your own estimates, job cost, change order pricing and correspondence are usually yours to license. Owner-provided documents, the architect's drawings and information a prime contract makes confidential may need consent or have to be left out. Conduit checks your contracts and software agreements before anything goes to market.

A data license covers a copy of the records. You keep the originals, and your retention schedule doesn't change.

Conduit Data brokers the license between the contractor and the AI company. Conduit doesn't buy or hold the data.

The buyer handles de-identification under the terms of the license.

Jobs with broad confidentiality clauses, like the Louisiana example above, get flagged for your attorney before any of their records are included. Records tied to an open claim or litigation hold stay out until counsel clears them.

Your software agreements matter too. If a vendor's export window has closed, the records left in that system may be out of reach for licensing as well.

Frequently asked questions