When Half Your Team Didn’t Train This Summer

Bekka showed up to the alumni race on a steamy Friday evening in August. She had barely run all summer. She won it. She beat every returner on the roster, including two girls who had logged three hundred miles since June.

So when practice started the following week, she went with the varsity group. Of course she did. She had just proved herself to be the fastest on the team.

Three weeks later she had shin splints. She was missing two or three days a week. She still raced well, because she was that kind of athlete, but she never again touched what she ran at that preseason race. And she chose not come back the next year.

Nothing about that is a talent story. It is a load story, and it is the most common way a program loses its best runner.

Bekka’s fitness on race day was real. Her structural readiness was not.

Winning a 5K off almost no summer running tells you what her engine can do. It tells you nothing about what her shins have been prepared to absorb. Those two things run on completely different clocks, and August is where coaches often confuse them.

Right now, some fraction of your roster is a version of Bekka. Another fraction did the work. You have one practice window, one or two coaches, and two populations who cannot safely do the same run. Most of us end up choosing between two bad options. Train everyone together and hurt somebody. Or split them and build a visible underclass in the first week of the season.

There is a third option. Here is the sequence.

Start with intake, not mileage

Do not open a spreadsheet. Look at an index card.

Three questions, handed out on the first day, answered privately:

1. What is the longest single run you have done in the last 30 days?
2. How many days per week have you run in the last 30 days?
3. Do you have any pain that changes how you run?

Then say the part that makes the card work. Nobody loses a spot over what is written here. A low honest number gets you a better plan than a high false one.

That is not a kindness. It is a system requirement. A lied-about number produces a mis-prescribed session, and the athlete pays for it, not you. Teenagers inflate summer mileage for the same reason adults do, because they think the number is a verdict on their character. Your job in that first conversation is to make the number boring. It is an input, nothing more.

Two answers on that card outrank everything else, and neither one is about volume. A systematic review of running injury risk in high school and collegiate cross country runners found the strongest predictors were sex and previous injury history. There was moderate certainty that markers of low energy availability raised injury risk, particularly bone stress injuries. Evidence linking training volume changes to injury was limited.

Read that again, because it reorders your worry list. The athlete who scares me in week one is not the one who ran nothing. It is the one who came back from summer noticeably lighter, or the one who limped through last November and never got it looked at. Those two get a conversation before they get a training group.

Add one more thing you cannot put on a card. Watch for the kid who grew four inches since June. The period around peak height velocity carries elevated injury risk on its own, and athletes growing faster than about seven centimeters a year warrant adjusted training regardless of what their summer log says.

The rule that governs everything: the 30-day ceiling

Most of us were taught to manage load by the week. Add ten percent to weekly mileage, take a down week every fourth week, stay healthy. Weekly framing is useful for planning a season. It is not what the injury data points at.

The Garmin-RunSafe Running Health Study followed 5,205 runners across 588,071 recorded sessions over eighteen months. Researchers tested three ways of measuring load change against injury: week-to-week mileage change, the acute to chronic workload ratio, and single-session distance compared to that runner’s longest run in the previous 30 days.

Only the third one predicted overuse injury. Week-to-week mileage change showed no relationship at all.

Sessions that ran ten to thirty percent past the longest recent run carried a 64 percent higher injury rate. Thirty to one hundred percent past carried 52 percent higher. More than double carried more than twice the rate.

This also explains something that has quietly bothered coaches for years. The ten percent rule has never survived an actual test. In a randomized trial comparing a thirteen-week graded program built on the ten percent rule against a standard eight-week program, injury rates came out the same. A prospective study of high school cross country runners found weekly volume and weekly changes in volume, duration, and intensity were not associated with injury either.

So the danger to Bekka was never week three. It was the first Saturday. Her longest recent run was probably three miles. Varsity ran seven. That single session was more than double what her body had recently done, and we handed it to her because she won a race.

The rule that comes out of this is simple enough to run in your head on a Monday:

No athlete’s single run goes more than about ten percent past the longest run they have completed in the last 30 days.

That number is their ceiling. It is individual, it updates weekly, and it explains itself to a parent in one sentence. It is also the reason the group split stops being your opinion of an athlete and becomes arithmetic from a number they gave you themselves.

One honest caveat, because you should know where the evidence thins out. That cohort was adult recreational runners with an average age in the mid forties, not fifteen year olds. Treat the ceiling as a decision rule that stops you from making the obvious mistake, not as a law of adolescent physiology. It sits on top of your existing volume framework. It does not replace it. For the weekly side, use the progressive mileage guidelines.

Four groups, sorted by what they have actually done

Run every athlete through the ceiling. Then group them by it. Not by grade. Not by personal best. Not by who you think should be varsity in October.

Adjust those numbers to your program. The structure matters more than my specific mileage, and your volume caps by class year still apply on top of it.

Two rules about the groups themselves.

