Build a dataset quality card
Updated 4 October 2026
The short answer
Use a quality card to show context, actions and outcomes without sharing records.
Build a dataset quality card
Before adding more systems to a proposed licence, describe what someone could learn from the systems already in scope.
Complete this quality card for one recurring workflow:
- Task: What work was being done?
- Starting context: What information was available?
- Actions: What steps or changes are recorded?
- Outcome: Is the result or resolution retained?
- Links: Which identifiers connect the records?
- Coverage: What period and count does this include?
- Gaps: What is missing, duplicated or inconsistent?
- Preparation: What would need to be excluded or cleaned?
Write a description, not a real customer example. A useful sentence is: We retain support tickets with status history and linked resolution notes. An unsupported sentence is: Our archive contains complete outcomes for every customer.
For code, describe whether a change links to an issue, review and test result. For media, use the same card to describe format, metadata, capture context and rights records. For text, describe provenance, structure and coverage.
Mercor says compensation depends on volume, connected tools and data depth. That is a reason to document useful connections, not a promise that adding any extra tool will increase a quote.
Your output should let a buyer ask a precise next question without seeing confidential records.
Sources and limitations
Programme descriptions can change. The signed agreement controls the price, licensed scope and payment conditions. These worksheets help prepare questions and do not certify rights or promise a deal.
- Mercor data programme, checked 3 October 2026
Related guides
Review your relevant buyers
Use confirmed facts and keep restricted records outside your proposed scope.
Start a free assessment