Your training plan shouldn’t be a PDF
How NexRex adapts after Garmin, Strava, or Apple Health sync — based on what you actually ran
You download a plan. Sixteen weeks, tidy mileage, a long run every Sunday. You save the PDF, screenshot the calendar, maybe print it for the fridge.
Then life happens.
Wednesday’s meeting runs long. Thursday’s easy run becomes a walk–jog. Saturday you feel great and go farther than the sheet said. By Sunday the long run on the fridge no longer matches the body that has to run it — but the PDF still looks confident.
That gap is the real problem. Not “discipline.” Not “motivation.” A plan that cannot see the week you just lived will keep prescribing the week it imagined.
NexRex is built for the other kind of plan: one that starts from your goal, then reshapes from the activities you actually complete — after your watch and apps sync in. Rex is not your coach. It’s the AI assistant that helps surface what changed and why, so you (or your human coach) can decide what next week should look like.
What a PDF can’t know
A static plan is a bet placed on day one. It assumes you’ll hit most sessions, recover on schedule, and stay healthy enough to stack volume the way the template expects.
Real training is messier:
- You miss a midweek workout because work won.
- You crush an easy day and accidentally turn it into something harder.
- You sleep badly for three nights and the “same” long run is no longer the same stress.
- You’re coming back from a niggle and the spreadsheet doesn’t care.
Your watch already has the truth of what you ran. A generic chatbot can give generic advice. What’s missing is a plan that lives next to that truth — and an assistant that can explain a proposed change in plain language instead of silently rewriting your calendar.
First: connect a device (or the plan is guessing)
NexRex needs activity data to analyze sessions, track progress, and adapt a plan. Connect at least one source under Settings → Connections:
- Garmin — authorize once; new activities sync after you finish.
- Strava — authorize once; new activities sync after you finish.
- Apple Health (iOS) — grant workout and heart-rate permissions.
If a connection drops, new activities stop arriving until you reconnect. No sync means the plan is flying partly blind — same as coaching from a spreadsheet while the watch lives in another app.
This is the unglamorous step that makes everything else possible. Adaptive isn’t magic; it’s “we saw what you did.”
How a NexRex plan is supposed to work
You pick a race distance and date (or a general goal). NexRex builds a weekly mix of easy runs, workouts, and long runs around your current fitness.
Then the important part: plans recalculate from the activities you complete. The more NexRex sees, the better it can tune pacing, volume, and recovery for what comes next.
Completion isn’t a vague vibe. Sessions tied to a plan carry a completion percentage and a clear band — on target, caution, off target — so you can tell at a glance whether a run tracked against what was scheduled. Going well over target is noticed too; overshooting volume is still information, not a free bonus.
That gives the system something a PDF never had: evidence.
Adaptation isn’t a silent rewrite
When there’s a reason to change your week — accumulated fatigue, a missed long run, a recent fitness jump — NexRex doesn’t have to ghost-edit your calendar and hope you notice.
For athletes on Pro, Rex can put a Plan adjustment card on Home (app and web). The card leads with why the change is suggested, what it does to the weekly objective and goal race, and a side-by-side of original vs proposed workout. You choose:
- Accept — apply the proposed workout.
- Keep original — leave the plan as it was.
If you keep the original, Rex can ask a short optional follow-up (work got in the way, protecting the long run, doesn’t match how you feel, ask me before changing, or a free note). That feedback makes the next proposal fit you better — and if you have a coach, they can see the reason without a separate message.
Not every check produces a proposal. When the evidence doesn’t warrant a change, the week stays as scheduled. No card, no noise.
Increases are conservative on purpose. Rex can propose raising next week’s load, not only cutting it — but volume only (distance or duration), never pace, intensity zones, or interval structure, and never more than 10% above the scheduled target. Increases only appear when recent training supports them (strong completion, no injury/illness/fatigue/overtraining signals, readiness not declining, no race inside three weeks, and no unfinished earlier increase). If those checks can’t be verified, no increase is proposed. An increase card also shows the evidence — completion rate, load trend, readiness — so you can see the numbers before you tap Accept.
You can also turn AI Dynamic Adjustment off per plan when you enroll. Off means no weekly proposals or adjustment notifications for that plan; other plans keep their own setting.
If you have a coach
When a coach manages your training, weekly proposals go to them. You can still see what Rex suggested (read-only); Accept and Keep original belong to the coach. That keeps the human in the loop for roster decisions — Rex proposes, the coach decides.
Group plans work the same idea at squad scale: the coach owns the template; your synced activities still show how the week actually landed.
A week that isn’t on the PDF (synthetic story)
Meet Maya. She’s eight weeks out from a half marathon. The plan says Wednesday threshold, Thursday easy, Sunday long.
Wednesday: a client emergency. She gets out for 25 minutes easy instead of the workout — about half of what was on the calendar.
A PDF still expects Thursday easy + Sunday long as printed. Maya’s body is carrying a missed quality session and a shorter midweek dose.
With devices connected, NexRex sees the incomplete Wednesday. Rex can surface a proposal that protects the Sunday long run — for example easing Thursday or reshaping weekend volume — with the reason on the card: missed key session, weekly objective at risk. Maya (or her coach) accepts or keeps original. After an accepted change, a short How did it feel? check (too easy / just right / too hard) helps calibrate the next suggestion.
None of that requires Maya to paste her week into a chatbot and re-explain her race date. The plan and the assistant are already looking at the same week she lived.
(Maya is a composite. Your weeks will look different; the point is the loop: sync → evidence → proposed change → human decision.)
Memory makes adaptation personal
Adaptation without memory is still generic: “you missed a session, so cut volume.”
Rex also carries who you are as a runner — preferences, history, lessons from what you and your coach already tried — so a proposal can respect more than raw completion. Morning-only schedule. A cranky left knee last block. The time you pushed through a niggle and paid for it.
Charts keep the numbers fresh. Memory keeps the person. Together they’re why the conversation after a messy week doesn’t start from zero.
What this is not
- Not a promise to hit a PR. Adaptation improves the odds that next week matches reality; it doesn’t guarantee a finish time.
- Not medical advice. Anything that looks like injury or illness comes first. Rex can flag; you and qualified professionals decide.
- Not “AI coach.” Rex is an AI assistant. You — or your coach — still own Accept, Keep original, and the hard calls.
Start with one boring, high-leverage step
- Open NexRex and connect Garmin, Strava, or Apple Health.
- Enroll in a plan (solo) or accept the plan your coach assigned.
- Train as you train. When a Plan adjustment card appears, read the why — then Accept or Keep original.
- Ask Rex about the week in plain language: If I can only train four days, how should this week flex?
A fridge PDF can’t answer that with your actual Wednesday on the table. A living plan plus an assistant that saw the week can at least ask the right question.
Ready to leave the static sheet behind? Open the app, connect a device, and let next week meet the runner you are this week. Prefer the memory story first? Read How NexRex remembers you.