# Who can license RFI and change order records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-rfi-to-change-order-decisions-records
Last updated: 2026-11-04

Introduce the CEO, who can authorize a licensing discussion, and bring the project controls director in as the working contact. Document controllers and platform administrators can describe the archive but cannot approve its use. Counsel weighs owner contracts, design copyright and federal handling terms. Whether any record can actually be licensed stays unknown until SourceX's rights review. The decision tree below walks a partner through each branch.

This page is part of [change order data in construction](/data-types/change-order-data-construction) and answers one narrow question: who can say yes.

## Branch 1: who holds the records

Start at the records and ask who touches them. Every role here is useful to talk to, and none of them is the answer to "who can say yes".

| Role | What they hold or know | Can they authorize a licensing discussion? |
|---|---|---|
| Document controller | Drawing versions, transmittals, document control mail | No; they can describe coverage and gaps |
| Platform administrator | RFI module, user seats, export settings | No; system access is not authority |
| Project engineer | RFI questions and official responses on their projects | No; project-level knowledge only |
| Project manager | Notice letters, owner correspondence | No; may hold key records in a personal mailbox |
| Project controls director | Cost codes, change order log, how the pieces connect | Sponsor and working contact, not the decider |
| CEO (often the owner) | Company policy, contracts, appetite for a data agreement | Yes; authorizes and signs |

One detail affects what the contractor holds at all. In Oracle Aconex, an organization sees another organization's document versions only once they are transmitted to it, so a contractor's own archive may not include every version of the owner's or designer's drawings. The document controller is the person who knows how complete it is. The [system map](/guides/rfi-to-change-order-decisions-records-across-systems) shows where each record sits.

## Branch 2: who can authorize the discussion

Follow the tree upward until you reach someone who can commit the company's time and its records to a conversation.

1. **Does the person run a system?** If yes, they describe; move up.
2. **Does the person run the change process across projects?** If yes, this is usually the project controls director. Ask them to sponsor the introduction and bring in the CEO.
3. **Can the person sign agreements that involve company information?** If yes, this is the executive to introduce: the CEO, who in a family-held firm is often the owner.
4. **Is there a parent company or private equity owner?** If yes, note it. The decider may need their consent, and SourceX will ask.

Technical access and authority are different things. An administrator who can export every RFI in a minute still cannot approve what happens to them.

## Branch 3: what needs counsel, owner or designer sign-off

Some records carry other parties' rights. A partner flags these and stops; the company's counsel and SourceX's rights review decide.

| Record or situation | Whose rights may attach | Who weighs it |
|---|---|---|
| Owner contract with confidentiality or ownership clauses | Project owner | Contractor's counsel |
| Drawings, sketches and specifications from the design team | Architect or engineer | Contractor's counsel, then SourceX review |
| Federal or security-sensitive projects | Contracting agency | Contractor's counsel and contracts manager |
| Subcontractor pricing inside change proposals | Subcontractor | Contractor's counsel |
| Open claims, disputes or litigation holds | Parties to the dispute | Counsel only; records on hold are left alone |

Design documents deserve a note. The U.S. Copyright Office explains that architectural works created on or after December 1, 1990 can be protected, and that technical drawings are protected as drawings separately from the building. A contractor may hold thousands of sheets it did not author. That is why the RFI question, the answer, the notice and the cost record, which the contractor did produce, are often the core of what can be discussed. On federal work the Changes clause, FAR 52.243-4, governs the notice and change order exchange with the Contracting Officer, and the contract may add handling terms that counsel should read. [Why data rights matter](/proof/why-data-rights-matter) explains how these checks shape what is licensable, and the [architecture firm page](/industries/refer-architecture-firm-data-licensing) covers the designer's side.

## Where the answer stays unknown until SourceX's rights review

Even with the right executive in the room, four answers are open until SourceX reviews them:

- **Rights.** Whether each record class can be licensed given the contracts behind it.
- **Scope.** Which projects, years and record types are included, and which are excluded.
- **Demand.** Whether any buyer wants this kind of data at the time of review.
- **Terms.** Any offer, payout amount and schedule.

A partner should not predict any of these. Saying "they will want this" or "this is worth a lot" sets expectations no one has checked.

## The baseline the company must meet

Before the tree matters, the company itself must qualify: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. The [referral brief template](/resources/rfi-to-change-order-decisions-referral-brief-template) gives you the fields to send with it, and [construction data monetization](/questions/construction-data-monetization) answers the company's broader questions.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the project controls director has named the executive who can say yes, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://www.copyright.gov/circs/circ41.pdf
- https://help.aconex.com/documents/how-do-version-control-and-the-aconex-audit-trail-work/
- https://www.acquisition.gov/far/52.243-4
- https://refer.sourcex.si/terms
