Learn
How to Program Concurrent Training: Strength and Endurance in One Plan
Why concurrent training is hard
Most programming advice assumes you are specialising. Strength programs ignore your running. Running programs ignore your lifting. The athletes who actually need both, hybrid athletes, triathletes in off-season, team sport players wanting to add endurance, get told to “just balance it”. That is not programming, that is guessing.
Concurrent training is the deliberate practice of developing strength and endurance together, in one plan, without losing adaptation in either. It has real science behind it, and it is doable, but it demands intention.
The interference effect, understood
The classical finding from Hickson (1980) is that combining high-volume strength and endurance training blunts both adaptations compared to training either in isolation. That result, cited for 40 years, is true but overstated.
Modern research refines the picture. Interference mostly affects:
- Sessions within 6 hours of each other. The molecular signalling pathways for strength (mTOR) and endurance (AMPK) compete when stacked close together.
- High-intensity endurance. Zone 4-5 work blunts strength adaptation more than Zone 2.
- Novice athletes. They have more to gain and more to lose; trained athletes interfere less because their adaptations are already established.
Practical takeaway: separate hard strength and hard endurance sessions by at least 6 hours, use lower-intensity endurance on strength days, and schedule them intelligently rather than colliding them.
A four-day template that works
For a recreational athlete with strength and endurance goals:
- Monday: Strength (lower body primary)
- Tuesday: Endurance tempo run
- Wednesday: Rest or easy Zone 2 cross-training
- Thursday: Strength (upper body primary)
- Friday: Endurance interval session
- Saturday: Long easy endurance session
- Sunday: Rest
Strength sessions land on days that do not follow hard endurance. Hard endurance does not precede strength. Zone 2 work fills the gaps without compounding fatigue.
Scale up to five or six sessions only if the four-day template is fully recoverable. Most recreational athletes plateau on the four-day version long before volume becomes the limiter.
How to manage volume week to week
The most common mistake in concurrent training is adding sessions without removing anything. You start running three days a week, add a fourth, keep the three strength sessions, and wonder why your squat stalls.
Rules of thumb:
- If you add an endurance session, drop one set across each strength session. Net volume is protected.
- If you add a strength session, reduce endurance duration by 10-20%. Your legs feel it.
- Every fourth week is a deload. Volume down 30-40%, intensity maintained. This is where adaptations actually land.
How Pelaris programs concurrent training
Programming concurrent training by hand is doable but tedious. You are managing interference timing, weekly volume math, and recovery markers across two systems at once. Pelaris treats concurrent training as a first-class problem, not an afterthought, and automates the parts that break down when done by hand.
Tell it the shape of athlete you want to be. Pelaris asks for your strength and endurance goals at intake, along with weekly availability, equipment, and any blocked training days. The generator picks a named methodology for each pillar (for example, 5/3/1 on the strength side paired with Pfitzinger or 80/20 on the running side) and writes a unified weekly plan from both.
It respects the six-hour rule. Hard endurance and heavy strength are scheduled with at least six hours between them on the same day, or on separate days entirely when your availability allows. Interference timing is part of the scheduler, not a rule you have to enforce yourself.
It reads your data and bends. Every session you log feeds back into the next week. Strength RPE climbing on the same loads cuts next week’s endurance volume before strength collapses. A hard long run logged at higher RPE than expected pulls the next heavy squat day back 24 hours. The concurrent training page walks through the scheduling model in detail.
Deload weeks are automatic. Every fourth week drops volume 30-40% on both systems at once, not just one of them. Deloads are programmed, not requested.
Match days and races win. If you have a half marathon on the calendar, everything around it reshapes: taper protocol before, active recovery after. Same for a meet or a tournament. Match-day aware scheduling is how the team sports framework and the Hyrox race prep and CrossFit programming flows all sit inside the same concurrent training engine.
Free to log, paid to coach. The tracker records every concurrent training session for free forever. The AI program generation that coordinates all of this is the one thing behind the paid tier. See the workout tracker page for the full free-tier breakdown.
For the theoretical basis Pelaris implements, the methodology library lists every named strength and endurance system the generator can draw from.