The Athlete AI Planning Framework: Macrocycles, Mesocycles, and Microcycles with AI

There’s a useful distinction in coaching between the art and the architecture.

The architecture of training — how load should accumulate, how recovery blocks should be placed, how intensity should cycle across a season — is relatively codified. Tudor Bompa spent decades formalizing it. The research holds up. Periodization works.

The art is everything else: reading the athlete’s fatigue, watching movement patterns, sensing when to push and when to protect. That part requires a human.

AI belongs firmly in the architecture column. The Periodized Block framework defines exactly where.

What Is The Periodized Block?

The Periodized Block maps AI assistance onto the three nested levels of classical periodization:

Level 1 — Macrocycle: Your full training season, anchored to a target event. Sets the broad arc.

Level 2 — Mesocycle: 4-to-6-week blocks, each built around a single adaptation goal. Structures the progression.

Level 3 — Microcycle: Your weekly training schedule. Executes the plan against real-life constraints.

The critical design principle: AI’s role increases as the time horizon shrinks.

At the macrocycle level, AI is a sounding board — you set the destination, it helps you map the route. At the mesocycle level, AI is a designer — you specify the goal and constraints, it generates the block structure. At the microcycle level, AI is an adapter — it rebuilds the upcoming week based on what actually happened last week.

Most amateur athletes who use AI for training jump straight to the microcycle. That’s backwards. A microcycle that isn’t anchored to a mesocycle goal, which isn’t anchored to a macrocycle arc, is just a list of workouts. It has no training logic behind it.

Level 1: The Macrocycle (AI as Sounding Board)

The macrocycle is a document you build once per training season, typically 8 to 24 weeks in duration. It should answer three questions:

1. What is the target event and when is it?
2. What distinct training phases are needed between now and then?
3. What is the rough volume and intensity arc across those phases?

AI’s role at this level is reactive, not generative. You bring the goal; AI helps you stress-test the structure.

A useful macrocycle conversation:

I'm planning a 20-week build toward a sprint triathlon. My background: 5 years of recreational cycling, two years of running. This is my first triathlon. I can train 8–10 hours per week across swim, bike, and run. I need one complete rest day per week (Sunday). The race is on [DATE].

Draft a 20-week macrocycle with distinct phases. Include swim, bike, and run volume guidelines for each phase, and flag any week where total volume drops for planned recovery.

After getting the output, review it against what you know about your body. Do the volume jumps look manageable? Is there enough recovery built in before the event? Are the phase durations appropriate?

If you’re new to triathlon, consider taking the AI-generated macrocycle to a coach or experienced club athlete for a single review session before committing to it. That’s not a failure of the system — it’s using the system correctly.

Level 2: The Mesocycle (AI as Designer)

Each mesocycle has a dominant adaptation goal. The most common for endurance athletes:

When you design a mesocycle with AI, provide:

• Where you are in the macrocycle (week X of Y)
• The adaptation goal for this block
• Your current fitness markers
• Any injury or health considerations
• The loading pattern you want (typically 3:1 or 2:1 — build weeks to recovery week)
• Daily schedule constraints

A sample mesocycle design prompt:

I'm starting week 6 of a 20-week triathlon plan. I just finished a 5-week base block. Swim: ~8,000m/week, Bike: ~100km/week, Run: ~25km/week. No current injuries. 

Design a 4-week threshold development mesocycle using a 3:1 loading pattern. Each week should include: 3 swim sessions (one with threshold intervals), 3 bike sessions (one with sustained tempo), 2 run sessions (one with tempo efforts). Rest day on Sunday. Flag recovery week clearly.

The output will include session types and target volumes for each of the four weeks. This is your block plan — save it and refer to it each week during your microcycle check-in.

Level 3: The Microcycle (AI as Adapter)

This is where The Periodized Block earns its keep for amateur athletes.

A static plan can’t account for Monday’s tight hamstring, Wednesday’s client dinner, or Sunday’s weather that made the long run impossible. A human coach adapts in real time. AI, given sufficient context, can produce a reasonable adaptation — not because it’s observing you, but because you’re telling it what happened.

The Microcycle Check-In has a fixed structure:

Part A — Last Week Report What you planned vs. what you actually did. Be specific. Quantify missed volume. Note any pain, soreness, or unusual fatigue.

Part B — This Week’s Constraints Schedule changes, work obligations, travel, anything that limits session windows.

