Evaluation-only vs training license: which is lower risk?

Which is lower risk, an evaluation-only license or a training license?

Evaluation-only is usually the more cautious choice. The buyer uses your records to measure how a model performs, not to teach it, so the concern that your material becomes embedded in a model is smaller. Training licenses are typically broader and raise more questions about retention and deletion.

Neither is risk-free, and neither is automatically available. SourceX deals are typically exclusive for AI training for an agreed term, so an evaluation-only structure is a narrower use that a cautious owner can raise and discuss with SourceX. SourceX does not train AI models; buyers do.

What is the difference in plain terms?

Training data is used to adjust a model's behavior. Evaluation data is held back and used to check whether the model does a task correctly. Records that show real tasks with known outcomes, such as resolved tickets or approved requests, are useful for both purposes, and a license can name which one is permitted.

Side-by-side comparison

Value comparisons are qualitative. No price is implied; pricing is agreed between the company and SourceX before buyers review.

When does an evaluation-only license win?

Choose or propose it when:

• Leadership is nervous about any content shaping a model, but is open to testing use.
• The records are sensitive, though lawfully licensable, and the company wants the tightest possible footprint.
• Contracts with clients allow limited analytical use but not wider training.
• The company wants to learn how the process works before a broader license.
• A narrow, time-limited, auditable use is easier to explain to the board; see the stakeholder objection map.

When does a training license win?

Choose it when the company wants the broadest commercial outcome, has cleared rights for model-shaping use, and accepts an exclusive license for AI training for an agreed term. It matches how SourceX deals are typically structured.

Questions to ask for either structure

1. What exactly is the permitted use, in the contract's own words?
2. What happens to the data at term end: return, destruction or certification?
3. May the buyer share the data with affiliates, contractors or other model teams?
4. What retention does the buyer keep for audit or reproducibility?
5. Is the use exclusive, and for how long?
6. What redaction applies, and who approved it?

Written restrictions on use matter because the FTC's staff guidance says companies that promise not to use customer data for undisclosed purposes, such as training or updating models, must keep those promises (FTC staff post, January 2024). That post concerns consumer data and is staff guidance, not a rule. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

Illustrative example: one company, two structures

Illustrative and fictional. A 150-person IT services firm holds eight years of resolved support tickets and change approvals. Its CFO is open to a payment but its general counsel worries about client-derived content.

Under a training structure, the firm would grant an exclusive AI-training license for an agreed term over a redacted ticket set. Under an evaluation-only structure, it would grant a narrower right to use a smaller, curated subset to score models, with return or certified destruction at term end.

The counsel's checklist differs. For training, she focuses on exclusivity, downstream use and what redaction removes. For evaluation, she focuses on how long the buyer may keep the set, who may access it and how deletion is certified. Both need the same rights review first: the firm must show it created the records and that client contracts allow licensing.

Decision rule: the three-gate test

Run any proposed structure through three gates, in order.

• Rights: can the company show it owns or may license the records, including client and employee terms?
• Comfort: does the sponsor accept the exposure that this use implies, in writing, after counsel review?
• Closure: are the end-of-term steps (return, deletion, certification) specific enough to verify?

If a gate fails, fix it or choose the narrower structure; if rights fail, neither structure works.

What other risks do both structures share?

• Subpoena and legal process: see whether licensed data can be subpoenaed from the buyer.
• Prior incidents: see whether a company with a breach can still license.
• Changing law: see what happens if AI law changes after you license.
• Who to tell: see who to notify before licensing data.

How does SourceX fit?

SourceX manages the process for either structure: inventory, rights review, price and terms, buyer review, delivery and payment. The company receives one all-in price with SourceX's fee included, and nothing is binding until it agrees price and terms and signs. Redaction rules are agreed before any work begins, and data is delivered only after an executed agreement and the company's authorization.

How should a partner raise this?

If an owner is hesitant, do not argue; say that narrower uses exist to discuss with SourceX and leave it there. Never promise that a buyer will accept an evaluation-only structure. The partner reward is a share of SourceX's fee and is paid only after the buyer pays; it never changes the company's price.

Next step

If a company you know wants a more cautious structure, register as a partner and make the introduction, or have the sponsor raise the question at sourcex.si/apply. The referral earnings calculator shows how the published reward formula works, and no reward is guaranteed.