Yo-Yo IR1 Field Conditioning Test: Full Protocol and Tracking Guide

A squad grinds through six weeks of a punishing preseason aerobic block, everyone assumes conditioning is climbing, and the one number that would confirm or contradict that assumption never gets checked until week eight — by which point there's nothing left to adjust. That's the gap this guide is built to close. The Yo-Yo Intermittent Recovery Test Level 1 (IR1) is usually taught as a one-off benchmarking exercise: run it once, compare the distance to a normative table, file the result away. Used that way it barely earns the 15–20 minutes it costs to administer. Its real value shows up when it's run repeatedly across a training cycle — preseason baseline, mid-block checkpoint, in-season maintenance — and the athlete's own trend line becomes the reference point instead of someone else's chart. Bangsbo, Iaia, and Krustrup's widely cited review describes exactly this application, noting the test is sensitive enough to training-induced changes in intermittent-exercise capacity to function as a genuine conditioning tracker rather than a screening formality (Bangsbo, Iaia & Krustrup, 2008). What follows is the field setup, the protocol run correctly, and — the part most guides skip — how to read a series of IR1 scores across a season and let that trend actually change what gets programmed next.

Why IR1 for Conditioning Monitoring

The Yo-Yo family splits into Level 1 and Level 2 versions, and the two are not interchangeable for this purpose. IR2 starts faster, escalates faster, and leans harder on anaerobic capacity and repeated high-speed recovery — it's a sharper tool for in-season top-up players who are already well conditioned, but it also carries more neuromuscular fatigue into the following 24–48 hours, which makes frequent retesting harder to justify. IR1 starts at a comfortable 10 km/h and builds more gradually, placing a larger share of its demand on aerobic and cardiovascular recovery capacity rather than raw sprint repeatability. That lower fatigue cost is precisely what makes it suitable as a repeated conditioning gauge rather than a once-a-year benchmark.

Bangsbo, Iaia, and Krustrup's review is explicit that IR1 is the more appropriate variant for tracking aerobic and intermittent-exercise conditioning changes over a training block, reserving IR2 for higher-level squads monitoring in-season readiness (Bangsbo, Iaia & Krustrup, 2008). If the goal is a single conditioning number to plan next block's running volume around, IR1 is the right instrument for the job.

What IR1 Actually Stresses

Each shuttle pair is 20 meters out and 20 meters back, followed by a 10-second active recovery jog covering 2×5 meters behind the line before the next pair begins. That short recovery window is the defining feature — heart rate only partially drops before the next effort starts, which repeatedly challenges stroke volume recovery rather than testing pure aerobic pacing the way a continuous run would. In the original validation cohort, Krustrup and colleagues recorded blood lactate concentrations averaging around 13.6 mmol/L at exhaustion and heart rates reaching 90–98% of individual maximum in the closing stages, confirming the test drives athletes into a genuinely maximal, mixed aerobic-anaerobic state rather than a submaximal aerobic one (Krustrup et al., 2003).

That same study reported IR1 distance correlating with laboratory-measured VO2max at r = 0.58 — a moderate relationship, not a substitute for direct testing, but strong enough to support a widely used field estimate: VO2max (mL/kg/min) ≈ IR1 distance (m) × 0.0084 + 36.4 (Bangsbo et al.). Treat that number as a planning estimate rather than a diagnostic value; the moderate correlation means individual error can run several mL/kg/min in either direction.

Field Setup and Equipment

• Course: Two parallel lines 20 meters apart, marked with cones or field paint, plus a 5-meter recovery zone marked behind each line for the walk-jog during the 10-second recovery window.
• Audio track: A calibrated, official Yo-Yo IR1 audio file. Re-encoded or unofficial copies commonly drift by fractions of a second per shuttle — small per-rep, but compounding across a 10–20 minute test into a meaningfully altered distance.
• Speaker: At least 10W, positioned centrally, audible over ambient noise at 20 meters — outdoor group testing without amplification is a common source of missed beeps and disputed distances.
• Surface and conditions: Note surface type and weather every session; ambient temperature above roughly 25°C measurably raises heart rate and perceived effort at a given running speed, which matters when comparing scores across a season that spans different climates.
• Timing: Schedule at least 48 hours after the last match or maximal session — IR1 distance is sensitive to residual neuromuscular fatigue, which is exactly the confound a conditioning tracker needs to avoid.

