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: bibs before the race
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: bibs after the finish
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 to one thing is what lets a single person keep up with 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.
It does assume the field is small enough for one recorder to identify at the chute, which is about 30 finishers in a heat today. Past that the times are still captured, but the finishing order and the bibs stop keeping up with each other. See field size in a pack heat.
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 |
| Field known in advance | Lanes assigned ahead, any can be left open | Optional |
| Field size | Limited by your lane count | No lane limit, about 30 finishers in practice |
| A walk-up entrant | Any open lane, up to the gun | Any time, no cutoff |
| Result complete at | The finish | Bib collection |
Walk-up entrants deserve a note, because lane heats handle them better than the table suggests. Drop them into any open lane and go. The bib does not have to be on your roster, and it does not have to be filled in at all: an unfamiliar number is flagged so you notice it, but it neither blocks the heat nor stops the start line from sending it. What a lane heat genuinely cannot do is take more runners than you have lanes, or take one after the gun has fired. A pack heat has neither limit, though how many finishers one recorder can identify is a ceiling of its own.
Collecting at the start is optional, and usually worth it
Nothing requires you to gather bibs at the starting line. A lane heat can be set up with bibs typed in at the line, and a pack heat can run as a pure walk-up where every bib is collected after the finish. Both work.
But the starting chute is almost always the calmer place to do it. Athletes are standing still, in order, waiting for a start that happens when you say it does. Nobody is under pressure. The finish is the opposite: runners arrive on their own schedule, they need to be moved off the track for the next heat, and whoever is collecting bibs is competing with that clock.
So the question is less "where do the bibs get collected" than "which end of the race absorbs the work." Moving as much of it as you reasonably can to the start makes the finish faster, and the finish is the end that cannot wait.
What this looks like in practice:
- In a lane heat, assign bibs to lanes at the chute rather than at the finish. Each lane's timer then already knows whose time it is capturing, and there is nothing to collect afterward at all.
- In a pack heat, attach the expected runners before the gun. Bibs are still collected after the finish, but the recorder gets autocomplete instead of typing every number cold, and anyone who never finished can be marked a no-show in one step.
- Either way, photographing bibs at the chute is faster than typing them, and leaves a picture behind for anything that needs sorting out later.
The tradeoff is that work done at the start is work done on a field that can still change. A scratch, a lane swap, or a late entry means revisiting an assignment you already made. That is a real cost, but it is a cost paid in a calm moment rather than a frantic one, and every field remains editable right up to the gun.
Rule of thumb: if you have a spare volunteer and they are not sure where to stand, put them at the starting chute with bibs. It is the cheapest place in the meet to buy time.
An unmatched time is still a valid result
This is what makes collecting bibs after the race safe: a crossing with no bib on it is recorded anyway, as a real time with an unknown runner.
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. Who ran can be sorted out afterward; a time you never captured cannot.
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 pure walk-up, every bib gets typed in, and there is no list to check off the runners who never appeared. 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.