Coaching speed in-season without cooking your athletes
In-season speed work has a different job than off-season development. The goal is to keep important speed qualities alive while practice, games, meets, travel, and lifting already fill the week.
Protect quality before adding volume
Speed work is high-intent work. If you want an athlete to sprint fast, the session has to give them a realistic chance to move fast.
That becomes harder in-season because the athlete is carrying more total load.
A football player may have practice, position work, lifting, and a game. A soccer player may have multiple matches in a short window. A track athlete may already be getting high-intensity exposure through competition.
Adding a large "speed session" on top of that can solve the wrong problem.
In-season, the first question is not how much speed work you can fit into the calendar. It is how little high-quality work is needed to maintain or sharpen the quality you care about without compromising the rest of the week.
Quality over fatigue.
Small doses can still be real speed work
Reducing volume does not mean turning speed training into conditioning.
The intent should stay high. Recoveries should be long enough for the athlete to produce quality reps. The number of reps can come down while the standard of each rep stays high.
That may mean a few accelerations early in practice. It may mean short flying sprint exposures on a day that already fits the weekly high-intensity rhythm. It may mean preserving one specific speed quality instead of trying to train every quality every week.
The right dose depends on the sport, competition schedule, athlete, and what the rest of the program already provides.
That last point matters.
A game can contain high-speed running. A meet can already be the week’s most demanding sprint exposure. A hard team practice can change what makes sense two days later.
Speed programming has to live inside the whole week.
Retest without turning testing into another hard session
In-season retesting can be useful, but it should answer a specific question.
If you are trying to maintain acceleration, a small repeatable test may tell you whether that quality is holding. If top-end speed is the priority, a consistent flying sprint measure may provide better information.
The test does not need to become a combine.
Use a familiar protocol. Keep the volume low. Put it where the athlete can perform honestly enough for the number to mean something. Then compare it with a previous test collected the same way.
If performance is holding, you may not need more work. If it changes, look at context before reacting. Competition load, recovery, recent training, testing conditions, and schedule congestion all matter.
The point of retesting is to adjust intelligently, not to create another score athletes have to survive.
The in-season question
Off-season speed development gives you more room to build.
In-season coaching asks for restraint.
- What quality matters most right now?
- What stimulus is the athlete already getting from the sport?
- Where can high-quality speed fit without burying the next practice or competition?
- What can be removed so the speed work has room to work?
That is the balance.
Keep the intent. Reduce unnecessary volume. Respect total load. Use competition as part of the training picture. Retest only when the information will change a decision.
You do not maintain speed by exhausting athletes in the name of speed work.
You maintain it by protecting the qualities that matter and giving them enough high-quality exposure to stay available when competition asks for them.
