How Amateur Athletes Use AI Planning (A Step-by-Step Guide)

You’ve got a 10K on the calendar in twelve weeks. You’re running three or four times a week, putting in somewhere between 20 and 25 miles. You’d like a plan that actually holds together when work gets hectic — but you’re not going to hire a coach for a local 10K.

This is the situation most amateur athletes are in. AI is not going to replace the coach you don’t have. But it can do something genuinely useful: help you think clearly about how to structure the weeks between now and race day, and rebuild that structure when life disrupts it.

Here’s how to do it step by step.

Step 1: Define Your Event and Baseline Before Touching AI

The single biggest mistake athletes make with AI planning is starting the conversation too early — before they’ve clarified what they’re actually working with.

Before you open any AI tool, write down the following:

• Target event: Distance, date, location.
• Performance goal: Is this a finish, a personal best attempt, or somewhere in between?
• Current weekly volume: Honest average over the past three to four weeks — not your best week.
• Recent performance marker: A race result, a time trial, an estimated threshold pace. Something concrete.
• Injury history: Any recurring issues in the past 12 months. Flag these explicitly.
• Weekly schedule constraints: Days you can’t train, hard limits on session length, anything non-negotiable.

This 10-minute pre-work makes every subsequent AI conversation significantly more useful.

Step 2: Generate Your Macrocycle Skeleton

The macrocycle is the full arc from today to your target event, broken into distinct training phases. You’re not asking AI to design every session — you’re asking it to outline the structure.

Use a prompt like this:

I'm training for a 10K on [DATE]. I'm currently running 22 miles per week across 4 days. My most recent 5K was 26 minutes. No current injuries. I have a work trip in week 7 that will limit me to 2 runs that week.

Build me a 12-week macrocycle with the following phases:
- Weeks 1–4: Base building (easy volume, no speedwork)
- Weeks 5–9: Build phase (introduce tempo and interval work)
- Week 10: Cutback week
- Weeks 11–12: Taper and race

For each phase, give me: weekly mileage range, key session types, and one note about what adaptation we're targeting.

Read the output carefully. Edit anything that doesn’t match your actual situation. If the suggested mileage jumps look too steep, say so and ask for an adjustment. The macrocycle is a hypothesis — yours to own and modify.

Step 3: Plan Your First Mesocycle in Detail

A mesocycle is a 4-to-6-week block with a single dominant goal. For a 12-week 10K build, your base phase (weeks 1–4) is your first mesocycle.

Ask AI to build it out:

I'm starting week 1 of a 12-week 10K plan. This is a base-building mesocycle — 4 weeks of aerobic development, no structured speedwork. Target weekly mileage: 22–26 miles. I run on Tuesday, Thursday, Saturday, and Sunday. Tuesday and Thursday sessions should stay under 60 minutes.

Design 4 weeks of microcycles using a 3:1 pattern (3 build weeks, 1 recovery week). Include: easy runs, a long run each Sunday, and strides 2x per week in weeks 2 and 3 to maintain leg speed without taxing the aerobic system.

This gives you a complete four-week block. Print it or copy it somewhere you can reference it daily.

Step 4: Run the Weekly Microcycle Check-In

This is where the real value of AI planning shows up. Every Sunday evening — or Monday morning — spend 10 minutes on a review-and-rebuild conversation.

The format has three parts: report last week, state this week’s constraints, request a rebuild.

LAST WEEK PLAN: Tue 6mi easy, Thu 7mi with strides, Sat 5mi easy, Sun 10mi long.
ACTUAL: Tue done, Thu I did 5mi easy (felt under the weather), Sat skipped (still tired), Sun 8mi felt okay.

THIS WEEK CONSTRAINTS: Wednesday evening I have a work dinner so can't run. Friday is available if I need it.

GOAL THIS WEEK: Make up some of the missed volume if possible without overloading. I'm in week 3 of 4 in my base mesocycle — still no speedwork.

Rebuild this week's microcycle around these constraints.

The conversation that follows is often more useful than the original plan. AI can suggest whether to absorb the missed volume, skip it entirely, or redistribute it — and it can reason through why.

Step 5: Track Your Intensity Distribution

One of the most common errors amateur athletes make is training too much in the moderate “grey zone” — effort that’s harder than easy but not hard enough to be genuinely high-intensity. Stephen Seiler’s research on polarized training suggests this is a suboptimal distribution for endurance adaptation.

Use AI to audit your intensity distribution weekly. If you use a GPS watch or cycling computer, you likely have zone data already:

My sessions this week by zone:
- Tuesday 6mi: 90% Z1-2, 10% Z3
- Thursday 5mi: 70% Z1-2, 30% Z3 (drifted on the hills)
- Sunday 8mi: 85% Z1-2, 15% Z3

Total time: approximately 80 minutes. Calculate my intensity distribution. I'm targeting a polarized profile: 80%+ low intensity, less than 10% moderate, and anything high-intensity for race-specific blocks only.

Seeing the numbers often changes behavior faster than advice does.

Step 6: Handle Injury Interruptions Thoughtfully

At some point, something will hurt. The way you handle a training interruption matters as much as the interrupted training.

When a symptom appears, use AI to think through your options — while being honest about its limitations:

I've had a tight right calf for the past two days. It appeared during my Thursday run and I felt it again on a short test run this morning. No sharp pain, just significant tightness.

Given that I'm in week 6 of a 12-week plan with a target 10K in 6 weeks, what are my options for this week? I understand AI can't assess the injury — I'm going to call my physio Monday morning. I want to think through my schedule options while I wait for that appointment.

That framing matters. You’re not asking AI to diagnose you. You’re asking it to help you think through scheduling contingencies while a professional assessment is pending. That’s an appropriate use of the tool.

Step 7: Taper Your Final Two Weeks with AI’s Help

Tapering — reducing volume while maintaining intensity in the weeks before a race — is counterintuitive. Most athletes struggle to back off when they feel the race approaching.

AI can help you design and commit to a taper:

I'm entering my two-week taper for a 10K. My peak week was 28 miles. I've been doing one tempo run and one long run per week.

Design a 2-week taper: Week 1 should drop volume by roughly 30% and keep one short tempo session. Race week should drop volume by 50–60% with easy running only, except one short race-pace segment to stay sharp. My race is on Saturday of race week.

The taper plan that comes out of this conversation is worth printing. Tape it to your mirror. The urge to “get one more long run in” before a race is nearly universal and nearly always wrong.

What You’re Actually Building

By following these steps, you’re not just creating a training plan. You’re building a feedback loop: plan, execute, report, adjust. That loop — run weekly — is what separates athletes who arrive at their target event prepared from those who arrive overtrained, underrested, or derailed.

AI doesn’t make the training easier. It makes the planning more responsive to reality.

Open a conversation with your AI tool of choice and write down your target event, your current volume, and your timeline. That’s the first move.

Related:

• The Complete Guide to AI Planning for Athletes
• The Athlete AI Planning Framework
• 5 AI Prompts Every Athlete Should Know
• The Science of Periodization and AI
• Building Habits with AI

Tags: AI training plan, amateur athlete planning, how to use AI for fitness, training periodization, AI running plan