Skip to content

Gear

Cycling Computer Data Fields: Which Metrics to Display for Training and Racing

Cycling computer data field configuration affects real-time decision-making during rides. Learn how to set up training-specific and race-specific screen layouts with the right metrics for each ride type.

Author

NorthLine Performance Team

Published

November 16, 2026

Read Time

10 min

Gear
Cycling Computer Data Fields: Which Metrics to Display for Training and Racing

A cycling computer can display 80+ data fields, but your brain can effectively process only 3–4 pieces of information per glance — and each glance takes your eyes off the road for 0.5–1.5 seconds. Displaying the wrong metrics, or too many metrics, creates information overload that degrades both decision-making quality and riding safety. Research from the Human Factors and Ergonomics Society (2020) found that cyclists who displayed more than 6 data fields per screen made 23% more pacing errors in time trials compared to those who displayed 3–4 targeted fields.

The solution is not minimalism for its own sake — it is intentional screen design matched to ride purpose. A zone 2 endurance ride requires different information than a threshold interval session, which requires different information than a road race or gran fondo. Most cycling computers support multiple screen pages with different layouts; the athletes who get the most from their devices configure purpose-specific pages and switch between them based on the session type.

The Essential Four: Metrics Every Screen Should Include

Regardless of ride type, four metrics form the decision-making foundation. These should appear on every screen, typically in the largest font positions:

  • Elapsed time or lap time: The fundamental temporal reference for interval timing, fueling schedules, and session duration management. For interval sessions, lap time (auto-reset or manual) is more useful than elapsed time
  • Current heart rate: The primary intensity gauge for aerobic sessions and the ceiling limiter for all ride types. Heart rate has known limitations (cardiac lag, drift, temperature sensitivity) but remains the most universally applicable intensity metric across all power levels and fitness states
  • Speed or pace: Useful primarily for outdoor road riding where speed provides terrain and wind feedback. Less useful for interval training (where power or HR should drive intensity) but essential for pacing on time-trial-format events and for estimating arrival times on longer rides
  • Distance: Critical for ride planning, nutrition timing (e.g., fuel every 30 km), and mental segmenting during long rides. For structured training, distance is informational rather than prescriptive

Zone 2 Endurance Screen: Stay in the Box

Zone 2 rides have one primary objective: accumulate time at 60–75% of maximum heart rate (or 55–75% of FTP if power-equipped). The data screen should make it effortless to stay in the target zone and tedious to drift above it. Recommended 4-field layout:

  • Field 1 (large): Heart rate — primary pacing metric. Set heart rate zone alerts to beep when you exceed zone 2 ceiling
  • Field 2 (large): Time in zone — many computers can display cumulative time spent within a target heart rate band. This is the primary training quality metric for zone 2 work
  • Field 3: Elapsed time — for session duration management and nutrition timing
  • Field 4: Power (if available) — secondary metric for monitoring cardiac drift. If power remains constant but heart rate drifts upward over 90+ minutes, you are observing normal cardiovascular drift (1–5 bpm/hour is typical) rather than intensity creep

Deliberately exclude average speed from the zone 2 screen. Average speed invites ego-driven pace creep on aerobic rides — the single most common training error that undermines base phase development. If your zone 2 ride requires riding at 25 km/h to stay in the zone and the group is at 30 km/h, the data screen should make it obvious that you are exceeding your target, not reinforce the satisfaction of a higher average speed.

Interval Training Screen: Precision Under Load

Interval sessions demand real-time intensity regulation — the ability to hit a specific power or heart rate target within ±3–5% for the prescribed duration. The screen must provide instantaneous feedback with minimal visual clutter. Recommended 5-field layout:

  • Field 1 (large): 3-second average power — smoothed to reduce the visual noise of pedal-stroke power spikes (which can swing ±50W with each stroke) while maintaining real-time responsiveness. Avoid 10-second or 30-second averages during intervals — they are too slow to detect and correct intensity drift
  • Field 2 (large): Lap time — for interval duration tracking. Use manual lap for structured intervals and auto-lap for distance-based efforts
  • Field 3: Heart rate — ceiling monitor and effort validation. HR should confirm that power output is physiologically consistent (high power + low HR suggests a calibration issue; low power + high HR suggests fatigue or illness)
  • Field 4: Cadence — pedaling efficiency monitor. Most athletes have an optimal cadence band (85–95 rpm for most road cyclists) that maximizes power at minimal cardiovascular cost. Cadence outside this band during intervals signals form breakdown
  • Field 5: Lap average power — end-of-interval quality check. Was the interval within target power ±5%? If consistently below, reduce target. If consistently above, increase target for future sessions

Race/Gran Fondo Screen: Decision Metrics Under Fatigue

During competition, cognitive function degrades by 10–20% after 2+ hours of sustained effort. The race screen must present actionable information that requires minimal interpretation:

  • Field 1 (large): Normalized Power (NP) or Intensity Factor (IF) — provides a fatigue-weighted average of your effort that accounts for the higher metabolic cost of variable power. If your race plan calls for IF 0.75 and the screen shows 0.82 after 30 km, you are overcooking it and need to ease back — this single metric captures what average power or heart rate alone cannot
  • Field 2 (large): Elapsed time — for nutrition timing (fuel every 20–30 minutes) and race time management
  • Field 3: Heart rate — decouple from power after 3+ hours. If HR rises but NP stays constant, cardiovascular drift indicates mounting fatigue — reduce target power by 3–5% to prevent bonking in the final quarter
  • Field 4: Distance remaining or ETA — mental fuel. Knowing "32 km to go" or "estimated finish in 58 minutes" provides psychological structure that maintains motivation and pacing discipline

Screen Management Best Practices

Configure 3–4 screen pages and assign each to a ride type. Name the pages (most computers support custom page names) so you select the right layout before starting. Disable auto-scroll between pages — accidental page changes during effort force a cognitive interruption to navigate back to the correct screen. Set font sizes to the largest available for primary metrics — at race pace, you need to read the number in a 0.5-second glance. Use high-contrast color schemes if your computer supports them.