FeaturesMembershipGuideLog inSign up
Guide

Training plan

How a plan is built

5 min read

trace builds every plan with fixed rules, from what you enter and what trace knows about your training. No AI is involved, neither in the sessions nor in the texts.

Key points

  • The hours you choose apply from the first week. If a week stays below them, the plan names the reason.
  • Key sessions follow a ladder for your goal and get more demanding from week to week.
  • In running only the long run gets longer than your longest run of the last 30 days.
  • Loading and recovery weeks alternate, and a taper comes before a race.

What you enter

Under “Create plan” you enter what you are working towards, how experienced you are, on which days and for how long you can train and how intensity should be distributed (Intensity distribution). If you also do strength training or another sport, those days stay free. On top of that comes what trace knows about you, such as your fitness, your threshold and your longest sessions of recent weeks. Without this data the wizard asks for your longest session of the last four weeks.

The framework

From this input trace first builds a framework of phases, base, build, peak and taper, with loading and recovery weeks. Usually three loading weeks are followed by a recovery week without hard sessions. On the level “Recreational”, for older athletes and if you report an injury, poor sleep or a lot of stress, it comes after two. Plans without a race of up to seven weeks run from the level “Ambitious” upwards without a recovery week in the middle, through to the test week at the end. trace set this rhythm. It is common in training practice but not proven to be the only right one.

The hours you choose apply from the first week. trace only plans less with a reason, for example when you recently trained much less or your days cannot hold the time. Week 1 then names the reason and the week from which the full hours apply. Progress comes from the stimulus, the sessions get more demanding, and the long session grows.

For every week trace projects, with the same model as on the training load page, how fitness, fatigue and form develop. Before a race trace tunes the last weeks so that your projected form on race day lands in the target range (Tapering).

Fitness (CTL)Fatigue (ATL)Form (TSB)
Example data. An example plan over twelve weeks, as trace projects it. Fitness and fatigue at the top, form at the bottom, which rises in the two taper weeks before the race.

The sessions

  1. Input

    Goal, days, hours and experience, plus your data in trace

  2. Framework

    Phases, loading and recovery weeks, hours per week

  3. Sessions

    Key sessions, the long session, easy sessions and extras

  4. Check

    no AI

    Fixed rules check every week before you see it

Schematic. How your input becomes a plan week. Every step follows fixed rules.

Into the framework trace first places the key sessions, the ones that matter most in the week. They come from a ladder for your goal and the phase. The first is the session your plan is about in this phase, for example threshold in the FTP builder. It gets more demanding from week to week, with more work, longer repetitions or shorter recoveries. Further key sessions rotate from week to week between the other forms of the phase, for example sweet spot, short VO2max intervals and tempo, and each one keeps climbing when its turn comes again. If one stays the same for once, its text names the reason. How many key sessions a week carries depends on your experience, the phase and your free days. Two hard days never come back to back, and trace plans an easy day between two key sessions wherever your days allow it.

The long session is always the longest of the week and grows in small steps from your longest sessions of recent weeks. In running a limit from a large observational study applies as well. Jesper Schuster Brandt Frandsen and colleagues followed 5205 runners with GPS watches for up to 18 months. When a run was more than 10 percent longer than the longest of the 30 days before, overuse injuries were about 50 to 60 percent more common, and more than twice as common when the distance more than doubled. Spikes in weekly load, by contrast, were not linked to more injuries (Schuster Brandt Frandsen et al., 2025). In trace only the long run therefore gets longer than your longest run of the last 30 days.

Easy sessions fill the remaining time, never longer than the long session. On top come extras that fit the goal, such as strides after an easy run or race-day fuelling in the long session. The load of the week is the sum of its sessions.

The texts follow rules too. The description of a session is built from fixed building blocks. The title of a week names its purpose, such as “Base with tempo work” or “Practise race pace”, and follows from the sessions currently in it, also after an adaptation. Long plans are built in stages, the later weeks shortly before they begin, with your state at that time.

A plan can also combine cycling and running (Cycling and running in one plan).

After it is created

Every morning trace checks whether the planned session fits your state, and over recent weeks whether the plan fits your actual training (How your plan adapts). The Coach can suggest changes too (What the Coach can do). Only what you confirm is applied. If you change days or hours in the plan settings, trace rebuilds the plan from the next week.

How trace calculates it

  • Framework, sessions, texts and taper come from fixed rules, without AI.
  • trace set the rhythm of recovery weeks, the number of hard sessions and how fast the long session grows, based on studies and training practice. An automated test checks thousands of weeks from all templates against these rules.
  • The projection uses the same model as fitness, fatigue and form, with 42 and 7 days.

Limits

  • The plan only knows what you enter and what trace measures. Holidays, illness or a full calendar only come in through adaptation or your own changes.
  • The study behind the 30-day limit observed runners and measured distance. It does not show that the limit prevents injuries, and trace applies it to duration.

Next article · 5.2

Cycling and running in one plan

A training plan in trace can combine cycling and running. You choose how much time the second sport gets, and trace spreads the sessions across both by fixed rules.

2 min read

Related

Training plan

Intensity distribution

Training plan

How your plan adapts

Sources

  1. Schuster Brandt Frandsen, J., Hulme, A., Parner, E. T., Møller, M., Lindman, I., Abrahamson, J., Sjørup Simonsen, N., Sandell Jacobsen, J., Ramskov, D., Skejø, S., Malisoux, L., Bertelsen, M. L., & Nielsen, R. O. (2025). How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study. British Journal of Sports Medicine, 59(17), 1203–1210. https://doi.org/10.1136/bjsports-2024-109380
All sources
Try trace

See your own numbers.

Connect your watch or bike computer, and trace computes fitness, readiness, critical power and durability from your sessions. Starter is free.

Get started freeGet the app

Training analytics for cycling and running.

Product

  • Features
  • Membership
  • Guide
  • Glossary
  • Blog
  • App
  • Log in

Company

  • About
  • Support

Legal

  • Terms & Withdrawal Instructions
  • Privacy
  • Legal Notice
  • Cancel contracts here
  • Withdraw from contract
  • Delete account
© 2026 trace · All rights reserved