Training plans and race fueling

Open a client and tap the Training tab. Add a single session, or tap Build a plan: pick the event they are building toward and a template (5K or 10K, half marathon, marathon, triathlon, cycling, HYROX, CrossFit competition, powerlifting meet, or a general strength block).

FuelPath lays out the weeks from the next Monday: a weekly pattern that builds, a lighter week every fourth week, and a taper into the event. Edit or delete any session after; remove the plan and its upcoming sessions go with it while anything already done stays in the log.

Every planned session fuels its day the moment it exists, so the nutrition is ready before the training starts.

Add the event with its date, start time, and priority. Each kind carries a default protocol: carb-load days at a set number of grams per kilogram for long events, a carb-rich breakfast 2 to 4 hours out, carbs per hour during, and recovery after.

Override any number per client under Customize the protocol, and add notes for race week. The client sees the whole timeline on their Calendar, and their carb-load days raise carbs to the target on their own, easing fat back a little so the extra food sits easy.

Strength meets and competitions with short events get no carb load by default. Any weight-class cut is your call and is not automated.

Once a client's training is in FuelPath, their day type comes from it: race, carb load, big day, recovery, training, or rest. You see it on the week strip with a ✦, on their food days, and in your briefs.

Rest is only called for someone whose training is really tracked (a few sessions in three weeks, a plan, or an event coming), so a client who never logs training keeps their full target every day. A day the client picks by hand always wins.

If you would rather set days by hand for someone, turn training fuel off on their Manage tab; that also turns off the automatic day types.

Load is minutes times effort (1 to 10), compared with the client's usual week. Readiness reads that next to their recovery, heart rate variability, resting heart rate, and sleep. When it says rest, the client's Today and Daily Brief suggest an easy day and tell them to check with you if something hard is planned.

The client's AI coach, their Daily Brief, and your client brief all read the same training facts. Open What the AI coach sees on the Training tab to see exactly what it knows.

Treat a rest flag as a conversation, not an order: a planned overload block is supposed to push load up.