Run By Numbers

Demo

Weekly Structure Interpreter

See how the workouts in your week affect one another.

Required

Optional: sharper analysis with more context

Run this on your athletes →

Example output

Weekly Identity

This week is built around one Saturday race, and everything else in the week is subordinate to it. That's not a filler week and not a base-building week — it's a race-week architecture. The dominant signature is: touch threshold early, touch speed late, race Saturday. The volume is deliberately restrained across every session — nothing here is designed to create new fitness. It's designed to express fitness that already exists while keeping the athlete sharp, aerobically ticking over, and neurologically primed. This is a taper-flavored championship week, not a training-load week.

Each Workout's Role

Mon: 45 min easy + 6 strides — Genuine aerobic ticking-over, Endurance zone, well below AeT-to-vLT stress. The strides are the only "quality" texture here, and at 100m or so they're neuromuscular primer, not conditioning — near-free, as intended. Sitting first in the week, this is the furthest session from Saturday's race, so it can absorb a small amount of density (easy run + strides) without threatening recovery.

Tue: 5 x 1000m at threshold effort on grass, 90 sec jog — This is the week's single meaningful stress dose. Threshold effort sits in the Stamina zone — above AeT, at or near vLT — which by the role tables is Direct Endurance to Endurance Support territory relative to 5K, not Specific Endurance itself. Total volume: 5000m at threshold, well inside any reasonable ceiling for a 5K athlete and appropriately submaximal for six days out from a race. Running it on grass is notable — softer surface, lower impact cost, and terrain-specificity if the invitational is also on grass. The short jog recovery (90 sec vs. a full lap) keeps the session dense and controlled rather than truly race-pace-intensive.

Wed: 35 min recovery — The hinge day. Positioned exactly 24 hours after the week's only hard session and roughly 72 hours before the race, this is where the Tuesday threshold bill gets paid down. Stamina-zone work costs 36-48 hours of recovery — this run respects that window rather than fighting it.

Thu: 10 x 200m relaxed fast, full walk-back — This is Direct Speed to Speed Support territory relative to 5K — short, fast, and, critically, "relaxed." Full walk-back recovery is a deliberate choice here (an exception to default jog recovery, and correctly so): the intent isn't conditioning, it's turnover and mechanical sharpness with essentially no aerobic cost. This is a neuromuscular primer, 48 hours before the race — exactly the window where speed-zone work clears (48-72h) in time to race fresh.

Fri: 30 min easy — Pure shake-out. Nothing borrowed against Saturday.

Sat: 5K invitational — The point of the entire week. This is Specific Endurance itself, run at full race intensity — the target the rest of the week was built to deliver the athlete to fresh.

Sun: Off — Full recovery after the highest-cost day of the week (racing is Aerobic Power/Speed-zone stress in a 5K, carrying a 48-72h bill).

How the Sessions Interact

The week has exactly one hard day (Tuesday) and one very hard day (Saturday's race), separated by four days — comfortably clearing even the longest zone-based recovery timeline. Wednesday's recovery run and Friday's easy run are not filler; they are the mechanism by which Tuesday's threshold fatigue clears without the athlete losing aerobic rhythm. Thursday's strides-style 200m work is the one piece that could look like a second "quality" day, but its cost is neuromuscular, not metabolic — it primes leg speed without touching the same energy system Tuesday hit, and it clears well within 48 hours. So structurally this is a one-quality-day week with a speed touch-up, which is exactly what championship race week should look like: protect the taper, don't introduce a second real bill.

Architectural Assumptions

This structure assumes the aerobic and threshold work has already been built in prior weeks — nothing here develops fitness, it maintains and expresses it. It assumes the athlete arrives at Tuesday already comfortable with threshold effort (5 x 1000m is a confirmation dose, not an introduction). It assumes 48-72 hours is sufficient recovery for this specific athlete between Thursday's speed touch and Saturday's race — true for a well-conditioned varsity runner, less safely assumed for an athlete carrying unresolved fatigue into the week. It also assumes the invitational itself is being treated as a hard effort worth protecting recovery for — not a tune-up meet the coach might otherwise have loaded around.

Reflection

This is a race week wearing a taper's clothing: one moderate threshold stimulus early, a speed primer late, easy volume everywhere else, all funneling toward Saturday. The architecture protects the race rather than building around it — every non-race session exists either to deliver fitness forward or to clear fatigue in time to use it.

Teaching Moment

Notice what's absent as much as what's present: no long run, no big aerobic volume day, no second threshold session. In a championship week, the training doesn't need to ask new questions of the athlete's body — it needs to keep the answers sharp. A week built to develop fitness and a week built to deliver it look completely different on paper, even when both contain a "threshold day" and a "speed day." The role a session plays in the season calendar changes what the same workout is for.

This demo is a replay. The real tool runs on your team.

Your athletes, your race times, your season. All nine tools, one purchase, lifetime access. Founding Coaches enrollment opens July 21, and founding coaches get the book, 200 bonus credits, and a live season-design call.

Save My Founding SpotSee the other tools →