RFI-to-paid-change record chain: the identifiers that join Procore, Bluebeam and Viewpoint, hop by hop

Short answer

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.

Visual briefFull-size diagram
Five records, RFI 147, its answer, sheet FP-301 revision C, a $54,600 change order and the pay application, click together as a chain; the link at the drawing is highlighted as weak, then turns green when the RFI number is carried into the markup.
Illustrative chain for one sprinkler main relocation. The drawing hop holds only when someone types the RFI number into it.

This page is part of the RFI-to-paid-change records guide, 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.

HopStepRecordSystemKey it carriesJoin strength
1Question raisedRFIPM toolRFI numberNative to the tool
2Answer givenResponse marked official, with its review historyPM toolSame RFI numberNative to the tool
3Drawing changedMarkups, then reissued sheet and revisionDrawing reviewSheet number and revision; RFI number only if typedWeak, depends on habit
4Change approvedPending, then approved change orderERP, change moduleChange order number; RFI number if typed in the descriptionModerate
5Change paidJob Cost entry, pay application lineERPChange order number, interface dateNative 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.

DateSystemRecordReference carried
June 3PM toolRFI 147 raised: sprinkler main and gas line clash in the east corridorRFI 147
June 7PM toolEngineer's response marked official and returned to the RFI ManagerRFI 147
June 10Drawing reviewSheet FP-301 marked up, then reissued as revision C with the main lowered"RFI 147" typed in the markup comment
June 17ERPPending change order for the relocation, $54,600RFI number in the description
July 1ERPApproved change order, cleared for accounting and posted to job costChange order number
July 31ERPRelocation billed on the monthly pay applicationChange 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 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.

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 and change order data pages describe each record type; Procore project data export covers what tends to come out of Procore, and 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.

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, confirm it on who qualifies and read the program terms before you introduce its CFO or COO.

  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

Which identifier is the best spine for the chain?

Whichever one the company already types into every system. Often that is the RFI number; some contractors use a change event or potential change order number instead. A weaker key used everywhere beats a stronger key used in one system.

Can a sheet number alone join a drawing to a change order?

Only loosely. A sheet such as FP-301 can carry several revisions answering several RFIs, so a sheet number tells you where to look, not which change paid for which line. Pair it with a revision letter and a reference to the RFI.

Does SourceX connect to Procore, Bluebeam or Viewpoint?

No connector is implied. The tools are named because they commonly hold these records. If a contractor proceeds, it decides what to share under a signed agreement.

Sources

  1. support.procore.com/products/online/user-guide/project-level/rfi…
  2. support.bluebeam.com/revu/how-to/track-and-manage-markups-using-m…
  3. help.trimble.com/en/vista/vista/project-management/change-ord…
  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