Choosing Which Running Watch Fields to Display

06 March 2023

A running watch can show more information than a runner needs while moving. A simpler screen may make the important observation easier to find.

A practical approach

Choose fields that fit the session's purpose and check the units before leaving. Avoid adding a metric merely because the device offers it. Stop safely for detailed adjustments, and remember that a display cannot replace awareness of the route or personal wellbeing. Review other data afterwards when it can be read calmly.

Choose watch information that supports the session

A running watch screen is useful when it shows the information needed for the current task. Too many changing values can distract from effort, footing and other people. A simple display is often easier to interpret than a crowded collection of metrics.

Decide whether the session needs elapsed time, lap pace, distance or another supported field. Test the display before an event and know how to use it without stopping abruptly in a crowd. Keep battery and recording settings organized, but do not let a missed button press define the value of the run. The device is a tool for the activity, not the reason the activity exists.

Decide whether the plan uses miles or kilometers

A running plan is easier to follow when its units are consistent. An event may use one distance unit while a watch or training group uses another. The difference should be resolved before a pacing note is copied into a race plan.

Write the unit beside distances, paces and split targets, and check any conversion with ordinary arithmetic. One mile is 1.609344 kilometers, so a pace number in minutes per mile is not numerically interchangeable with minutes per kilometer. Keep rounding visible when a simplified value is used. Clear notation matters more than an impressive-looking pace chart whose units are missing.

Plan the actual route and a way to shorten it

A running route should be checked for access, surfaces, crossings and practical return options. A distance shown by an app does not establish that every section is open or suitable. Local conditions and the responsible land manager's rules take priority over an attractive map line.

Choose a route that fits the session and let an appropriate person know the plan when relevant. Keep a safe alternative for closures or changing conditions, and do not rely entirely on mobile reception in unfamiliar areas. A shorter loop can be easier to manage than a long route with no convenient return. The useful plan explains where you will go and how you can stop, not just how many miles the map suggests.

Record context alongside distance and time

A useful running log includes enough context to explain the session. Distance and pace alone can hide hills, weather, pauses, unusual fatigue or a changed route. The record does not need to be long, but it should distinguish observation from interpretation.

Note the purpose of the run, the conditions and one or two practical observations. Keep sensitive route and health information private where appropriate, especially when sharing screenshots. Avoid assigning a diagnosis to discomfort or treating one slow session as proof of lost fitness. Over time, a clear log can support a conversation with a coach or healthcare professional because it shows what actually happened rather than only the result you hoped to achieve.

An example to work through

For a straightforward timed outing, a clear elapsed-time field may be more useful than several changing estimates crowded onto one screen.

What to check

Match fields to the purpose.
Check units.
Save detailed review for later.

Sources and further guidance

RRCA: runner safety tips