How to Analyze a Workout

You do not need to be a pro, a coach, or a data nerd to get useful information from a workout. If you have a watch that records laps, pace, heart rate, and time, you already have enough to learn a lot.

This post is not really about which platform is best. Garmin, Coros, Strava, TrainingPeaks, intervals.icu, and plenty of others can all help. The important part is knowing what questions to ask and where to look for the answer.

I am going to use one threshold session as the example: 6 x 5 minutes at threshold with 90 seconds recovery.

Record It So You Can Actually Analyze It Later

When I analyze a workout, I am not focused on the overall averages. I am focused on the individual reps. That may be a little bit of Strava heresy, but if you are doing a real workout, your average pace for the full run is probably going to look slow once you mix the recoveries in with the hard efforts, especially if the recoveries are standing rest or very easy jogging instead of continuous float.

For this session, the workout was 6 x 5 minutes at threshold with 90 seconds recovery. My target was about 7:05 pace, with some room for small fluctuations because we were on grass and the route was not flat. In reality, some of the recovery ended up a little longer than 90 seconds because we had to loop back to the start before beginning the next rep. The original plan was actually only 4 reps, but I added 2 more at the end. On those last 2, I let the pace drift closer to 7:20 instead of forcing 7:05, partly because my second rep had been interrupted and partly because I was running the extra reps with another athlete.

That is why the biggest thing I do when recording a workout is just let the watch run. The recoveries count too. Short rest gives the workout one feel. Longer rest gives it another. I want the file to show the whole thing: how the reps went, how much recovery I took, and how that recovery affected the reps that came after.

So the first rule for analyzing a workout is simple: do not stress about the overall averages. If you record the whole session honestly, those numbers may look slower than you want them to. That is fine. I would rather have a workout file that tells the truth than one that looks prettier in the summary.

The First Pass: Check the Lap Table

After a workout, I always go straight to the lap table in my app of choice to see how well I hit my paces.

That is the fastest way to get a basic read on the session. Before looking at charts or any deeper analysis, I want to know whether the reps were on target, whether they stayed consistent, and whether anything unusual happened that I need to account for.

For this workout, the first rep was 7:04, which is right where I wanted it. Maybe a touch quick, but close enough that I would call it a good opening rep. The second rep is a little different because it got cut short. I stopped with about a minute left to help someone, so I would not judge that one the same way as a normal rep. The third rep came back at about 7:03 or 7:02 depending on the app, which is slightly quicker than the first. That makes sense to me because I had effectively gotten a little extra recovery after the interrupted second rep.

The fourth rep was right on 7:05, which is probably the best sign in the whole workout. It showed that I was still controlled and still hitting the original goal pace. The fifth and sixth reps were slower, but that was intentional. Since those were bonus reps, I eased off a bit and ran them more around 7:20 pace instead of trying to force two more full-threshold reps at 7:05.

So from the lap table alone, I would already call this a good workout. The first four reps were right on target, and the last two were slower by choice, not because I was falling apart. That is an important difference, and it is one of the main things I am always trying to sort out when I look back at a workout file.

The Next Layer: Use the Charts to Explain the Reps

Once I have looked at the lap table, the next thing I want to know is how each rep actually unfolded. The lap splits tell me whether I hit the pace. The charts help explain how I got there.

One pattern that shows up pretty clearly in this workout is the start of each rep. There is usually a little quick surge early on, partly because the reps started from basically zero and took a few seconds to settle, and partly because I was running with faster athletes and could get pulled along a bit at the start. That is pretty normal. What I want to see is not a perfectly flat line from the first second, but a quick acceleration and then a controlled settle into the actual working pace.

The other pattern I look for is what happens late in the rep. In a few of these, you can see the pace start to slip a little before the end. If I only looked at that in isolation, I might think I was fading. But the full chart tells a better story. The pace drops slightly, then recovers, and when I line that up with the elevation, it makes sense why: that slowdown is happening near the top of a long incline.

That is the kind of thing the charts are good for. They keep me from overreacting to a small change in pace without context. Since we were covering the same ground and starting from the same place each time, the hill showed up in basically the same spot in every rep. So when I see a similar little dip there over and over, I do not read that as the workout falling apart. I read it as the course asking the same question each time.

The charts also make the interrupted second rep much easier to understand. In the lap table it just looks abnormal. In the chart you can actually see the rep end early, which is why the slightly quicker third rep does not bother me much. It makes sense after the extra rest.

Overall Read: What I Took From the Workout

Stepping back from the individual charts and splits, I would call this a good threshold workout.

The biggest reason is that the first four reps were basically right where I wanted them. Rep one was on target, rep two got interrupted, rep three came back a little quick but for a pretty understandable reason, and rep four landed right on pace again. That is a pretty good sign that the workout stayed controlled instead of turning into a fight.

The last two reps do not really change that read for me. Since those were bonus reps, I was not trying to prove I could keep hammering 7:05 pace forever. I backed off a bit on purpose and kept them more around 7:20. That still made them useful, but it also kept them in the category of extra work instead of turning them into a different workout than I meant to do.

That is probably the main thing I want a workout file to help me answer: was the change in pace a problem, or was it a decision? In this case, I think the answer is pretty clear. The early reps were controlled, the interruption in the second rep explains some of what came after, and the slower finish was intentional rather than a sign that I cracked.

So overall, I came away happy with it. The main set did what I wanted it to do, and even the bonus work stayed steady enough that it still added something without muddying the point of the session.

What I Actually Look For in Workout Data

Before I can really analyze a workout, I need to understand the purpose of it. That tells me what I should be looking for in the data. Different workouts ask different questions, so they should not all be judged the same way.

Most of the time, I am looking for some version of control, consistency, and workout-specific intent. I want to know whether the session unfolded the way it was supposed to, whether the reps stayed honest, and whether any changes in pace make sense in context.

That is why I like looking at both the lap table and the charts. The lap table tells me what happened. The charts help explain how it happened. Between the two, I can usually tell the difference between a real problem, a deliberate choice, and something caused by terrain, recovery, or the structure of the workout.

Different Workouts Ask Different Questions

In a threshold workout like this one, especially with longer reps, I am usually looking for control and consistency. I want the reps to be steady, repeatable, and close to the intended effort without turning into a grind too early.

In a shorter speed-focused workout, I am still looking for consistency, but the shape is different. Usually I want to see steady pacing or progression unless the workout specifically calls for something else. I do not want the first couple reps so fast that the quality disappears by the end.

If I am doing something like 2 sets of 300, 200, 100 at mile pace, 800 pace, and 400 pace before a race, I care less about perfectly matching some exact race pace and more about whether the workout is moving in the right direction. I want to see the reps get faster as they get shorter, and I want that pattern to still be there later in the workout.

Same with something like a broken 400 with a 200 float in the middle and a faster final 200. I would not be too concerned with one average pace for the whole rep. I would want to know whether the float stayed honest and whether I could accelerate again at the end.

That is really the broader point: good workout analysis is not just asking whether the watch showed the right pace. It is asking whether the data matches the purpose of the workout.

Final Thought

The best workout analysis is not about finding one perfect number. It is about understanding what the workout was supposed to do and then checking whether the data matches that purpose.

For me, that usually starts with the lap table, then moves to the charts, and then ends with a pretty simple question: did this workout unfold the way it was supposed to? If the answer is yes, that is usually more useful than whether the overall summary page made the run look fast.