This contents list is part of benchmark contamination in LLMs. The main guide explains why a private archive is not automatically clean; this page is the practical inventory of what a company puts in front of a review to show how clean its candidate tasks are.
The packet at a glance
| Order | Document | What it shows | Who prepares it | When |
|---|---|---|---|---|
| 1 | Cover sheet | Record type, years, rough volume, systems, owner | Company, from answers an introducer can collect | Before or at the introduction |
| 2 | Task specification | What a model would receive and what counts as the right output | Operations lead | After a discussion starts |
| 3 | Provenance worksheet | One line per candidate task: dates, systems, recipients, public-twin result | Records or operations team | After a discussion starts |
| 4 | Exposure register | Every route by which records left the company | Legal or operations | After a discussion starts |
| 5 | Outcome check | The exact rule a task must pass to stay in the set | Operations lead | After a discussion starts |
| 6 | Exclusions log | Tasks removed, with reasons | Records team | During preparation |
| 7 | Rights notes | Ownership, vendor and client restrictions | Legal | Before the rights review |
The structure borrows from dataset documentation practice. The Datasheets for Datasets proposal asks creators to record a dataset's composition, collection process, recommended uses and distribution so that others can judge it; this packet asks the same of a candidate task set before anyone sees it.
Document by document
1. Cover sheet
One page, metadata only: which workflow produced the tasks (for example, escalated support cases closed with a resolution), the years covered, a rough count, the system of record and the named owner. This is the only document an introducer can help with, because every field is an answer, not a record.
2. Task specification
The input a model would receive, such as the case as first submitted, and the expected output, such as the resolution code and the fix applied. It also names the reference material in force on the case date: the product version, the policy or the runbook revision. Without that version, the right answer may have changed since.
3. Provenance worksheet
One row per candidate task, with five columns: creation date, systems that held it, outside recipients, public-twin search result and an exposure band (no twin found, near-topic page, shared with a named recipient, quoted publicly). The bands follow the benchmark rule of thumb in the BIG-bench documentation: assume anything online without a canary marker may have been seen.
4. Exposure register
A list of routes rather than tasks: outsourced support vendors, resellers, industry data pools, acquired businesses, public help pages and community forums. Each line says which record types the route touched and since when. Pools deserve their own line; see data shared with an industry benchmark consortium.
5. Outcome check, stated exactly
One sentence a reviewer can apply mechanically. For example: a task passes if its recorded resolution code matches the case system by case ID, its creation date is known, and a phrase search of the company's public pages and named recipients' copies finds no matching case text, product serial or customer wording. Objective, checkable answers are what make tasks usable for evaluation; LiveBench, for instance, scores answers automatically against objective ground-truth values.
6. Exclusions log
Every task removed and why: no creation date, outcome never recorded, near-twin found, shared with a vendor. The log lets a reviewer audit what remains instead of trusting it.
7. Rights notes
Who owns the records, which vendor contracts allow reuse and which client agreements restrict sharing, with the CEO named as the signer. These feed the rights review; they are not a legal opinion.
An Illustrative cover sheet
Illustrative and fictional. A 300-person B2B software company considers its escalated support cases as evaluation material.
| Field | Entry |
|---|---|
| Workflow | Escalated support cases, each closed with a resolution code and a fix |
| Years | 2018 to 2025; creation dates kept throughout |
| Rough volume | About 9,000 escalations |
| System of record | Help desk, with fixes linked to engineering tickets |
| Known exposure routes | An outsourced tier-1 vendor since 2022; a public knowledge base |
| Version reference | Product release number recorded on each case |
| Owner | VP of Customer Support; the CEO signs |
Nothing on that sheet is a record. It tells SourceX enough to decide whether the next six documents are worth the company's time.
What the packet does not settle
The packet shows how carefully the company has described its tasks. It does not prove that no model has seen them, it does not say whether a buyer wants them, and it does not set a price. How evaluation-only use is licensed, and how it differs from training use, is covered in evaluation-only data licenses. For what professional-task evaluations look like from the buyer side, see what GDPval is.
Before assembly even starts, the company has to qualify: 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. The qualification scorecard helps decide that, and the evidence gaps analysis shows how to describe a document the company cannot complete. Other record types are listed under data types.
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 company you know could fill in the cover sheet today and name who would prepare the rest, register as a partner, check who qualifies and read the program terms before you introduce its owner.