Track

A track is a named subset of a hackathon with its own rubric and prize pool, used to keep judging apples-to-apples within a set of comparable projects. Tracks may be theme-based (Education, Health, Inequality, Energy and Environment as in HackDuke's Code for Good), technology-based (Best Use of X), or audience-based (Best First-Time Hacker submission). NASA Space Apps publishes twenty to thirty Challenge Statements grouped into ten award categories annually; ETHGlobal uses partner bounties as parallel evaluation tracks; HackDuke runs four social-good tracks with majority-novice sub-prizes inside each. See fair-judging and format-taxonomy.

Tracks solve the cross-domain bias problem by refusing to make cross-domain comparisons. Each track has its own rubric, its own judges (assigned for domain context), and its own winner; no project is evaluated against work that operates by different conventions. The cost of the track architecture is track imbalance — if one track attracts twenty teams and another attracts three, the prize pools feel mis-calibrated — and its mitigation is publishing track-specific rubrics in advance and sizing prizes to expected participation. See rubric and cross-domain-bias.