Predicting How Training Load Affects Your HRV — Help Us Build Personalised Models

We’re a research group at ISGlobal (Barcelona) studying how training load shapes autonomic recovery — and we need your data.

→ dlnm.isglobal.org

Every endurance athlete knows the feeling: you’ve followed the plan, the numbers look right, but you show up to race day flat. Or the opposite — you felt buried in fatigue all week and then produce a personal best. The gap between what the training plan says and what your body actually does is real, and it’s largely invisible in the metrics we currently use.

A big part of that gap lives in your autonomic nervous system — the machinery behind your heart rate variability (HRV). Morning RMSSD is one of the best windows we have into how recovered (or how suppressed) you actually are. Most athletes already track it. But interpreting it is harder than it looks.

The problem with rolling averages

The standard approach — a 7-day rolling average — assumes your body responds to training immediately and linearly. Neither is true. A hard block of intervals doesn’t fully hit your autonomic system the next morning; the suppression builds, peaks days later, and fades at its own pace. And the relationship isn’t proportional: doubling TSS doesn’t double the HRV drop. The response is delayed and non-linear, and rolling averages simply can’t capture that.

What if the model actually matched the physiology?

That’s the question driving our research. We use a class of statistical models called Distributed Lag Non-Linear Models (DLNM) — originally developed for environmental epidemiology — to capture exactly this kind of delayed, non-linear response. Instead of flattening everything into a 7-day window, the model learns your individual lag structure: how long it takes for a given training load to affect your HRV, how intense the effect is, and how quickly you bounce back.

Once calibrated with enough data (~4–6 months), the model can do something genuinely useful: predict your RMSSD trajectory under a planned training week before you execute it. Different load distributions — say, front-loading a block versus spreading it evenly — produce measurably different predicted autonomic suppression, even when total weekly TSS is identical. This is the kind of insight that rolling averages structurally cannot provide.

We will present our preliminary results at the European Congress of Sport Science (ECSS) in Lausanne this July, and they’re promising. But our current sample is small (12 athletes), and we need a much larger and more diverse dataset to validate whether these personalised models generalise across the broader endurance population.

What we need from you

We’re asking for a minimal, fully anonymised dataset:

  • Daily TSS (your training load) + Session duration (in minutes)

  • Morning RMSSD (your HRV)

  • Age

No names, no locations, no identifying information whatsoever. The age is only because HRV has a well-documented decline with age, and without accounting for it we’d be confounding training effects with biology.

Ideally, we’d love time series of at least 4–6 months (the minimum needed to calibrate the lag structure), but longer is better.

Why this matters for you

This isn’t just academic. The end goal is a tool that athletes and coaches can actually use — one that moves beyond “your HRV is lower than your 7-day average” toward “given what you’ve done this week, here’s where your autonomic system is likely headed.” Understanding the delayed effects of load distribution, not just load volume, could meaningfully improve how we plan tapers, recover from blocks, and arrive at key events in the right state.

How to participate

We’ve set up a study page with all the details:

→ dlnm.isglobal.org

If you have questions, feel free to ask in this thread — we’re happy to discuss.

Thank you to David for supporting this and for building a platform that makes this kind of research possible.

Please remark that activities must be synced to Intervals.icu through any connection type except Strava since the API terms don’t allow to get the needed information.


Víctor Nàcher Castellet, Prof. Juan Ramón González

Bioinformatics Research Group

Barcelona Institute for Global Health (ISGlobal)

20 Likes

I have connect my Intervals.icu account. However, I get a message that the only data source is Strava and I need to connect something else. I use an Apple Watch Ultra. On the main page it mentions this. My HRV data is definitely being synced from Apple Health to Intervals.icu. There’s no way for me to get past that page, so I don’t know if data will sync or not. I did grant access though.

Signed up!

1 Like

Sounds really interesting — I just connected my Intervals.icu account as well.

I’d love to see this kind of data and modelling eventually incorporated directly into Intervals.icu once the model is mature enough. Being able to better understand how training load affects HRV over the following days, especially in a personalised way, could be very useful for planning harder blocks, recovery periods, and tapers.

Looking forward to seeing how the project develops — and happy to contribute my data. :slight_smile:

1 Like

Hello,

I’ve just signed up and I’m really interested by the result you’ll get: this is the kind of tool I’d really need right now if it already existed!

I’ve one question: my HRV is the overnight HRV measured by my Suunto watch, not my morning HRV, does it matter?

1 Like

Connected

1 Like

I’ve signed up too :flexed_biceps:.

1 Like

Signed up as well.

1 Like

Hi Jordan, thank you for your comment, I sent you a private message :slight_smile:

