How Runapt's Plan Builder Builds Your Training Plan | Runapt Blog

Most runners do not need another PDF. They need a training plan builder that fits a real race date, a real weekly mileage base, and the days they can actually train. A static 12-week spreadsheet assumes an average body and an empty calendar. The day you download it is usually the only day it is fully right.

Runapt’s in-app plan builder is the opposite of that. You answer a short guided flow — goal, who you are as a runner, how your week looks — and a live preview updates as you go. When the plan looks right, you build it. From there the plan does not stay frozen: readiness, missed runs, and real paces keep reshaping the week.

This post walks through how the plan builder works, what inputs matter, and how to get a solid first plan without overthinking every slider.

What a running training plan app should ask for

A useful plan is a negotiation between three things:

The goal — distance, race date, and whether you care about finishing strong or chasing a time.
Your current fitness — recent volume, longest run, and a recent race or hard effort if you have one.
Your life — how many days you can run, which day owns the long run, and which days are off-limits.

Skip any of those and you get either a plan that is too aggressive, too vague, or impossible to stick to. The builder’s job is to collect those inputs in order, show you the shape of the week before you commit, and hand the details to a VDOT-based engine instead of a one-size template.

If you want the science behind the paces, start with what VDOT is and the free VDOT pace calculator. The builder uses the same methodology once your plan is live.

Inside the in-app plan builder: four steps

The web and app plan builders follow the same structure: Goal → You → Schedule → Preview, with a sticky live preview so you never design in the dark.

1. Goal — distance, timeline, and intent

Pick a race block:

5K — default around 8 weeks, speed and race sharpness.
10K — default around 10 weeks, speed meets endurance.
Half marathon — default around 14 weeks.
Marathon — default around 18 weeks.

You can also enter a custom target distance (for example a 7.5 km local race or a 10-mile classic). The builder maps that to the nearest plan archetype so periodization still makes sense.

Optional but useful:

Plan length from 4 to 32 weeks (race date can set this automatically).
Goal race date so the block ends on the right weekend.
Goal pace or finish time if you are chasing a number rather than “just finish.”
Training focus / goal intent — race, run faster, run further, or maintain. For half and marathon this is framed more like finish strong vs get faster / PB, because that choice changes long-run build and race-pace work.

If you only know the distance and want to move fast, you can still generate a sensible default plan and refine later. The live preview on the side already reflects what you chose.

2. You — fitness, volume, and a recent result

This step is where generic plans usually fail. The builder asks for:

Fitness level — beginner, intermediate, or advanced (honest self-placement is better than flattering yourself).
Current weekly kilometres and longest recent run so progression starts from reality, not from week one of a brochure plan.
Conversational / easy pace if you know it.
Training age (years of consistent running) when you want the engine to treat you as experienced rather than brand new.
A recent race result (distance + time) when you have one — that is the cleanest way to anchor VDOT and training paces.

You do not need every field. A race result plus rough weekly volume is often enough for a strong first draft. Missing data just means more conservative defaults.

3. Schedule — days, long run, and hard limits

Training only works if it fits the week you actually live:

Days per week of running.
Long-run day (many people keep Saturday or Sunday).
Unavailable days so quality sessions do not land on travel or late-shift days.
Max run duration if time is the real constraint, not distance.

Fine-tune options are available when you want more control without leaving the builder:

Intensity style — balanced, polarized (mostly easy + hard quality), or pyramid (more threshold).
Terrain — flat, rolling, or hilly, so sessions respect the roads and trails you use.
Conservative progression when returning from time off or injury caution.
Deload week inclusion for longer blocks.
Strength sessions when you want them in the plan structure.

This is still a training plan, not a full life OS — but protecting the long run and avoiding “quality on the day you always cancel” matters more than perfect polarisation theory.

4. Preview — then build

While you fill the steps, the live preview regenerates on a short delay. You see the shape of the plan, warnings if something is inconsistent, and can jump back to the step that needs fixing. When it looks right, you name the plan (optional) and build.

