The work intervals were clearly separated on your watch, but in another app the end of the first fast section spills into the next row. The displayed average pace is slower too, and even the number of repetitions seems wrong. Before judging the runner’s execution, check whether the two interfaces are comparing the same section boundaries.

A lap may be marked manually or automatically, a work interval may be a structured workout step, and kilometre splits may be a view calculated afterwards. These do not necessarily coincide. Our straightforward time-and-distance examples show how fast running and an easy section can end up in one summary row, and how to restore a comparable time window. The aim is to interpret data, not prescribe an interval workout for everyone.

First establish what kind of laps the interface shows

The Garmin FIT Activity documentation treats Lap messages as summaries of laps or sections, which can be marked manually or automatically. A lap is not inherently a fast repetition. A recording can contain a single continuous running session with many laps serving different purposes. Its number alone therefore cannot tell you whether a section was a warm-up, work interval or easy running.

The receiving app may also show its own kilometre splits. These rows may be generated by distance, independently of where you marked laps on the watch. The two tables can look similar while their boundaries follow different principles. Before placing two numbers side by side, check the view’s title and whether it shows original lap data or recalculated splits.

In our example log, “lap three” means the third kilometre covered on one interface and the second work interval on another, because a warm-up and an easy section came before it. The number matches; the part of the activity does not. For troubleshooting, start and finish times and section distance are therefore more useful than the row number alone. They reveal whether you are discussing the same window.

Eight hundred metres of work and two hundred easy make a kilometre

In our fictional block, eight hundred metres take four minutes, followed by two hundred metres in two minutes. Average work-interval pace is five minutes per kilometre; the easy section is ten. Together they make exactly one kilometre and six minutes, so the combined section’s pace is six minutes per kilometre. That six-minute figure does not prove the four-minute work interval became slower: the average simply includes a different part of the activity.

If we repeat this pair three times, the work intervals total 2,400 metres and twelve minutes. The easy sections total six hundred metres and six minutes, making the whole block three thousand metres in eighteen minutes. The kilometre-split view may show three six-minute rows if its boundaries align with the pairs. Meanwhile, the work-interval view may report three sections at five-minute kilometre pace.

Neither display is necessarily wrong. The kilometre table describes each whole kilometre covered; the other describes the designated work interval. The comparison becomes flawed when we judge the six-minute kilometre against a five-minute target as though it consisted solely of work. Understanding section boundaries comes before assessing execution.

Warm-up distance can shift every later distance boundary

Now place a 1,300-metre warm-up before our previous block. The work interval no longer begins at a whole-kilometre boundary. The activity’s second full kilometre may contain the end of the warm-up and part of a work interval. The next full kilometre may mix fast and easy running in another proportion. The table’s rows can therefore change even while the block’s internal structure stays the same.

A runner can adjust the endpoint of an open warm-up to the situation, while the FIT Workout documentation distinguishes open-ended steps from steps with other end conditions. The completed warm-up is therefore not necessarily a round distance known in advance. Follow the work intervals from the actual transition. It is incorrect to cut the same fixed ten minutes from the beginning of every recording merely because that is often the usual duration.

On our fictional second day the warm-up is 1,500 metres; on the third it is 1,200. A view based on whole kilometres covers different portions, so changes in its individual rows are not a clean comparison between repetitions. Each work interval’s own start and finish provide the comparable basis. A distance breakdown of the whole run can remain useful for other questions, but cannot replace this.

A runner completes a controlled section on the track while a coach observes their agreed pace practice.Enlarge image
AI-generated editorial illustration of targeted race-pace practice; not a documentary photograph or a performance prediction.

A workout-step index may preserve the connection

According to the Activity documentation, a structured-workout recording may contain Workout and Workout Step data, while a lap’s Workout Step Index field may refer to the corresponding step. This can help connect the target with the completed lap. However, the presence and preservation of that field are not guaranteed for every recorder or subsequent export. Check both the actual file contents and the receiver’s capabilities.

In our example data pair, one lap belongs to plan step 2 and the next to step 3. If step 2 is work and step 3 is easy, their roles may remain traceable. If only lap times transfer, that connection may disappear from the view. The running data may survive, but the programme no longer has a direct reference for identifying the planned task.

An index does not mean the same thing in every system as the on-screen numbering that starts at one. A machine-readable list and the user view may begin numbering differently, while a repeating block may link the same instruction to several completed sections. Rely on the documented relationship rather than the number alone. Checking exact time boundaries provides a useful cross-check here too.

An extra button press can create another lap boundary

