ChatGPT writes a programme, Happy Assistant keeps it alive
Asking a generalist AI for a training plan gives you a good document. Six weeks later that document knows nothing about your missed sessions, your knee pain or your progress. A useful plan is one that updates itself with reality.
The frozen plan problem
A programme produced in a chat is a snapshot of intent. It ignores what actually happened, unless you re-explain everything in every conversation — which nobody keeps doing.
- It does not know your real volume over the last three weeks.
- It does not know you skipped two runs.
- It cannot move a lighter week around your constraints.
Logging a session in ten seconds
- You dictate: "45 minutes running, 8 km, easy pace, heavy legs".
- The session is stored with sport, duration, distance, pace, intensity and feeling.
- Quick feedback (effort, fatigue, pain) completes the context.
- The session joins your sport history and weighs on next week's plan.
Strength sports also record sets, reps and loads, so the same session can be compared from one month to the next.
Structured, browsable sport history
- Day view: the day's sessions, without statistical noise.
- Week view: statistics first, detail after, load progression over twelve weeks.
- Month view: monthly consolidation and a twelve-month curve.
- Free navigation to past weeks and months, up to several years.
Split by sport, total duration, estimated calories: statistics always follow the displayed period, never an arbitrary window.
A plan that projects and adapts
- The current week is detailed: intentions per sport, key session, target volume.
- Next week is already visible, so you can judge the coherence of the progression.
- Later weeks show a trend, up to the lighter week.
- The classic rhythm of three loading weeks followed by a lighter one is not rigid: the lighter week can be moved earlier or later to fit your constraints.
- Volume progression is capped to avoid unrealistic load jumps.
Data, estimates and guardrails
Completed work comes from logged sessions. Load combines duration and perceived intensity; calories remain an estimate. The plan uses these data to organise what comes next, with capped weekly increases and an easier week after incomplete training or reported pain.
- Measurement: entered duration, distance, sets, reps or load.
- Estimate: calories and training load when data are incomplete.
- Recommendation: AI-generated weekly intentions, not a prescription.
- References: gradual progression and perceived-exertion scales; a qualified coach or clinician takes priority.
Frequently asked questions
Do I need a dated goal?
No. A general goal ("get back to three sessions a week") works too; a race date simply helps organise the phases.
Does it replace a coach?
No. It helps with organisation and consistency, it is not medical follow-up nor individual technical coaching.
What if I stop for two weeks?
The next plan restarts from your real volume rather than the theoretical one, with a progressive ramp-up.