From PDF to Apple Watch: how to actually use a training plan you didn't make in your watch's coaching app

If your training plan lives in a PDF, an Excel from your coach, or a chat with ChatGPT, getting it onto your Apple Watch is harder than it should be. Here's the workflow that actually works in 2026.


You have a 16-week marathon plan. It's good. It came from a coach, a book like Advanced Marathoning, or from a careful prompt to ChatGPT. The plan is solid - the kind of thing that, if you actually execute it, will get you to your goal.

The problem isn't the plan. The problem is everything that happens between the plan and your watch.

You open Apple Watch's native Workout app on a Tuesday morning and stare at it. The plan says "10K easy with 4×100m strides." The watch says: outdoor run. You start running. By the time you remember to add strides, you've forgotten how many you've done. Two days later you do the workout from memory, slightly wrong. By week six, the plan and your actual training have drifted so far apart that you stop checking the plan at all.

This is the silent failure mode of the "self-coached athlete using a non-app training plan." Not getting injured. Not bonking. Just slowly losing the structure that made the plan worth following in the first place.

Here's what's broken, why, and the workflow that actually solves it in 2026.

What's broken: a quick anatomy

Apple Watch's Workout app can do structured workouts. It can do intervals. It can do warmups and cooldowns and target ranges. As of watchOS 10, you can even build custom workouts directly on the watch or in the iPhone Workout app.

So why is it so hard to use a real training plan with it?

Three reasons:

1. The Apple Watch Workout app is one-workout-at-a-time. You can create a custom workout - say a tempo run with intervals - and save it. But there's no calendar. There's no "Monday is easy 8K, Tuesday is the tempo, Wednesday is recovery 6K". You'd have to manually navigate to each saved workout every single day. For an 18-week plan with 90+ unique workouts, that's not a workflow. That's data entry as a job.

2. Plans live in formats Apple doesn't understand. Your coach's plan is a PDF. Your friend's ChatGPT plan is a markdown blob in a chat. Hal Higdon's Novice 1 is a printable table on his website. Pfitzinger's 18/55 is a chapter in a paperback book. Apple's Workout app reads none of these. It expects you to translate every line of every plan into its custom workout builder manually.

3. The "structured workout" features are incomplete. Apple Watch indoor running workouts only support heart-rate targets, not pace. RPE-based workouts (the foundation of Daniels' method and Pfitzinger's plans) can't be synced at all. Unstructured workouts ("Easy 30 min") often won't push to the watch. So even if you do laboriously enter every workout into Apple's builder, parts of your plan will silently degrade.

The combination of these three problems is the friction that kills self-coached athletes' adherence. The plan is good. The execution is a death by a thousand small re-types.

The five workflows people use today (and why they all break)

I've seen people try every one of these. They all eventually fail for the same reason.

Workflow 1: Manual transcription into Apple's Workout app. The athlete sits down on a Sunday and types every workout into the iPhone Workout app. Custom Run → Warmup → Work → Recovery → Cooldown → repeat. For 18 weeks, this takes 3-4 hours. The plan changes mid-block? Start over.

Workflow 2: Manual transcription into TrainingPeaks. Same as above but you pay $20/month for the privilege. TrainingPeaks does have an Apple Watch integration that pushes structured workouts to the watch, which is genuinely useful. But the transcription work is identical - and TrainingPeaks' CSV import is explicitly unreliable per their own help docs.

Workflow 3: Screenshot the plan, look at it every morning. The plan lives in Photos. You squint at it before your run. You can't trigger a structured workout from a screenshot. So you just start "Outdoor Run" and try to remember which intervals you were supposed to do.

Workflow 4: Just run by feel, ignore the plan structure. This is what most self-coached athletes default to within four weeks of starting a structured plan. It's not necessarily bad - but it means you paid for or wrote a plan you're not actually executing.

Workflow 5: Switch to a subscription AI coach. Runna and similar apps generate your plan for you and push the workouts to your watch automatically. This works but has two problems: it's expensive (€120-180/year), and as PTs have started noting, the algorithmic plans are sometimes too aggressive, leading to a wave of injury reports across r/running and TikTok. You also give up the plan you actually wanted to follow.

None of these are good. They share a common failure: they treat the plan as the input, but force the athlete to do the structural translation work manually every single day.

What actually needs to happen

If you sit with the problem for a while, the answer becomes obvious. The athlete shouldn't be doing the translation work. A tool should:

  1. Accept the plan in whatever format it lives in - PDF, Excel, ChatGPT markdown, screenshot, coach's email.
  2. Parse it into structured workouts with proper distances, paces, HR targets, intervals.
  3. Show it on a calendar so you can see what's coming.
  4. Push each workout to the Apple Watch one day at a time, ready to start.
  5. After the workout, pair the completed activity back with the plan so you can see how you're tracking.

That's it. No AI coach replacing your decision-making. No subscription that costs more than your running shoes. No locking you into someone else's algorithmic plan.

This is what Apple Watch should have done natively. They haven't. So someone has to fill the gap.

The right tool exists in 2026 - barely

The space is filling in. Here's the honest landscape as of mid-2026:

For strength athletes: Repport does this exact workflow but for lifting. PDF/spreadsheet/screenshot in, structured gym workout out, export to CSV. Closed iOS beta. If you lift, it's worth a look.

For endurance athletes: This is the gap. The major players are all building from the AI-coach end (generate plans for you) rather than the BYO-plan end (take your plan, get it on your watch). TrainingPeaks is the closest functional fit but it's expensive, coach-centric, and the CSV import doesn't actually work.

That's why we're building Stopa. iOS-only, endurance-focused, designed around the exact workflow above: paste any plan, see your calendar, sync to your Apple Watch, track how you're doing.

If this is the problem you're solving manually right now, join the waitlist. We're launching to Apple Watch users first. Garmin support follows when their Developer Program reopens.

What to do today, while waiting

If you don't want to wait:

Use TrainingPeaks for free. Their free tier supports one structured workout per day pushed to Apple Watch, manually entered. It's not the workflow you want, but it works.

Or accept the trade-off. Print your plan, put it on the fridge, do the workouts by feel, use Apple Watch's standard "Outdoor Run" mode and capture splits manually. Self-coached athletes have been doing this for 50 years. It's not optimal, but it's not nothing.

Or wait a few weeks. We're shipping the version of this that doesn't suck. Join the waitlist and you'll get an early TestFlight invite.

The plan you wrote, or the plan ChatGPT wrote with you, or the plan your coach handed you in a PDF - all of those deserve to actually be on your wrist. Not in a Notes doc you check every morning.


Stopa is an iOS app for endurance athletes who already have a training plan and want it on their Apple Watch without retyping every workout. Pre-launch waitlist open at stopa.app.