This before-and-after reading belongs to the quantity-to-progress-claim guide. It takes one Illustrative pay period and reads it three ways in isolation, then once more with everything side by side.
Before: three exports, each internally consistent
Illustrative. A fictional 260-person electrical contractor is fitting cable tray on deck P2 of a hospital parking structure. Halfway through, the architect moves the EV charging layout, and the design team reissues the deck. A reviewer handed each export separately would see this.
From the design model. Issue C of deck P2 shows 2,800 feet of tray in the east bay. Issue D, released three weeks later, carves a new ramp bay out of the east bay and draws 450 feet of tray there. Two tidy drawing sets, each correct for its date.
From the Excel workbook. Row one: east bay, 2,800 feet. Row two: ramp bay, 450 feet. Total billed as installed: 3,250 feet. The cells pull from exported quantity lists. Nothing on the sheet says which issue a row came from.
From the ERP. Payment application certified on 3,250 feet. Next period: a negative line of 450 feet, with an amount and a posting date.
Each looks normal. The drawings show routine design change. The workbook shows a finished deck. The ledger shows an adjustment like dozens of others that year. No single file contains a mistake a reader could point to.
After: one pay period with every source side by side
Line the exports up by deck, bay and month, and add the field count that triggered the cut.
| Month | Design model | Excel workbook | Field count | ERP |
|---|---|---|---|---|
| Month 1 | Issue C: east bay, 2,800 feet | Nothing billed yet | Tray going in | Nothing |
| Month 2 | Issue D: 450 feet of east bay runs redrawn as ramp bay | East bay 2,800 from issue C plus ramp bay 450 from issue D | No count | Certified on 3,250 feet |
| Month 3 | Unchanged | Ramp bay row deleted | Counted: 2,800 feet in place | Cut by 450 feet |
Now the reason appears. The ramp bay tray was never extra material. It was the same runs already billed under the east bay, redrawn under a new bay name. The workbook added both. Nobody put issue C beside issue D before billing, so the owner's certifier approved 3,250 feet, and the foreman's count exposed it a month later.
The connected version teaches far more than any lone file, for the reason set out in why data quality beats quantity: three accurate fragments explain less than one sequence with its error and repair labeled.
The gap table: what goes missing and who holds it
This table is the asset to bring to a first conversation. It names each lost fact, the place it normally sits and the person who can say whether it survives.
| Lost when one export is read alone | What it explains | Where it lives | Who can confirm it |
|---|---|---|---|
| Which model issue fed each billed line | Whether a total mixes two drawing sets | A revision column on the workbook, if one exists | Project controls lead |
| What changed between issue C and issue D | That ramp bay runs were redrawn, not added | Model version history and its compare view | Design manager or BIM lead |
| How quantities were pulled | Whether the export named its issue | Quantity export files and their names | Estimator |
| What was physically in place | The true length against the bill | Field count or measurement records | Site manager or foreman |
| Why the certified amount was cut | That the cut corrected a double count | ERP adjustment note or letters to the certifier | Finance or commercial manager |
| Each month's bill as submitted | The state before correction | One saved workbook per month, if kept | Project controls lead |
The model rows are usually the easiest to answer. Autodesk Construction Cloud became part of Autodesk Forma in March 2026, with Autodesk Docs renamed Forma Data Management and Autodesk Takeoff renamed Forma Takeoff, and Autodesk says existing project data was not migrated or changed. In Autodesk Docs, one version of a file can be compared with another in the viewer, for formats including RVT, DWG, PDF and IFC, so issue C and issue D can usually still be put side by side. Forma Takeoff, Autodesk's quantity takeoff tool, is one common source of the exported lists. None of that says which issue a billed line used, which is why the first row is the fragile one. The cut's reason is the other: it often lives in correspondence with the certifier, not the ledger, and may not outlast a mailbox clean-up.
Phrases that reveal a missing column
A partner never sees these tables. What a partner hears in conversation are phrases that point at a missing column, and each maps to a row above.
| What the project controls lead says | What it usually means |
|---|---|
| "We overwrite the workbook each month" | Bills as submitted are gone; only the ERP keeps the history |
| "The quantity export is just called final" | The issue behind a number has to be guessed from dates |
| "Finance handles adjustments" | The reason for a cut may sit outside project files |
| "We compare drawing issues before every bill" | A double count would likely be caught and noted |
| "Old BIM 360 jobs were archived" | Earlier model versions may be missing for early bills |
None of these rules a contractor out. Each locates a gap, and the record chain page names the key that would have closed it. The completeness checklist scores whether the trail is complete enough to discuss, and what data is missing from AI training explains why missing reasons matter to buyers.
Describing the gap without opening a file
What SourceX needs from a partner is which columns of the after table the contractor can still fill, for which jobs and years. That is metadata: whether each month's workbook is kept, whether it names the model issue, how far model history goes back and where reasons for cuts are written. It is the kind of signal covered in measuring referral quality instead of volume.
Before introducing, confirm: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact: the CEO, with the COO or commercial director often as sponsor. 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.
Unknown until SourceX reviews the opportunity: whether the designer, owner or contractor holds rights to each model, client confidentiality terms, SourceX's current data needs and any offer. Partners never handle raw records. Other system guides are in the systems hub.
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 say which columns of the after table it still holds, and on which jobs, register as a partner, confirm it against who qualifies and read the program terms before introducing its commercial lead.