Quantity-to-progress-claim completeness scorecard: six metadata checks before promising an AI data opportunity

Short answer

A quantity-to-progress-claim trail breaks in four ways: one quantity is counted in two revised models, quantity exports carry no revision, claim sheets are overwritten each month, or the ERP records a reduction without its reason. The scorecard below turns those breaks into six checks across coverage, linkage, timestamps, outcomes and gaps. Each is answered at metadata level and scored pass, partial or fail, so a partner can describe the trail honestly before anyone mentions an AI data opportunity.

Visual briefFull-size diagram
Six check cards for model history, export revision, revision column, monthly sheets, claim number and adjustment reason turn pass, partial or fail in turn while a horizontal bar fills to 8 of 12 points.
Illustrative score for a fictional mechanical contractor: 8 of 12, discussable for recent projects with its gaps labeled.

This scorecard is part of the quantity-to-progress-claim guide. It does not replace SourceX's review; it makes the first review conversation shorter and more accurate.

Scoring rules

Score each check 2 for pass, 1 for partial and 0 for fail, for a maximum of 12. Ask about folder structures, naming rules and settings. Never ask to see a model, a takeoff, a claim sheet or a certified claim.

  • Score a period, not the whole company. Pick the years the contractor would discuss and score those. Note when each pass begins.
  • Unknown is a fail. If nobody can answer, record 0 and "not known".
  • Score the weaker project type. If large projects pass and small ones fail, score the small-project answer and note the split.
  • No frequency estimates. Whether double counts happen once a year or once a month is not a scorecard question.

The six checks

CheckAreaHow to check at metadata levelPass (2)Partial (1)Fail (0)
1. Model historyCoverageAsk which platform holds models, from what year, and whether superseded revisions are keptAll revisions kept for every project in the periodKept for recent projects, or archived without old versionsOnly current models kept
2. Export revisionLinkageAsk how quantity exports are named and whether they state the model revisionRevision in every export name or headerOn some projects onlyNever; names like "final"
3. Claim sheet revision columnLinkageAsk whether each claim line records the model revision it came fromColumn used on every projectUsed on some projectsNo such column
4. Monthly sheets keptTimestampsAsk whether each month's claim sheet is saved separately or overwrittenOne sheet per month per projectSaved for some years or projectsOverwritten in place
5. Claim number on the sheetLinkageAsk whether the ERP claim number is written on the matching claim sheetAlwaysMostlyNever
6. Adjustment reasonOutcomes and gapsAsk whether ERP reductions carry a note or a reference to the measurement that caused themNote or reference requiredSometimes written, or kept in emailAmount and date only

Checks 3 and 4 carry most of the weight. A revision column without monthly sheets shows only the latest claim; monthly sheets without a revision column show every claim but not where its numbers came from.

The double-count test

Before scoring, run one test that exercises checks 1, 2, 3 and 6 at once. Ask the project controls lead: "Think of a job where the model was revised after a quantity had already been claimed. Without opening anything, where would I find which revision each claimed quantity came from, and where would I find why a later claim was reduced?"

AnswerWhat it shows
"The revision column on the claim sheet, and the adjustment note in the ERP"Checks 3 and 6 likely pass
"We compare revisions before each claim, but we do not write the revision down"The control exists but leaves no record; check 3 fails
"We would have to ask the estimator who did that job"The join lives in a person; checks 2 and 3 fail
"Finance has the reason in an email to the certifier"Check 6 is partial at best

A contractor that says "yes, we have caught double counts after redesigns, and we keep each month's sheet" is describing a trail that can be rebuilt with its exceptions labeled. That is the answer worth bringing to SourceX.

A scored example (Illustrative)

A fictional 230-person mechanical contractor, scored for projects from 2021 onward.

CheckAnswer givenScore
1. Model historyAll revisions kept since 2021; earlier BIM 360 projects archived without old versions2
2. Export revisionRevision in export names on hospital and lab projects only1
3. Claim sheet revision columnAdded in 2023, used on most projects since1
4. Monthly sheets keptOne sheet per month since 20202
5. Claim number on the sheetMostly1
6. Adjustment reasonUsually in email to the certifier, sometimes an ERP note1
Total8 of 12

Eight of twelve. For SourceX, that reads as a trail that can be followed for recent projects, where revision links are partial before 2023 and adjustment reasons have to be found outside the ERP.

What the total means

TotalReadingWhat the partner does
10 to 12Trail can be followed end to end for the period scoredIntroduce and attach the scorecard
6 to 9Followable with labeled gapsIntroduce, naming the partial checks and their years
3 to 5Records exist but rarely joinIntroduce only if the sponsor is comfortable discussing the gaps
0 to 2Too little knownAsk the sponsor to involve project controls first

The record chain page shows which key each check depends on, and the missing-context comparison shows what a reviewer loses when a check fails. The certifier's side of the cycle is covered on the pay application review page, and the finance side of unexplained adjustments resembles accounts payable exception handling.

Owners, sponsor and open questions

For recent work, check 1 rarely stalls the call. The March 2026 move of Autodesk's construction products under the Forma name did not relocate project files, according to Autodesk, so a 2022 job should still be found in the same place. Scoring "superseded revisions kept" as pass matters because version comparison in the Docs viewer only works when the earlier version still exists; a platform that keeps just the current model leaves a reviewer nothing to set against the claim. Check 2 is scored the same way whether the estimator measures with Forma Takeoff or by hand on PDFs.

The design manager answers check 1, the estimator check 2, the project controls lead checks 3 to 5 and finance check 6. The CEO, or the owner in an owner-run contractor, authorizes a licensing discussion. If an ERP replacement is planned, note the date and use the ERP replacement handoff checklist, since claim history and adjustment notes are easily left behind in a cutover.

Confirm 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 never handle raw records. Other system guides sit 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 scores 6 or more for a defined period and its commercial lead will take a call, register as a partner, confirm it against who qualifies and read the program terms, then send the scorecard with the introduction.

  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 a partner try to estimate how often double counts happen?

No. The scorecard asks whether records exist and join, not how often errors occur. Frequency is something SourceX can only judge after review, and a partner's guess would mislead both sides.

What if the contractor scores well on recent projects and poorly on old ones?

That pattern comes up often. Score the period the contractor wants to discuss, and write the year each pass begins. A clean trail from 2021 onward is a clear, useful answer.

Who should answer the checks?

The project controls lead answers most of them, with the design manager for model history and finance for ERP adjustments. All answers come from folder structures, naming rules and settings, not from opening files.

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