# RFI-to-paid-change record chain and join keys | SourceX

Canonical: https://refer.sourcex.si/guides/rfi-to-paid-change-record-linkage
Last updated: 2026-11-04

A company connects RFI-to-paid-change records by carrying one reference, usually the RFI number or a change event number, from the question through the drawing revision to the approved change order and the bill, and by recording where that reference drops out. The project management tool makes the question end explicit and the ERP makes the money end explicit. The drawing in between, commented on and reissued, is the weakest hop, because nothing forces anyone to write the RFI number on it.

This page is part of the [RFI-to-paid-change records guide](/guides/chain-rfi-to-paid-change), which sets out the metadata packet for the same chain. Here the focus is narrower: the identifiers that join each hop, and how to tell a strong join from a weak one.

## The chain in five hops

A change that starts as a field question and ends as a payment crosses five records. Each record has its own identifier, and the chain holds only where one record carries the previous record's identifier. In the stack used below, the PM tool is Procore, drawing review happens in Bluebeam and the ERP is Viewpoint Vista; other stacks have the same five hops under different names.

| Hop | Step | Record | System | Key it carries | Join strength |
|---|---|---|---|---|---|
| 1 | Question raised | RFI | PM tool | RFI number | Native to the tool |
| 2 | Answer given | Response marked official, with its review history | PM tool | Same RFI number | Native to the tool |
| 3 | Drawing changed | Markups, then reissued sheet and revision | Drawing review | Sheet number and revision; RFI number only if typed | Weak, depends on habit |
| 4 | Change approved | Pending, then approved change order | ERP, change module | Change order number; RFI number if typed in the description | Moderate |
| 5 | Change paid | Job Cost entry, pay application line | ERP | Change order number, interface date | Native to the tool |

Hops 1 and 2 hold inside the project management tool, which records whose court a question sat in and lets one of several responses be marked official, so "what was the answer?" has a recorded reply. Hops 4 and 5 hold inside the ERP: an approved change order reaches Job Cost only when Ready For Accounting is checked, and the interface date is recorded. The cross-system joins, from hop 2 to 3 and from hop 3 to 4, are where the chain is made or lost.

## A joined timeline for one sheet (Illustrative)

A fictional 520-person fire protection and plumbing contractor finds that a sprinkler main in a hospital corridor clashes with a medical gas line. Every value is invented to show how references carry, not drawn from a real project.

| Date | System | Record | Reference carried |
|---|---|---|---|
| June 3 | PM tool | RFI 147 raised: sprinkler main and gas line clash in the east corridor | RFI 147 |
| June 7 | PM tool | Engineer's response marked official and returned to the RFI Manager | RFI 147 |
| June 10 | Drawing review | Sheet FP-301 marked up, then reissued as revision C with the main lowered | "RFI 147" typed in the markup comment |
| June 17 | ERP | Pending change order for the relocation, $54,600 | RFI number in the description |
| July 1 | ERP | Approved change order, cleared for accounting and posted to job cost | Change order number |
| July 31 | ERP | Relocation billed on the monthly pay application | Change order number |

Every row joins, but only because people typed "RFI 147" into the next system twice: once in a markup comment and once in a change order description. Neither tool required it.

## Where the reference drops out

Four places where the reference commonly drops out:

1. **The markup has no RFI number.** Bluebeam's Markups List tracks each markup's author, dates, status and comments, and can be saved as CSV or XML. If the comment says "lowered per engineer" without "RFI 147", the drawing joins to the question only by date and sheet.
2. **The revision answers two RFIs.** One reissued sheet can carry changes from several questions. A revision letter alone cannot say which change belongs to which RFI.
3. **The change order description is free text.** If estimators write "east corridor main" instead of the RFI number, hop 4 joins to hop 3 by sheet and date, which is guesswork across hundreds of changes.
4. **The change never reaches the commercial system.** A revision is built without any change order. This is the hardest case: the drawing revision has no matching commercial approval, so there is no record for hop 4 to carry anything. The related page on [what a single-system RFI export loses](/guides/rfi-to-paid-change-missing-context) reads that case in full.

A fifth, quieter break sits inside the ERP. An approved change order still in pending status cannot be interfaced to Job Cost, so for a while it is approved but not yet visible on the cost side. A contractor that tracks those separately has a cleaner hop 5.

## How a weak link gets repaired

The repair is rarely software. It is a habit that puts one identifier in one more place. Four habits do it:

- **RFI number in the markup subject or comment**, required by the design coordination lead before a sheet is reissued.
- **A revision log that lists the RFIs each revision answers**, kept with the drawing set.
- **RFI or change event number as a required field on the pending change order**, not only in the description.
- **A closeout reconciliation** that lists every revision of every sheet against approved change orders and flags the ones with none.

The graphic on this page shows the first fix: the drawing link turns from weak to sound once "RFI 147" is carried into the markup. Ask which of the four a contractor uses and since when. The year a fix began is the year the joined history becomes dependable.

## What to record about linkage, and who can authorize it

A partner records how the chain joins, never the records themselves. Five notes are enough: the spine identifier and whether it appears in all three systems; which hop is weakest; whether revisions are ever reconciled against change orders; whether closed jobs remain live, were exported or survive only as PDFs; and the year any repair habit began. Dollar values, drawings, question text and approval documents stay out of the notes.

The person to introduce is the CEO, who has authority to start a licensing discussion and sign; the people who can explain the joins are the project controls lead and whoever administers the ERP. Before that, confirm 50+ full-time employees at peak (contractors excluded, so trade partners' workers do not count), 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.

Several things only SourceX's review can settle: limits set by owner contracts or design copyright, treatment of names and personal data, which jobs and years a buyer would want, and the contractor's compensation. Partners never handle raw project records. The [construction RFI log](/data-types/construction-rfi-log) and [change order data](/data-types/change-order-data-construction) pages describe each record type; [Procore project data export](/systems/procore-export-project-data) covers what tends to come out of Procore, and [BIM 360 to ACC migration data](/systems/bim-360-to-acc-migration-data) covers a common point where drawing history is lost. To mark the trail pass, partial or fail, use the sibling [RFI-to-paid-change completeness checklist](/resources/rfi-to-paid-change-completeness-checklist).

## 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 can name its spine identifier and say where it drops out, [register as a partner](/register), confirm it on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce its CFO or COO.

## Sources

- https://support.procore.com/products/online/user-guide/project-level/rfi/tutorials/respond-to-an-rfi
- https://support.bluebeam.com/revu/how-to/track-and-manage-markups-using-markups-list.html
- https://help.trimble.com/en/vista/vista/project-management/change-orders/about-the-pm-approved-change-orders-form
- https://refer.sourcex.si/terms
