The workout sent to your watch called for four repetitions, but six laps appear in the training log. Another upload retains the run’s full curve yet loses the goals for individual sections. These files are not necessarily faulty. Planned instructions and actual execution are different information that a system may store separately.

In FIT, Workout and Activity also distinguish two file types. One describes what to do; the other describes what happened during the activity. We follow their relationship through an original fictional workout example involving duration, targets, repeated blocks, open sections and manual advancement. The numbers illustrate data interpretation, not an individual running prescription.

Instructions and recording tell two separate stories

The official FIT Workout description stores instructions for performing a structured activity. The Workout message and Workout Step messages describe the task’s structure. The FIT Activity documentation, in contrast, records the completed activity’s timing, sections, sensor data and events. The same file extension therefore does not mean the same content role.

In our original example, the plan specifies a warm-up, four work sections with easy parts between and finally a cool-down. The recording describes when the runner started, how long sections lasted and what distance and sensor values were recorded. The plan alone does not prove completion. The actual recording does not necessarily fully preserve the original coaching intention either.

If only the plan survives, we do not know whether it was performed. If only the mapped line remains, it may not reveal which section belonged to which instruction. Together, the information explains differences between intention and events. This is not a minor administrative detail in a log: later conclusions depend on what we actually see of both sides.

The end of a section and target intensity are separate settings

A Workout Step can separately specify what determines its end and what its target should be. The end condition might be time or distance; the target might be a speed range corresponding to pace or another supported parameter. “For three minutes” and “Within the specified range” are therefore different fields. Correct display needs both interpreted, not merely the section’s name.

Two original instructions both last three minutes. The first has no numerical pace target, while the second has a fictional target-speed range. Section lengths match, yet the instructions differ. The reverse is possible too: two tasks may share a target but one ends by time and another by distance. Completion must be compared with the condition actually specified.

A target is not a measurement result. A runner’s actual value may fall inside or outside a planned range and change during it. Return to recorded data to see what happened. An attractive average calculated from the target field does not replace analysis of execution. Plan consistency and completion quality are separate assessments.

Pace and speed describe the same target differently

A runner often thinks in minutes per kilometre while a machine field may use speed. In an original example, an exclusively illustrative range of 4:30 to 4:50 minutes per kilometre corresponds to approximately 3.70 to 3.45 metres per second. Faster pace is a smaller minutes-per-kilometre value but a higher speed. Boundary labels can therefore easily be reversed in conversion.

Over eight hundred metres, the same example would give a time range of 3:36 to 3:52 if that average pace were achieved. This is arithmetic, not a recommended workout length or expected result. A plan may specify eight hundred metres and a target pace, while the actual lap time later lets you check execution. Do not confuse calculated target time with measured lap time.

The Garmin guide to Workout encoding separately discusses machine representations of targets and durations and dynamically interpreted fields. Read appropriately decoded values rather than treating a raw integer as an everyday unit. The exporter performs format-specific conversion. For user checks, units and target type should be explicitly displayed.

A runner completes a controlled section on a track while a coach observes the agreed pace practice.Enlarge image
An editorial illustration created using AI showing focused race-pace practice; not a documentary photograph or a performance prediction.

A repeated block creates more executed sections from fewer instructions

FIT can describe a recurring task with a repeat step. In our original plan, a three-minute work section is followed by two minutes easy, and the pair repeats four times. The work and easy parts can each be described once, with repetition referring back to them. Instruction count therefore need not equal the number of sections eventually run.

The four work sections total twelve minutes. If a two-minute easy section follows all four, that adds eight minutes for a twenty-minute block. If the last easy section is omitted, easy time is only six minutes and the block eighteen. These are different plans. Turn the everyday phrase “recovery between repetitions” into an unambiguous structure.

An exporter may show repetition as an expanded list or a compact block. Either can be clear if the repetition count’s scope and inclusion of the final easy section are visible. Do not compare only row counts when troubleshooting. First describe the full execution order in plain language, then compare the machine view with it.

An open-ended warm-up has no predetermined time

