Build One Squad Training Week With Individual Tweaks

Coaching a squad usually means one good week and a dozen small exceptions. Most of the team does the planned session. One athlete is racing Sunday, one is coming back from a cold, and one can only ride indoors on Thursday. Building each calendar by hand is where the evening goes.

With TrainingDojo connected to your AI assistant, you can describe the week and the exceptions once. Your assistant builds a version for each athlete, publishes it hidden, and you reveal it when you are happy.

How It Works

Your assistant publishes one athlete at a time, so a squad is a series of requests that it runs for you. In the TrainingDojo web app you also publish to one athlete at a time, which suits a single athlete better than a squad.

• You will need a TrainingPeaks coach account connected in TrainingDojo.
• Each athlete you publish a new workout to counts toward your plan’s athlete allowance.
• Your AI assistant does the building in your AI account, so this uses no TrainingDojo credits.

Step 1: Plan the Week in Conversation

Start with the team week and the exceptions you already know about. Do not publish anything yet.

Here is next week for the squad. Use my methodology.

Tue: 15 min easy, 4 x 10 min Z3 with 3 min recovery, finish easy
Thu: 90 min Z2 with 6 x 30 sec openers
Sat: Long ride, 3 hours Z2

Exceptions:
- Maya is racing Sunday. Make Saturday 60 min easy with openers.
- Theo is back from a cold. Replace Tuesday's main set with 60 min Z2.
- Sam is indoors Thursday. Keep it to 75 min.

Read my roster, then show me each athlete's week as a table. Check
each calendar for conflicts. Do not publish yet.

Your assistant calls list_trainingpeaks_athletes and get_upcoming_workouts, then shows you the result. Read it and correct anything that is off.

Step 2: Publish Hidden

When the table looks right, publish it so that only you can see it.

Validate each workout, then publish each athlete's week using their
athlete_id, with hidden_from_athlete: true. Confirm the athlete name on
each result before you move on to the next athlete. Tell me about any
failures. Do not retry anything unless I ask.

This uses validate_structured_workout and push_structured_workouts_bulk, one call per athlete. Each call returns the athlete’s name, so you can see exactly whose calendar was changed. If one workout fails, the others are kept, so only that one needs another attempt.

Step 3: Review on the Calendar

Open TrainingPeaks and look at the week in context. The athletes cannot see these workouts yet. If you want to change something, make the change in TrainingPeaks, or ask your assistant.

Move Sam's Thursday session to Wednesday. Keep it hidden, and don't
touch anyone else's week.

Step 4: Reveal the Week

Find next week's hidden workouts for the squad and list them by
athlete. After I confirm, reveal them.

Your assistant uses get_upcoming_workouts to find the drafts, then update_platform_workout to reveal each one. You can reveal the whole squad at once, or hold one athlete back while you think about it.

Keep Your Approval Step

Each client handles write approvals differently, and a squad means a lot of writes. Your AI app’s permission settings decide when it stops to ask, so read them before you start. Hidden drafts give you a second check: even when the writes go through, nothing reaches an athlete until you reveal it.

Where to Go Next

A squad week is only as good as the rules behind it, so start with teaching your AI your methodology. Then use the Monday roster review to see how the week went. For the full picture, see TrainingDojo for coaches.