The Ultimate Mid-Block Training Assessment: Week Three Review

A mid training block check in at week three is the window that decides your race. Your body has now had six to eight weeks to respond to your training. The gains from your early work show in your data. So do the gaps. A plateau at week two will still be there at week ten if you do not act. The runners who hit a new Personal Best are not always the hardest trainers. They are the ones who caught their weak driver in time.

Week-3 signal	What it means	Action
Projected Time flat for 2+ weeks	One or more drivers got no new stress this block	Find the lowest driver score. Add one targeted session per week
Wrong workout mix for your goal	You are building the wrong engine for your race	Shift the next two weeks to the drivers your distance needs most
No data behind your goal time	Feeling is filling the gap. Doubt will follow	Check your Supported Range. Set your goal inside it, not above it
Load spike: one very hard week	Injury risk is rising. Tissue lags behind your lungs	Make the next week short and easy. Keep the chain moving
Speed Exposure near zero at week 3	Your top-end pace has had no new signal this block	Add one short fast session. Six to eight hard efforts with full rest
Event Readiness below 75	Body is in Building phase. More hard work now will not help	Hold the next hard block. Add base work for one to two weeks first

What does a mid training block check in at week three reveal?

It reveals your ceiling. By week three, your five driver data is real. It is no longer thin. Your Aerobic Base has had time to grow from easy miles. Your Threshold Density has felt the effect of your tempo runs. Your Speed Exposure score has moved, or it has not.

The ceiling is not fixed. It is the product of your five drivers. A plateau at week three is almost always a driver gap. One driver has had no new stress. It holds the whole chain down. To learn how the five drivers work together, read the 5 performance drivers guide.

Why does a Projected Time plateau happen by week three?

A plateau happens when the signal stops being new. Your body adapts fast. Give it the same load for six weeks. It matches that load. Then it stops growing. Same pace, same miles, same effort: these lock in the same finish time every season.

A study found illness and pushing too hard were tied to training days that all look alike (Foster, 1998). The Personal Best ceiling post has the full math: the body needs contrast, not the same old signal.

80%

of elite endurance training sessions happen at easy effort. Most plateau runners are stuck in the middle (Seiler, 2010)

The fix depends on your lowest driver. A low Speed Exposure score means add one fast session this week. Use six to eight short, hard efforts with rest in between. Short, hard efforts raise top-end power more than slow runs (Helgerud et al., 2007). A thin Aerobic Base means add two easy runs. Easy means you can hold a full talk. A clear easy/hard split builds more fitness than the middle zone (Seiler, 2010). Contrast is the signal.

Are you training the right workouts for your goal distance?

Week three is also the time to check workout fit. A 5K runner who does only easy miles builds the wrong engine. A marathon runner who fills weeks with speed work skips the base that holds pace at mile 20.

The post on right workouts for your race goal shows the full map. For the 5K, Speed Exposure and Threshold Density lead. For the marathon, Aerobic Base and Load Consistency lead. A study looked at 917 Boston runners. Higher weekly volume was one of the strongest links to a faster finish time (DeJong Lempke & Ackerman, 2025). Volume drives long events. Speed drives short ones.

If your week-three driver scores do not match your goal distance, fix the mix now. You have enough weeks left for a change to take hold. Race week is too late.

Do you know what race time your training actually supports?

By week three, your Projected Time is built on real data. Your Supported Range has narrowed. You can now set a goal your data backs.

The post on knowing your race potential before race day shows why this matters. Belief in what you can do follows real proof. A review of 44 studies found a clear link between pre-race belief and race results (Lochbaum & Sisneros, 2023). Your Projected Time is that proof.

A goal inside your Supported Range is one your data backs. A goal above it is a wish. Week three is the time to be honest about which one you have.

Is your Load Consistency score showing a danger sign?

Load Consistency guards all the other drivers. Big load jumps lower the score. Runs that were too long lower it too. So do weeks with very different totals. A low score means the injury window is open.

The post on mid-block injuries and overtraining shows what happens when one driver breaks. More than 44 percent of runners had an injury in the past year. Most were overuse injuries (Stenerson & Melton, 2023). In a study of more than 5,200 runners, one run that was too long raised injury rates (Frandsen et al., 2025).