The official fēnix 8 activity settings discuss automatic lap marking and Lap Key operation separately, with available options also varying by sport mode. On a particular device, a button press may behave differently during a free run and a guided workout. Avoid applying a single button rule recalled from memory to every watch. The documentation for your own model and mode is what matters.

In our simple fictional free run, a new lap accidentally starts halfway through a section intended to last four minutes. The lap list shows two shorter parts, but the movement remains continuous. If an analysis treats every second row as an easy section, the extra boundary may shift the entire classification. The cause is then not necessarily a recorded value, but the alternating labels imposed afterwards.

A short note is valuable for such a recording: when did the extra marker occur, and did the planned movement continue? An analyst can then use the appropriate windows if the necessary detailed data remain available. Keep the original lap list as well. An adjusted analysis boundary and the originally recorded boundary are two separate pieces of information.

Recalculate the average from the correct time window

If the work interval’s beginning and end are known, match its time to its distance. In our example, eight hundred metres were covered in four minutes, so pace is 240 seconds divided by 0.8 kilometres: 300 seconds per kilometre. That is the same five-minute pace calculated for the earlier work interval. There is no need to classify it as slower because an easy section was mixed in.

If the selection accidentally includes thirty seconds of easy movement, both distance and time change. In this numerical example, the easy section’s steady ten-minute pace adds fifty metres, giving 270 seconds over 0.85 kilometres. The result is approximately 5:17.6 min/km. The work interval has not changed; only the edge of the analysis window has shifted. Even a short boundary error can produce a visible difference.

It is incorrect to add two section paces and divide by two when they apply to different distances. The average of our eight-hundred-metre section at five-minute pace and two-hundred-metre section at ten-minute pace is not 7:30, but 6:00 min/km based on total time and distance. Preserving original time and distance therefore matters more for interval reconstruction than averaging already calculated, rounded pace columns.

Sparser record points do not replace marking section boundaries

The FIT decoding guide treats laps, timestamped records and timer events separately. There may be longer gaps between sparsely recorded points even though running was continuous. A gap between data points must not automatically be interpreted as rest or a new interval. A separate event and sampling density have different meanings.

In our example, the end of a work interval falls between two retained speed points. If the exact lap boundary is stored separately, the section’s time may still be known. If it is missing and we try to estimate the boundary from sparse points alone, the result is less certain. A straight line drawn between two graph points is not a new measurement. Label an estimated boundary separately from an actually recorded timestamp.

Automatically detected intervals can therefore be useful analytical suggestions, but they are not infallible copies of the original plan. A steadier easy section or an unusual acceleration may be divided differently. Compare detected sections with what actually happened and the available markers. More coloured blocks on screen do not necessarily mean more completed repetitions.

A runner and coach review side-view running footage on a tablet beside an athletics track.Enlarge image
AI-generated editorial illustration; not a documentary photograph.

How to check differing interval tables in two apps

First save the original activity file and the plan, if available. Choose one clearly identifiable work interval and note its actual start, finish and distance. Then find the data for that same window on the other interface. Do not try to pair every row in the whole table immediately. One exact connection can reveal the difference causing the later shift.

Next establish whether the interface shows original laps, kilometre splits or its own detected intervals. Third, check whether the link to the plan step survived. Without that information, assigning a role may depend on your notes or cautious retrospective analysis. Do not automatically label anything you cannot identify confidently as work or recovery.

Finally, record the boundaries used beside the recalculated result. Our example checking statement is: “work interval from 12:00 to 16:00, 800 metres; the kilometre row covers a different window”. This is clear and can be checked again. It also gives a coach more to work with than saying one app shows a “better pace”. The right question is whether the content matches, rather than which number looks more favourable.

Be clear about the purpose of recording on the next run

If comparing work intervals matters, review before starting how you will mark their boundaries and how they will reach your log. Kilometre splits can still be useful for an overview of the whole run; they simply answer another question. Every view need not be forced into the same structure. Match the recording and analysis method to what you want to learn later.

If something differed during execution, write a short note afterwards while it is fresh. Waiting, an extra lap marker or an omitted section can easily be forgotten later. Data do not always preserve the reason, even if they record the timestamp precisely. A human explanation then supplements the measurement series rather than retrospectively making it look better.

Intervals that fall apart in another app can often be understood through different boundaries or lost connections. A lap, a planned step and a subsequent kilometre breakdown are distinct concepts. Using the same time window and full time-and-distance data can make the comparison meaningful again. You can then assess the runner’s execution from the actual work interval rather than a mismatched table row.

Sources

Helpful? Pass it on.