50 Things to Ask Your AI

You've connected your AI assistant — Claude or ChatGPT — to Training Tilt. Now what do you type?

That blank chat box is the hardest part. This library gives you 50 example real prompts, organized by what you're trying to get done. Copy any of them, swap in your athlete's name, and press enter. Once you've used a few, you'll stop needing the library — you'll just talk to your platform the way you'd talk to an assistant coach.

Three things to know before you start:

Start here on day one. These prompts confirm the connection works and show you what your AI can see.

1. "Confirm which Training Tilt account I'm logged in as before we do anything."

2. "Show me my athlete roster."

3. "Give me a full overview of Cam's profile, recent training, what's planned, and their goals."

4. "What workout types are set up in my organization?"

5. "What can you actually do with my Training Tilt account? Give me the short version."

This is where most coaches feel the difference first. Instead of opening an analysis screen, picking a date range, and scrolling for the number that matters, you ask for it.

6. "Summarize Cam's last four weeks of training. What stands out?"

7. "Show me Cam's training load trend over the past three months. Are they building, holding, or fading?"

8. "Compare Cam's planned versus completed sessions for the last two weeks. What did they skip?"

9. "Pull Cam's completed rides from the last month and tell me how their long rides have progressed."

10. "Is Cam showing any signs of overreaching? Look at their recent load and how their sessions have felt."

11. "Give me a weekly volume breakdown for Cam by sport for the last six weeks."

12. "What did Cam do yesterday, and how did it go?"

13. "Cam races in six weeks. Based on their recent training, where are the gaps?"

You know the session you want. Instead of building it interval by interval in the app, describe it once. Your AI builds the structured workout, warm-up, work sets, recoveries, cool-down, and shows you the whole thing before it touches the calendar.

14. "Build Cam a run session: 15 minute warm-up, then 6 x 800m at threshold pace with 90 seconds jog recovery, 10 minute cool-down. Show me before scheduling."

15. "Create a 90-minute endurance ride for [athlete] with 3 x 10 minutes at tempo in the middle. Prescribe by power zones."

16. "Write a swim session for Cam: 2km total, main set focused on pacing control."

17. "Build me a 45-minute strength session for a travelling athlete, dumbbells and a kettlebell only. Put the exercises and sets in the description."

18. "Take the session I described and make an easier version for my beginner group, same structure, lower intensity and volume."

19. "Build Cam's next threshold progression. Last week was 4 x 8 minutes - what's the sensible next step? Show me your reasoning first."

Tip: tell your AI whether you prescribe by training zones (1–5) or by percentage of threshold or RPE. It should ask if you don't - and it applies your answer to everything it builds.

20. "Schedule that workout for Cam on Tuesday at 6am."

21. "What does Cam have planned for next week?"

22. "Move Cam's Thursday intervals to Friday, same time."

23. "Cam is sick. Clear their next three days and tell me what we removed so I can rebuild later."

24. "Swap Cam's Saturday long run for an easy 45-minute ride, they've got a niggly calf."

25. "Cam just told me they're travelling Monday to Wednesday. Replace those sessions with hotel-friendly alternatives and show me the plan before changing anything."

26. "Plan Cam's week: Tuesday intervals, Thursday tempo, Saturday long run, Sunday recovery spin. Build all four and show me the full week before scheduling."

Your library is where good sessions go to be reused. Your AI can search it, pull sessions from it onto calendars, and save new templates into it.

27. "Search my library for threshold run sessions between 45 and 75 minutes."

28. "Find every brick session in my library."

29. "Show me the full structure of the run called Threshold set X-23."

30. "That session we just built for Cam, clean out anything specific to them and save it to my library as a template."

31. "Schedule Threshold set X-23 from my library for Cam on Saturday morning."

32. "I'm missing a good VO2max bike session in my library. Build one, 5 x 3 minutes hard with equal recovery, and save it as a template the whole team can use."

Your AI drafts, you approve, then it sends. Nothing should reach an athlete without you seeing the exact words first.

33. "Draft a comment on Cam's race yesterday, congratulate them on the negative split and note their pacing discipline paid off. Show me before sending so I can customize."

34. "Send Cam a note explaining why next week is a recovery week. Keep it short and reassuring. Use my tone"

35. "Read the comments Cam left on their workouts this week and summarize how they're feeling."

36. "Have any of my athletes left workout comments I haven't replied to? Show me the recent ones."

37. "Write a private coach-only note on Cam's file: watch their left knee, mentioned discomfort after Tuesday's session." (Private notes are visible to you, never to the athlete.)

38. "Log feedback on Cam's session yesterday, Rate it as hard, RPE 8."

These are the prompts that replace a standing block in your calendar. Run the same one every Monday and it becomes your routine.

39. "Monday review: for each of my assigned athletes, summarize last week, what they completed, what they skipped, and anything I should follow up on."

40. "Which of my athletes had their biggest training week of the year last week?"

41. "It's race week for Cam. Review their taper, is the load actually coming down, or did I leave too much in?"

42. "Check my athletes' goals. Whose target races are in the next eight weeks?"

43. "End-of-month report for Cam: total hours, volume by sport, key sessions completed, and one sentence on the trend. I'll send it to them."

44. "Before I write next week's plans: give me a two-line status on each athlete, fresh, tired, or somewhere in between."

Structured workouts can go straight to your athletes' devices — Garmin, Wahoo, Zwift, Suunto, and Coros — so the intervals beep on their wrist instead of living on a screenshot.

45. "Which training platforms does [athlete] have connected?"

46. "Send [athlete]'s workouts for the next week to their Garmin."

47. "I just rebuilt [athlete]'s Tuesday session. Push the updated version to their device."

48. "Remove Thursday's workout from [athlete]'s Zwift — we cancelled it."

Note: device sync covers the next 7 days of planned workouts. Sessions further out sync once they come inside that window.

49. "Pull Cam's next four weeks and create a printable PDF training calendar, color-coded by sport."

50. "Turn Cam's last month into a one-page summary I can attach to our monthly check-in call."

Chain your requests. The real time savings come from combining steps: "Review Sarah's last two weeks, then build next week based on what you find, show me the plan, and once I approve it, schedule it and push it to her Garmin." One instruction, four jobs done.

Say "show me first" whenever you're unsure. Your AI already previews changes, but adding "show me before you do anything" slows it down at exactly the moments you want to stay in control.

Teach it your style once. Tell it how you prescribe intensity, your session naming conventions, and your usual weekly structure at the start of a chat. Everything it builds after that follows your rules.

Start read-only. Spend your first session just asking questions, reviews, summaries, comparisons. Once you trust what it sees, let it start writing to your calendar.

If a prompt misses, add one detail. Nine times out of ten, a vague result comes from a vague date range or an ambiguous athlete name. Tighten those and ask again.