Construction technology advisors: the data introduction hidden in project closeout

Short answer

Only the ones whose records still point to each other. On most projects, an RFI raises a design question, a change event or potential change order prices it, and a signed change order fixes the cost and time outcome. Under AIA's G716, an RFI by itself authorizes no change in cost or time, so the commercial outcome lives in the change order. At project closeout, construction technology advisors can ask the contractor's owner this metadata-level question and, if the company appears eligible and wants to proceed, introduce its decision-maker to SourceX.

Visual briefFull-size diagram
A continuity ledger of five illustrative design changes, each traced across RFI, change event, change order and final outcome, with three linked chains in green (one owner-directed, with no RFI) and two broken chains in orange whose commercial outcome is not traceable.
Illustrative ledger. A design change keeps its commercial outcome only when the RFI, the change event and the signed change order still point to each other.

Which approved design changes retain their commercial outcome?

Ask the owner exactly that, then ask what share of design changes they could trace from the RFI to the signed change order and the final cost. "Most of them" on dozens of closed projects is a strong answer.

RFI-to-change-order continuity is easy to overlook because each log is maintained by a different person for a different reason. The RFI log belongs to project engineers who need an answer from the design team. The change order log belongs to project managers and accounting, who need the contract sum and schedule updated. AIA's G716 instructions say an RFI does not authorize changes in cost or project time, and its G701 instructions say an executed change order records agreement on the change in contract sum and contract time. So the answer and the money sit in separate documents by design, and the only thing joining them is a reference someone chose to record.

Some tools make that reference easier to keep. Procore's documentation describes creating a change event directly from an RFI, provided both tools are on the project. Where teams work that way, the link may already exist; where they price changes in spreadsheets or email, it often does not. What a Procore export can carry out of the system is covered in exporting Procore project data. The general value of these logs is covered on change order data and RFI logs. This page is about whether they still connect at closeout.

The continuity ledger

Illustrative. A 300-person general contractor closing out a mid-rise medical office project.

Design changeRFI recordedChange event or PCOExecuted change orderCommercial outcome retained
Revised footing depth after soils reportYes, with design responseYes, created from the RFIYes, sum and days adjustedYes
Relocated mechanical shaftYesYesYes, no time change recordedYes
Substituted curtain wall anchorYesPriced by email onlyYes, bundled with other itemsPartly: cost not traceable to this RFI
Added fire-rated corridor doorYesYesNot executed; resolved in closeout negotiationNo: outcome sits in a settlement memo
Owner-requested finish upgradeNo RFI; owner directiveYesYesYes, but no design question to pair it with

Rows three and four show the two typical breaks: a change order that bundles several causes, and a change resolved outside the change order process at closeout.

Four metadata questions after the opener

  1. How many closed projects, over how many years, used the same RFI and change order practice? One well-linked project is an anecdote; forty over eight years is a record set worth describing.
  2. Do change events or change orders reference the RFI number that started them? A reference field, even if filled in by habit rather than rule, is what makes the ledger above possible.
  3. Where are disputed or bundled changes resolved, and is that resolution written down? Closeout settlements often sit in memos or email, outside the change order log.
  4. Who keeps project records after closeout, and in which system? Many contractors archive a project once the warranty period starts, and some lose access when a project-level license ends.

Why closeout is the moment: while a project is live, every log is being edited and nobody has time to talk about history. After archive, the people who knew which RFI caused which change have moved to the next job. Closeout is the short window when the project team still remembers the links and the records are complete.

Does the contractor qualify, and what stays unknown?

Count employees carefully: full-time field crews on the contractor's own payroll count; subcontractors and other contractors do not.

  • 50+ full-time employees at peak, contractors excluded.
  • A documented operating history and rights to license the records, subject to owner and design-team terms on each project.
  • An authorized contact who can open a licensing discussion.
  • 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.
Known at introductionUnknown until SourceX reviews it
Number of closed projects and years, as the owner describes themSourceX's current data needs for design-change records
How consistently RFIs link to change ordersThe rights review result, project by project
Where records go after closeoutAny offer to the contractor
That the reward was disclosedWhether a reward becomes payable

Partners stay at metadata level. For the broader partnership, see construction technology consultant referrals and technology advisor referral programs; for manufacturing's equivalent record, see the engineering change order process; and for the owner's side of the question, see construction data monetization. The partner hub and network opportunity finder list other moments.

Reward disclosure and owner permission

Sign the Channel Partner Agreement before submitting. The first valid introduction within the 90-day window is credited when the company submits a verified application; one partner per company. Tell the owner you may receive a referral reward that SourceX pays separately, so it never reduces the contractor's payout. The default reward is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap. Illustrative arithmetic only: if the contractor were paid $250,000 for a qualifying completed handoff, the reward would be $62,500. 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.](/rewards) for payment statuses. A short introduction then names the closeout date, the project count and years the owner described, and the fact that SourceX licenses approved operating records directly from companies.

Go deeper on project closeout

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.

If the owner can trace most design changes to their commercial outcome and wants to talk before records are archived, register as a partner, check the contractor against who qualifies, and read the program terms before you make 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

Who owns RFI and change order records on a finished project?

It depends on the prime contract and on who created each record. A contractor usually controls its own logs, while owner and design-team documents may carry confidentiality terms. SourceX's rights review settles it; the partner only notes which contracts exist.

Does the company have to use Procore for this to work?

No. Any system, or a disciplined spreadsheet, can hold the chain. Procore is mentioned because its documentation describes creating a change event directly from an RFI, which tends to keep the link intact.

Is one large project enough?

Usually the value is in many projects recorded the same way over several years. Ask how many closed projects follow the same RFI and change order practice.

Sources

  1. help.aiacontracts.com/hc/en-us/articles/1500009325281-Instructions…
  2. help.aiacontracts.com/hc/en-us/articles/1500009322061-Instructions…
  3. support.procore.com/products/online/user-guide/project-level/rfi…
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

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