Methodology
Pacer plans your running on two levels: a season plan up to your goal race, and a weekly briefing that adapts this plan to your current form and to what you actually ran. This page explains the rules behind it.
1. Data sources
Pacer works with four sources:
- Strava — your runs from the last two years. From them Pacer builds your performance curve (your best efforts across different durations) and derives your current weekly volume, your long runs, your races and your quality sessions. Activity names and descriptions are never passed to the AI.
- Garmin (optional) — HRV, sleep, Body Battery and resting heart rate result in a readiness rating. The raw values stay on our server.
- Your profile — lactate test, threshold values from your watch, maximum heart rate, running and rest days, race goals. Measured values take precedence over estimates.
- Your feedback — how last week felt, and notes on the coming week (travel, appointments, niggles).
2. Thresholds
All pace targets are anchored to two thresholds:
- LT2 (second lactate threshold) — roughly the pace you can sustain for one hour. Pacer uses the best available value, in this order: lactate test (valid for 180 days), threshold value from your watch, your Strava performance curve, a recent race result, VO₂max estimates.
- LT1 (aerobic threshold) — the upper limit for easy running. Measured (lactate test or a validated estimate from heart rate and pace of your easy runs), otherwise derived from LT2.
When your LT2 changes — through a test, a race or a new best effort — zones and pace targets follow automatically, unless you have locked your zones in your profile.
3. Training zones
From LT1 and LT2 Pacer derives five zones:
- Zone 1 — recovery, slower than your easy pace
- Zone 2 — base, easy, below LT1
- Zone 3 — between LT1 and LT2 — where many runners' marathon pace lies
- Zone 4 — threshold, around LT2
- Zone 5 — VO₂max range, faster than LT2
Each zone has a pace range (min/km) and, where measured values exist, a heart rate range.
4. Season plan and periodisation
For your A race, Pacer calculates a season plan backwards from race day: weekly volume, long-run length and quality sessions for every week. The season plan follows fixed rules — the same data yields the same plan. It is divided into phases:
- Base — build volume and easy mileage
- Build — VO₂max, threshold and, for 10 km and 5 km, speed endurance, each as its own block; for the marathon VO₂max first, then threshold
- Race pace — for the marathon: goal pace in quality sessions and long runs
- Sharpening — race-specific sessions in the weeks before the taper
- Taper — usually two weeks of reduced volume with intensity maintained, so you start fresh
- Recovery — after races, before the next build begins
The order and length of the phases and the type of quality sessions depend on the goal distance (marathon, half marathon, 10 km, 5 km, trail). If Pacer identifies your biggest lever from your performance curve (such as VOâ‚‚max, threshold or endurance over long distances), the matching block gets longer; the order stays the same. Within a phase, quality sessions progress step by step; after several build weeks comes a lighter week.
If time to the race is short, Pacer drops phases rather than increasing load faster. How much volume may grow from week to week does not depend on the time remaining.
B races get their own race week in the season plan, followed by recovery; then the plan continues.
5. The training week
Every week Pacer turns the season-plan week into a briefing: one session per day with distance, target zone and pace, and for quality sessions their structure and purpose.
Volume: the target is the week from the season plan. As a safety limit, Pacer plans at most about 10% above your load of recent weeks; 30% above is a hard limit that is never exceeded.
Intensity: most of the volume is easy, below LT1. On top come a long run and one quality session per week. Runners with enough volume and running days get a second quality session: it keeps abilities from earlier blocks alive before their effect fades, prepares the next block, or complements the current one. For beginners and below about 20 km per week the focus is on building volume, with short strides instead of quality sessions. Once your volume grows past that point, the first quality session starts at the lowest step. The long run changes its form without becoming a quality session: sometimes plain easy, sometimes with a steady finish, a fartlek, or on a rolling course. Runners with little or no quality work get this variety in the long run more often.
Readiness: your check-in, Garmin data and health notes give one of four levels. With clear fatigue the week gets lighter — less volume, one quality session instead of two, a shorter long run; with injury or illness the quality work is dropped entirely. With very good recovery the week may carry a little more, at most 5 % volume.
6. Adapting to what you run
Every week Pacer compares plan and execution and adapts, without reacting to single outliers:
- Volume: if you average below 85% of the plan over three weeks, the following weeks are reduced. If you are clearly above (over 115%), the plan steps up once.
- Breaks, illness, injury: if a week largely drops out or you take a break, Pacer brings you back gradually — up to 5 days off at full volume, longer breaks first at 50%, then 75% (after Daniels). After more than two weeks off, the plan restarts from your current level. Pacer detects breaks from your data; you don't need to report anything.
- Quality sessions build on what you actually ran: the next session is at most 50% larger than your last completed one. Skipped sessions therefore slow down the progression.
- Long run: the next long run is at most one planned progression step above what you last actually ran.
7. Rules and AI
Everything that concerns load and safety is calculated by fixed rules: season plan, volume limits, long run, size of quality sessions, pace targets and zones. The AI (Claude by Anthropic) decides within these limits — for example which format a quality session takes from a curated catalogue and how sessions are spread across the week — and writes the briefing. It receives:
- your profile (goals, thresholds, zones, running and rest days)
- the season-plan week with phase, volume, long run and quality session
- a derived readiness rating, no raw Garmin data
- your notes and feedback
Strava activity names and descriptions are removed beforehand. Raw Garmin data (HRV values, Body Battery, stress scores) never leaves our server.
8. Checks before delivery
Every plan is automatically checked against the rules before delivery — including volume, paces and spacing between hard sessions — and then approved by a human. Only then is it sent to you. If something is off, the plan is regenerated with a correction note.
The Pacer Check
The free Pacer Check analyses the last 18 months of your Strava runs: volume, consistency, long runs and races. It suggests a goal distance and a preparation time, estimates your race time with the same performance curve the app uses, names strengths and weaknesses and, where the data allow, your biggest lever. No account needed. Go to the Pacer Check
Privacy
All data flows — in particular which information is transmitted to external services (Strava API, Garmin Health API, Claude API) — are documented in the Privacy Policy. Processing of Strava data is carried out only with your explicit consent (GDPR Art. 6(1)(a)).