Hi !
I’ve been using the app in order to plan my marathon training, love it but i’ve seen that the load of my programmed easy runs are very low compared to what I end up doing.
The workout for my last run was : * 9km Z1 HR (119-149bpm), which gives me a load of 23.
I followed the planned workout and I end up with a load almost 2x higher than expected.
I’m wondering how is the load calculated, and what could lead to this ?
Thanks !
For HR zone target, the load is calculated from the mid-zone HR.
If you execute at top of zone, the difference can be significant.
Other thing is the distance target. Then duration is guessed from the corresponding pace zone, but can be off quit a bit. HR intensity factor * time makes the load.
One thing that can happen with planned workouts is that the predicted load is based on a simplified assumption about how the intensity will look during the session.
But once the activity is recorded, the load is calculated from the actual HR curve across the whole run. Small things can change the outcome quite a bit — for example HR drifting upward during the run, spending time near the top of the zone, or the HR zones themselves not perfectly matching your current physiology.
Even when you follow the planned zone quite well, those small differences can easily double the calculated load compared to the estimate.
Which training load priority do you use? HR or pace?
In term of distance load estimation, it’s pretty simple for me: as I use %FTP in the workout for a run type, Intervals cannot simply do any estimation and all projected run in calendar are showing 0km and that’s what I receive in the report on Sunday evening 
Stryd using %CP works perfectly so what I have to do is look at the estimated distance in calendar there and input manually the projected load in Intervals calendar.
Not exactly the original question from this post but an example of functionality one would expect it would work but in practice not. I imagine for cyclist and ride it works fine?
Thanks @R2Tom ! I did not see that this could be configured in the settings of the sport, everything was set as “Power>HR>Pace”. After setting it as “HR>Pace>Power” I have way more coherent values 
The other settings next to it made it also possible ot get a better view on my past workout.
I see that this is an app made on the first though for cyclists, so the power is seen as the Nº1 metric, maybe for running the default value for these settings could be something else, as for most workouts pace and HR are the most important values.
For reference here is what I find to be the best for me for running :
Yes off course, didn’t think about that.
But, to be coherent, I would suggest that use the same setting for Training Load Priority and Workouts.
As you have it now, the planned workouts will estimate load from Pace (if specified in the workout - else HR) while your finished activities will use HR to calculate load unless HR is not available. Then it will fallback to Pace.
This on the other hand will only have effect if your activity data has Power. If no Power stream is in your data, there will be no difference because both settings would then use HR first.
