Before and after: one unbilled drawing revision read from three separate exports, then joined

Short answer

A single-system export of RFI-to-paid-change records loses the joins between question, drawing and money. The RFI log shows questions and answers but not which answers cost anything. The markup file shows the design conversation but carries no commercial status. The accounting export shows approved changes and billing but is silent about any revision that never got approval. That silence is the biggest loss: a missing record cannot be seen from inside the system that should have held it.

Visual briefFull-size diagram
A timeline strip for revision C of sheet M-305 shows RFI 138 answered and the sheet marked up, with blank gaps for commercial approval and billing; the gaps fill with the labels no change order and not billed as context from the job cost side slides in.
Illustrative. Joined, the records show a labeled gap; any one export alone shows either nothing wrong or nothing at all.

This page is part of the RFI-to-paid-change records guide. It reads one fictional revision three times, once from each export alone, and then joined.

Before: three single-system readings of one revision

Illustrative. A fictional 380-person mechanical contractor moves a fire damper on level 4 after a design question, RFI 138, and reissues sheet M-305 as revision C. Earlier the same sheet went through revision B for a separate change that was approved at $41,700 and billed. Every value is invented.

Reading 1: the question log alone

What the question log showsEarlier change (RFI 131)Damper move (RFI 138)
Question recordedYesYes
Answer chosen as finalYesYes
Who was responsible at each stageRecordedRecorded
Cost impactNot in the logNot in the log

The project management tool (Procore, here) records which response counts as the answer and whose court the question sat in, so both questions read as closed. A reader sees two equally complete questions. Nothing says one produced a paid change and the other produced nothing billed.

Reading 2: the markup file alone

The design team's PDF markups, saved as a list with each comment's author, dates, status and text, describe the damper discussion in detail. Revisions B and C look equally finished: both have comments, authors, dates and a status. A comment carries no commercial status, so the file cannot say which revision anyone paid for.

Reading 3: the accounting export alone

The ERP (Viewpoint Vista, here) shows the $41,700 change as approved, posted to job cost and billed. It shows nothing about the damper, because a change that was never approved never entered the system. A reader concludes that sheet M-305 changed once, fully paid.

All three readings are accurate. All three miss the same thing.

After: the joined sequence with its labeled gap

Join the three on question number and sheet revision, and a sequence appears with a gap in it:

StepRevision BRevision C (damper)
QuestionRFI 131, answeredRFI 138, answered
DrawingCommented, sheet reissuedCommented, sheet reissued
Commercial approval$41,700 approved change orderNo change order found
Cost postedYesNothing to post
BilledYesNot billed
Built on siteYesYes

Revision C is now a labeled exception: drawn, answered, built and never approved commercially. Whether that work was absorbed, disputed, folded into another change or missed is the next question, and only the company can answer it.

What is lost and where it lives

Each row is context a single export drops, where it usually lives at a mid-size contractor, and who owns it.

Lost contextLost from which exportWhere it usually livesUsual owner
Whether an answer cost moneyProcore RFI logVista change orders, if the RFI number was typedProject controls lead
Which revision an answer producedProcore RFI logBluebeam markups and the drawing revision logDesign coordination manager
Whether a revision was paid forBluebeam markup exportVista approved change orders and pay applicationsVista administrator in accounting
That a revision exists with no approvalVista exportOnly in the join of Procore, Bluebeam and VistaNobody, unless closeout reconciles it
Why an approval is missingAll threeCloseout log, claims file or a project manager's spreadsheetProject manager
Approved but not yet on the cost sideVista Job Cost viewVista PM, where pending items sit until Ready For AccountingVista administrator

The last row comes from Vista's own rules: an approved change order with pending status cannot be interfaced to Job Cost, and PM and Job Cost store change order detail in different tables. A Job Cost export alone can therefore miss changes that are approved but not yet interfaced.

Why the absent record is the most important loss

Most missing context can be recovered by asking the right owner. An absent approval cannot, because no system holds a row saying "this should have been approved." The only evidence is the mismatch between systems. That is why the joined history is worth more than any single export: it records judgment under uncertainty, a field decision taken without a commercial one, and what happened next. What data is missing from AI training explains why that kind of record is scarce.

The same absence appears on the design side. Architects and engineers hold drawing revisions and answers but rarely see the commercial outcome, which is one reason architecture firm data licensing has to be scoped separately. The construction RFI log and change order data pages describe each record type on its own; this page is about what disappears between them.

Asking about context without opening a file

A partner never needs the exports to test this. Ask the project controls lead three questions:

  1. "Has anyone ever matched drawing revisions against approved change orders, for example at closeout or in a claim?"
  2. "When a revision is built without a change order, where is that written down?"
  3. "Do markups and change orders quote the RFI number, or do joins rest on dates and sheet numbers?"

If the answers show a real gap that the company knows about, check the company itself: 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 person who can sponsor a licensing conversation internally is usually the CFO, since the gap sits between operations and accounting; the CEO authorizes it.

Your three answers say nothing yet about rights or value. Owner contract clauses, design copyright, the handling of names, buyer interest in particular jobs and the contractor's eventual compensation are all settled in SourceX's review. For the wider picture, see construction data monetization. To trace the identifiers that make the join possible, use the sibling RFI-to-paid-change record linkage page; to mark the trail pass, partial or fail, use the 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 tell you where it records revisions built without approval, register as a partner, confirm it on who qualifies and read the program terms before you introduce its CFO.

  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

If every export looks complete, how would anyone notice the gap?

Only by joining them. A missing change order leaves no row in the commercial system, so it cannot be seen from inside that system. Contractors usually find these cases at closeout, in a claim, or when a project manager reconciles revisions against approvals.

Is an unbilled revision a sign of poor records?

Not necessarily. It can mean the work was absorbed, disputed, folded into another change or simply missed. What matters for an introduction is whether the company records which of those happened, not how often it occurs.

Should I ask the contractor to send one export of each system so I can compare them?

No. Exports hold project names, amounts and people's names. Ask which systems hold each step and whether anyone has reconciled them; the comparison itself happens only under a signed agreement with SourceX.

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