The business task the packet describes
On a construction project, the contractor is paid as work is completed. Each month, someone measures how much has been installed, prices it against the contract, and submits a progress claim. The client's certifier checks it and certifies an amount. Behind that simple cycle sit three kinds of record: the model or drawings that quantities are measured from, the spreadsheet where measured quantities become a claim, and the ERP where certified claims and payments are recorded.
Models are revised constantly as design changes. When a revision re-models an element that was already claimed, the same quantity can be counted twice unless someone notices. Across many projects and years, the joined history of revisions, measurements and claims is a record of how a contractor measures, claims and corrects itself. The packet does not capture that history. It tells SourceX where it lives, how far back it goes and how well the pieces can be joined.
What each system can tell you without opening it
Fill in the packet from one conversation with the project controls lead or the commercial manager.
- Model platform. Which platform holds models and revisions, and since when? Autodesk Construction Cloud became part of Autodesk Forma in March 2026, with Autodesk Docs renamed Forma Data Management and Autodesk Takeoff renamed Forma Takeoff; Autodesk says existing project data was not migrated or changed. In Autodesk Docs, a file with several versions can be compared against another version in the viewer, for formats including RVT, DWG, PDF and IFC. So "are older revisions kept?" is usually answerable with a yes and a start year.
- Quantity extraction. Are quantities taken off the model with a tool such as Forma Takeoff, Autodesk's quantity takeoff software, or measured manually? Does the takeoff record which revision it used?
- Excel claim sheets. Is there one sheet per project per month, or one sheet overwritten each month? Does the sheet have a column for the model revision behind each quantity?
- ERP. Which ERP holds certified claims, variations and payments, and for which years? Is the claim number in the ERP also written on the claim sheet?
Sample packet, filled in
Illustrative: a fictional 380-person mechanical and fire protection contractor; every answer is invented to show the level of detail.
| Packet field | Model platform | Excel claim sheets | ERP |
|---|---|---|---|
| Object types | Models, revisions, takeoffs | Monthly claim sheets per project | Certified claims, variations, payments |
| Date range | Autodesk Construction Cloud since 2021; BIM 360 from 2017 | Each month kept since 2020; earlier sheets overwritten | 2015 to today |
| Rough volume | About 25 projects a year with revised models | About 300 claim sheets a year | About 300 certified claims a year |
| Revision marker | Revision ID on every model file | Revision column on some projects only | None |
| Link to next step | Takeoff names the revision | Claim number on the sheet, mostly | Claim number |
| Step owner | Design manager | Project controls lead | Finance |
| Planned change | Archive clean-up of closed projects | None | ERP replacement next year |
| Unknown until review | Who owns the model: designer, client or contractor | Personal data in sheet comments | Client confidentiality terms |
The "Planned change" row matters. A migration from BIM 360, an ERP replacement or a file-share clean-up can break the chain without anyone deciding to. The BIM 360 to ACC migration page and the ERP replacement handoff checklist cover those moments. Keep quantities, model files, sheets and claim amounts out of the packet; ranges and yes-or-no answers are enough.
How the packet flags a quantity counted twice
The case to surface is one quantity counted in two revised models. In the illustrative contractor, sprinkler pipe on one floor was measured at 1,240 meters from model revision R7 and claimed. Revision R8 re-modeled 310 meters of the same run after a ceiling change, and the next takeoff added those 310 meters as new. The claim sheet showed 1,550 meters, and the ERP recorded 1,550 meters certified. A site measurement found 1,240 meters installed, so the next claim was reduced by 310 meters.
The partner never sees those quantities. The packet makes the case findable through two rows: "Revision marker" shows the claim sheet records the model revision only on some projects, and the ERP not at all; "Date range" shows which months still have their own sheet. Together they tell SourceX where a double count could hide, and from which year it could be traced. Ask the project controls lead one question: "When a model is revised, how do you stop the new takeoff counting what you already claimed?"
Who owns models, measurements and claims?
Three owners usually share this chain. The design team or the client may own the model; the contractor owns its measurements, claim sheets and ERP records; the client's certifier produces the certified amount. Licensing depends on who holds rights to each piece, which SourceX establishes in its rights review. The question of provenance is covered in chain of title for training data, and the wider reconciliation workflow in progress claim reconciliation.
Introduce the executive who can authorize a licensing discussion, the CEO, often titled managing director, with the COO or commercial director as a likely sponsor and the project controls lead as the person who can answer the packet. Check the basics first: 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.
What stays unknown until SourceX reviews the opportunity: demand for this record type, the rights review result, how client and personal data would be handled, what the company would be offered, and any reward. Partners never ask for or handle raw client records. More construction context is on the construction and field services page, the pay application review page and the guide to linked task instructions and completed outputs; other system guides are in the systems hub.
Go deeper on quantity-to-progress-claim records
- Quantity-to-progress-claim record linkage: the record chain, step by step, with the identifier that joins each hop and where it breaks.
- Quantity-to-progress-claim completeness checklist: a pass, partial or fail scorecard for judging whether the claim trail is complete enough to discuss.
- What a single-system claim export loses: a before-and-after reading of one claim, with and without its surrounding records.
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 fill most of this packet and say who owns each piece, register as a partner, confirm it against who qualifies, and read the program terms before you introduce its commercial lead.