RFI-to-change-order referral brief template: fill-in fields plus a completed Illustrative example

Short answer

A company introduction about RFI-to-change-order decisions needs eight core facts, and none of them are records. You need the company's size and location, the systems in use, the years of history, rough record volumes, any documented access event, the open question about the records, a working contact and the executive who can authorize a discussion. The template below lists those fields, plus four supporting ones, with who usually supplies each. A completed Illustrative brief follows.

Visual briefFull-size diagram
A blank referral brief form with eight fields, company size, systems, years of history, record volumes, access event, open question, working contact and authorized decider, fills in one field at a time with Illustrative values.
Illustrative values for a fictional contractor. Every field is metadata; no record leaves the company.

This template is part of change order data in construction. It turns what you learned into a handoff the project controls director can forward as is.

How to use the template

Fill it in after one conversation with the working contact, usually the project controls director. Every field should be answerable from memory or a quick internal check; nothing requires opening a file.

  1. Ask, do not collect. Write the company's answers in its own words. Never request an export to "check" a number.
  2. Use ranges. "Roughly 40 to 60 projects a year" is the right precision.
  3. Mark unknowns. "Not yet known" is a valid entry and tells SourceX what to ask.
  4. Name two people. The working contact and the person who can say yes. The who-can-license decision tree helps you find the second.
  5. Send it with the introduction, after you have signed the Channel Partner Agreement.

The blank template

Copy the left two columns; the third tells you who normally knows the answer.

FieldWhat to writeUsually supplied by
CompanyTrade (general, mechanical, civil), headcount at peak, countryWorking contact
Business taskOne line: which decision the records showPartner, confirmed by contact
Record classesWhich of RFIs, drawing versions, notices, change-coded cost, change orders existProject controls director
SystemsProject platform, document control, job cost or ERP, by namePlatform administrator
Years of historyFirst year each system holds, and any migration in betweenPlatform administrator
VolumesProjects per year and RFIs that led to a change, as rangesProject controls director
JoinsWhether the RFI number reaches notices, cost codes and change ordersProject controls director
Access eventAny documented date access changes: license end, handover, retention endContracts manager or IT
Rights flagsOwner contract terms, design documents, federal work, open claimsCounsel, noted not judged
Open questionWhat the company itself does not know about its recordsWorking contact
Working contactName and rolePartner
Authorized deciderName and role of the person who can authorize a licensing discussionWorking contact

Two system details are worth a line in the "Systems" field when the company uses these tools. Autodesk documents that a single-RFI export from Autodesk Build can include references, photos, the activity log and comments, so ask whether the company's archives were made that way. Oracle Aconex keeps prior versions with a system version number and shows an organization only versions transmitted to it, so ask whether the contractor holds its own document control or only access to the owner's.

A completed brief (Illustrative)

Invented for this page. Every value is fictional.

FieldIllustrative entry
CompanyMechanical contractor, about 260 full-time employees at peak, United States
Business taskRecovering cost when an RFI answer changes scope without a change request
Record classesRFIs with official responses, drawing versions and transmittals, notice letters, change-coded cost, change orders including rejected ones
SystemsAutodesk Build since 2021, Procore before that; owner-run Aconex on larger jobs; job cost in the company ERP since 2016
Years of historyERP cost from 2016; RFIs from 2018 across two platforms
VolumesRoughly 30 to 45 projects a year; the contact estimates a few hundred RFIs a year led to a notice
JoinsRFI number typed into notices and cost code descriptions since 2020; patchy before
Access eventProcore license ends at the end of next quarter, per the contracts manager
Rights flagsSeveral federal projects under the Changes clause; design documents authored by owners' design teams
Open questionWhether notices from 2018 to 2020 can be matched to the RFIs that caused them
Working contactProject controls director
Authorized deciderCEO, with the CFO preparing the case

Notice what this brief does not contain: no project names, no owner names, no dollar amounts from real changes, no drawings and no letters. The federal flag matters because notices on that work follow FAR 52.243-4(b), which treats an interpretation that causes a change as a change order only with written notice, so it is worth asking whether notices on those projects were filed centrally. That is a reason to mention the records, not a judgment on any claim.

What never goes in a brief

  • RFI text, responses, sketches or drawings
  • Notice letters or owner correspondence
  • Cost reports, timecards, proposals or change order amounts
  • Owner, architect, engineer or subcontractor names
  • Screenshots of any system
  • Opinions on whether any change was recoverable or what the records are worth

If the contact offers any of these, thank them and decline. SourceX handles records only after the company applies, agrees terms and a rights review approves them.

Checks before you send it

Confirm the company meets the baseline: 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. If the access event is real and near, say so plainly; if there is none, leave the field as "none documented". The closeout retention timeline helps you fill that field. Construction technology advisors will find more on spotting these companies on the construction technology consultant page. The engineering change order page shows the manufacturing equivalent, and other sectors are in the industries hub. Company questions about the wider picture are answered in construction data monetization.

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.

The reward is paid by SourceX and never deducted from the contractor's payout. When your brief has a named decider and no raw records, register as a partner, check who qualifies and read the program terms, then submit 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 I attach a sample RFI or change order to make the brief stronger?

No. The brief is metadata only. Samples, exports and screenshots stay with the company; SourceX asks for anything it needs after the company applies and a rights review starts.

What if the company cannot estimate volumes?

Write 'not yet estimated'. A blank honestly marked is better than a guess. Rough ranges, such as 'tens of projects a year', are enough.

Who should send the brief, the partner or the company?

Usually the partner submits the introduction, and the working contact forwards the brief internally to the decider. Credit goes to the first valid introduction within the 90-day window, recorded when the company submits a verified application.

Sources

  1. help.autodesk.com/cloudhelp/ENU/Build-Rfis/files/work-rfis/Exp…
  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