An open section can indicate an instruction without a preset time or distance end. The particular device determines how the user advances from it. In an original example, warm-up continues until the runner is ready for the next part at an appropriate, safe place. The plan intentionally does not give a fully calculable total duration here.

If the block is twenty minutes and warm-up and cool-down are open, the whole workout cannot automatically be called twenty minutes. In our original recording, warm-up lasts thirteen minutes and cool-down nine, giving forty-two overall. The planned fixed portion and the completed full activity are different numbers. Comparing them requires knowing which includes open sections.

A predicted duration displayed beforehand may therefore be partial or based on assumptions. Check the app label and treatment of open steps separately. A difference from the estimate does not establish the runner performed incorrectly. The plan may deliberately contain adaptable parts, and execution may have used exactly that flexibility.

Manual advancement is part of execution, not rewriting the plan

In an original example, a runner ends a three-minute instruction at two minutes forty seconds because they reach the next location. The plan still said three minutes; the recording shows a section twenty seconds shorter. The difference need not be erased. It shows what happened during execution. A brief training note can explain the details.

Manual advancement, skipping a task and pausing the whole activity can be different operations. One moves to the next instruction, another may stop the timer; handling depends on the device. A resulting lap list does not always reveal the operating history on its own. Recording events and the runner’s reminder together may clarify the situation.

A wrong button press does not necessarily make the whole run worthless either. If continuous sensor data survives, appropriate analysis may identify the affected section separately. A retrospective note should not, however, present edited laps as though they were recorded exactly that way originally. Keep actual recording and later analytical segmentation separately traceable.

A workout step and lap can be linked without being identical

The Activity documentation explains that structured activities may also contain Workout and Workout Step messages. A Lap message’s Workout Step Index can connect an executed section to the relevant planned step. This is useful, but does not mean every device and later export fully preserves it. Check actual file contents.

In an original counterexample, a runner also uses automatic kilometre laps. These distance boundaries do not necessarily align with three-minute work sections. A kilometre can include parts of two instructions, or one instruction can span several laps. Lap names and numbers are therefore insufficient to assign an automatic one-to-one plan relationship.

The FIT decoding guide also notes that message names found inside do not reliably determine file type: Activity files can contain Workout messages too. The appropriate File Id field identifies type. This explains why seeing one “workout” word when opening an export cannot immediately establish that only the plan survives.

A woman runner reviews a notebook beside a café window, looking for patterns in her running log.Enlarge image
An editorial illustration created using AI showing a running-log review; not a documentary photograph.

What does the export preserve, and what does the receiving log show?

An export can contain the actual run’s map and timing even if structured-instruction links do not reach the receiving interface. Preserving the file, importing fields and supporting a plan-versus-completion view are separate functions. A neat pace graph does not imply the log knows original targets. A missing target band does not prove the watch lacked that instruction.

The Strava export description distinguishes downloading the original file from exports in other formats. For later detailed analysis, retain both the actual original activity file and original plan where available. A generic route export serves another task. Do not automatically expect it to preserve every instruction and section link.

In your archive, link plan and recording with a shared understandable name while keeping planned and executed versions visible. If a coach changed the task meanwhile, its date or version also helps. A plan rewritten afterwards is not the instruction the runner saw at the start. Mixing the versions can lead to unjustified judgements of deviations.

Make plan-versus-execution differences useful training notes

Before starting, briefly review order, repetition count, target units and how open sections end. This is technical understanding of the task, not deciding individual suitability. If something is unclear, clarify the instruction rather than guessing buttons and numbers while running. A simple, clear description should also be followable without the watch.

Afterwards, note separately the plan, what happened and why it differed. An original sample sentence: “Three complete work sections instead of four; skipped the fourth because of a route closure; the full recording survives.” This provides more information than “It didn’t work”. State a reason as certain only if you actually know it; guesses should not enter a log as facts.

Workout therefore carries instruction structure, while Activity carries the history of activity performed. Their connection helps when targets, section boundaries, actual data and later explanations remain distinct. Export differences then look like a traceable data chain rather than incomprehensible file faults. A good log does not erase deviations: it preserves them accurately enough to inform the next decision.

Sources

Helpful? Pass it on.