RFI-to-change-order system map: where each record lives and the keys that join one case

Short answer

To reconstruct an RFI-to-change-order decision across systems, you need two keys carried from record to record: the RFI number and the drawing's system version. They have to reach the notice letter, the cost code for the extra work and the executed change order. Each of five systems holds one piece under its own label, so the map below shows where each record sits, which key reaches it, who owns it, and what one fully joined case looks like.

Visual briefFull-size diagram
Five system nodes, the project platform, document control, correspondence, job cost and the change order log, surround one joined case, with RFI 117, sheet A-411 version 6, cost code 09-117 and change order 14 travelling along the connectors to it.
Illustrative system map. Each system keeps one piece of the case under its own label; the keys are what join them.

This map is part of change order data in construction. That page explains why the notice letter matters. This one covers where the records sit and how they connect.

Five systems, one case: system, record, linking key and owner

A typical mid-size contractor spreads one scope decision across five places. Read across a row to see what a system contributes and which key reaches it.

SystemRecord it holdsLinking key it carriesUsual owner
Project platform (Autodesk Build or similar)RFI, official response, activity log, attached referencesRFI number (native) and the referenced sheetProject engineer, platform administrator
Document control (Aconex or similar)Drawing versions, transmittals, mailSystem version number; revision typed as free textDocument controller
Correspondence (Aconex mail or email archive)Written notice that the answer is regarded as a changeRFI number and sheet cited in the letter body or subjectProject manager
Job cost or ERPCost code opened for the extra work, labor and material postingsCost code, sometimes with the RFI number in its descriptionProject controls, accounting
Change order logChange order request, priced proposal, executed change orderChange order number, usually citing the RFI or noticeContracts manager, estimator

Two columns matter more than the rest. The key column shows whether a join exists at all. The owner column tells you who can describe it. Neither tells you who can approve a licensing discussion; that is a separate question, covered in who can license these records.

The keys that travel, and where each one slips

Two identifiers do most of the joining work, and a third carries the money. Each has a known weak point.

RFI number. Native and reliable inside the project platform. Outside it, the RFI number survives only if a person types it: into a transmittal subject, a notice letter, a cost code description or a change order request. When the notice says "per the recent clarification" instead of "per RFI 117", the join is a guess.

Drawing system version. Oracle Aconex documents that every supersede creates a new system version kept in the audit trail, while the revision field is free text of up to 15 characters that Aconex does not validate. "4", "Rev 4" and "D" can therefore name the same sheet. The system version is the dependable key. Aconex also shows a contractor's organization only the versions transmitted to it, so the contractor's view of the drawing history may be partial.

Cost code. The one key that carries money. It joins the field work to the proposal only if the extra work was coded separately from base scope, ideally with the RFI number in the code's description. Where the extra hours were booked to base scope, the cost of the decision cannot be isolated later.

A fourth link, the notice itself, is not an identifier but a hinge. On federal fixed-price work, FAR 52.243-4(b) treats an interpretation that causes a change as a change order only when the contractor gives written notice stating the date, circumstances and source and that it regards the order as a change. A notice that cites the RFI number and the sheet version joins the commercial side of the case to the technical side in one document.

Export limits shape the joins too. Autodesk documents that a single RFI exported to PDF can include its references and activity log, but only PDF files are embedded and files over 30 MB are left out, so a marked-up model or a large drawing set may not travel with the RFI.

One fully joined case, record by record (Illustrative)

Invented for this page. A fictional 240-person general contractor is building a private hospital wing. RFI 117 asks how a fire-rated wall meets a new duct shaft; the answer adds a rated shaft enclosure on three floors.

StepSystemRecordKey value that carries the join
1Project platformRFI 117, official response with sketchRFI 117
2Document controlSheet A-411, system version 6 (revision field reads "D")A-411 v6, transmittal cites RFI 117
3CorrespondenceNotice letter regarding the response as a changeCites RFI 117 and A-411 v6
4Job costCost code 09-117 opened for shaft framing and boardCode description reads "RFI 117 shaft"
5Change order logRequest, priced proposal of $41,800, executed change order of $38,900Change order 14 cites the notice and RFI 117

Every record names at least one key held by the record before it, so a reviewer can walk from the question to the signed amount without guessing. Now break one link: if the transmittal for A-411 had cited nothing and the revision field read "Rev 4" on one floor's copy, the drawing could no longer be matched to the answer with confidence. The amounts are fictional and say nothing about what any real change is worth. For the late-notice version of this kind of case, see the exception example.

Reading a client's own map at metadata level

A construction technology advisor can sketch this map for a client in one conversation, without opening a file. Ask the project controls director, and write down only the answers:

  • Which system holds each of the five record types, and since which year? Platform migrations matter; the BIM 360 to Autodesk Construction Cloud page and Procore project data exports cover two common cases.
  • Is the RFI number a required field anywhere outside the platform? If not, joins depend on habit.
  • Is extra work coded separately, and does the code name the RFI?
  • Do notice letters live in document control mail or in personal mailboxes?
  • Roughly how many RFIs per year led to a change order? The company's own estimate, as a range.

Partners never ask for or handle RFIs, drawings, letters or cost reports. What stays unknown until SourceX reviews it: whether owner contracts limit use of the records, whether design documents carry the designer's rights, and whether any buyer wants this shape of data. The company needs 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. The RFI log page covers the RFI record on its own.

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 a contractor you advise can name its keys and the owner of each system on this map, register as a partner, confirm the basics on who qualifies and read the program terms before introducing its decision-maker.

  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

What if the contractor uses Procore or another platform instead of Autodesk Build?

The map keeps the same shape. Every project platform has some native RFI number and some way to attach drawings; what changes is the export format and which references travel with it. Ask the platform administrator what a single-RFI export actually includes.

Does a partner need to test the joins?

No. A partner only records which keys the company says it carries between systems and where it thinks they break. Any testing happens later, inside the company or in SourceX's review, never on records a partner has handled.

Is a map with gaps still worth an introduction?

Usually yes. Most contractors cannot join every case end to end. A clear description of which joins hold and which fail is more useful than a claim that everything connects.

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