When you ask MyNextRow for a workout, the coach is not pulling a session out of thin air. It reads your Concept2 Logbook history, your onboarding goal (race, fitness, recovery, or technique), and any preferences you have shared in chat. From your Logbook it pulls the last ten sessions — date, average split, distance — plus a longer view used to compute your reference pace and your training-load trend. That handful of numbers is what the model has to work with. The session it returns is shaped by those numbers, not by a static template. The coach is opinionated about safety (no back-to-back hard sessions, respect a high acute load) but conservative about personalization (it will not invent goals you did not set). This article walks through what the coach reads, in what order, and which signals move today's prescription the most.
Key points
- The coach reads your Logbook history, onboarding goal, and chat preferences — not a static template.
- Your last ten sessions supply date, split, distance; a longer history supplies reference pace and load trend.
- No back-to-back hard sessions and respect for a high acute load are safety rules, not personalization choices.
- Your onboarding goal (race, fitness, recovery, technique) is the strongest single signal in the prescription.
- What you have not done in chat is just as important as what you have — the coach will not invent goals for you.
Sources and further reading
- Concept2 — Logbook— The source of truth for workout history MyNextRow reads to build your coach context.
- MyNextRow — How the AI Coach Works— Product description of the prescriptive AI coach and how it differs from passive logging.
- World Rowing — Adaptive Rowing— Reference for how the international federation frames individual athlete context for training.