This record chain is part of the quantity-to-progress-claim guide, which covers the metadata packet a partner fills in. Here the job is narrower: trace one school wing through seven records and name the reference that ties each record to the one after it.
Seven records from model revision to adjusted claim
Illustrative, built for this page. A fictional 230-person HVAC contractor fits supply-air diffusers in a secondary-school wing whose classroom layout is redrawn halfway through the job. Quantities here are counts of units, not lengths.
| Step | Record | Key that joins it to the next step | System |
|---|---|---|---|
| 1. Model revision | Revision C: north wing, 412 diffusers across 18 classrooms | Model revision C | Model platform |
| 2. Diffuser count | Units counted off revision C and saved for the month's claim | Revision named in the count file | Quantity tool |
| 3. Layout change | Revision D moves six classrooms into a new east wing; 64 of the same diffusers re-drawn there | Model revision D | Model platform |
| 4. Claim sheet | North wing counted from C, east wing from D: 476 diffusers claimed as fitted | Revision column, if the sheet has one | Excel |
| 5. Certified claim | Progress claim certified on 476 units | Claim number | ERP |
| 6. Site count | Room-by-room walk finds 412 diffusers fitted | Walk date and room list | Site records |
| 7. Adjustment | Next claim reduced by 64 units | Claim number and adjustment note | ERP |
Five of the seven keys appear on their own: the platform stamps revision letters, the ERP issues claim numbers, the site walk has a date. Two exist only if somebody bothers: writing the revision on the count file (step 2) and on each claim line (step 4). Whether anyone can spot the duplicate a year later rests on those two. On Autodesk projects the step 2 count may be made in Forma Takeoff, Autodesk's quantity takeoff product (called Autodesk Takeoff before March 2026), which works from the model; the revision still has to be written onto the file that feeds the claim.
The hop that decides everything: claim sheet back to revision
Step 4 adds two wings together. With a revision column, a later reader sees revision C beside the north wing and revision D beside the east wing of the same building, and immediately wonders whether six classrooms appear twice. Without one, the reader sees 476 diffusers for the school and nothing else. Rebuilding the tie to steps 1 and 3 then means guessing from file dates and wing names, an inferred join the company should label as an inference.
The model platform usually still holds both revisions, as the section on platform moves below explains. It cannot say which revision fed which claim line.
The general pattern, an instruction linked to its completed output, is described in how to recognize linked task instructions and completed outputs. In this chain the instruction is the revised layout and the output is the number of diffusers billed.
Key strength, hop by hop
| Hop | Key | Strength | What weakens it |
|---|---|---|---|
| Revision to diffuser count | Revision named in the count file | Medium | Counts saved as "school diffusers final.xlsx" with no revision |
| Count to claim sheet | File link or pasted values | Weak to medium | Values pasted, so the sheet no longer points at any count file |
| Claim sheet to revision | Revision column | Weak unless present | Column used on some projects only |
| Claim sheet to ERP | Claim number written on the sheet | Strong | Sheet overwritten each month, so earlier claim numbers vanish |
| Claim to site count | Walk date and room list | Medium | Room lists kept in a supervisor's notebook, not with the claim |
| Site count to adjustment | Adjustment note citing the walk | Weak unless written | ERP records the reduction with no reason |
A chain of system keys can be followed by anyone. A chain with pasted values and missing revision columns needs the people who built the sheets, and they may have left the project.
Where revision keys go missing
Three moments tend to strip revision keys, and each leaves a recognizable trace in the metadata.
Month-end pressure. The count is saved late, renamed for the claim and pasted into the sheet. The trace: count files with no revision letter in their names, bunched into the last days of each month.
Platform moves. Projects that started on BIM 360 and moved to Autodesk Construction Cloud, or archives cleaned up after close-out, can lose the older revisions the claim sheets point to. The BIM 360 to ACC migration page covers what to ask before such a move. The trace: closed projects whose model history begins later than their first claim.
Do not mistake the March 2026 naming change for such a move: Autodesk folded its construction cloud into the Forma brand and states that project data stayed put. Where older revisions do survive, the Docs viewer (now Forma Data Management) can set one version of a file beside another for formats such as RVT, DWG, PDF and IFC, so revision C and revision D can still be compared.
In-place sheets. A claim sheet overwritten each month keeps only the latest totals and the latest claim number. The trace: one claim workbook per project rather than one per month.
Repairing the revision link
The repair for the weak link is a habit, not a system. It also tells a partner what to ask about.
| Weak link | Repair | Key it creates |
|---|---|---|
| Claim sheet line to model revision | A revision column on every claim line | Recorded join from claim to model |
| Diffuser count to revision | Revision letter written into the count file name or header | Traceable count |
| Overwritten claim sheets | One saved sheet per month | Claim history that matches ERP claim numbers |
| Unexplained ERP reduction | Adjustment note citing the site walk | Outcome tied to its cause |
For an introduction, the point is not to repair anything. It is to learn which of these repairs already exist, on which projects and from which year. The completeness checklist scores that, and the missing-context comparison shows what each system loses when read alone. For the money side of a claim, see progress claim reconciliation.
Owners of each hop, and the sponsor
The BIM coordinator owns steps 1 and 3, an estimator step 2, the project controls lead step 4, the site supervisor step 6, and finance steps 5 and 7. The model may belong to the designer or the client rather than the contractor, which SourceX's rights review settles. Each owner can describe their hop from folder structures and naming conventions without opening a model, a sheet or a claim. The CEO authorizes a licensing discussion, often with the COO or commercial director as sponsor.
Check the basics: 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.
Unknown until SourceX reviews it: who owns each model, client confidentiality terms, SourceX's current data needs and any offer. Partners record which hops exist and who owns them; they never handle raw records. More on the record type is on construction estimating data.
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 whether its claim sheets record the model revision, and since when, register as a partner, confirm it against who qualifies and read the program terms before introducing its commercial lead.