Group duplicate shipment records before creating training: What control directly addresses this evaluation

Duplicate or related shipment records must be grouped before splitting, preventing information leakage into held-out evaluation.

The question

Preparing for AIGP? Take the free 5-min readiness quiz →

1. Tune the scheduler threshold using the current held-out predictions.

   Threshold tuning cannot repair information leakage because duplicate shipment information has already crossed the evaluation boundary.
2. Increase the held-out sample size without changing the split procedure.

   A larger random split can still place related records across partitions, preserving leakage and overstating held-out performance.
3. Add a second random test split to confirm the reported scheduling accuracy.

   Repeated random splitting can reproduce the same duplication problem unless related records are grouped first.
4. Group duplicate shipment records before creating training and held-out partitions. ✓

   Grouping related records before splitting keeps duplicate information within one partition and protects the independence of evaluation.

How to remember it

Duplicate or related shipment records must be grouped before splitting, preventing information leakage into held-out evaluation.

More Understanding How to Govern AI Development questions

• Evaluate it on a held-out set excluded from training: Which evaluation design best distinguishes learning from →
• Set subgroup acceptance criteria and investigate: Before deployment, which evaluation decision is most →
• Estimate costs and capacity before comparing: Which next decision best supports a defensible threshold? →
• All 426 Understanding How to Govern AI Development questions →