What you get is not a PDF dump. You get a full adaptive block with paced workouts, and — once you are training — readiness-aware adjustments, missed-run reshuffles, and coach notes on top. Routes can be generated for sessions so the plan and the path stay connected. See features and how adaptive plans differ from static ones.

How the plan builder is different from a sample PDF

Static sample plan

Fixed weeks and paces for a generic runner
Same template for everyone
No preview of your week
Miss a week → improvise
Route planning is a separate chore

Runapt plan builder

Weeks, race date, and VDOT-linked paces from your inputs
Fitness, volume, long run day, and unavailable days shape the block
Live preview before you commit
Adaptation after the plan is live
Workouts can pair with automatic routes

Sample plans still have a role for learning structure. Runapt’s free resources include starting points like an 8-week 5K training plan, a 10K plan for busy runners, and a first half marathon plan. Use those to understand the shape of a block; use the in-app builder when you want that shape calibrated to you.

Tips for a better first plan

Be honest about weekly volume. Starting a marathon plan at 60 km/week when you are really at 25 km is how people get hurt. The builder can progress you; it cannot invent a base you have not run.
Prefer a recent race over a fantasy goal pace. A 10K from last month anchors VDOT better than a marathon goal time you have never approached in training.
Protect the long-run day. Everything else can flex; the long run is hard to replace mid-week without wrecking recovery.
Use custom distance for real races. Local 7.5 km races, 10 milers, and odd charity distances are valid. Enter the kilometres; do not force a 10K template if the race is not 10K.
Start simpler, then fine-tune. Goal + fitness + days per week already produces a usable plan. Intensity style and deload weeks are polish, not the first decision.
Preview until the warnings clear. If the rail flags the goal or schedule step, fix that before building. A two-minute correction beats a plan you ignore by week three.

After you build: what happens next

The plan builder is the front door. Once the plan is active:

Sessions show target distance and pace ranges grounded in VDOT methodology.
Daily readiness can suggest recovery, maintain, or reduced intensity before a bad week becomes an injury week.
Missed runs reshape the remaining week instead of stacking guilt doubles.
Post-run notes and, on Pro, AI coach chat explain adjustments in plain language.
You can plan or generate routes so easy days and long runs have a path, not just a number — see the running route planner.

If your goal is a specific distance, the product landing pages spell out the race-focused path: 5K, 10K, half marathon, and marathon.

FAQ

Is the training plan builder free to try?

Yes. You can start on the free tier and build training plans for shorter distances (5K and 10K), with limits described on pricing. Half marathon and marathon plans, unlimited plans, and full adaptive coaching features sit on Pro. The marketing site also has a lightweight plan preview so you can see the kind of week Runapt builds before you register.

Do I need a recent race time?

No, but it helps. Without a race, fitness level, weekly volume, and conversational pace still produce a plan. With a recent result, paces are better anchored from day one. You can refine later as real runs come in.

Can I build a plan for a non-standard race distance?

Yes. Enter a custom distance in kilometres (comma or dot decimals both work). The builder aligns the plan archetype to that distance so progression still matches something like a 7.5 km race or a 10-miler rather than forcing a pure 5K or 10K template.

How is this different from an AI chat that writes a plan?

Chat can draft text. The in-app builder is wired to the same plan engine the app uses for previews, persistence, paced workouts, adaptation, and routes. You get structure you can run against, not a paragraph you have to re-type into a calendar.

What if my schedule changes after I build the plan?

That is what adaptation is for. Low readiness, missed sessions, and pace drift feed adjustments after the plan exists. For a bigger life change you can always build a new plan from updated inputs — the builder is meant to be used again, not once forever.

Where do I open the plan builder?

In the web app under plans (create / build a new plan), and in the mobile app’s plan creation flow. On the marketing site, try the interactive preview first, then start free and complete the full builder with your real numbers.

Building a plan should feel like a short conversation with a coach who has your calendar open — not like filling a tax form or downloading a spreadsheet that never saw your Tuesday night meetings.

Start free and open the plan builder. Explore features or check pricing if you already know you want half/marathon and full adaptation.