Never name a group for what it lacks. No slow group, no beginner group, no C group. Name the training block, because that is what the group actually is. Foundation is a phase of training, not a category of person.

Publish the promotion criteria on day one, with dates. A group with a visible exit is a phase. A group with no exit is a label. Athletes will accept almost any starting point if they can see the road out of it and the date they get reassessed.

Build the practice so nobody watches anybody finish

This is the part that decides whether your split reads as coaching or as punishment, and it has nothing to do with the training.

Shared start. Everybody together for warmup, drills, strides, and whatever your team does before the work begins. Same field, same voice, same expectations.

Split middle. Groups separate only for the main set. This is the ten to forty minutes where the training actually differs.

Shared finish. Everybody back together for core, strength, stretching, and the team ritual at the end. Nobody leaves before anybody else.

The detail that makes it work is start times. Stagger them so the groups converge instead of trailing in. If the Sharpen group is running fifty minutes and Foundation is running twenty five, Foundation does drills and strength first and goes out later. What you are avoiding is the image of the Foundation group standing around watching varsity come in. That image is the punishment, not the mileage.

The last thing worth saying about practice design: give the Foundation group real content, not less content. Hill sprints, strides, drills, and strength load tissue without adding distance. They should leave practice tired. An athlete who feels like they are being given the leftovers of your attention has already started drafting the sentence they will say to their parents in the car.

The 5K is a spike

Here is the decision most of us get wrong, because meet entries are due before the training has caught up.

For an athlete whose longest run in the last 30 days is two miles, a 5K is a distance spike and an intensity spike in the same afternoon. It is roughly 55 percent past their longest recent run, and it is run at a pace they have not touched since June. Every research band above applies, and race intensity compounds it.

So treat race entries as load decisions. Three options for an athlete under their ceiling:

• Hold them out of the opener. Two to three weeks of building, then a controlled time trial, then race.
• Enter with a pace cap and a pull point. They run the first two miles at a prescribed effort. You pull them at a set place, agreed in advance, in front of everyone, without drama.
• Race a shorter option if your schedule offers one.

Say the quiet part to the athlete directly. A kid who races unprepared in week two often disappears by October. You are not protecting a place in the standings. You are protecting a four-year athlete.

When the freshman beats the returner

This is Bekka’s situation from the other side, and it comes up every August.

There are two clocks. The fitness clock runs in weeks. The development clock runs in years. An August time trial measures the fitness clock only.

Your junior with three years of base did not lose her engine over eight quiet weeks. She lost her August sharpness. She will get it back faster than the freshman can build it for the first time.

What that means in practice:

• Publish the varsity selection policy before the first time trial. Policy stated in advance is data. The same policy stated afterward is favoritism, and every kid on your roster knows the difference.
• Use the result as information, not as a verdict. To the returner: this is what eight weeks off costs, and here is the four-week plan to get it back. No speech about commitment. The result already made your point better than you can.
• Protect the outlier freshman from your own excitement. This is the exact athlete who accumulates a bone stress injury in October. Incidence in adolescent athletes runs between roughly 4 and 19 percent depending on the population, with recurrence rates as high as 21 percent. A talented freshman does not need to be at the front in September.

How to say it so it does not sound like punishment

Everything above fails if you deliver it badly. Here are the words.

To the athlete, frame by physiology and destination, never by fault.

“Your body has been running two miles. We are going to spend three weeks earning the right to run six. On September 15 we reassess.”

Not: you should have run this summer. That sentence costs you the athlete and buys you nothing. June is over. You are coaching the roster that showed up.

Give them choices inside the constraint. Athletes who perceive their coach as autonomy supportive report more self-determined motivation and stronger commitment to the sport. Practically, that means letting them choose things that do not change the load. The route. The training partner. The constraint is yours. The decisions inside it can be theirs.

To the returner who is angry about the group they are in.

“This group is where your last 30 days put you, not where your season ends. You have three years of base that a freshman does not have. That is why you will move up faster than anybody here.”

To the parent who calls.

“We group by the longest run each athlete has done in the last month, because that is what the injury research points at. Everybody warms up together, everybody finishes together, and we reassess every week.”

And one for yourself. There is a real temptation to let the athletes who skipped summer feel the cost of it. That instinct is understandable and it is expensive. You can be honest about the consequences without engineering them.

The three-week checkpoint

Rerun the index card at three weeks. Same three questions.

Move athletes on criteria, not on effort or attitude. If you promote a kid because she is trying hard and her ceiling does not support it, you have just done the varsity-group thing to her that we did to Bekka.

For the athlete who is not progressing, look past the training first. Sleep, fueling, and school stress explain more stalled Septembers than mileage does. That conversation is usually more useful than another week of adjustments to their long run.

And set the standard for yourself now, before the first meet gives you a reason to move it. You judge these August decisions by the November roster, not the September results. Count the kids still running. Count the kids who come back next year.

Bekka was fast in August. That was never the problem.

Frequently asked questions