Three ways to run a meet

There is no single "FinishLine setup." The app is a set of positions that devices can occupy, and which positions you fill is a choice you make per meet, based on how many people showed up and how much the times need to be trusted.

Three shapes cover almost everyone. They are not tiers or upgrade paths. They are different answers to different problems, and it is normal to run more than one of them in the same season. The first shape comes in two versions, and choosing between those two matters more than most people expect.

The shapes at a glance

The account column is the one people misread. Only the coordinator needs a subscription. Everyone who joins with a join code joins as themselves, with no sign-up, on whatever phone is in their pocket. The solo shape needs no account at all.

The tradeoff nobody tells you about: accuracy costs time

The turnaround column is the one to read carefully, because it is the axis that decides whether a shape survives contact with a real meet schedule.

More accurate finish capture is slower per heat, and the reason is structural rather than a performance problem to be tuned away. A hand-timed lane result is finished the instant the operator taps: the time already exists, and recording it is a confirmation. A photo-finish result does not exist yet when the runners cross. The camera has captured evidence, and someone still has to read that evidence, finding each crossing on the strip and placing a mark on it before there is a time at all.

So the two shapes fail in opposite directions when you are behind schedule:

• Lane timing turns a heat around in seconds, in parallel, across six people. It buys throughput and pays in reaction error.
• Photo finish removes the reaction error entirely, and pays with a reading step between heats that lands on one device.

Neither is the right answer in general. The right answer depends on how tight your schedule is and how close your finishes are, which is why the last section of this article is about mixing them.

1. Replace the stopwatches and the clipboard

This is the shape most programs start from, because it maps one-to-one onto what they already do. Today a volunteer stands in each lane with a stopwatch, calls a time down the line or writes it on a slip, the slips go in a folder, and somebody types them into a spreadsheet two days later. Every one of those steps stays, except the folder and the spreadsheet.

What actually changes. The volunteer in lane 3 does the same thing they did before: watch the line, press at the torso. The difference is that their device computes the official time itself, as their capture minus the start on a shared clock, and sends a finished result rather than a number to be read out and transcribed. There is no slip, no folder, and no Monday.

It comes in two versions, and the difference between them is worth more than it sounds: whether you put a device at the start. Version 1a is the smaller crew. Version 1b adds one person at the chute and, counterintuitively, is the faster of the two rather than the more elaborate one.

1a. Lane timers only

Nobody needs a device at the start for this. Your starter keeps doing exactly what they do now: raise the pistol and fire it. The only positions that need a phone are the ones that were already holding a stopwatch or a clipboard.

So who starts the clock? The finish crew does, together. With no device claiming the starter position, every lane timer's screen shows a Start button instead of a "waiting to arm" indicator. They each tap it when the gun goes, exactly as they would have thumbed a stopwatch, and the app takes the median of those taps as the official start time for the whole heat.

That is worth a second's thought, because it is strictly better than what a bag of stopwatches does. On paper, every watch carries its own operator's reaction, and each lane's time is wrong by a different amount. Taking the median across the crew throws out the volunteer who was looking the wrong way and the one who flinched early, and hands every lane the same start instant. Six independent errors become one shared, much smaller one.

Where the time goes. Someone still has to put each heat on the wire, and with no start-line device that someone is the coordinator: they load the next heat from the heat sheet and broadcast it to the crew. It works, and for a small meet it is the right amount of machinery. But it means heats get built one at a time, between races, by the person who is also running the meet. Every heat costs a little dead air while its lanes are filled in, and that dead air is serial: nothing else happens during it.

1b. Add a device at the start, and work ahead

Put one person at the chute in the Starting Line role and the meet stops being a sequence of heats. It becomes a pipeline with several heats alive at once, each at a different stage.

The staging device holds a queue rather than a single heat. While heat 2 is on the track, heats 4, 5 and 6 are already built, their lanes already filled in, their rosters already broadcast to the finish crew. The chute works ahead, and the track never waits for it.

Three specific things buy back time, and it is worth separating them because they compound:

• Bibs are resolved before the race, not after. Organizing lane-to-bib assignments, photographing a bib that is hard to read, and flagging a duplicate all happen in the chute while the athletes are standing there waiting. By the time the heat is sent off, each lane timer's screen already shows the bib for their lane. The finish operator never types a number: they capture, glance at a pre-filled confirmation, set the place, and record.
• Building the next heat costs nothing, because it already happened. The dead air between heats in 1a disappears, not because anyone works faster but because the work moved off the critical path.
• The start line never waits on results. When the starter is done with a heat they advance, which retires it from the chute while it keeps collecting results elsewhere. Heat 1 can still be landing lane times on the record keeper's screen while heat 3 is already on the line.

