Running intervals versus gym interval timers
Short answer
A gym interval timer counts time and speaks a countdown, while a running interval session has to know how far you have run as well as how long you have been running. That is why a Tabata app can say go and rest but cannot end a repetition at four hundred metres, and why the useful cue in a running session is an instruction about what to do next rather than a number read off a clock.
A stopwatch cannot end a repetition at four hundred metres. A gym interval timer counts seconds, which is its entire model of the world, and for a circuit on a mat that is enough. A running interval session needs a second axis, because a repetition can end at four hundred metres instead of at ninety seconds, and because ninety seconds standing at a crossing is not ninety seconds of work. The two categories look alike in a search result and behave nothing alike once you are moving.
What a gym timer actually knows
One number: the clock.
How long the current block has been running is the whole of it. Every spoken line a gym timer produces comes from that number and from the block names you typed in beforehand.
Both listings say so directly. Seconds Pro states that it "Speaks your interval names & can provide warning for upcoming intervals" on its App Store listing, fetched 2 August 2026. The Float Tech app Interval Timer, HIIT Timer promises "Voice or beep guides for every workout" in its App Store description, fetched 2 August 2026, and that description mentions no distance and no pace anywhere in its feature list.
That is not a criticism. For burpees the clock is the whole truth, and the decisions a timer can make from it are short and complete:
- This block is over
- Start the next one, which is called work, or rest, or round three
- There are five seconds left, so brace
- Every block in the list has now run, so the session is finished
None of those need to know where you are or how fast you are going, which is exactly why none of them can close a repetition at a distance.
What a running repetition needs to know
Three inputs, not one. Distance covered and moving time, and then whether you are moving at all. A paused run should freeze the repetition; it must not run down while you stand there.
Four hundred metres is four hundred metres whether it takes you seventy seconds or ninety five, and converting it to a duration turns a track session into a different workout, which is the obvious half. Moving time matters more than people expect. If the session advances on wall clock time, a red light in the middle of a three minute tempo block eats the block. You planned three minutes of work and ran two.
The calls a running session has to make
Five moments deserve a spoken line. A countdown is not one of them.
- Entering a work repetition, where the instruction is to go harder
- Entering a recovery, where it is to back off
- Entering the final work repetition, which changes how much you are willing to spend
- The plan finishing, so you know the remaining running is unstructured
- Pause and resume, so you know whether the session is still counting
Wording decides whether the line is usable. "Interval three of eight" gives you a position in a list you cannot see, while "Speed up" tells you what to do with your legs, and the cue has to survive being heard once, at effort, with music underneath it.
Runflake takes the second approach and keeps the vocabulary small. Every word the coach can say is a fixed string written in the app's source, and there is no generated or improvised wording. The interval calls are the whole set: "Speed up." at a work repetition, "Last interval." at the final one, "Recover." at a recovery, "Cool down." at the cooldown, and "Intervals done." when the plan finishes. Entering the warm-up says nothing at all, because it lands immediately after the start of the run.
The second problem is collision. A repetition boundary and a kilometre split can land in the same second, and speaking both turns into noise. The fix is a rank. Cues are ranked and a more urgent one cuts off a less urgent one already playing, so pause, resume and finish outrank everything; turn and interval calls outrank the kilometre readout; pacer talk sits at the bottom. That ranking settles collisions between cues during the run. The run ending is a separate moment, and what you hear then is a short finish tone.
For which announcements are worth hearing at all, see what running apps say out loud.
Distance based repetitions versus timed rounds
Both axes are standard training. One minute hard with two minutes easy is a timed session. Eight by four hundred metres is a distance session. A gym timer can express only the first.
| Session shape | What ends a repetition | What must be measured | Where it goes wrong |
|---|---|---|---|
| Tabata rounds, 20 on and 10 off | Elapsed seconds | A clock | Nothing. The clock is exact and always available |
| Track repeats, 400 m fast and 200 m easy | Distance covered | Distance and moving time | If the position signal stalls, the repetition never closes |
| Tempo blocks, 5 minutes hard and 3 minutes easy | Moving time | Moving time, not wall clock time | If it counts wall clock time, a stop at a crossing shortens the work |
| Mixed, timed warm-up with distance repeats | Both, block by block | Both axes at once | A tool that supports one axis silently converts the other |
The last row is the practical test. Most real sessions are mixed: a timed warm-up, repeats measured in metres, then a cooldown in minutes, and a running interval engine can support both axes because it already holds both numbers.
A gym timer supports one, so the only way to load a track session into it is to guess how long four hundred metres will take you, which is the number you were trying to find out.
Coaching apps in the running category run intervals through their own audio layer, and their documentation is the cheapest place to see what that layer covers. Runna lists its outdoor cues as "Get ready to start (there's a visual countdown, but no verbal countdown)", "Start running", "Pace alerts (speed up / slow down)", "Pausing / Resuming", "Halfway information", "Lap x completed in x time" and "Workout completed in x time", in Setting Up and Managing Your Audio Cues, fetched 2 August 2026. Two lines there are worth reading twice. The countdown before the start is visual only, with no spoken numbers, in an app built for runners. And the same page warns that with the Intervals/Tempo on Track setting on, "interval or tempo laps won't automatically end and you won't receive audio guidance", so you close each lap by hand. Ending a lap and speaking about it turn out to be one feature rather than two: where the app cannot decide the boundary, it stops speaking instead of announcing a boundary it has not found.
What is deliberately not announced
Restraint is the harder half. Your attention has a budget, and every line that does not change a decision spends it.
- No countdown into a repetition boundary, which in a gym set tells you to get into position, but on the road you are already running, so it costs attention and returns nothing
- No number when there is no basis for it. If there is not enough recent data to compute a pace, saying a pace anyway is worse than silence
- No backlog. If several boundaries pass at once after a gap, reading them all in sequence puts you further behind, not closer to current
- No whole run average at a repetition boundary. That number belongs to the kilometre readout
Timing is part of restraint. In Runflake, a cue that has been waiting more than 12 seconds is thrown away instead of being read late, on the reasoning that a late announcement is a wrong announcement.
Being told to speed up a quarter of the way into the recovery is the opposite instruction, and that is not a small error.
In Runflake each category of cue has its own switch, so a runner can silence splits but keep interval calls, or keep pause announcements only. The other half of restraint belongs to you, and that granularity is worth looking for wherever you train, because on a track session splits at every kilometre are noise and the repetition boundaries are the only structure that matters. A walkthrough of which switches to set for which session is in how to set up running audio cues.
Choosing between the two categories
Pick by what ends your repetitions, not by which app has more features.
- Every repetition is defined in seconds and you are not covering groundUse a gym interval timer. Circuits, Tabata, EMOM and strength supersets are pure clock work, and a dedicated timer is faster to program than a running app pressed into that role.
- Any repetition is defined in metresYou need a running app. No clock can close a four hundred metre repeat, and converting it into an estimated duration changes the session. This is the decisive test.
- Repetitions are timed but you are running outdoorsPrefer a running app that advances on moving time. A gym timer counts the ninety seconds you spent waiting to cross a road as part of your work interval, and you never see that it did.
- You want the interval structure and the run recorded togetherUse one tool. A gym timer running alongside a tracking app shares no reference with the recorded track, so afterwards you cannot tell which part of the trace was the fast bit.
If you are still unsure, run the test yourself. Take eight repeats of four hundred metres and try to load them into a gym timer. The point where you have to type in a guessed duration is where the two categories separate, and no amount of extra features closes that gap.
Common questions
- Can a gym interval timer end a repetition at 400 metres?
- No. A gym interval timer advances on elapsed seconds, so the only thing it can use to close a block is the clock. Ending a repetition at a distance requires the app to be measuring how far you have travelled, which is a different category of tool. If your session is written in metres, a stopwatch based timer cannot run it for you.
- Why should an interval cue not count down the last seconds of a repetition?
- Because you cannot act on it. In a gym set the countdown tells you to brace for the next movement, which is useful. On the road you are already running, and the only decision left is whether to change effort. An instruction such as recover or speed up carries that decision in one short phrase, while three, two, one carries none of it.
- What happens to a distance based repetition if the position signal drops out?
- The measured distance stops growing, so the repetition does not reach its target and does not end on its own. A gym clock never meets that failure, because it does not depend on a position signal at all, and moving time is only a partial safeguard, since it is credited from the same position data. This is the main practical risk of distance targets, and it is why any session built on them needs a way to end the workout by hand while you are still running.
- Is elapsed time the same thing as moving time in an interval session?
- No, and the difference decides whether your session is honest. If you stop at a crossing for ninety seconds and the app counts that against a three minute work block, you have run a much shorter repetition than you planned. Advancing phases on moving time rather than wall clock time keeps the work interval the length you intended.