# Verifiable rewards data qualification scorecard | SourceX

Canonical: https://refer.sourcex.si/questions/does-verifiable-rewards-data-qualify
Last updated: 2026-11-04

Ask about six criteria. Four are gates the company must pass: 50+ full-time employees at peak, documented operating history, rights to license with an authorized contact and, outside the U.S., Canada and the EU, at least 70% of the data in English. Two are scored, because they decide whether the records can support verifiable rewards: record depth (years of the workflow) and linkage (rule, action and outcome tied together). Pass every gate and score well on both, and the company is a strong fit to raise with the owner.

This scorecard is part of the [reinforcement learning with verifiable rewards guide](/guides/reinforcement-learning-verifiable-rewards). For what a checkable workflow looks like in practice, see the [worked freight dispute example](/guides/verifiable-rewards-workflow-example).

## Why a scorecard instead of a yes or no

Verifiable rewards depend on a rule that can mark a result right or wrong. The Tulu 3 paper defines the method as rewarding a model only when a verification function confirms its output is correct. DeepSeek-R1 applies the same idea with rule-based accuracy rewards, requiring answers in a fixed format so a rule can check them. For a business archive, that translates into a practical test: did the company keep the rule, the action and the outcome together, for long enough, with the authority to license them?

Few companies are all yes or all no. A scorecard lets an introducer separate a promising archive from a theoretical one without asking for a single record.

## The six criteria

| Criterion | Type | Question to ask | Who answers |
|---|---|---|---|
| Company size | Gate | Did the company have 50 or more full-time employees at its peak, not counting contractors? | Owner or HR |
| Operating history | Gate | Is there a documented operating history behind these records? | Owner or CFO |
| Rights and authority | Gate | Does the company control the records, and who can authorize a licensing discussion? | Owner and counsel |
| Record depth | Scored | How many years does the workflow cover, and roughly how many items a year? | Controller or COO |
| Linkage | Scored | Are the rule in force, the action and the final outcome tied together by reference? | Controller or process owner |
| English share | Gate where relevant | Outside the U.S., Canada and the EU, is at least 70% of the data in English? | Owner or IT |

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.

## Strong, borderline and weak fits

Linkage is the criterion that most often decides the outcome, so it has the most detail below.

| Criterion | Strong | Borderline | Weak |
|---|---|---|---|
| Record depth | Five or more years of one workflow, consistent volume | Two to four years, or a system change midway | Under two years, or only current-year data |
| Linkage: supporting documents | Attached to the transaction itself | Stored in a shared drive with a reference number | In inboxes or paper files |
| Linkage: rule in force | Policies and limits kept with effective dates | Current version only, but changes logged | Overwritten with no history |
| Linkage: approvals | Named person and timestamp, distinct from preparer | Named but sometimes the same person | Shared logins or no approval record |
| Linkage: outcome | Reversals, credits or reopenings linked to the original item | Outcomes recorded but matched by date or amount | Outcome not recorded |
| Rights | Company owns the records; counsel sees no blocking contract terms | Some counterparty terms need review | Records held or owned by a third party |

Illustrative scoring. A fictional 600-person medical supplies distributor reports eight years of customer pricing overrides, each attached to an approved price exception form with a named approver, a policy table with effective dates, and credit notes linked to the original invoice. All gates pass, depth is strong and linkage is strong on four of four lines: raise it with the owner. A fictional 140-person engineering firm with three years of change orders, approvals by shared login and no outcome field passes the gates but is borderline on depth and weak on linkage: note it honestly and let the owner decide whether to proceed.

## Reading the result honestly

- **All gates pass, depth and linkage mostly strong:** a candidate worth introducing if the owner opts in. Describe the answers plainly in the introduction.
- **Gates pass, linkage mixed:** still worth a conversation, but say which links are missing. The [evidence gaps analysis](/questions/verifiable-rewards-evidence-gaps) shows how to word that.
- **Any gate fails:** stop. A company below 50 full-time employees, without rights, or outside the geography rule is not eligible, however good the records.

Scores are a screening aid. They do not estimate value, predict acceptance or imply that any buyer wants a particular workflow. What stays unknown until SourceX reviews it: rights to the records, which entities and years are in scope, how personal and counterparty details are de-identified, and whether any buyer wants the record type. Partners collect answers and never handle ledgers, forms or exports.

## Asking the questions without making it an audit

Ask the gates first, briefly, so you do not spend an hour on records a company cannot license. Then ask depth and linkage as curiosity about how the workflow runs: "When someone approves a price exception, where does the approval live?" sounds like interest; "Please confirm your approval controls" sounds like an audit and closes the conversation.

Before raising licensing, disclose that you are a SourceX referral partner and may receive a reward, paid separately by SourceX and never deducted from the company's payout. Sign the Channel Partner Agreement before submitting anything. The [company qualification checklist](/resources/company-qualification-checklist) covers the baseline in more detail, the [introducer guide to operational data licensing](/guides/a-business-introducer-guide-to-operational-data-licensing) explains the wider process, [why finance data is valuable](/proof/why-finance-data-is-valuable) gives background, and [customer referral versus partner programs](/questions/customer-referral-program-vs-partner-program) explains where this program sits.

## 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.

When a company passes every gate, scores well on depth and linkage and the owner agrees, [register as a partner](/register), confirm it on [who qualifies](/who-qualifies) and read the [program terms](/terms).

## Sources

- https://refer.sourcex.si/terms
- https://arxiv.org/abs/2411.15124
- https://arxiv.org/abs/2501.12948