Because someone is marshalling the chute, this is also the only version where you can safely run two heats at once, which is the largest throughput lever in the app and is unmanageable without a person organizing the line.

And it is where the acoustic start lives. Once a device is at the start, it can hear the gun and stamp the real instant instead of relying on the finish crew's median. This is the single best trade in the whole article: it is a genuine accuracy upgrade that costs zero turnaround time, because nothing has to be read or adjudicated afterward. See how the acoustic start works.

True of both versions

Places still come from a human. A hand-timed lane heat does not derive place from the clock. The finish-line judge calls the places and the lane operator records that call, which is exactly the division of labor a paper meet already has. See the finish timer for why the judge is the better instrument on a close finish, and how the record keeper can overrule it either way.

The spreadsheet becomes an export. When the meet ends, results go out as Generic League CSV, Athletic.net / MileSplit, or USATF Junior Olympic, plus any custom format you define. That is the step this shape is really buying back.

Volume buttons matter more than you think. Tell your lane volunteers to rest a thumb on the volume key and never look at the screen. It is the single largest accuracy difference in this shape, and it costs nothing.

Where this shape wins: speed

This is the fastest way to run a meet, and it is worth being explicit about why, because it is the main reason to keep it rather than upgrading everything to photo finish.

The work is parallel and already finished. Six operators each handle one lane at the same moment, and each one's job ends a few seconds after their runner crosses: confirm the bib, set the place, record. There is no reading step, no adjudication, and nothing queued for later. The heat is closed as soon as the slowest of the six taps Record, and every screen resets for the next heat on its own.

Version 1b then goes further, and it does it by a different mechanism worth naming, because it is the mirror image of what makes photo finish slow. Staging moves work to before the race; marking moves work to after it. Anything you can do while the athletes are still standing in the chute is effectively free, because the track is busy anyway. Anything that has to happen after they cross sits directly between you and the next heat.

For a league meet running thirty or forty heats against a schedule, that matters more than the last tenth of a second of accuracy. A shape that keeps the meet on time is worth a great deal, and this is the shape that does it.

What you pay for that speed is honest and unavoidable: six independent human reactions in the data at the finish, plus, in 1a, the crew's median reaction at the start. On a heat decided by half a second, nobody will ever notice. On a heat decided by three hundredths, this shape cannot tell you who won.

2. Build the meet around accuracy

The second shape is for when the times need to hold up: a qualifying meet, a league that publishes standings, or a program tired of a photo-finish argument it cannot settle. Counterintuitively, it needs fewer people than the first shape, not more.

Two human errors get removed, one at each end of the race.

At the start, the starter's device listens for the gun and timestamps the sound itself, so timing runs from the actual report rather than from a thumb pressed after hearing it. That removes roughly 150 to 250 ms of bias that every hand-started time carries. See how the acoustic start works.

At the line, a single device images the finish plane continuously and produces a strip you read crossings off afterward. Nobody is reacting to anything, so nobody's reaction is in the time. Places in a photo-finish heat are ranked by the times read off the strip, because those times are precise enough to sort on. See how the photo finish camera works.

Why it needs fewer people. One photo-finish operator replaces every lane timer at once. Six volunteers become one operator plus a bib collector, and the result is more accurate rather than less. For a short-staffed program this is the shape to reach for, not the fallback.

What this shape costs: the marking step

Fewer people does not mean less work. It means the work moved, and it moved to a place where it happens serially, on one device, between heats.

After the field crosses, the operator has a strip rather than a set of times. Producing results means scrubbing to each crossing on that strip and placing a mark on it, one per lane. Only then do times exist and places get ranked. Two things make this the throughput constraint of the whole shape:

• It scales with lanes, and it is one person doing all of them. In the lane shape, six lanes are six people working simultaneously. Here, six lanes are six marks placed one after another by the same operator.
• It gets slower exactly when it matters most. A strung-out field is quick to read. A bunched finish takes real care to resolve, and a bunched finish is precisely the situation you brought the camera for. The cost peaks on the heats where the value also peaks.

While that is happening the review screen is up, so the device is reading the last heat rather than watching the track. In a meet where heats are sent off quickly, the marking of one heat can still be in progress when the next one is called.

Handing marking to the record keeper

