It belongs to the RFI-to-paid-change records guide, which sets out the metadata packet for the same chain. The contractor runs these tests on its own records; the partner only learns whether it can.
Before you start: who to ask and how to mark
Book 30 minutes with whoever runs project controls and, ideally, the person who administers the accounting system. Put each test as a yes-or-no question first, then follow up with "since what year?" and "on every job?" to choose between pass and partial.
- Pass: true on most jobs, and the contractor can name a start year.
- Partial: true on some jobs, in some years or for some project managers only.
- Fail: not done, or nobody knows.
Ask for no examples and make no estimate of how often anything happens. Write down the contractor's answer in its own words.
The eight checks
The tests use tool-neutral terms (question log, drawing comment history, commercial approval system) because contractors run this chain on many different stacks. Each row says what the test covers, the question to ask and what earns each mark.
| # | Covers | Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|---|---|
| 1 | Coverage | Projects and years | How many years of jobs do the question log, the drawing comment history and the approval system each hold, and were older jobs migrated? | Five or more overlapping years | Two to five overlapping years | Under two overlapping years |
| 2 | Linkage | RFI number on markups | Do drawing comments cite the question number? | Required before a sheet goes out again | Habit of some coordinators | Never; matching relies on dates and sheet numbers |
| 3 | Linkage | RFI number on change orders | Does each pending change order carry the question or change event number? | As its own field | In free text, sometimes | Not recorded |
| 4 | Timestamps | Markup history kept | Were closed jobs archived with comment history and revision dates intact? | Comment lists stored as data with dates | Recent jobs only | Final sheets only |
| 5 | Versions | Reissue control | Can a sheet go out again without anyone opening or considering a change event? | No; every reissue triggers a commercial review | Only for large changes | Yes, freely |
| 6 | Outcomes | Pending approvals tracked | Are approved changes still in pending status followed until they post to cost? | Kept as a list | Accounting knows, but no list | Not followed |
| 7 | Outcomes | Paid, disputed or absorbed | When a change goes unbilled, is the reason written down? | Reason recorded per change | On claims only | "Not billed" with no reason |
| 8 | Gaps | Unbilled revision log | Does job closeout produce a list of revisions built with no approved change order? | Logged per job | Some jobs | Never |
Where documented tool behavior backs a check
Three checks map onto documented behavior in tools many contractors use, which is why they are worth asking about:
- Check 4, markup history. Bluebeam's Markups List records each comment's author, creation and modified dates, status and comments, and the list can be saved as CSV or XML. A contractor that saved those lists has dated drawing history; one that kept only the final PDF set does not.
- Check 6, pending approvals. Trimble's Viewpoint Vista help says an approved change order with pending status cannot be interfaced to Job Cost, and only change orders marked Ready For Accounting interface. Pending items sit outside the cost view until someone moves them.
- Check 1, the question side. Procore records who held Ball In Court and which response was marked official, so each question kept in Procore carries its answer and its handoffs. Coverage still depends on how many years of jobs were kept.
Other tools may behave differently, so ask rather than assume. Naming a tool here is not a claim that SourceX connects to it.
Reading the marks together
Single marks matter less than the patterns they form:
| Pattern | What it tells SourceX | Write-up line |
|---|---|---|
| Checks 2, 3 and 8 pass | Questions, revisions and approvals line up, and mismatches are already labeled | "Matched on question number, with a closeout list of unbilled revisions" |
| Check 2 or 3 fails, 8 passes | Matching is weak, but the contractor knows where the gaps sit | "Matched by sheet and date; unbilled revisions listed at closeout" |
| Checks 4 and 1 fail | Drawing history is short or flat | "Drawing history only as PDFs before a stated year" |
| Checks 6 and 7 pass, 8 fails | Commercial outcomes are clean, but nobody compares them with drawings | "Clean approval and billing history; no drawing-to-approval reconciliation" |
A contractor that says "we catch unbilled revisions at closeout, roughly like this" is describing a labeled exception. That label is the most useful thing the checklist can surface.
A marked example (Illustrative)
A fictional 450-person electrical contractor working on hospitals and data centers, marked in one call with its project controls lead and accounting systems administrator. All answers are invented.
| # | Check | Answer heard | Mark |
|---|---|---|---|
| 1 | Projects and years | Question log since 2017, accounting system since 2011, drawing comments since 2018 | Pass |
| 2 | RFI number on markups | Some coordinators type it; no rule | Partial |
| 3 | RFI number on change orders | Required field since 2020 | Pass |
| 4 | Markup history kept | Comment lists exported at closeout since 2019 | Pass |
| 5 | Reissue control | Commercial review only on changes over a set size | Partial |
| 6 | Pending approvals tracked | Accounting keeps a weekly pending list | Pass |
| 7 | Paid, disputed or absorbed | Reason recorded on claims only | Partial |
| 8 | Unbilled revision log | Not done | Fail |
Write-up: "Matched question, drawing and change order history from 2020, with the question number required on change orders; drawing comments only sometimes cite it; no closeout list of unbilled revisions." That is enough for an introduction. The single fail means the records can show revisions and approvals, but nobody has labeled the ones that do not match. The related page on what a single-system RFI export loses explains why that label matters.
Owners, sponsor and what stays open
Each check has a natural owner. Project controls answers checks 1, 3, 7 and 8; design coordination answers 2, 4 and 5; the accounting systems administrator answers 6. A licensing discussion needs someone with authority to open it: the CEO, who in an owner-run contractor is usually the owner.
Before introducing, confirm the basics: 50+ full-time employees at peak (contractors excluded, so count direct hires rather than trade partners' field staff), 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.
Still open until SourceX's review: owner contract restrictions, design copyright, how personal names would be treated, which jobs a buyer might want and what the contractor would receive. Partners never ask for or hold raw job records. The change order data page describes the commercial records, Procore project data export covers the question side, and BIM 360 to ACC migration data explains a common point where drawing history goes flat. For the identifiers behind checks 2 and 3, see the sibling RFI-to-paid-change record linkage page; for the wider context, read construction data monetization.
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 mark all eight checks and sum up its trail in one honest sentence, register as a partner, confirm it on who qualifies and read the program terms before you introduce its owner or CEO.