# RFI-to-change-order referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/rfi-to-change-order-decisions-referral-brief-template
Last updated: 2026-11-04

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.

This template is part of [change order data in construction](/data-types/change-order-data-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](/questions/who-can-license-rfi-to-change-order-decisions-records) 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.

| Field | What to write | Usually supplied by |
|---|---|---|
| Company | Trade (general, mechanical, civil), headcount at peak, country | Working contact |
| Business task | One line: which decision the records show | Partner, confirmed by contact |
| Record classes | Which of RFIs, drawing versions, notices, change-coded cost, change orders exist | Project controls director |
| Systems | Project platform, document control, job cost or ERP, by name | Platform administrator |
| Years of history | First year each system holds, and any migration in between | Platform administrator |
| Volumes | Projects per year and RFIs that led to a change, as ranges | Project controls director |
| Joins | Whether the RFI number reaches notices, cost codes and change orders | Project controls director |
| Access event | Any documented date access changes: license end, handover, retention end | Contracts manager or IT |
| Rights flags | Owner contract terms, design documents, federal work, open claims | Counsel, noted not judged |
| Open question | What the company itself does not know about its records | Working contact |
| Working contact | Name and role | Partner |
| Authorized decider | Name and role of the person who can authorize a licensing discussion | Working 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.

| Field | Illustrative entry |
|---|---|
| Company | Mechanical contractor, about 260 full-time employees at peak, United States |
| Business task | Recovering cost when an RFI answer changes scope without a change request |
| Record classes | RFIs with official responses, drawing versions and transmittals, notice letters, change-coded cost, change orders including rejected ones |
| Systems | Autodesk Build since 2021, Procore before that; owner-run Aconex on larger jobs; job cost in the company ERP since 2016 |
| Years of history | ERP cost from 2016; RFIs from 2018 across two platforms |
| Volumes | Roughly 30 to 45 projects a year; the contact estimates a few hundred RFIs a year led to a notice |
| Joins | RFI number typed into notices and cost code descriptions since 2020; patchy before |
| Access event | Procore license ends at the end of next quarter, per the contracts manager |
| Rights flags | Several federal projects under the Changes clause; design documents authored by owners' design teams |
| Open question | Whether notices from 2018 to 2020 can be matched to the RFIs that caused them |
| Working contact | Project controls director |
| Authorized decider | CEO, 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](/guides/preserve-rfi-to-change-order-decisions-records) helps you fill that field. Construction technology advisors will find more on spotting these companies on the [construction technology consultant page](/for/construction-technology-consultant-referral). The [engineering change order page](/data-types/engineering-change-order-process) shows the manufacturing equivalent, and other sectors are in the [industries hub](/industries). Company questions about the wider picture are answered in [construction data monetization](/questions/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](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms), then submit the introduction.

## Sources

- https://help.autodesk.com/cloudhelp/ENU/Build-Rfis/files/work-rfis/Export_RFIs.html
- 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