Part C — Rebuild Request Ask AI to rebuild the upcoming microcycle within the mesocycle’s target parameters, accounting for last week’s actual output.

An example check-in:

MESOCYCLE CONTEXT: Week 2 of 4, threshold development block. Target: 3 swims, 3 bikes, 2 runs, Sunday rest.

LAST WEEK ACTUAL:
- Swim Mon: done (3,000m with threshold intervals)
- Bike Tue: done (35km easy)
- Run Wed: only 5km easy, skipped the tempo (calf tightness)
- Swim Thu: done (2,500m easy)
- Bike Fri: missed completely (work ran late)
- Run Sat: 8km easy, calf felt fine
- Sunday: rest

MISSED: threshold run, one bike session.

THIS WEEK CONSTRAINTS: Thursday evening unavailable. Friday and Saturday both available.

Please rebuild this week's microcycle. Given the calf tightness last week, should we keep the threshold run this week or substitute a longer easy run?

The conversation that follows will surface options, tradeoffs, and reasoning. You make the final call. But you’ll make it with more clarity than you’d have starting from scratch.

The Intensity Ledger: Tracking Your Polarized Profile

The Periodized Block includes a lightweight weekly accounting practice we call the Intensity Ledger.

Each week, when you report completed sessions, include a rough zone breakdown. Ask AI to calculate your weekly intensity distribution and compare it against a polarized target (approximately 80% low intensity, 10% moderate, 10% high during base and threshold phases).

Stephen Seiler’s research demonstrated that amateur athletes who track and enforce polarized distribution see better long-term adaptation than those who train without attention to zone ratios. The grey zone — moderate effort, not quite a tempo — is where a lot of amateur training hours disappear without generating proportional benefit.

The Intensity Ledger doesn’t require a lab. It requires your GPS watch’s zone data and five minutes of calculation. AI handles the math.

When to Override the AI Plan

There are specific situations where you should override or abandon AI-generated plan elements:

Physical symptoms that weren’t present when you gave your last input. AI’s plan reflects the information it had. If something new develops — a sharp pain, unusual swelling, dizziness during effort — the plan is no longer valid for that session.

Significant life events that compress your schedule. If your available training time drops from 10 hours to 4 hours for a week, tell AI and rebuild. Don’t try to cram the existing plan into half the time.

When your gut contradicts the output. You’ve been training in your body for years. If a suggested session looks wrong to you — too much volume, wrong intensity, poor timing — ask AI to reason through it. If the reasoning doesn’t satisfy you, change it. The framework requires your judgment to function.

When a doctor or physiotherapist gives you a specific directive. AI yields to qualified medical professionals. Always.

Putting the Framework Into Practice

The Periodized Block runs on a simple weekly rhythm:

• Sunday evening: Microcycle Check-In (10–15 minutes). Report last week. Rebuild this week.
• Every 4–6 weeks: Mesocycle design conversation (20–30 minutes). Review what the current block achieved, design the next one.
• Start of season: Macrocycle architecture conversation (45–60 minutes). Set the full arc.

That’s roughly 20 minutes per week of AI-assisted planning time in exchange for a training plan that adapts to your actual life rather than an idealized version of it.

Beyond Time is built around this kind of time-blocking discipline — the idea that your training sessions need to become scheduled commitments with the same protection as any other fixed appointment. The weekly microcycle you design with AI belongs on your calendar as hard blocks, not floating intentions.

The Framework Is a Scaffold, Not a Cage

Periodization is not a rigid prescription. Bompa’s original work, and subsequent research by practitioners like Joe Friel and coaches across endurance sports, consistently emphasizes that the framework should serve the athlete — not the other way around.

The Periodized Block reflects this. The macrocycle sets direction. The mesocycle provides structure. The microcycle adapts. AI assists at each level without replacing the most important ingredient: your own honest self-reporting about what’s actually happening in your training.

Use the framework for 6–8 weeks. Pay attention to what the planning conversations reveal about your training patterns. Adjust the prompts to your sport, your schedule, and your goals.

Start by designing your macrocycle — that’s the first conversation.

Related:

• The Complete Guide to AI Planning for Athletes
• How Amateur Athletes Use AI Planning
• The Science of Periodization and AI
• Marathon Runner Uses AI: Case Study
• Measuring Goal Progress with AI

Tags: athlete AI planning framework, periodization AI, macrocycle planning, training block design, AI fitness planning