# RFI-to-paid-change metadata packet | SourceX

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

A partner can note, without opening a single record, which systems hold each step from design question to reviewed drawing to change payment (here Procore, Bluebeam and Viewpoint Vista), how many projects and years each covers, which object types exist, who owns each one, and whether every drawing revision can be matched to a commercial approval. That is the whole packet. The records stay with the contractor; whether they can be licensed is settled later, after SourceX reviews them.

## The business task behind the records

A field team hits a conflict, say a duct that will not fit under a beam. Someone raises a request for information (RFI), the design team answers, the drawing is marked up and reissued, the contractor prices the extra work, the owner approves a change order, and the cost is billed. Each step answers a different question: what was asked, what was decided, what it cost, and who agreed to pay.

The graphic on this page shows the pattern for one sheet (Illustrative). Revision D carries RFI 212, a set of drawing comments, a $38,200 approved change order and a bill. Revision E carries RFI 219 and drawing comments, but no approved change order and no bill. The packet's job is to tell SourceX whether a contractor can show that difference across years of projects, not just one sheet.

## What metadata can a referral partner collect about RFI-to-paid-change without reading private content?

A checklist, filled in from one conversation with the project controls lead or the head of operations. Every line is a description; none needs a file.

- **Systems and modules.** Procore RFIs (and change events, if used); Bluebeam Revu or Studio for markups; Viewpoint Vista project management and job cost. Plain-text names only.
- **Span and volume.** Years of projects in each system, rough number of projects per year, rough RFIs per project.
- **Shared reference.** Does the RFI number, change event number or sheet number appear in all three? Answer yes, sometimes or no.
- **Revision matching.** Has the company ever reconciled drawing revisions against approved change orders, for example at closeout or in a claim?
- **Archive form.** Are closed projects kept in the live systems, exported, or flattened to PDF?
- **Owners.** Who administers the project management tool, who keeps the drawing archive, who runs the ERP.
- **Contract limits to flag.** Owner contracts with confidentiality clauses, design copyright held by the architect or engineer, public-sector work.
- **Unknown until review.** Whether there is demand for these records, the rights review result, how names and personal data would be handled.

Leave out amounts, sheet images, RFI text and change order documents. "About 40 projects a year since 2016, all in Procore and Vista, markups in Bluebeam since 2019" is a complete answer.

## A sample packet, one column per system (Illustrative)

The values describe a fictional 260-person mechanical contractor. They show the level of detail an introduction needs, nothing more.

| Packet field | Procore (design question) | Bluebeam (reviewed drawing) | Vista (change payment) |
|---|---|---|---|
| Object types | RFIs, official responses, Ball In Court history | Markups with author, dates, status and comments | PM change orders, Job Cost change detail, interface dates |
| Years held | 2016 to today | 2019 to today; earlier sheets as flat PDFs | 2012 to today |
| Rough volume | About 40 projects a year, 150 to 300 RFIs each | Markup sets on most revised sheets | Several hundred approved change orders a year |
| Reference carried | RFI number, sheet number | Sheet number in the file name | Change order number; RFI number typed in a description, sometimes |
| Owner | Project controls lead | Design coordination manager | ERP administrator in accounting |
| Known gap | None stated | Markups before 2019 not kept as data | Pending change orders cannot reach Job Cost until marked Ready For Accounting |
| Unknown | Share of RFIs that led to a revision | Whether markup lists were ever exported | Share of change orders that cite an RFI |

The vendor help pages listed under Sources describe the fields named here: Procore's official response and Ball In Court, the Bluebeam Markups List columns and its CSV or XML export, and Vista's rule that only change orders marked Ready For Accounting interface to Job Cost. Naming a field in a packet is not a claim that SourceX connects to any of these tools.

## What to note when a revision has no matching approval

Revision E is the line to ask about. Do not investigate it; record how the company handles it. Three facts are enough: whether the contractor knows how often a revision is built without an approved change order, where that knowledge lives (a closeout log, a claims file, a spreadsheet kept by the project manager), and who could say how such cases ended. "We find these at closeout and keep a list per project" is a useful answer. "We would have to look" is also useful, and honest.

Pending change orders deserve one extra line. The ERP's help pages say a change order that is approved but still pending cannot be interfaced to Job Cost, so the packet should say whether pending items are tracked separately.

## Owner contracts, drawings and who can authorize the discussion

The contractor owns its own operating records, such as RFI logs, change order history, job cost and billing. The drawings may belong to the design team, and owner contracts may restrict reuse of project information. SourceX checks both in its rights review; the partner simply notes the questions. The question of drawing ownership is covered in [who owns construction drawings](/questions/who-owns-construction-drawings-copyright).

The packet goes with an introduction to the executive who can authorize a licensing discussion, the CEO, often titled president, with the COO as a possible sponsor, plus the names of the two people who can answer its lines: the project controls lead and the ERP administrator. Check the basics first: 50+ full-time employees at peak (contractors excluded, so count the company's own payroll, not the trades it hires), 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.

Partners never ask for or handle raw client records. Construction technology advisors will find more on spotting these companies in the [construction technology consultant page](/for/construction-technology-consultant-referral); the [construction RFI log](/data-types/construction-rfi-log) and [change order data](/data-types/change-order-data-construction) pages describe the two record types, and the [pay application review page](/data-types/pay-application-review-process-construction) covers the billing step. Other system guides are in the [systems hub](/systems).

## Go deeper on RFI-to-paid-change records

- [How to link RFI, drawing and change order records across systems](/guides/rfi-to-paid-change-record-linkage): a guide to the join keys and matching rules that connect the three systems.
- [RFI-to-paid-change completeness checklist](/resources/rfi-to-paid-change-completeness-checklist): a checklist of the breaks that leave the evidence trail incomplete.
- [What a single-system RFI export leaves out](/guides/rfi-to-paid-change-missing-context): a guide to the context lost when only one system is exported.

## 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 fill in the packet above and name who owns each system, [register as a partner](/register), confirm it against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its president or COO; [how referral payments work](/questions/how-to-get-paid-for-referrals) explains what happens after an introduction.

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