Every result ends up as a time attached to an athlete. What differs between a lane heat and a pack heat is when that attachment happens: before the gun, or after the finish.
Lane heats: pre-collect
Athletes are assigned to lanes during setup, before the race is run.
Because the assignment already exists, each lane's finish timer knows whose time it is capturing the moment it captures it. Results come together as the heat runs, and by the time the last runner is across, the heat is essentially complete.
This is the right choice when lanes are assigned anyway: sprints, hurdles, relays, and anything run out of blocks in a seeded field.
Pack heats: post-collect
Runners start as a pack, with no lanes to assign.
The work splits across two people:
- One operator taps each crossing. They record the finish order and the times, and they never see or enter a bib. Keeping that job single-purpose is what lets one person sustain a fast pack.
- A second operator collects bibs afterward at the chute, or from an expected-athlete list, and matches them to places.
This is the right choice when the field is too large for lanes or the event does not use them: distance races, cross country, and open community events.
The comparison, side by side
| Lane heat | Pack heat | |
|---|---|---|
| Bib attached | Before the gun | After the finish |
| Finish devices | One per lane | One tapping, one recording |
| Knows the field in advance | Yes | Optionally |
| Handles a walk-up entrant | Poorly | Naturally |
| Result complete at | The finish | Bib collection |
An unmatched time is still a valid result
This is worth stating plainly, because it is what makes the post-collect model safe: a crossing with no bib on it is recorded anyway, as a real time with an unknown identity.
Nobody has to hold up the meet to chase down a runner who lost their bib. The time is captured, it sits in the results as unidentified, and the record keeper attaches an athlete to it later, even after the meet has ended. The time is never the thing at risk. Identity is recoverable; a missed capture is not.
Practical consequence: never delay a tap to figure out who someone is. Capture first, identify second. The system is built assuming you will.
Where the expected-athlete list helps
If you attach the set of athletes expected in a pack heat, the bib recorder gets autocomplete as they type, and anyone on the list who never finished can be marked as a no-show in one step rather than tracked down by hand.
It is optional. Without it the pack is a pure walk-up, every bib is typed, and there is no no-show backfill. With it, the recorder's job gets meaningfully faster. Building the list is what a heat sheet is for.
Did this answer your question? If something here is wrong, missing, or out of date, tell us at support@finishlinetimer.com and we’ll fix it.