# RFI-to-change-order system map and linking keys | SourceX

Canonical: https://refer.sourcex.si/guides/rfi-to-change-order-decisions-records-across-systems
Last updated: 2026-11-04

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.

This map is part of [change order data in construction](/data-types/change-order-data-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.

| System | Record it holds | Linking key it carries | Usual owner |
|---|---|---|---|
| Project platform (Autodesk Build or similar) | RFI, official response, activity log, attached references | RFI number (native) and the referenced sheet | Project engineer, platform administrator |
| Document control (Aconex or similar) | Drawing versions, transmittals, mail | System version number; revision typed as free text | Document controller |
| Correspondence (Aconex mail or email archive) | Written notice that the answer is regarded as a change | RFI number and sheet cited in the letter body or subject | Project manager |
| Job cost or ERP | Cost code opened for the extra work, labor and material postings | Cost code, sometimes with the RFI number in its description | Project controls, accounting |
| Change order log | Change order request, priced proposal, executed change order | Change order number, usually citing the RFI or notice | Contracts 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](/questions/who-can-license-rfi-to-change-order-decisions-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.

| Step | System | Record | Key value that carries the join |
|---|---|---|---|
| 1 | Project platform | RFI 117, official response with sketch | RFI 117 |
| 2 | Document control | Sheet A-411, system version 6 (revision field reads "D") | A-411 v6, transmittal cites RFI 117 |
| 3 | Correspondence | Notice letter regarding the response as a change | Cites RFI 117 and A-411 v6 |
| 4 | Job cost | Cost code 09-117 opened for shaft framing and board | Code description reads "RFI 117 shaft" |
| 5 | Change order log | Request, priced proposal of $41,800, executed change order of $38,900 | Change 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](/guides/rfi-to-change-order-decisions-exception-examples).

## 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](/systems/bim-360-to-acc-migration-data) and [Procore project data exports](/systems/procore-export-project-data) 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](/data-types/construction-rfi-log) 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](/register), confirm the basics on [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its decision-maker.

## 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
