Designing an In-Season Power Testing Schedule That Doesn't Wreck Legs

A collegiate strength coach running a 16-week volleyball season faces a specific version of a common problem: the team plays two matches a week, travels for one of them, and still needs weekly power data to catch a hamstring strain risk or an overreaching setter before it turns into a missed match. Test too often and the testing itself becomes another fatiguing session stacked on top of an already dense calendar. Test too rarely, or on the wrong day, and the numbers bounce around so much from residual match fatigue that nobody trusts them enough to act on a real drop when one shows up.

The mistake most programs make isn't choosing the wrong test - it's placing the right test on the wrong day. A countermovement jump measured 18 hours after a five-set match is measuring match fatigue, not the athlete's underlying power trend, and a coach who reacts to that number by pulling an athlete from practice is treating noise as signal. This guide lays out where power testing should sit inside a competitive microcycle, how testing frequency should differ by sport and calendar density, and the specific thresholds that separate a real neuromuscular red flag from ordinary week-to-week variation.

Countermovement jump height and other power metrics are sensitive to acute fatigue on a timescale most programs underestimate. Gathercole, Sporer, and Stellingwerff (2015, International Journal of Sports Physiology and Performance) tracked CMJ variables across the 72 hours following simulated team-sport match play in a sample of 15 male athletes and found that flight time and eccentric-phase kinetics remained measurably depressed at 24 hours post-match, with several variables not returning fully to baseline until closer to 48-72 hours depending on match intensity. That timeline is the single most important number in this entire guide, because it defines a hard floor for how close to a competition you can test and still call the result a baseline reading rather than a fatigue reading.

The practical implication is that a Monday test following a Saturday match is defensible for most team sports, while a Sunday test following the same match is measuring residual fatigue that hasn't cleared yet. Programs that test the day immediately after competition tend to see systematically depressed numbers every single week, which either gets normalized as the athlete's new baseline (masking a real decline) or triggers unnecessary alarm every cycle (eroding trust in the data). Either failure mode defeats the purpose of testing in the first place.

The flip side matters too. Testing too close to the next competition - inside roughly 48 hours - risks the test itself contributing meaningful neuromuscular fatigue into a match, particularly for jump-based protocols that involve multiple maximal efforts. The workable window for most in-season power checks sits in the middle third of the gap between two competitions, far enough from the last match for fatigue to clear and far enough from the next one that the test doesn't compete with match preparation for recovery resources.

There is no single correct testing frequency across all sports, because the answer depends entirely on how much recovery time sits between competitions. A sport with one game a week has room for a genuine mid-week testing checkpoint; a sport with three matches in nine days often doesn't, and forcing a weekly test schedule onto a congested calendar just adds another fatiguing session where there's no room for one.

Malone, Owen, Newton, et al. (2015, Journal of Science and Medicine in Sport) monitored elite Gaelic football players across a competitive season and reported that acute:chronic workload ratios, closely tied to the same fatigue mechanisms that depress jump output, predicted injury risk with meaningfully elevated odds when spikes exceeded roughly 1.5 relative to the athlete's rolling 4-week average. That finding underscores why testing frequency should track the calendar rather than a fixed weekly habit - the weeks that matter most for catching a real problem are the ones immediately following a spike in competition or travel load, not necessarily the weeks that happen to fall on your default testing day.

For a standard one-game-per-week team sport, the following structure keeps testing inside the recovery window described above while still producing a data point every week for trend tracking.

Day +2 works as the primary checkpoint for most weekly-competition sports because it sits roughly 48 hours removed from the prior match - inside the window where Gathercole et al.'s data shows most CMJ variables have substantially recovered - while still leaving four clear days before the next competition. The optional Day +5 check is a shorter single-jump readiness screen rather than a full battery, useful for flagging an athlete who needs a load adjustment heading into game day without adding meaningful fatigue that close to competition. Programs managing power alongside strength work often layer this schedule against the broader in-season loading model described in our in-season power maintenance program guide.

Not every checkpoint needs the full testing battery, and trying to run one every week is itself a common driver of in-season testing fatigue. A tiered structure keeps the weekly checkpoint fast enough to survive a real season while still capturing enough data to act on.

• Weekly checkpoint (5-8 minutes per athlete): CMJ height and reactive strength index (RSI) via a modified drop jump, both trackable on a standard IMU or jump mat setup without a dedicated testing day.
• Monthly checkpoint (15-20 minutes per athlete): Add a linear sprint split (10m and 30m) and a load-velocity check on the athlete's primary lower-body lift to catch trends that a jump-only battery can miss, particularly for athletes whose power expression is more sprint-dominant than jump-dominant.
• Pre-season and mid-season only (30+ minutes per athlete): Full force-velocity profiling and a complete testing battery matching the structure in our athlete testing battery guide, reserved for windows with genuine recovery room rather than a congested competition stretch.

RSI deserves a specific mention because it is one of the more sensitive markers for detecting accumulating neuromuscular fatigue before it shows up as a jump-height drop, since it reflects how efficiently an athlete converts ground contact time into height rather than raw output alone. Programs that haven't built this into their weekly checkpoint can reference our drop jump RSI test protocol and the related guidance on using RSI for plyometric readiness decisions.

The single biggest reason coaches stop trusting in-season testing data is reacting to normal week-to-week noise as if it were a real decline. CMJ height in trained athletes typically carries a test-retest coefficient of variation in the 3-6% range even under well-controlled conditions, which means a jump height that dips 4% from last week's number is very likely measurement noise, not a meaningful drop in an athlete's underlying power.

Comparing against a rolling 3-4 week baseline rather than a single prior session or a preseason number matters here, since a single early-season test can become an outdated anchor once fitness and fatigue patterns shift over a long competitive block. The same rolling-average logic used to flag acute:chronic workload spikes in the Malone et al. research applies directly to power output tracking: a moving baseline adapts to genuine long-term change in the athlete while still catching an acute deviation worth acting on. Coaches building this into a broader monitoring system can pair it with the flagging logic in our training readiness monitoring guide.

Most in-season testing programs don't fail because the test itself is wrong - they fail because of small scheduling inconsistencies that compound across a season until the data stops meaning anything.

• Testing at different times of day. A morning test compared against an afternoon test from three weeks earlier introduces diurnal variation of several percent into a comparison that should be measuring training effect, not time of day.
• Skipping the checkpoint during a bye week and calling it a data gap. Bye weeks are actually the best window for a full battery precisely because both directions of the recovery window are clear - skipping it wastes the single easiest data point of the month.
• Changing the warm-up before testing. A shortened warm-up on a rushed practice day changes CMJ output independent of any real fitness change, and coaches rarely log the warm-up difference when reviewing the number later.
• Testing everyone on the same day regardless of individual game-minutes played. A starter who played 90 minutes and a reserve who played 10 are not on the same fatigue clock, and a single team-wide testing day treats them as if they were.
• Abandoning the schedule the moment results look good. A few clean weeks of data is exactly when programs stop testing consistently, which is also exactly when an emerging problem is most likely to go undetected until it becomes a soft-tissue injury.

None of these fixes require new equipment or a longer testing session - they require treating the schedule itself as part of the protocol, with the same discipline a coach would apply to load prescription or lifting technique.