This is a very interesting project. Personalized HRV models could help people better understand how their bodies respond to different training loads and recovery periods. Since every individual reacts differently to exercise intensity, having data-driven predictions can improve performance while reducing the risk of overtraining. In a similar way, consumers choose trusted products like a Hawkins Pressure Cooker because they know consistent performance and reliability matter. I’m excited to see how your research develops and what insights it can provide for athletes and fitness enthusiasts looking to optimize their training routines.

Also connected my intervals.icu account.

Woulde be nice to have periodically updates on your research! :slight_smile:

1 Like

Connected, you have access to over 5 years of consistent HRV morning data measured with Kubios app.
FYI: In October 2021 I had a thyroid lobectomy resulting in a drastic resting HR decrease.

1 Like

Is HRV data from Apple Watch good? Is it even integrated in intervals.icu?

Apple records SDNN iso RMSSD, stubbornly going in to all others, but the data can still be usefull.

1 Like

Connected my intervals.icu account, but I think the only HRV data from my Garmin 955 is the overnight average, I hope this is useful? I’m just coming back into training after about 3 months off, so likewise I hope that is useful?

1 Like

Like @MedTechCD said, I also have just over 5 years of (almost) daily HRV data at your disposal. None of my athletes I coach use HRV, but would be cool to understand how I can leverage this with my data beyond what I do know.

You’ll find my training cycle is slightly different to the norm, with afternoon training in the week and mornings on weekends.

Data was a mix of HRV4Training and Kubios. You should be able to pick up the difference where some Kubios-data fields have values initially and then stop. Got tired of having to do the manual input.

1 Like

This is very interesting, but, keep in mind that not only training/recovery influences HRV. Alcohol has big influence, and I think it can lead to wrong conclusions.

4 Likes

The way to get reasonable morning HRV from AW is to have a mindfulness session every morning and to sync that data to i.icu, e.g., using HealthFit – which will sync also the rMSSD from that mindfulness session…

1 Like

Víctor , Juan, @BRGE-ISGlobal, looking around a bit it seems that this is also your entry into the bioinformatics of HRV or did I miss previous work?

I am happy to share the data, but second previous comments that it would be great to get some updates, even as simple as “by now received n years of data (overall)” or “analyzed X” or “progressing with Y” …

Moreover, it would be very useful if you would provide a bit more on your ansatz. Maybe along these lines:

  • Are you planning to simply brute force the analysis, supervised or unsupervised learning, will you use something along the lines of physics-informed neural networks, do you have clear models that you wish to fit to the data? Or?
  • How much data do you estimate you will need for statistically significant results?
  • How will you handle the mixed data quality you’ll receive?
  • I assume this is part of Victor’s doctoral thesis – are there local or non-local collaborators involved?

I understand that you might want to protect your research-methodology idea until publication, but you can surely provide some details on idea and the general picture;-)

3 Likes

Honestly I can’t really help with data here, I’m a sprinter (50 free), so my profile is pretty useless for an endurance load model. But I got curious reading it, so a couple of thoughts.

The load side is what I keep getting stuck on. Is intensity distribution going into the model, or just daily TSS plus duration? Because TSS ranks sessions kind of wrong for this. A steady Z2 hour vs an hour of anaerobic intervals can end up at the same or even lower TSS for the intervals, since the rests pull the average down, but the hit on the nervous system is completely different. Z2 your system shrugs off, anaerobic work flattens you.

There’s a paper on this, Seiler et al. 2007, where below VT1 the HRV recovered within minutes, but anything at threshold or above dragged it out. They describe VT1 almost as an on/off switch rather than a gradual thing. A continuous load number can’t really capture that, and since intervals.icu already tracks time in zone, a “time above LT1” flag would probably be an easy add. But the study is acute recovery over a few hours, not next-morning RMSSD, so don’t know if that’s relevant.

Also, are you controlling for lifestyle stuff? Drazen mentioned alcohol. Sleep and stress are the big ones for me. Quick thing from my own data: on a training day my HRV is down the next morning, and the morning after it’s back to normal. So one night down, recovered by the second. But honestly even that pattern isn’t stable. The same session can come out completely different depending on how much stress I’ve got that day or on the recovery day, enough that I’d say stress moves it at least as much as the training does. And that’s where I got stuck looking at it myself. I only have one reading per day, so I genuinely can’t separate whether the recovery is sleep, stress, just time passing, or load clearing. At daily resolution they’re all the same thing. And that’s the bit I’m actually curious how you handle, because with one morning value per person per day you can probably nail the average recovery curve across everyone, but pinning down what one specific person needs seems really hard with that sampling. Which is kind of the whole “personalised” part. How do you get from one reading a day to an individual lag curve, rather than a population one with some spread around it?

Maybe you’ve got all this covered already. Curious where it goes.

2 Likes