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 shows | Earlier change (RFI 131) | Damper move (RFI 138) |
|---|---|---|
| Question recorded | Yes | Yes |
| Answer chosen as final | Yes | Yes |
| Who was responsible at each stage | Recorded | Recorded |
| Cost impact | Not in the log | Not 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:
| Step | Revision B | Revision C (damper) |
|---|---|---|
| Question | RFI 131, answered | RFI 138, answered |
| Drawing | Commented, sheet reissued | Commented, sheet reissued |
| Commercial approval | $41,700 approved change order | No change order found |
| Cost posted | Yes | Nothing to post |
| Billed | Yes | Not billed |
| Built on site | Yes | Yes |
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 context | Lost from which export | Where it usually lives | Usual owner |
|---|---|---|---|
| Whether an answer cost money | Procore RFI log | Vista change orders, if the RFI number was typed | Project controls lead |
| Which revision an answer produced | Procore RFI log | Bluebeam markups and the drawing revision log | Design coordination manager |
| Whether a revision was paid for | Bluebeam markup export | Vista approved change orders and pay applications | Vista administrator in accounting |
| That a revision exists with no approval | Vista export | Only in the join of Procore, Bluebeam and Vista | Nobody, unless closeout reconciles it |
| Why an approval is missing | All three | Closeout log, claims file or a project manager's spreadsheet | Project manager |
| Approved but not yet on the cost side | Vista Job Cost view | Vista PM, where pending items sit until Ready For Accounting | Vista 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:
- "Has anyone ever matched drawing revisions against approved change orders, for example at closeout or in a claim?"
- "When a revision is built without a change order, where is that written down?"
- "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.