Lifting and Running in the Same Week: What Your Garmin Can and Cannot See
Your squat stalls, you run four times a week, and your watch says you are recovered. All three can be true. Garmin measures one systemic state from heart rate, HRV and sleep, but running and squatting draw on the same quads, hamstrings and calves, and that overlap is invisible to a whole-body score. Here is the two-clock way to plan a hybrid week: a fast decay for the cardio hit, a slower one per muscle group for the lifting, with the actual model constants Rack uses.
The question comes up every week in hybrid training threads, in some version of this: I run four times a week and my squat has stopped moving. My watch says I am recovered. My legs disagree. Who is right?
Both, sort of. Your Garmin is answering a question you did not ask. Here is what it can see when you run and lift in the same week, what it structurally cannot see, and how to plan the week around the difference.
What Your Garmin Actually Measures
Training Load, Recovery Time, Body Battery and Training Readiness are built from heart rate, heart-rate variability, sleep and the intensity of your recorded activities. Every one of them collapses your body into a single number describing one systemic state.
For running that model is close to correct. An easy 10k and a threshold session tax the same cardiovascular system, and the recovery that matters is mostly systemic. This is why Garmin got endurance right first. The model matches the sport.
Lifting breaks the match in a specific way. The limiter on your second squat session of the week is rarely your heart. It is your quads, your hamstrings, your lower back. That fatigue is local, it lives in tissue, and no wrist sensor reads it. So Garmin sees a heavy lower session as a moderate cardiovascular event, prices it accordingly, and clears you for tomorrow.
The Real Problem With Concurrent Training Is Overlap, Not Volume
Most hybrid advice is about total volume: do less of one thing. That is often the wrong knob. The thing that stalls a squat while you run four days a week is usually not the amount of running. It is that the running and the squatting are drawing down the same muscles, and nothing in your week is tracking that overlap.
Run a mile and the bill lands, in rough order, on:
- Quads and calves, heavily.
- Hamstrings, close behind.
- Glutes and hip flexors, meaningfully.
- Trunk, lightly.
That is the same list a squat day hits. Two sessions, one recovery budget, and the only instrument watching is a whole-body score that was never told either session happened at the muscle level. Your upper body, meanwhile, is fresh all week and the score never says so.
Two Clocks, Not One
The other half of the problem is that running fatigue and lifting fatigue do not decay at the same speed. A hard run leaves a big hole that fills fast. A heavy set of five leaves a smaller systemic hole that fills slowly, because the recovery is structural.
A single readiness number cannot express that. It has one clock. If you want to schedule a week honestly, you need at least two: a fast one for the cardio hit, and a slower one per muscle group for the lifting.
How Rack Models It
Rack is a strength app for Garmin athletes, and it runs exactly that two-clock model. Since the numbers are the interesting part, here they are as they exist in the app today.
A logged run is mapped onto the muscles it loads, weighted: quads and calves at full weight, hamstrings at 0.8, glutes at 0.7, hip flexors at 0.5, trunk at 0.25. Cycling, rowing, swimming, hiking and walking each get their own map, which is why a rowing session shows up on your lats and a bike session does not. The size of the hit scales with duration and with intensity, taken from average heart rate in bands, and from pace when heart rate is missing.
Then both kinds of fatigue decay on their own clocks. Cardio uses a 24 hour time constant. Strength uses 72 hours for legs and back, 48 for chest and shoulders, 36 for arms and core. So Tuesday’s tempo run has largely cleared your quads by Thursday, while Monday’s heavy squats have not, and the app can tell you which of those two is standing between you and today’s session.
Worth saying plainly: those constants are a model, not a measurement. Nothing on your wrist reads how repaired your quads are, and Rack does not pretend otherwise. What a set-level and session-level model buys you is an estimate built from what you actually did, which beats a cardiovascular proxy that never saw the barbell or the hill repeats. It is a better guess, not a lab result.
What This Changes About Your Week
Once running and lifting sit in the same ledger, a few scheduling calls stop being guesswork:
- Stop putting hard runs the day before heavy lower work.On a 24 hour cardio clock, yesterday’s hard run is still sitting on the exact muscles you are about to load. Same-day is often kinder than adjacent-day, because it spends one recovery window instead of shortening two.
- Upper days are not rest days, and easy runs are not free. They are just cheap on different accounts. That is the whole argument for tracking by muscle group rather than by a single readiness score.
- A stalled squat with recovered upper body is a distribution problem. Not a motivation problem, and usually not a program problem. Your leg budget is being spent twice and only one of the two spends is showing up in your training log.
Getting Both Halves Into One Ledger
None of this works if the two halves of your training live in different apps. The setup is short.
Log your lifting where the watch can record it. Rack logs sets, reps and weight on the wrist through its Connect IQ app and writes the session to Garmin Connect as a standard FIT activity over Garmin’s partner channel, so the lift still feeds Training Load and Body Battery like any other activity. You keep Garmin’s systemic picture rather than trading it away.
Then let your runs into the same model. On iOS, Rack reads running workouts from Apple Health, and Garmin Connect can write your activities there. Once your runs land, they enter the same fatigue map as your sets, and readiness starts reflecting the week you actually trained instead of half of it.
Frequently Asked Questions
Does Garmin account for lifting when it calculates recovery?
Only as a cardiovascular event. Recovery Time, Body Battery and Training Readiness are built from heart rate, HRV, sleep and activity intensity, so a strength session contributes to the whole-body estimate but the model never learns which muscles did the work. It cannot tell a heavy squat day from an upper day of the same duration and heart rate.
Why is my squat stalling when my Garmin says I am recovered?
Usually because your running and your squatting draw on the same muscles and only the cardiovascular cost is being tracked. Whole-body readiness can read fine while your quads, hamstrings and calves are carrying accumulated local fatigue from both sources.
How many days should I leave between a hard run and heavy leg day?
There is no universal number, and anyone quoting one is guessing about you specifically. What the two-clock model implies is that adjacent days are the expensive arrangement: running fatigue clears on roughly a one day time constant, leg strength fatigue on roughly three, so a hard run the day before squats lands squarely on muscles that have not recovered. Stacking them on the same day, or separating them by two days or more, spends less.
Do my runs count toward recovery tracking in Rack?
Yes. Runs imported from Apple Health are mapped to the muscles they load and folded into the same per-muscle fatigue map as your logged sets, with a shorter decay than strength work. Cycling, rowing, swimming, hiking and walking are mapped too, each with its own muscle profile.
Does logging strength in Rack still feed Garmin’s own metrics?
Yes. The session is written to Garmin Connect as a standard FIT activity, so it contributes to Training Load, Body Battery and Training Readiness the same way a run does. You gain the per-muscle view without giving up the systemic one.
The hybrid athlete’s problem was never that the watch is bad. It is that a watch built to answer “how tired am I” is being asked “which legs do I have left.” Log both halves of the week, track them on their own clocks, and the answer stops being a guess.
If you run and lift and want to know how this behaves with your specific week, send me a message. I’m the dev, and I read everything.