RFI-to-paid-change completeness checklist: eight contractor record checks marked pass, partial or fail

Short answer

An RFI-to-paid-change trail breaks wherever a reissued drawing has no commercial record behind it. Smaller breaks cluster around that one: drawing comments and change orders that never cite the question number, closed jobs stored as flat files, sheets reissued with no change event, approvals parked in pending status, and outcomes logged only as "not billed." The checklist below turns each break into a test a partner can mark pass, partial or fail in one call, without opening a drawing, a question log or a change order.

Visual briefFull-size diagram
A clipboard of eight contractor record checks ticks pass, partial or fail one at a time while a ring meter fills to four passes, three partials and one fail on the unbilled revision log.
Illustrative marks for a fictional electrical contractor. The marks describe the trail; they do not predict acceptance.

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.

#CoversCheckQuestion to askPassPartialFail
1CoverageProjects and yearsHow 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 yearsTwo to five overlapping yearsUnder two overlapping years
2LinkageRFI number on markupsDo drawing comments cite the question number?Required before a sheet goes out againHabit of some coordinatorsNever; matching relies on dates and sheet numbers
3LinkageRFI number on change ordersDoes each pending change order carry the question or change event number?As its own fieldIn free text, sometimesNot recorded
4TimestampsMarkup history keptWere closed jobs archived with comment history and revision dates intact?Comment lists stored as data with datesRecent jobs onlyFinal sheets only
5VersionsReissue controlCan a sheet go out again without anyone opening or considering a change event?No; every reissue triggers a commercial reviewOnly for large changesYes, freely
6OutcomesPending approvals trackedAre approved changes still in pending status followed until they post to cost?Kept as a listAccounting knows, but no listNot followed
7OutcomesPaid, disputed or absorbedWhen a change goes unbilled, is the reason written down?Reason recorded per changeOn claims only"Not billed" with no reason
8GapsUnbilled revision logDoes job closeout produce a list of revisions built with no approved change order?Logged per jobSome jobsNever

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:

PatternWhat it tells SourceXWrite-up line
Checks 2, 3 and 8 passQuestions, 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 passesMatching is weak, but the contractor knows where the gaps sit"Matched by sheet and date; unbilled revisions listed at closeout"
Checks 4 and 1 failDrawing history is short or flat"Drawing history only as PDFs before a stated year"
Checks 6 and 7 pass, 8 failsCommercial 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.

#CheckAnswer heardMark
1Projects and yearsQuestion log since 2017, accounting system since 2011, drawing comments since 2018Pass
2RFI number on markupsSome coordinators type it; no rulePartial
3RFI number on change ordersRequired field since 2020Pass
4Markup history keptComment lists exported at closeout since 2019Pass
5Reissue controlCommercial review only on changes over a set sizePartial
6Pending approvals trackedAccounting keeps a weekly pending listPass
7Paid, disputed or absorbedReason recorded on claims onlyPartial
8Unbilled revision logNot doneFail

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.

  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

Should I estimate how often revisions go unbilled?

No. Record whether the contractor knows and how it finds out. A partner's estimate is a guess that SourceX cannot check, while the contractor's own description of its closeout process is evidence.

Who answers the checklist at a contractor?

The project controls lead for most checks, the design coordination manager for the drawing checks and the Vista administrator for approvals and cost posting. A 30-minute call with two of them usually covers all eight.

Does a fail on markups before a certain year matter?

It sets the start of the joined history rather than ruling anything out. If markups before 2019 survive only as flat PDFs, the drawing hop is reliable from 2019; note the year and move on.

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