Best-Running-Tips.com

Managing Total Training Load: Running, Strength & Cross-Training

Your body doesn't care whether yesterday's fatigue came from a hard run, a heavy squat session, or an hour on the bike. It only cares how much fatigue there is to recover from. Here's the fix: multiply each session's RPE (1-10 scale) by its duration in minutes to get that session's load points. Add up a rolling week's points across running, strength, and cross-training alike. One number, every modality, the same scale.

I've had runners add two strength sessions during a base phase and hold their mileage dead flat. Their weekly load nearly doubled without them noticing — until they started logging it this way. Below is the exact method, plus what to do when the numbers spike.

Why Total Load Matters Once You Add Strength or Cross-Training

The full doubles, strength, and cross-training framework gives you a fast gut-check: keep your combined hard sessions to roughly 2-3 a week. That heuristic works well for a quick decision on a Sunday night. It doesn't work if you want an actual number.

This page is for the runner who wants more than a gut-check. Maybe you're stacking a build phase, training for a specific race, or you've been burned before. Load that felt fine day to day can show up three weeks later as an injury or a flat patch — exactly the failure mode a hard-session count alone can miss.

Here's the trap: mileage-only tracking watches running and nothing else. Your weekly mileage can hold flat, or even fall, while your total training load quietly climbs, because strength and cross-training sessions add real fatigue that a mileage log never sees. If your question is really "am I ready to add a second daily run", check whether you're ready to add a double answers that specifically. This page answers the bigger one: is your combined week, across everything you're doing, actually sustainable?

The Acute:Chronic Workload Ratio, Explained Simply for Runners

Acute:chronic workload ratio — ACWR for short — sounds like sports-science jargon because it is. Strip away the jargon and it's simple: it's your recent load, the last week or two ("acute"), divided by your rolling four-week average ("chronic").

The commonly cited sweet spot sits between 0.8 and 1.3. Below 0.8 and you're likely detraining or under-loading. Above 1.3 and injury risk research — mostly team-sport, with some running-specific data now — starts climbing.


Beware one thing: ACWR was built and validated mostly on team-sport athletes wearing GPS trackers, not recreational runners with a notebook. That's exactly why the method below gives you a version that doesn't need a ratio calculator at all — just a pen and a weekly total.

A Simple RPE-Based Method to Combine Load Across Modalities

Here's the method in full: RPE (1-10, where 10 is an all-out effort) × session duration in minutes = load points for that session. It works identically whether the session is a run, a lift, or a bike ride. For the first time, a run and a strength session sit on the same scale.

Take a 45-minute easy run at RPE 4. That's 180 points. Now take a 45-minute strength session at RPE 6. That's 270 points — more load than the run, despite feeling like "just the gym" to most runners.

I have my athletes log RPE × duration for two weeks before we even discuss adding strength or cross-training. The runners who most need this exercise are usually the ones most convinced their new addition is easy relative to running. The numbers usually disagree.

Here's a full worked week:


Notice that Wednesday's strength session (270 points) outscored both easy runs (160 and 140) on its own. That's the whole point of tracking across modalities rather than mileage alone.

Once you've logged four weeks like this, you can calculate your own acute:chronic ratio by hand. Take your most recent week (or two) and divide by your rolling four-week average. Check it against the 0.8-1.3 range above — except now you've got real numbers instead of a guess.

Weighting a Hard Lift or Cross-Training Session Against a Hard Run

Under this method, a session's contribution to your total load is set by how hard it felt and how long it lasted — not by which modality produced it. A genuinely hard 45-minute lift can outweigh an easy 45-minute run. A long, easy cross-training ride can carry more total load than a short, brutal interval session, even though the interval feels worse in the moment.

One adjustment is worth making. It's my own practical call, not a claim from the sports-science literature: add a small multiplier, roughly 1.1-1.2x, to running-specific load when you're deep in a high-mileage phase. Repetitive impact loading carries an orthopaedic cost — the pounding through your joints and connective tissue — that RPE alone under-counts relative to non-impact modalities like cycling or swimming.

Low-Tech Alternatives If You Don't Use Training Software

Not everyone wants to log RPE × duration after every session, and that's fine — there's a lower-effort entry point. Count only sessions at RPE 7 or higher, regardless of modality, and cap your weekly total at 2-3, per the Tier-3 anchor's simple guideline. A fourth hard session in the same week is your trigger to check in on recovery, not push through.

Think of it as a ladder: the hard-session count is your entry-level rung, quick and workable with nothing but memory. The full point-based method above is the upgrade, for whenever you want more precision than a headcount can give you.

What to Do When Your Combined Load Spikes

Set the trigger at roughly 30-40% above your rolling four-week average. A week's total load rising past that isn't a badge of a good week — treat it as a spike that needs a response.

The response protocol, in order: cut the most recently added modality first. That's usually strength or cross-training, since your running volume is normally the base the rest of your schedule was already built around. If the spike came from running itself — a race, a long-run jump — hold strength and cross-training flat rather than also cutting them, so your total load actually drops instead of everything shrinking at once. Two consecutive spike weeks, or a spike paired with soreness that doesn't clear in 48 hours, is your signal for a genuine down week across all three modalities together.

I coached a club runner who added two strength sessions during a base phase without cutting anything else. Their weekly load points nearly doubled in three weeks. Mileage stayed completely unchanged. We caught it before it turned into an injury only because they'd started logging sessions — not because anything felt wrong day to day. That's the entire point of tracking this: the numbers see the spike before your body forces you to.

A Sample Week With Load Numbers Attached

The worked week above is intentionally compact — it's there to show you the method, not to double as your training plan. For the full weekly schedule question — how to actually arrange doubles, a lift, and a cross-training session across seven days — a full sample week combining all three is the dedicated page, including how to scale it down if you're running fewer days. This page's job stops at the numbers. That page's job is the calendar.

Your training load isn't fixed across a season, either. How much strength and cross-training you can carry shifts as your running volume rises and falls through the year. See how the mix should shift across your training cycle for the dedicated breakdown.

Total load doesn't care about your calendar, and it doesn't care which modality produced it — it only adds up. Track it honestly for a month and you'll know, in numbers rather than guesswork, whether your combination of running, strength, and cross-training is building you up or quietly digging a hole.

Some Other Pages You May Like

Home > Running Training > Two-a-Day, Strength, and Cross-Training > Managing Total Training Load

  ☕ Buy Dom a Coffee