1. PaceRunner
  2. Guides

How wide should a Garmin pace target range be?

For reps and tempo work, a range of about 10 seconds per km (16 s per mile), or ±5 s/km around your goal pace, works for most runners: tight enough to mean something, wide enough that GPS wobble doesn't set off alerts all the time. Easy runs need a much wider range, 30 to 40 seconds per km. If alerts still feel jumpy, it's usually because the watch is reacting to instantaneous pace; pace by lap pace instead.

Ranges that work

These are PaceRunner's default ranges: race paces from the Daniels–Gilbert equations as the pace ±5 s/km, easy as a band from about 62% to 70% of VO2max.
SessionRange widthExample, 25:00 5K runner
Easy and long runs30–40 s/km (50–60 s/mi)6:19–6:57 /km (10:10–11:11 /mi)
Marathon pace±5 s/km (±8 s/mi)5:33–5:43 /km (8:56–9:12 /mi)
Threshold or tempo±5 s/km5:11–5:21 /km (8:21–8:37 /mi)
10K pace reps±5 s/km5:06–5:16 /km (8:12–8:29 /mi)
5K pace reps±5 s/km4:55–5:05 /km (7:55–8:11 /mi)
Short reps (200–400 m)±5 s/km, or no targetRun by feel; check the lap time after
RecoveriesNo targetJog or walk

Work out your own from a recent race in the free pace calculator.

Why the alerts feel jumpy

During a workout step with a pace target, Garmin watches compare your pace with the range and alert you when you're outside it. The pace they react to moves second by second with GPS, and GPS pace is noisy: under trees, between tall buildings or on a twisting path it can swing by 20 or 30 seconds per km while you run perfectly evenly. Runners report exactly this, the watch nagging "too slow" then "too fast" on a steady rep (Garmin forum).

  • Too narrow (±2 s/km or less): you're "off pace" half the time, whatever you do.
  • About ±5 s/km: short wobbles still trip it now and then, but a real drift is caught.
  • Too wide (±15 s/km or more on a rep): the target stops meaning anything; a 5K-pace rep and a 10K-pace rep overlap.

Run by lap pace, not the instant number

Lap pace is your average pace since the step began. In a structured workout each step starts a new lap, so lap pace is the pace of the current rep, and it settles after the first 100 meters or so. It's the number to run by:

  1. In the Run activity's settings, edit a data screen and add Lap Pace (keep current pace too, if you like).
  2. Use the workout's own screen for the target range, and glance at lap pace to decide whether to adjust.
  3. Ignore the first 15 to 20 seconds of a rep: lap pace is still settling, and current pace is at its least reliable as you accelerate.

Other ways to tame the noise

  • A foot pod. Pace from a foot pod or the watch's accelerometer, calibrated, is steadier than GPS in cities and woods.
  • Distance steps on a track. Use the track's markings: run 400 m reps by lap time, and treat the watch's pace as a guide.
  • Heart rate for easy running. An easy run with a heart-rate target or no target at all avoids pace alerts on hills and in wind.
  • Effort, not pace, on hills. A pace target on a hill rep will always say "too slow". Give hill reps no target, or a heart-rate one. See hill repeats.

How PaceRunner sets the ranges

PaceRunner gives every effort a range from your profile: each race pace (marathon, half, 10K, 5K, mile) and threshold as the pace ±5 s/km, and easy as a wider band. A pace you type yourself ("6 x 800m at 4:00/km") gets the same ±5 s/km unless you give a range. Every range can be changed, per effort on your profile or per step in the editor. When it sends a workout, it reads back Garmin's copy and checks each range arrived within half a second per km of what you saw.

Type15 min easy, 3 x 2 km at threshold with 2 min jog, 10 min easy

3 x 2 km at threshold1 h 01 min
  1. 15 min easy
  2. 2 km at threshold, 5:11–5:21 /km
  3. 2 min jog
  4. 2 × 2 km at threshold, 2 min jog between
  5. 10 min easy

Questions

What's a good pace range for intervals on Garmin?
About ±5 seconds per km (±8 s per mile) around goal pace. Narrower and GPS noise sets off alerts constantly; much wider and the target stops meaning much.
Why does my Garmin keep saying I'm too fast then too slow?
It's reacting to moment-to-moment GPS pace, which swings even when you run evenly. Widen the range a little and run by lap pace.
Should easy runs have a pace target?
A wide one, 30 to 40 s/km, or a heart-rate target, or none. The point of an easy run is to stay easy, not to hold a number.
Can I change the ranges PaceRunner uses?
Yes. Change any effort's pace on your profile, or a single step's range in the editor.

Checked November 18, 2026