Construction software companies: what project data you can and cannot license

Which project data can a construction software company license?#

A construction software company can usually license the records it created while building and supporting its product: support tickets, implementation and onboarding notes, product engineering history in Jira and GitHub, release notes and the workflow templates its own team wrote. The project records its customers create inside the platform are a different matter.

Contractors use your software to run RFIs, submittals, change orders, daily logs, punch lists and pay applications. Your customer agreement almost certainly treats those as customer data that you host and process to deliver the service. Storing them on your servers does not give you the right to license them to an AI developer.

The practical result is two tracks. Your own operational records can move toward a license once rights review and privacy preparation are done. Contractor project records stay out unless customers agree, project by project, under terms written for that purpose.

Who controls each record family on a construction platform?#

Control of each record family on a construction platform depends on who created the record and which contract governs it, not on where it is stored. The table shows the default position for a typical platform; your own customer agreement and DPA decide the final answer.

Notice that the out-of-scope rows are exactly the records most people picture when they hear construction data. That is normal. Vendor-side records show how construction teams use software, where workflows break and how your engineers fixed them, which is a different and still useful view of the industry.

Why are RFIs and submittals so hard to clear?#

RFIs and submittals are hard to clear because several parties hold rights in each one, and your customer is only one of them. An RFI response may quote the architect's drawings, a submittal may include a manufacturer's product data, and both sit inside a prime contract with confidentiality terms the project owner negotiated.

Standard AIA contract forms show how tightly design rights are held. Under AIA B101-2017 Section 7.2, the architect and its consultants are deemed the authors and owners of their Instruments of Service and reserve their rights, including copyrights. AIA A201-2017 Section 1.5.2 lets the contractor, subcontractors and suppliers use and reproduce those documents only to perform the Work, and bars use on other projects or outside the scope of the Work without the specific written consent of the owner, the architect and the architect's consultants.

A general contractor agreeing to an AI license cannot waive rights it never held, and projects on other contract forms often carry similar terms. Owners of private projects, such as data centers or corporate campuses, may add confidentiality and security requirements that flow down to every party.

Personal details add another layer. Daily logs name workers and foremen, safety reports describe injuries, and site photos show faces and license plates. Even with a willing customer, those records need heavy preparation before anyone should consider them.

What do your own records show about construction work?#

Your own records show how construction teams use software under real pressure: which submittal workflows confuse project engineers, why mobile sync fails on a jobsite with poor coverage, and how your team diagnosed and fixed each problem. AI developers building agents for project management and software support value that linked history of request, diagnosis and resolution.

The strongest packages connect records across systems. A Zendesk ticket from a superintendent links to a Jira issue, the Jira issue links to a GitHub pull request, and the pull request ships in a release note. That chain shows a problem moving from the field to a fix, which isolated tickets cannot show.

Vendor records still contain customer material. Ticket bodies quote RFI numbers and project names, screenshots show drawing sheets, and implementation notes describe a customer's approval matrix. Each field needs a handling rule before anything leaves your systems.

When can contractor project data come into scope?#

Contractor project data can come into scope only through a customer opt-in program with its own agreement, separate from your subscription terms. Updating your terms of service to claim the right after the fact invites disputes and regulatory attention, and it does nothing to clear the rights held by design teams and owners.

Many vendors decide an opt-in program is worth running later, once a license of vendor records has shown how the process works. Starting with your own records keeps the first transaction simple and gives customers a concrete example of how their details are handled.

• 1Write a standalone data contribution agreement that names the record types, permitted AI uses and term.
• 2Let each customer choose projects rather than opting in a whole account, so it can leave out confidential owners.
• 3Ask the customer to confirm that its prime contracts and design agreements allow the use, or to exclude projects where they do not.
• 4Remove worker names, contact details, photos of people and site security details before delivery.
• 5Decide how participating customers are compensated or credited, and put it in writing.
• 6Keep a record of each opt-in, its scope and any later withdrawal.

Illustrative: a submittal software vendor sorts its records#

Illustrative: a fictional vendor sells submittal and RFI management software to mechanical and electrical subcontractors. It has eleven years of history in Zendesk, Jira, GitHub, Salesforce and Confluence, its platform database holds customers' project records, and a sync feature pulls RFI logs from a larger project management platform through that platform's API.

The CEO and CTO sort the archive with counsel. Platform project records are marked out of scope, and so is everything that arrived through the sync, because the partner platform's terms govern that data. Support tickets, Jira issues, pull requests and release notes are marked as candidates, with screenshots and attachments excluded and customer and project names replaced. Confluence implementation playbooks stay, but customer-specific onboarding pages are dropped.

The outcome is a scoped package of linked support and engineering records that needs no customer consent, plus a parked idea for an opt-in program with a few long-standing customers. Nothing from a contractor's project file or a partner integration is included.

Which mistakes put a construction software license at risk?#

The mistakes that put a construction software license at risk usually come from treating storage as ownership. Most of them surface when a sample is pulled from the production database or a support export without a field-by-field review.

Integration data deserves its own check. ENR reported in November 2025 that Procore's terms now say marketplace partners cannot bulk-download data from its platform for commercial purposes, including training large language models. If your product reads or syncs records through another platform's API, assume those records are out of scope until counsel has read the platform's current terms.

Each of these mistakes is easier to catch at the inventory stage than to unwind after a buyer has reviewed samples, so build the checks into the first record map.

• 1Reading an aggregated-data clause as permission to share raw RFIs, daily logs or photos.
• 2Leaving attachments in support tickets, where drawing sheets and site photos hide.
• 3Including records synced from another construction platform's API or marketplace integration.
• 4Forgetting acquired product lines, whose older customer contracts may say something different.
• 5Mixing shared Slack channels or email threads with customers into internal discussion records.
• 6Announcing a terms change to customers before deciding what you actually want to license.

How SourceX approaches construction software records#

SourceX approaches construction software records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check uses metadata only, such as system names, years of history and record families, so no tickets or project files are shared at the start.

Rights review separates vendor-owned records from customer project data before any scope is proposed, and the supplier approves every step. Each package that proceeds carries a SourceX Evidence Packet recording provenance, licensing rights, permitted use, the privacy record and release authorization. The records are licensed, not sold, and your company keeps ownership.