How to Use Claude or ChatGPT to Plan for Your Athletes
by The Next Race
Most coaches don't run out of knowledge. They run out of hours.
The thinking part of coaching, deciding what an athlete needs next, takes minutes. The work around it takes the rest of the week: reading every file, checking who did what, building next week's sessions one by one, typing the same message to six people, and remembering who has a sore calf.
An AI assistant is good at exactly that work, as long as it can see your athletes' training. This guide shows how to connect Claude or ChatGPT to The Next Race, what to ask it, and where you should stay firmly in charge.
Why copying and pasting into a chat isn't enough
You can paste a training log into ChatGPT and ask for a plan. You'll get something plausible. Then you have to type it back into your coaching platform, session by session, and it knows nothing about yesterday's run, last night's sleep or the message the athlete sent you this morning.
The useful version works the other way round. The assistant reads the athlete's real data and writes straight into their real calendar. That's what the Model Context Protocol (MCP) is for: a standard way for an AI assistant to use another app's tools, with your permission.
The Next Race has an MCP server. Once it's connected, Claude or ChatGPT can do most of what you do in the app: list your athletes, read what they share with you, build plans, schedule structured sessions, copy weeks between plans, and message athletes.
Set it up in five minutes
You need three things:
- A The Next Race coach account with your athletes on it. Coaching starts at $25 a month for up to 5 athletes, with a 14-day free trial. MCP is free on every plan.
- Claude or ChatGPT. The assistant runs on your own subscription, so there's nothing extra to pay us for it.
- The connector URL:
https://www.thenextrace.app/mcp
In Claude: The Next Race is listed in Claude's Connectors Directory. Open The Next Race in the directory, choose Connect, then sign in to The Next Race and approve access. You can also add the URL yourself: in claude.ai, go to Customize → Connectors, choose "Add custom connector" and paste it. In The Next Race, Settings → Connectors → Claude opens the directory listing for you.
In ChatGPT: add the same URL as a custom connector in ChatGPT's settings, under Apps & Connectors. Depending on your plan, custom connectors may sit behind ChatGPT's developer mode. Then sign in to The Next Race when asked.
Claude Desktop, Claude Code, Cursor and Gemini work too: see our MCP page. Prefer the terminal? The TNR CLI does the same from the command line.
What the assistant can see, and what it can't
This matters more for coaches than for anyone else, because you're handling other people's health data.
- The assistant acts as you. It can only reach athletes on your roster.
- Each athlete decides what you see: activities, training, daily health, physiology, and injuries and illness, each switched on or off. If an athlete doesn't share something with you, the assistant can't read it either. It gets a "not shared" answer, not the data.
- Whatever the assistant reads is sent to Claude or ChatGPT to answer you. Tell your athletes you use an AI assistant, the same way you'd tell them about any other tool that touches their data.
Five jobs to hand over
These prompts work as written. Swap in your own athletes' names. Each one uses the athlete's real data from The Next Race, not a copy in the chat.
1. Monday-morning inbox triage
Go through my coaching inbox. Who's waiting on a reply? Give me one line per athlete, then draft a reply to each. Don't send anything yet.
The assistant reads every conversation that's waiting on you: messages, comments on workouts, voice-note transcripts and injury notes. You get the whole picture in one place, and draft replies you can edit. When you're happy:
Send the replies to Anna and Jonas as written. Mark Sofie's conversation as done; I'll call her.
2. The weekly review
For each of my athletes, compare last week's planned and completed sessions and their average effort rating. Flag anyone under 70% completion or with an average RPE above 7.
It goes through the roster athlete by athlete and gives you a short list of the people who need a look. Then dig into one:
Show me Jonas's last four weeks. Is his load going up steadily, or did it jump?
3. A recovery-aware tweak
Check Anna's recovery today. If it says she's run down, move Thursday's intervals to Saturday, put an easy 40-minute run on Thursday, and message her why.
The assistant reads her HRV, resting heart rate, sleep and daily check-in against her own baseline, and only changes the week if the numbers support it. The changes land in her calendar and reach her watch, and she gets a push notification with your message.
4. A first draft of a training block
Build a 12-week half-marathon block for Jonas, starting Monday 5 January. Four runs a week, long run on Sundays, one quality session and one steady session. Use his zones. Show me weeks 1 to 3 before you schedule anything.
That last sentence is important. Ask for the plan first, read it like you'd read a new coach's work, then say "go ahead" or "make week 2 easier". The assistant reads his zones from his profile, writes structured sessions with steps and targets, and schedules them in a plan assigned to him. If he trains with a Garmin or Wahoo, the workouts go to his device.
5. One template, many athletes
Copy weeks 1 to 4 of my "Spring marathon base" template into the plans of everyone tagged spring-marathon, starting 12 January. Then message them that the first block is up.
This is where coaches save the most time. You keep one template plan that only you see. The assistant copies the weeks into each athlete's own plan, so you can still adjust every athlete's version afterwards. It then sends each of them their own message, so replies stay one-to-one.
A few more that work today:
Only let my athletes see the next 14 days of training.
Which of my athletes haven't rated their sessions this week?
Has anyone logged an injury or illness this month?
Where you stay in charge
AI assistants are confident, fast and sometimes wrong. A few rules keep them useful:
- Draft, then commit. Ask to see a plan or message before it's written or sent. "Don't send anything yet" is the most useful sentence you'll type.
- Judge load yourself. The assistant can read training load numbers, but it doesn't know that your athlete's last two marathons fell apart at 30 km because of fuelling. You do.
- Use your voice. Edit the drafts. Athletes pay for you, not for a model's tone. Many coaches ask for bullet points and write the message themselves.
- Check the first few writes. Look at the sessions it creates in the calendar the first few times, until you trust how it writes targets and steps.
- Mind the data. Only connect an assistant whose data terms you're comfortable with, and tell your athletes.
What this doesn't replace
The assistant won't notice that an athlete's messages have gone short and flat, or that they're quietly dreading a race. It can't have the phone call. It saves you the hours that used to go into reading files and building sessions, so you have more of them for that.
Try it
Start a 14-day coach trial, invite one athlete, connect Claude or ChatGPT, and run the Monday-morning prompt above. Coming from Final Surge? Your workout library and plans import in a few minutes, so you can try this on real training rather than a blank calendar.
