Quantity-to-progress-claim record chain: the revision and claim keys that join model, takeoff, claim sheet and ERP

Short answer

A contractor connects quantity-to-progress-claim records by writing a reference at every hand-off and checking it survives: the model revision on each quantity export, the revision on each line of the claim sheet, the claim number in the ERP, and the measurement date on any adjustment. Most hops carry a natural key. The hop from claim sheet back to model revision does not, because a person types the sheet, and that gap is where one installed item can be billed under two revised models.

Visual briefFull-size diagram
Seven records link in a two-row snake from revision C and its diffuser count through revision D, the claim sheet, the certified claim, the room-by-room site count and the reduced next claim; the claim sheet's missing revision column is flagged and repaired.
Illustrative chain for a fictional HVAC contractor. The link from claim sheet back to model revision is where 64 diffusers were counted twice.

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.

StepRecordKey that joins it to the next stepSystem
1. Model revisionRevision C: north wing, 412 diffusers across 18 classroomsModel revision CModel platform
2. Diffuser countUnits counted off revision C and saved for the month's claimRevision named in the count fileQuantity tool
3. Layout changeRevision D moves six classrooms into a new east wing; 64 of the same diffusers re-drawn thereModel revision DModel platform
4. Claim sheetNorth wing counted from C, east wing from D: 476 diffusers claimed as fittedRevision column, if the sheet has oneExcel
5. Certified claimProgress claim certified on 476 unitsClaim numberERP
6. Site countRoom-by-room walk finds 412 diffusers fittedWalk date and room listSite records
7. AdjustmentNext claim reduced by 64 unitsClaim number and adjustment noteERP

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

HopKeyStrengthWhat weakens it
Revision to diffuser countRevision named in the count fileMediumCounts saved as "school diffusers final.xlsx" with no revision
Count to claim sheetFile link or pasted valuesWeak to mediumValues pasted, so the sheet no longer points at any count file
Claim sheet to revisionRevision columnWeak unless presentColumn used on some projects only
Claim sheet to ERPClaim number written on the sheetStrongSheet overwritten each month, so earlier claim numbers vanish
Claim to site countWalk date and room listMediumRoom lists kept in a supervisor's notebook, not with the claim
Site count to adjustmentAdjustment note citing the walkWeak unless writtenERP 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.

The repair for the weak link is a habit, not a system. It also tells a partner what to ask about.

Weak linkRepairKey it creates
Claim sheet line to model revisionA revision column on every claim lineRecorded join from claim to model
Diffuser count to revisionRevision letter written into the count file name or headerTraceable count
Overwritten claim sheetsOne saved sheet per monthClaim history that matches ERP claim numbers
Unexplained ERP reductionAdjustment note citing the site walkOutcome 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.

  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

What is the single most important key in this chain?

The model revision recorded against each line of the claim sheet. Every other hop has a natural key, such as the claim number or the file version, but the claim sheet is built by hand and only carries the revision if someone adds a column for it.

Can file dates stand in for a missing revision column?

They can suggest which revision fed a claim, but that is an inference, not a recorded join. Describe it to SourceX as a date match so the review does not treat it as a link.

Does SourceX connect to Autodesk Forma, Excel or an ERP?

Nothing here implies a connector. The products are named because they are where these records commonly sit. How records would be prepared is settled after SourceX's review with the company.

Sources

  1. adsknews.autodesk.com/en/news/autodesk-construction-cloud-is-now-a…
  2. autodesk.com/products/forma-takeoff/overview
  3. knowledge.autodesk.com/support/docs/learn-explore/caas/CloudHelp/cl…
  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