The strip does not have to be read at the finish line. When the photo-finish operator finishes with a heat, the full-fidelity strip is uploaded and attached to that heat, and the record keeper gets a Review button on it: they can open the strip, mark it, and republish the times from their own device. That genuinely decouples capture from adjudication, and it is the right move when the finish line is the bottleneck.

One thing to be clear-eyed about before you plan around it: you have moved the bottleneck, not removed it. The record keeper is already the person fixing bibs, settling contested places, and watching results land for the whole meet. Handing them a queue of unread strips adds serial work to the one device that is least able to absorb it. What that buys you is a choice about when the work happens: the finish line stops holding up the track, and the results lag the meet instead. That is a good trade when results can be published after the last event, and a bad one when you are posting between events or feeding a scoreboard.

A useful middle setting is to mark only what the race actually turned on, usually the win or the one contested lane, and leave the rest of the field for the record keeper. The finish line keeps moving and the interesting call still gets made by the person watching it happen.

And you cannot solve it by adding a second camera. Photo finish is deliberately a single station: one device is aimed at the line and is unambiguously the timing source for every lane, which is what keeps authority clear about where a time came from. Its second device is the bib collector, not a second reader. So the lever you actually have is where the reading happens, plus the one below.

Use it for part of a meet, and the tradeoff mostly disappears. Nothing stops you running lane timers for most of the schedule and photo finish for the events where finishes are actually close. This is the answer to the throughput problem rather than a compromise on it: the sprints are where hundredths decide places and are also a small share of your heats, so you spend the reading time only where it changes an outcome. The distance events, where the field arrives strung out and a tenth of a second decides nothing, stay on lane timers and keep the meet moving.

3. One person, one device, no account

The third shape is not a meet at all. It is a coach at practice, a parent in the stands, or an athlete timing themselves, who wants their times kept somewhere better than a note on a phone.

What you get, at no cost and with no sign-up:

• Both capture methods. Photo finish is not a paid feature. The offline timer can capture a line-scan strip and mark crossings off it exactly like the connected photo-finish position does.
• The acoustic start, too. The solo timer listens for the gun on its own, which matters because it is usually sitting at the finish while the start happens a hundred meters away.
• Your own events and roster. Build them in Setup and every recorded time carries the event, the age group, and the bib, so the times mean something later.
• A record that accumulates. Times are saved on the device and stay there. Filter the results list by bib and you are reading one athlete's season back, which is the honest version of progress tracking.

What you do not get. Be clear-eyed about this before you plan around it:

• One device, no crew. There is no session to join, so no second phone can contribute to it.
• No publishing. Nothing goes to a team page and no family follows along, because there is no account to attach it to.
• No export. Getting results out as CSV requires a signed-in account and a team you own, so a solo record stays in the app.
• No progress chart. There is no graph, no personal-best badge, and no season summary. The record is a filtered list you read. If a chart is what you actually want, tell us at support@finishlinetimer.com.
• One running list, not per-meet archives. Solo results accumulate into a single list rather than being filed into separate meets the way a coordinated meet's results are.

If you only want to watch, you need even less than this. A parent following results from a team that runs coordinated meets does not need the app at all. That is a browser link, no account, no install. See how families follow results.

Moving between them

Roles belong to devices, not to people, and they are picked when a device joins rather than being fixed for the season. A volunteer who leaves at lunch hands their position to someone else. A device timing lane 4 in the morning can be the photo-finish camera after lunch. Nothing about choosing one shape today commits you to it next week.

The practical progression most programs follow:

1. Start solo. Time a practice with one phone. It costs nothing and it teaches the capture rhythm.
2. Run a full meet on lane timers. It is the shape your volunteers already understand, so the only new thing to learn is the app.
3. Put a device at the start. The best value of anything on this list, and the only step here that makes the meet both more accurate and faster. Staging works several heats ahead so the chute stops being dead air, and the same device can hear the gun, which costs no turnaround time at all because nothing has to be read or adjudicated afterward.
4. Add the camera on the events where finishes are close. Not everywhere, and not all at once. It needs fewer volunteers but more time per heat, so introduce it where that time buys you something and keep lane timers on the rest of the schedule.

Choosing, in one line each

• You have plenty of volunteers, a paper process to kill, and a schedule to keep: lane timing.
• Your meet is already running behind by the third event: lane timing with a start line (1b). The chute is usually the real bottleneck, not the finish.
• You are short on volunteers, or the times get published and argued about: accuracy first.
• Both at once, which is most people: lane timing everywhere, photo finish on the sprints, and a device on the gun for all of it.
• It is you, one phone, and a stopwatch you do not trust: solo.
• You just want to see your kid's results: you need a link, not a setup.