Create and manage training programmes
A programme is your plan: a goal, a stretch of weeks, and the sessions that get you there. Løbeapp programmes are structured — built from blocks, sessions, and segments — so your training has a shape, not just a pile of runs.
Open Programmes from the navigation to see all your plans.
[[SCREENSHOT OF THE PROGRAMMES LIST]]
How a programme is structured
Three levels, from the top down:
- Blocks — phases of training, each spanning a number of weeks. Name them for their purpose: Base, Build, Peak, Taper. Blocks are how you periodise — a cornerstone of training that actually works.
- Sessions — the individual runs inside a block: an easy run, intervals, a long run, a rest day. Each session has a run type (Easy, Long, Tempo, Intervals, Hill repeats, Rest).
- Segments — the parts that make up a session, each with a role: warm-up, work, recovery, cool-down. Segments carry the metrics — distance, target pace, duration — that make a session specific.
[[SCREENSHOT OF THE STRUCTURE EDITOR SHOWING BLOCKS, SESSIONS AND SEGMENTS]]
:::tip Why structure matters A flat list of runs can't tell you whether you're building correctly. Blocks let you load and recover in waves; segments turn "do some intervals" into "6 × 800m at 4:30/km with 90s recovery." That specificity is exactly what the analytics read back to you. :::
Create a new programme
Choose Create a programme. Løbeapp offers several ways to build one, so it always matches your ambition level:
| Method | What it is | Status |
|---|---|---|
| The Master | Build it yourself in the structure editor — full control. | Available, free |
| The Co-driver | Our AI writes a periodised plan from a short chat. | Available (beta) |
| The Futurist | Drive everything from your own agent via our MCP server. | Available (beta) |
| The Copy-Cat | Start from a template or classic goal. | Coming soon |
| The Coach | A human coach builds and follows up with you. | Coming soon |
[[SCREENSHOT OF THE CREATE-PROGRAMME METHOD PICKER]]
The Master — build it yourself
You're in control. Set the basics (name, optional start/end dates and duration — editing any two derives the third), an optional race goal (race name, date, target time, distance — shown on your dashboard), and a weekly schedule (sessions per week, and either fixed training days with time windows or no day preference, which spreads sessions evenly across each week).
Then open the structure editor to build by hand:
- Add a block and give it a name and goal (e.g. Base — build aerobic volume).
- Add sessions inside it, each with a run type and day.
- Add segments to a session — warm-up, work, recovery, cool-down — with their distances, target paces, and durations.
It stays an editable draft the whole time. Activating it later spawns the planned sessions onto your calendar.
The Co-driver — let the AI build it
The Co-driver replaces the manual form with a short chat interview — your goal, weeks, available days, level, and any extras. From your answers it generates a complete, periodised programme as a draft you can review and edit. It can also adjust an existing plan ("Regenerate with AI") — for example easing your volume back up after a layoff. See The Co-driver for the full flow and the generation limits.
The Futurist — drive it from your agent
Prefer to work from Claude, ChatGPT, or your own tooling? The Futurist connects your agent to Løbeapp over our native MCP server, so it can build, restructure, and follow up on your training for you. Three steps: create a scoped token, add the server, give your agent the starter prompt. See Agent access (MCP).
The life of a programme
A programme moves through clear states. You can soft-delete from any state.
draft → published → active
↑ ↓ (archive) │
└── (abort) ───────────┘
inactive (archived) → (restore) → draft
| State | Meaning |
|---|---|
| Draft | Editable work in progress. Build and rearrange freely. |
| Published | Locked and ready. Structure is frozen; revert to draft to edit. |
| Active | Live. Planned (Forecast) sessions are scheduled on your calendar. |
| Archived | Set aside (inactive). Restore it to a draft to reuse it. |
The buttons on a programme follow these transitions:
- Publish — lock a draft. (You need at least one session with a segment that carries a metric.)
- Revert to draft — unlock a published programme to edit it again.
- Activate programme — go live and generate your Forecast sessions.
- Abort — stop an active programme; it returns to published.
- Archive — set a published programme aside.
- Restore to draft — bring an archived programme back to draft.
:::info One active programme at a time You can only have one active programme. Activating generates all your planned sessions in one atomic step, so your calendar always reflects a single, coherent plan. :::
:::note When your first week starts Week 1 begins on the first Monday on or after your start date, and no session is ever scheduled before the start. If you start mid-week, the few days before that Monday are skipped — your plan picks up cleanly at the start of the first full week. :::
If you opted to add the plan to your calendar, the invites are sent in the background and arrive in your inbox a few moments after you activate.
[[SCREENSHOT OF A PROGRAMME DETAIL PAGE WITH LIFECYCLE ACTIONS]]
Reactivating a programme
Life happens — you miss a week, get injured, or pause. Løbeapp's lifecycle is resume-aware, so picking a plan back up doesn't mean starting over or double-counting.
- Aborting an active programme removes only your upcoming planned sessions. Runs you've already logged — and planned sessions now in the past — are kept as history, so your analytics stay intact.
- Reactivating is idempotent: any session you already logged is never recreated, so you can't duplicate sessions or shoe mileage.
- When you activate a programme that has history, the Resume dialog lets you anchor a chosen session to a chosen date (past dates allowed). That session's block re-spans to fit, later blocks and the end date shift by whole weeks, and only sessions from the anchor forward are scheduled. Completed sessions you edit afterward are re-spawned as re-dos.
[[SCREENSHOT OF THE RESUME / REACTIVATE DIALOG]]
The result: you resume training from where you actually are, with your past runs and shoe mileage intact.