Who can say yes to licensing RFI-to-change-order records? A decision tree for partners

Short answer

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.

Visual briefFull-size diagram
A top-down approval tree that starts at the records, passes the document controller as someone who can describe but not approve, reaches the project controls director as working contact, and lights the path to the CEO, with counsel and SourceX's rights review as side branches.
Who describes, who sponsors, who decides. The CEO decides; the shape of the path rarely changes.

This page is part of change order data in 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".

RoleWhat they hold or knowCan they authorize a licensing discussion?
Document controllerDrawing versions, transmittals, document control mailNo; they can describe coverage and gaps
Platform administratorRFI module, user seats, export settingsNo; system access is not authority
Project engineerRFI questions and official responses on their projectsNo; project-level knowledge only
Project managerNotice letters, owner correspondenceNo; may hold key records in a personal mailbox
Project controls directorCost codes, change order log, how the pieces connectSponsor and working contact, not the decider
CEO (often the owner)Company policy, contracts, appetite for a data agreementYes; 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 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 situationWhose rights may attachWho weighs it
Owner contract with confidentiality or ownership clausesProject ownerContractor's counsel
Drawings, sketches and specifications from the design teamArchitect or engineerContractor's counsel, then SourceX review
Federal or security-sensitive projectsContracting agencyContractor's counsel and contracts manager
Subcontractor pricing inside change proposalsSubcontractorContractor's counsel
Open claims, disputes or litigation holdsParties to the disputeCounsel 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 explains how these checks shape what is licensable, and the architecture firm page 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 gives you the fields to send with it, and 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, check the company against who qualifies and read the program terms before making the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the project controls director approve the discussion on their own?

No. They know where the records are and can sponsor the conversation, but a decision to discuss licensing company records sits with the CEO, who in a family-held firm is often the owner.

What if the owner of the project insists the records are theirs?

That is exactly the kind of question SourceX's rights review exists for. Note it in the introduction and leave the answer to the company's counsel and the review; a partner never argues ownership.

Does a partner need the architect's or engineer's permission?

No. A partner introduces the contractor only. Whether design documents can be part of any license is decided later, with the contractor's counsel and SourceX, and they are often left out.

Sources

  1. copyright.gov/circs/circ41.pdf
  2. help.aconex.com/documents/how-do-version-control-and-the-aco…
  3. acquisition.gov/far/52.243-4
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment