Training plans

A training plan is a reusable block of training laid out week by week — “week 1 Tuesday: threshold intervals, Saturday: long ride”, and so on. It’s a template, not an assignment: a plan has no dates and doesn’t belong to any athlete.

Like your workout library, your plans are personal. Nobody else sees them.

Libraries

Plans live in libraries — named containers you choose, exactly like the ones in your workout library. A plan belongs to one library at a time; a library holds as many plans as you like. “Race Prep”, “Masters squad”, “2026 base” — however you actually think about them.

Everyone starts with one called My Training Plans. It’s your default: any plan created without saying where it should go lands there. You can rename it, but you can’t delete it — there always has to be somewhere for a new plan to go.

Deleting any other library only works when it’s empty. If it still holds plans, PlanMyPeak refuses and says so, rather than quietly deleting the plans inside it. Move them somewhere else first, or delete them yourself.

Moving a plan between libraries changes nothing about the plan. Its weeks, its scheduled workouts and the notes on them are untouched, and it can still schedule workouts from any of your workout libraries — the two kinds of library are independent.

Importing from TrainingPeaks

There’s an Import from TrainingPeaks button at the top of this page. It needs the PlanMyPeak Importer  browser extension installed, and you need to be signed in to TrainingPeaks.

Pressing it opens the importer over the page, on its Plans Library tab, where your TrainingPeaks plans are listed under the plan libraries that hold them. Tick the plans you want, confirm what to bring across, and watch it run. When it finishes, this page refreshes on its own — no reload needed.

The importer’s tabs stay switchable while it’s open, so you can pick up a workout library or an athlete group in the same run without closing it.

If your extension is an older version it opens on its Workout Libraries tab instead — your plans are one click away, on the Plans Library tab, and importing works exactly the same. Updating the extension takes you straight there.

If the import won’t run

The button is always there. Press it and PlanMyPeak checks your extension right then — so if you fix something in the extension, just press it again rather than reloading the page. When it can’t run, it tells you why:

• “did not respond” — the extension isn’t installed, or it’s switched off for this site. Install or enable it, then press the button again.
• “out of date” — you have the extension but an older version than this import needs. Update it from the Chrome Web Store.
• “not signed in to TrainingPeaks” — sign in to TrainingPeaks in the same browser, then press the button again.
• “the importer is not signed in to PlanMyPeak” — open the extension itself and sign in there. That’s a separate sign-in from the one you’re using on this page.
• “signed in to a different PlanMyPeak account” — the extension is signed in as somebody else, so importing would put your plans in their account. Open the extension and sign it in as you. PlanMyPeak stops the import rather than letting it go to the wrong place.

Imported plans

Plans come across from TrainingPeaks the same way your workouts do, and they behave the same way on a re-sync: a plan you’ve already imported is updated in place, not added again. Import the same source twice and you still have one plan.

Two things follow from that, both deliberate:

• The library follows TrainingPeaks. A plan lives in one folder there, and each import files it in the matching library here. If you import a plan before its folder exists, it lands in your default library and moves to the right one on the next import.
• Your schedule is left alone. Re-importing updates the plan’s name, description and length. It doesn’t rearrange the workouts you have scheduled in it.
• Your day notes survive a move. Move a session to a different day in TrainingPeaks and re-import: PlanMyPeak recognises it as the same session and moves it, rather than removing one and adding another. The note you wrote on that day stays with it.

Imported plans arrive in their own library, and re-importing reuses it rather than creating another one each time. That library is never your default — your default stays yours, and an import can’t move it. A library you create yourself is never adopted by an import either, even if it happens to share a name.

A plan you build here yourself has no connection to TrainingPeaks and is never touched by an import.

Your plans

Open Training Plans from the sidebar. Your libraries are listed down the left, each with the number of plans it holds; pick one to see only its plans, or leave it on All libraries to see everything, grouped by library. You can search by name or description at any time, and sort by Recently updated, Name A–Z, Longest first or Highest load.

Each plan is a card, and the card answers “what does this actually ask of an athlete?” before you open it:

• Sessions — how many workouts are scheduled across the whole plan.
• Total — the time all of them prescribe, added up.
• Per week — that total spread over the plan’s length. The quickest way to tell a 6-hour week from a 12-hour one.
• Planned TSS — the plan’s total training load.
• A focus bar under the numbers, split by ride type — how much of the plan’s time is endurance, threshold, VO2 max and so on, widest slice first. The key beside the list names the colours in play.

Which library a plan is in shows on its card while you’re looking across all of them, along with when it was last updated.

Some sessions can’t be timed or loaded — an open-ended ride, or one prescribed by distance. Rather than quietly leaving them out, PlanMyPeak shows a + after the total (“18.5h+”) and says underneath how many sessions aren’t in it. Rest days aren’t counted as missing: they genuinely prescribe nothing.

Select a plan to open its schedule.

Reading a plan

A plan opens on two things: what it asks for in total, and how that is spread across its weeks.

The overview strip

At the top, the plan’s own figures — its length, how many sessions it holds, its total time, the time that works out to per week, and its planned TSS. They are the same numbers the plan’s card showed in the list, so nothing changes meaning when you open it.

Beside them, one bar per week, tallest week hardest. This is the shape of the plan: whether the load builds, holds, or backs off into a recovery week. Select a bar to jump straight to that week — it opens the block the week sits in if you had folded it away. Plans whose sessions have no derivable load (heart-rate workouts with nothing planned by the provider, for example) draw the bars from prescribed time instead, and say so.

Blocks

The weeks are stacked in blocks of four — Block 1 is weeks 1–4, Block 2 is weeks 5–8, and so on. The last block is short if the plan does not divide evenly: a nine-week plan reads 4 / 4 / 1.

Each block header carries that block’s own total time and TSS, so you can compare one stretch of the plan to another without opening either. Select the header to fold the block away; select it again to bring it back.

Week cards

Every week is a card: Week 1, Week 2 and so on, for as many weeks as the plan is long. Its header shows what that week asks — total time, planned TSS, how many of the seven days are training days — and a colour bar splitting the week’s time by ride type.

Below that are the seven days, Monday through Sunday:

• A day with a workout shows a card with the workout’s name, its ride type, how long it takes and its planned TSS. A stripe in the ride type’s colour runs across the top.
• A day with two sessions shows both, in the order they’re meant to be done.
• A day with nothing scheduled narrows to a marked-out sliver, so the days that do hold training get the width. It still reads as No workout scheduled to a screen reader — an empty day is never confused with a missing one.

Weeks are relative, so there are no dates: week 1 is simply the first week of the plan, whenever you eventually use it.

On a narrow screen the schedule scrolls sideways rather than reflowing, so a week always stays a single row of seven days.

Week totals follow the same rule as the plan’s: a + means some of that week could not be timed or loaded, and never that it was quietly left out.

Opening a scheduled workout

Select any card and the full workout opens over the schedule — the same details you’d see in the library, plus any note attached to that particular plan day.

The first tag in the header names the workout library the session comes from. That is the thing the schedule itself cannot tell you, and it matters: the plan references the workout rather than copying it, so editing it in that library changes it in every plan that schedules it.

That note belongs to the plan, not to the workout: “hold the low end today” applies to this Wednesday in this plan, and doesn’t change the workout anywhere else.

Close with the ✕ or Escape. You come straight back to the card you opened, with the schedule exactly where it was.

Editing plans

Not yet. This release lets you read your plans; there’s no dragging workouts around, no adding or removing days, and no way to create or delete a plan from the app. Building plans in the app is coming next.

Libraries are the same for now — you can browse by library here, and creating, renaming and deleting them arrives with plan editing.

Moving a plan between libraries isn’t something you do here either — an import puts each plan in the library its TrainingPeaks folder names, and keeps it there.