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
| Check | Area | How to check at metadata level | Pass (2) | Partial (1) | Fail (0) |
|---|---|---|---|---|---|
| 1. Model history | Coverage | Ask which platform holds models, from what year, and whether superseded revisions are kept | All revisions kept for every project in the period | Kept for recent projects, or archived without old versions | Only current models kept |
| 2. Export revision | Linkage | Ask how quantity exports are named and whether they state the model revision | Revision in every export name or header | On some projects only | Never; names like "final" |
| 3. Claim sheet revision column | Linkage | Ask whether each claim line records the model revision it came from | Column used on every project | Used on some projects | No such column |
| 4. Monthly sheets kept | Timestamps | Ask whether each month's claim sheet is saved separately or overwritten | One sheet per month per project | Saved for some years or projects | Overwritten in place |
| 5. Claim number on the sheet | Linkage | Ask whether the ERP claim number is written on the matching claim sheet | Always | Mostly | Never |
| 6. Adjustment reason | Outcomes and gaps | Ask whether ERP reductions carry a note or a reference to the measurement that caused them | Note or reference required | Sometimes written, or kept in email | Amount 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?"
| Answer | What 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.
| Check | Answer given | Score |
|---|---|---|
| 1. Model history | All revisions kept since 2021; earlier BIM 360 projects archived without old versions | 2 |
| 2. Export revision | Revision in export names on hospital and lab projects only | 1 |
| 3. Claim sheet revision column | Added in 2023, used on most projects since | 1 |
| 4. Monthly sheets kept | One sheet per month since 2020 | 2 |
| 5. Claim number on the sheet | Mostly | 1 |
| 6. Adjustment reason | Usually in email to the certifier, sometimes an ERP note | 1 |
| Total | 8 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
| Total | Reading | What the partner does |
|---|---|---|
| 10 to 12 | Trail can be followed end to end for the period scored | Introduce and attach the scorecard |
| 6 to 9 | Followable with labeled gaps | Introduce, naming the partial checks and their years |
| 3 to 5 | Records exist but rarely join | Introduce only if the sponsor is comfortable discussing the gaps |
| 0 to 2 | Too little known | Ask 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.