The fix is not full rest. Keep running. Keep every run short and easy for one week. Then build back in small steps. When recent load tops 1.3 times your four-week base, that is your warning. Pull back before it climbs higher.

What does your Event Readiness score say about your next hard session?

Event Readiness is a 0 to 100 score. The bands are: 95 to 100 Race Ready, 88 to 94 Sharpening, 75 to 87 Building, and 60 to 74 Foundational.

A score in the Foundational range means your body is not ready. Do not add another hard block yet. More hard work now will not help. It will cost you rest time you cannot get back. Add base work. Let the score move to Building before the next hard session.

The post on Event Readiness and your next interval covers how to use this score to time hard work. One rule is simple. If a hard session leaves you flat for two or more days, the next one came too soon.

Is your hard training showing up in your Projected Time?

Hard training and a faster race are not the same thing. Some runners log their best block and then run a flat race. The post on why hard training does not always show on race day looks at the gap.

If your Projected Time has not moved, the cause is almost always a driver that has not responded. The workout may have been too easy for that driver. Or it was the wrong driver for your goal. Or Load Consistency broke and rest took over.

Check each driver. Find the one that has not moved. That is where your next week of work goes.

How does PIRX do the mid-block check for you?

Generic apps track miles and pace. They do not show which driver is lagging. They do not flag a Load Consistency drop before it costs you weeks.

PIRX uses a proprietary machine-learning prediction engine. It reads your real runs. It breaks your fitness into five drivers. They are Aerobic Base, Threshold Density, Speed Exposure, Load Consistency, and Running Economy. Each driver earns or costs seconds. The total builds your Projected Time. It updates after every synced run. A change shows only when the shift is at least 2 seconds. You see real moves, not noise.

A single fixed formula treats every runner the same. It cannot spot a driver gap or a load spike. PIRX can.

98%

validated prediction accuracy (PIRX users)

Stop following a broad plan. Get a projection built for you.

Online plans are built for a runner who does not exist. They are made for an average person, not your driver mix. They do not know if Speed Exposure is your gap. They do not know that Load Consistency dropped two weeks ago.

Week three is the time to stop using a plan that does not know you. Your training data holds the answer. Connect your Garmin, COROS, or Strava to PIRX in under 30 seconds. See your five driver scores. Find where your seconds come from. Get a Projected Time built on your own data. Not a formula that treats every runner the same. Free, with no signup.

Sources

• Foster, C. (1998). Monitoring training in athletes with reference to overtraining syndrome. Med Sci Sports Exerc. (High training sameness and strain predict illness and overreaching in trained athletes.)
• Seiler, S. (2010). What is best practice for training intensity and duration distribution in endurance athletes? Int J Sports Physiol Perform. (Elite athletes train about 80 percent easy and 20 percent hard; contrast between zones drives growth.)
• Helgerud, J. et al. (2007). Aerobic high-intensity intervals improve VO2max more than moderate training. Med Sci Sports Exerc. (Short, hard intervals raise top oxygen power more than steady running.)
• DeJong Lempke, A.F. & Ackerman, K.E. (2025). Training Volume and Training Frequency Changes Associated with Boston Marathon Race Performance. Sports Medicine. (Higher weekly volume linked to faster marathon finish times in 917 Boston runners.)
• Stenerson, L.R. & Melton, B.F. (2023). Running-Related Overuse Injuries and Their Relationship with Run and Resistance Training Characteristics in Adult Recreational Runners. J Funct Morphol Kinesiol. (44.6% of runners reported a running-related injury in the past year; most were overuse injuries.)
• Frandsen, J.S.B., Hulme, A., Parner, E.T., & Moller, M. (2025). How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study. Br J Sports Med. (Single sessions more than 10 percent longer than usual linked to higher overuse injury rates in 5,200 runners.)
• Lochbaum, M. & Sisneros, C. (2023). Pre-Event Self-Efficacy and Sports Performance: A Systematic Review with Meta-Analysis. Sports (Basel). (Pre-event belief had a moderate positive link to sports results across 44 studies; r = 0.31.)
• Gabbett, T.J. (2016). The training-injury prevention paradox: should athletes be training smarter and harder? Br J Sports Med. (Steady load reduces injury risk; acute:chronic ratio of 0.8 to 1.3 is the lower-risk zone.)