Planned vs actual: reading your Moveee calendar after a week of riding

The calendar is where a plan stops being a promise and becomes a record. Planned sessions and the rides you actually did sit side by side on every day, each week shows what was planned against what you rode, and every ride that lands on a planned day gets a verdict. Here is how to read it after a week, and where the honest gaps are.

The week banner

Each week in a plan is tinted by its phase: green for Base, blue for a build week (labelled "Threshold build", "VO₂ build" or "Tempo build" after whatever quality dominates), amber for Peak, red for Race week, grey for a recovery week. The banner across the top of the week has two halves.

• Left is planned. Hours, training load in TSS, and the number of sessions. A week with nothing planned reads "rest week".
• Right is ridden. Time on the bike so far, load ridden, and the number of rides. The current week carries a "This week" badge and reads "no rides yet" until the first one lands.

Read them together. Planned 8 h and 420 TSS against ridden 5 h and 310 TSS tells you most of what you need before you open a single day. Weeks outside a plan get a character instead, worked out from your rides: a load tier ("easy" under 300 TSS, "medium" under 550, "big" above) and, if at least two rides carry an intensity factor, a prefix such as "Polarized", "Threshold", "Endurance" or "Mixed". A week at 550 TSS or more that is also three and a half times your normal week is called "Brutal week", which is not a compliment.

The day cell

A planned session is a chip coloured by its zone: grey for recovery, teal for endurance, amber for tempo, violet for threshold, pink for VO₂. Rest days are a plain grey "Rest" chip. Under the planned chips sit your rides, always in solid purple, showing distance and time, with a tick icon for an outdoor ride and a controller icon for a Moveee Indoor ride. The two are not merged: a day with a planned threshold session and a ride shows both chips, one above the other.

A few markers are worth knowing. A pulsing pencil on a ride means you have not logged how it felt yet; that prompt lasts fourteen days. A warning-coloured ring and dot on a planned chip means the adaptive coach changed it in the last three days, and the tooltip tells you what it was before. The struck-through date with an "Unavailable" chip is a blocked date. If you have set your home address, each day also carries a weather icon and temperature; past days show the conditions "as it was at 4 pm".

How a ride is matched to a session

This is the part to understand properly, because it is simpler than people assume. Matching is by calendar date only. The day's longest ride (ties broken by load) is the "main" ride, and it is compared with the day's highest-load planned session that is not a rest day. Nothing else is considered: not the ride's type, its duration, or how similar it looked to the plan.

Three consequences follow. A second ride on the same day is never judged. A session done a day late looks like a missed session plus an unmatched ride. And a ride on a rest day, or on a day with nothing planned, gets no verdict at all.

The verdict

Open a ride (click its chip) and the "Planned session" card shows one of four badges, with three boxes underneath: Planned, You did, and vs plan as a percentage. The rules are fixed numbers, not judgement calls.

The typical intensity factors the engine assumes per session kind are 0.55 for recovery, 0.68 endurance, 0.70 long ride, 0.80 tempo, 0.88 threshold and 0.92 VO₂. So a planned endurance ride done at IF 0.81 is "Overreached" even if the load matched, and that is deliberate: riding your easy day at tempo is the most common way amateurs undo a plan. The two-axis rule mirrors the way sports scientists talk about training load: an external dose (how much work) and an internal response (how hard it was for you), which are related but not interchangeable.

The card also writes a sentence. "Right on plan — 92 vs 90 TSS." Or, for an overreach, a note that "On an adaptive plan we ease the next hard day so you absorb it," which is what the adaptive plan does that evening.

Log how it felt

The same ride popup carries the check-in: "Overall, how did it feel?" (Strong, Good, OK, Tired, Cooked), "How hard was it?" (Easy to All-out, an RPE from 2 to 10), "Complete what you set out to do?" (Nailed it, Most of it, About half, Cut it short) and optional notes. The footer says "Feeds your adaptive plan", and it does: on an adaptive plan, saving a check-in runs the re-tune immediately rather than waiting for the evening pass. Self-reported wellness and effort turn out to be surprisingly good at tracking how an athlete is coping with training, often better than the objective measures they are compared against, and the session-RPE method that the "How hard was it?" question borrows from has held up for over twenty years.

What you can do from here

• Drag a session to another day. The chip moves at once and saves in the background. Dropping it on a day that already has a session stacks them; nothing is swapped. Completed sessions and rides cannot be dragged, and blocked days refuse drops.
• Remove with the hover cross, or add with the plus: pick from the Moveee library or your own workouts, or build one from %FTP segments.
• Change for similar. In the session popup, VO₂, threshold and tempo sessions can be swapped for a built-in session in the same zone within about 30% of the load.
• Ride it indoors in Moveee Indoor, or download a FIT file for a head unit, ZWO for Zwift and MyWhoosh (written straight into their folders if you have connected them), ERG or MRC for trainer apps. FIT and ERG need an FTP on your profile because they are written in watts.

The honest gaps

• The verdict does not show on the calendar. The cell shows the two chips; you have to open the ride to see On plan or Overreached. We would like to change this.
• There is no "missed" state. A past session with no ride next to it looks exactly like a future one, still draggable and removable. The only sign it was missed is the absence of a purple chip. Nor is there a weekly completion percentage; the banner gives you planned and ridden numbers and leaves the arithmetic to you.
• Rides without power get their load estimated from heart rate, or a flat rate per hour, and may have no intensity factor. That pushes their verdicts towards "On plan" or "Under target".
• Rides come from Strava and Moveee Indoor. Strava rides arrive via webhook within moments, with a poll every few hours as a backstop. Garmin, Wahoo and Hammerhead accounts can be connected, but ride import from them is not live yet and the device sync menu says "Coming soon". We would rather tell you than have you wait for a ride that will not appear.
• The interval-by-interval "vs target" table on a completed session without a real matched ride is illustrative, not measured. Trust the ride card, which uses your actual data.

The habit that makes the calendar useful is a short one: once a week, read the banners top to bottom, open any ride that is not "On plan", and log how the hard ones felt. Ten minutes, and the Fitness & Form chart will start making sense. Your calendar is here.