What European rules ask of the people preparing the data

The obligations that reach data teams are mostly about evidence. Not only that a dataset is suitable, but that you can show how you established it.

Records to keep from the start

• Where each part of the dataset came from and on what terms
• The collection design and the groups it set out to represent
• Known gaps and the reasoning for accepting them
• Bias checks performed and what changed as a result
• Annotation guidelines and the versions used for each batch

Write it as you go

Reconstructing sourcing decisions a year later is slow, incomplete and often impossible. A short record written at the time of each decision costs little and holds up.

It travels with the data

Documentation should move with the dataset between teams and vendors. A dataset without provenance becomes unusable for regulated applications.

Practical checklist

• Define the acceptance rule before any volume starts
• Review a small pilot before committing the full budget
• Track errors by category, language and reviewer
• Keep consent, source notes and version history with the files

Before you ask for a quote

A clear brief saves days. Share a sample file, target language or region, expected volume, deadline, quality threshold and any privacy restrictions. A supplier can then price the work on real effort rather than assumptions.

• Which languages, markets or user groups must be represented?
• What format does the final file need to arrive in?
• Who will approve ambiguous cases during the pilot?