Scrim data hygiene: keep practice evidence useful

Teams collect map scores, opening duels, compositions and coach notes, but the spreadsheet often outlives the conditions that made those numbers useful. Scrim data hygiene keeps practice evidence comparable without pretending that every opponent, patch and training goal belongs in one sample.

Define the unit before recording it

Agree what counts as a conversion, failed setup or communication error. Store patch, map, side, opponent level and the stated practice objective beside the result. A round played to test a new default should not be graded like a tournament rehearsal.

Expire evidence deliberately

Mark when a system changed enough to close the old sample. Keep the archive, but remove it from current dashboards. Coaches should also separate observation from interpretation so later reviewers can challenge the conclusion.

The goal is not a perfect database. It is a trustworthy trail from a repeated event to a decision the team can test in the next block.