Dataset quality guide
How to audit an annotation-vendor delivery
Use a repeatable local acceptance check for vendor data.
Turn a brief into checks
Translate class names, geometry rules, and split expectations into an acceptance checklist before delivery arrives.
Sample failures
Inspect representative findings rather than accepting a summary score without evidence.
Return a repair list
A reproducible local report makes disagreements about scope and corrections easier to resolve.
Decide what blocks training
Set the decision rule before reading the report. Invalid annotations, missing media, split leakage, and incomplete coverage should block a training run until a reviewer resolves or deliberately accepts them. Less severe findings can still matter, but they need a documented disposition instead of being buried under a single aggregate score. The matching solution page explains which local checks apply to this dataset shape and why the result is limited when evidence is unavailable.
Keep evidence with the dataset revision
Save the local report, quality profile, and repair manifest beside the dataset version that entered training. That record lets a teammate reproduce the same finding, compare a later export, and distinguish a data change from a model change. A report is evidence from configured checks at a point in time. It is not a guarantee of model performance or an independent certification.
Repeat the check after every material change
Run the same local check again after relabeling, changing class mappings, moving images between splits, or accepting a vendor correction. Rechecking is more useful than carrying a historical score forward because the score only describes the records and coverage that were examined. For scripted review, keep the quality command and threshold in the training repository so a new dataset revision receives the same gate.
Check your dataset locally
Use the matching local check before starting a training run.