How a Coach plan works.
Your riders, read by your AI.

A cycling coach who uses Claude, ChatGPT or another AI assistant can ask it about their own Intervals.icu training through IntervalSync. A Coach plan lets that same assistant read the training of the riders they coach, once each rider has agreed: last Tuesday's threshold session, a month of power curves, the week's planned workouts, this morning's wellness. It reads and never writes.

This article goes through a Coach plan step by step: who pays, how a rider agrees, what the coach's assistant reads, how the daily limit is counted, the shared context a coach keeps with each rider, and what each side keeps when coaching ends. Coach plans and Pro Team is the short overview of both, and How a Pro Team works covers the other way to share. The terms of service are the rules.

Who it is for, and what it costs

A Coach plan is for a coach whose riders keep their training in Intervals.icu. There are two sizes:

• Coach 5 costs $15 a month or $149 a year, for up to five riders.
• Coach 15 costs $29 a month or $289 a year, for up to fifteen riders.

It is the coach's own subscription, billed in advance through Stripe, monthly or yearly, and it includes everything in Pro for the coach's own account: their own rides read, and their own planned workouts and wellness records changed once they confirm the exact change. A new account's 14-day trial includes coaching up to five riders until the trial ends. The coach can move between Pro, Coach 5 and Coach 15 in their portal: a move to more riders applies when they confirm it, and a move to fewer applies at the next renewal. Pricing has every plan side by side.

The coach pays. Riders can stay on Free.

A rider needs no plan of their own to share with a coach: a rider on Free can. The Coach plan pays for the coach's access to the rider, not for the rider's own. What the rider's own assistant can do with their own training is still set by the rider's own plan, whoever they share with.

Inviting a rider, and the rider's approval

The coach makes an invitation in their portal and sends the link to the rider. Each invitation is for one rider, is used once and expires after seven days, and up to 20 can be open at once. An invitation cannot be made once every place on the plan is taken.

Opening the link shares nothing. The rider signs in and approves on a page that names the coach and the training account the approval covers. That is always the account they signed in to IntervalSync with through Intervals.icu. A training account connected by API key is never shared, because it can be somebody else's, and that person never saw the invitation. An account with no Intervals.icu sign-in is asked to sign in with Intervals.icu first, and nothing is shared until it does. If the coach's plan has no place left when the rider approves, the approval is refused and the rider is told to ask the coach to make room.

From then on the rider sees the coach under the coaches with access in their portal, and the coach sees the rider among the athletes they coach. The rider can withdraw at any time.

What the coach's assistant reads

The coach's assistant has one more tool, list_athletes, which names the riders sharing with the coach and gives an id for each. Every account is offered it, and the list stays empty until a rider shares. Fourteen read tools take that id as their athlete parameter: the athlete profile, the list of activities, one activity, its detail, its intervals, its streams, its blocks and its climbs, power curves, power durability, the training summary, planned workouts, wellness and sport settings. Without the parameter, a tool reads the coach's own training, as it always has.

So a coach can ask "How did my riders' threshold sessions go this week?", and the assistant lists the riders, reads each one's activities and intervals, and answers. Every one of those reads is read-only. The coach's assistant never sees a rider's saved training context or the feedback they have sent, and it reads only riders who have agreed: an id for anyone else is refused.

Every read is recorded, and counted against the coach

Each read of a rider appears in the rider's own activity history, with the coach's name and the tool that was used, so a rider can see what was read and when. It appears in the coach's history too.

Each read also counts against the coach's daily limit, not the rider's. Coach 5 can make up to 800 calls to Intervals.icu per UTC day and Coach 15 up to 1,800, for the coach's own reads and their reads of riders together. Each is 300 calls for the coach's own account and 100 for each rider the plan covers. The trial, which coaches up to five riders, keeps Pro's limit: up to 300 calls a day, rider reads included. The count starts again at midnight UTC, and a call past the limit is refused before it reaches Intervals.icu, with the time the count starts again.

More riders sharing than the plan covers

This happens when a coach moves to a plan for fewer riders. Take a coach on Coach 15 with nine riders who moves to Coach 5: from the next renewal, all nine stay listed by list_athletes, but only the five who shared first are read. A read of any of the other four is refused before anything is sent to Intervals.icu, so a smaller plan never quietly keeps a larger plan's reach. When a rider ahead of them stops sharing, the next in order is read.

Reading a rider at all needs a Coach plan, or its trial, on the coach's account. Without either, every read of a rider is refused, and the riders stay listed.

A shared context with each rider

Besides reading training, a coach and one rider can keep a shared context of their own: a brief, with a goal, a focus, priorities and constraints, and the updates the two of them publish, such as "Moved Saturday's long ride to Sunday" or "Knee is fine again, back to full intervals". Only the two of them and their connected assistants read it. A coach has one such space for each rider the plan covers, and riders never see one another's.

• The space is for a rider who shares their training with the coach. An invitation to it is refused without that permission, unless the rider gives it on the same invitation.
• The rider needs no plan of their own for it. They read it and publish in it, in their portal and through their assistant, while the coach has a Coach plan or its trial, and doing so uses none of Free's daily data pulls.
• A member can publish up to 50 updates per UTC day across their shared contexts, and updates are kept for 90 days. An assistant publishes only when its member asks or agrees.
• If the coach's plan ends while they work together, both keep their place. The space is closed to the coach until they have a Coach plan again, and to the rider too unless the rider's own account is on Pro, a Coach plan or a trial that is still running.

When coaching ends

Either side can end it. The rider can stop sharing, leave the space, disconnect that training connection or delete their account. The coach can remove the rider or close the space. Whichever happens, the space and the permission end together: the coach's assistant can no longer read the rider's training, and the rider can no longer read the space. The next read is refused.

The coach's record. When the rider stops sharing or leaves, or the coach removes them, the coach keeps what both published as a record that nobody can add to or be invited to. It is readable while the coach has a Coach plan and kept for one year from the day the space ended, and the coach can delete it sooner. A coach who closes the space instead deletes it for themselves.

The rider's own copy. However the space ends, unless they delete their account, the rider keeps a copy of their own: the space's name, the coach's name, the brief as it stood and the updates both had published, as they were that day. It is kept for one year from the day the space ended, on any plan, and the rider can delete it sooner. The rider and their assistant can read it while the rider's account is on Pro, a Coach plan or a trial that is still running; without one it stays stored and closed, and it opens again if the account is on one before the year is over. What the coach later does with their own record does not change the rider's copy. If the coach deletes their account, their words and name are taken out of it.

A later coach. A rider whose copy is open can let a later coach, one who has the rider's permission to read their training, read all of it, the earlier coach's brief and updates included, and can take that back. That coach reads it while their permission lasts, while the rider's account is on a plan of its own, and only while they have a Coach plan or its trial. The earlier coach is not told. What a coach publishes in a rider's space stays with that rider.

What a coach cannot do

• Write to a rider's calendar. The coach's assistant cannot create, change or delete a rider's planned workouts, or change their wellness records. The write tools act only on the coach's own account.
• Read a rider who has not agreed, or keep reading one who has withdrawn.
• See a rider's saved training context or feedback.
• Show one rider another. Riders do not read the coach's training or one another's, and never see each other's shared context with the coach.

A Coach plan or a Pro Team?

A Pro Team is the other way to share on IntervalSync: two to ten people who train together, such as a club's racing squad, read each other's training. The difference is who pays and who reads whom. How a Pro Team works goes through it in detail.

In a Coach plan, riders never see each other: each one shares with the coach alone. Coach plans and Pro Team compares the two in full.

Pricing · Terms of service · Coach plans and Pro Team · All articles · Connect your training