Building Blocks · Training · Chapter 8 of 11 · 4 min read

A training plan that listens

No one rides a plan exactly as written. You miss a Tuesday, cut a session short, add a group ride on Sunday. A plan that ignores this is wrong within two weeks. BlockRide reads the plan against what you actually rode every time you open it, and changes what comes next by fixed rules.

What happened to each day

For every planned day, BlockRide compares the session you did with the one planned, using two things from chapter 4: the load, and the share of it above threshold.

  • Done. Close to the planned load and the planned hardness.
  • Partial. You started the workout but did clearly less than its main work.
  • Swapped. You rode, but something else.
  • Missed. No ride.
  • Extra. A ride on a rest day.

Sessions from Strava, Garmin and FIT files count the same way as BlockRide rides, so an outdoor ride can tick off a planned day.

What changes next

  • A missed key session moves once. It goes to the next free riding day, never the day before another hard day. If there is no room, it is dropped and the plan says so. It does not pile up.
  • A partial key session is made up in part. The shortfall is added to the next key session as whole extra repeats, within a limit.
  • Too easy or too hard. After a workout the game asks how it felt. "Easy", or a session that left far more battery than predicted, makes the next hard sessions a step harder and suggests a test. "Too hard", or falling well short, makes them a step easier. The steps are small and capped until a stack-up or a test confirms where you really are.
  • An extra ride when you are already tired eases the hard sessions of the next few days.
  • Form far below zero pushes the next hard session back a day.

Whatever the rule, two limits from chapter 6 always hold: a week never exceeds your hours by more than a small margin, and never jumps too far above the week you last rode.

Each Monday, from what you rode

The first time you open the plan in a new week, the weeks ahead are sized again. The starting point is no longer what last week planned. It is what last week was, across all your sports. Ride more than planned and the plan steps up from there. Ride less and it steps down, with no debt to pay off. Days already ridden never change.

You can also change a week yourself. "Change this week" makes the rest of the week harder or easier by a set share, and "As planned" undoes it.

Why rules, and why these

The same session is not the same dose for everyone, and Busso's work shows it is not even the same dose for one rider at different times. A plan has to correct itself from the response, not only prescribe. Carl Foster's research adds a second reason: illness in athletes tracked training that was both heavy and the same day after day. Moving a hard day when you are tired, and never stacking missed sessions on top of planned ones, both follow from that.

Every change is made by a fixed rule and shown on the day it touched, with the reason in plain words: "Moved to Thursday", "Eased after Sunday's extra ride". If the plan changes, you can always see what and why.

Where AI comes in, and where it doesn't

After a ride, your coach (Mila, Otto or Brick) writes a short review. For BlockRide rides that text is written by an AI model from the ride's numbers: the workout, the load, the battery, and how you said it felt. The AI writes sentences. It does not decide anything. Targets, loads and plan changes all come from the formulas and rules in these chapters, and they are the same whichever coach you picked. What the coaches do change is the subject of the next chapter. No heart rate or other health data is sent to the AI, and nothing that identifies you.

Further reading

Garmin Connect and Body Battery are trademarks of Garmin Ltd. or its subsidiaries.