Running the Test Step by Step

Warm-Up (10 Minutes)

5 minutes of easy jogging, then 5 progressive 20-meter accelerations at roughly 50%, 60%, 70%, 80%, and 90% effort with 60–90 seconds of rest between reps. Skip maximal sprints in the warm-up — the test itself starts at a manageable 10 km/h, so pre-fatiguing the phosphocreatine system only adds noise to the result.

Conduct

1. Group athletes in lanes of no more than 8 so foot contact at the turnaround line stays visible to the administrator throughout.
2. Start the audio track. Each pair of beeps marks the two 20-meter legs; athletes run out, touch or cross the far line, and run back, aiming to arrive with the beep rather than ahead of or behind it.
3. At the end of each shuttle pair, athletes walk or jog the 5-meter recovery zone and back during the fixed 10-second window before the next pair begins.
4. Running speed increases in small increments as the test progresses, following the audio track. Fatigue accumulates from the repeated recovery demand well before top running speed becomes the limiter for most athletes.
5. The test ends when an athlete fails to reach the line in time with the beep on two consecutive occasions, or stops voluntarily. Record the total distance completed in meters, including the partial shuttle at termination.

Write the distance down immediately rather than relying on memory across a full squad session — a missed or misattributed score at this stage quietly corrupts every retest comparison built on top of it later.

Turning IR1 Into a Season-Long Tracker

A single IR1 score is a snapshot; a series of them, taken under matched conditions, is a conditioning curve you can actually plan against. The table below reflects typical ranges seen across applied preseason and in-season conditioning programs — treat it as a planning guide, not a guarantee, since starting fitness, training age, and program design all shift the numbers.

Before trusting a small change, weigh it against the test's own noise. Krustrup and colleagues reported a test-retest coefficient of variation around 4.9% in well-trained players and higher in less-trained groups (Krustrup et al., 2003), and Fanchini and colleagues' work in youth soccer players found IR1 biological variability substantial enough that only a change well into double-digit percentages could be attributed to training with confidence rather than day-to-day noise (Fanchini et al., 2014). In practice, that means a 4–6% swing between two tests four weeks apart is closer to measurement noise than a real conditioning shift — don't reprogram a block off a single small movement.

Adjusting Conditioning Blocks From IR1 Trends

The trend, not any single test, is what should change the next block's programming.

If IR1 distance climbs sharply through the first two or three weeks of preseason and then flattens despite maintained training load, that's the expected shape of an aerobic adaptation curve — most of the low-hanging aerobic improvement has already been captured. This is the point to shift emphasis toward repeated-sprint ability and high-speed running rather than continuing to chase aerobic volume that has diminishing returns.

If IR1 distance plateaus or drops across two consecutive retests despite continued hard training, check accumulated fatigue before assuming an aerobic problem — residual neuromuscular fatigue depresses shuttle-run performance more than it depresses continuous-running tests, and a genuine aerobic conditioning issue looks different from an athlete who simply needs a deload week. If the squad's IR1 average declines from one in-season monthly check to the next while match load has been heavy, that's a signal to lighten the next week's high-intensity running volume rather than add more.

Errors That Wreck Retest Comparisons

• Switching audio files between sessions: Even small tempo differences between two supposedly official copies of the audio track can shift distance by dozens of meters — use the exact same file for every retest of the same squad.
• Different surface or weather across dates: Comparing an indoor preseason baseline to an outdoor midseason retest in midsummer heat confounds the conditioning signal with environmental conditions.
• Inconsistent group size and motivation: Yo-Yo performance is strongly motivation-dependent; testing a full squad together produces higher scores than testing isolated individuals, so keep group composition and encouragement style consistent between retests.
• Testing at different points relative to match load: A baseline taken after a full rest day compared against a retest taken the morning after a match will show a false decline driven by fatigue, not lost conditioning.
• Skipping the standardized warm-up: A rushed or skipped warm-up on a busy retest day changes early-stage pacing and can shave meaningful distance off an otherwise valid score.