Adaptive weekly planning
The plan is built from the current training state rather than a fixed calendar.
Used in: weekly plan · replanningFrom the first training block to race day: see how PACE plans your training, recognizes progress, evaluates workouts and turns that into the next useful stimulus.
If you only have two minutes: this is where PACE differs from a static plan or pure tracking.
PACE is in early access. Status labels show what already exists in the current product and what is still ahead.
How PACE turns history, goals, availability and actual training into the next useful step.
The plan is built from the current training state rather than a fixed calendar.
Used in: weekly plan · replanningExisting Apple Health runs establish baseline, volume and demonstrated capacity at setup.
Used in: onboarding · baseline · first planReal weekly volume, frequency, long runs and demonstrated tolerance bound how quickly volume may grow.
Used in: weekly volume · long run · progressionPACE reassesses the remaining week instead of mechanically paying back missed mileage.
Used in: replanning · load managementPlanned sessions are distributed across the days the athlete can actually train.
Used in: weekly structure · replanningFoundation, specific work, peak/taper and race week change priorities and workout mix.
Used in: training phase · taper · race weekGoal time and current forecast can shape allowed priorities without artificially increasing the quality budget.
Used in: training focus · HM-specific workNORMAL, CAUTION and HIGH_FATIGUE can change volume and available quality; recovery takes priority over goal pressure.
Used in: daily decision · weekly replanningAfter a confirmed race, return to normal load is controlled rather than immediately jumping back to prior volume.
Used in: following week · return to normal loadNot just tracking: PACE compares plan and reality and uses the result downstream.
Structured workout steps are matched against the segments actually completed.
Used in: workout analysis · target adherenceEasy, long, threshold, HM pace, VO₂, hills and other workout types are evaluated with family-specific criteria.
Used in: analysis · response engineTarget ranges, completed distance/duration, heart rate, fade and other relevant metrics are interpreted together.
Used in: workout outcome · plan adaptationPerceived exertion and relevant feedback can refine interpretation and trigger reanalysis.
Used in: analysis · recovery · responsePrevious workout and race analyses remain available with the same rich analysis payload instead of degrading into a reduced historical view.
Used in: analysis history · reviewRaces, tests and suitable workout results can update individual pace anchors.
Used in: threshold · HM pace · training targetsCurrent performance evidence produces a model-based HM forecast with transparent data quality.
Used in: progress · training paces · race strategyMultiple forecast points show how the current performance anchor changes over time.
Used in: ProgressGoal time and current forecast remain separate; the desired goal does not simply become the performance anchor.
Used in: Progress · planning prioritiesPACE shows which factors support or limit the current forecast or race readiness.
Used in: Progress · coaching explanationFrom race date to post-race analysis and back into the next training cycle.
Specificity, durability, consistency, freshness/taper, recovery, safety and fueling are evaluated separately and combined.
Used in: Progress · race proximity · training focusA run is treated as a race only after explicit confirmation, not merely because of distance or pace.
Used in: performance evidence · race intelligenceKilometer splits and race phases show pace, heart rate and changes across the race.
Used in: race analysisStart behavior, first vs second half and late-race fade are interpreted separately.
Used in: race intelligence · training focusAbsolute intensity and change across the race are deliberately kept separate.
Used in: race analysis · coachingLearnings such as pacing discipline, HM durability or conditions adaptation persist and can shape later priorities.
Used in: next training cycle · race strategyCurrent forecast, readiness and retained race learnings produce pacing guidance and race cues.
Used in: race preparation · ProgressFueling practice and tolerance can be recorded on long/race-specific sessions and used in race readiness.
Used in: long run · race readiness · race coachingPACE separates uncomplicated return from situations that require professional guidance or assessment.
During illness or injury, running and Watch prescriptions are paused while prior training history remains intact.
Used in: safety · planner · Watch syncAfter resolved mild issues, PACE starts with a short very easy check followed by three reviewed easy-return steps.
Used in: return-to-training · automatic plan handoffSystemic, significant, recurrent or abnormal responses block the normal self-guided return and escalate to professional assessment.
Used in: safety · pause policyWhen explicit external restrictions exist, the runtime can store and enforce distance, frequency, spacing and reassessment limits. This is not the normal consumer return flow.
Used in: professional return plan · workout planningMissed mileage after illness or injury is not treated as debt to be repaid in the following week.
Used in: return · weekly planningFrom the planned workout to the imported result.
PACE builds workout steps with distance/time and pace, heart-rate or effort logic depending on the session.
Used in: workout · Apple WatchEasy, recovery, long run, threshold, HM pace, VO₂, hills, long HM blocks, calibration, strides, race and rest have distinct roles.
Used in: periodization · training stimulusPlanned structured sessions are sent to Apple Watch with stable plan IDs and reconciled after replanning.
Used in: workout execution · targetsApple Watch remains the recorder; PACE imports workout, heart rate, distance and running speed for analysis and replanning.
Used in: training history · analysis · engineRunning-specific strength sessions include development/maintenance variants, sets/reps, RIR, rest, explanations and exercise visuals.
Used in: plan · workout · prehabTargeted mobility can precede quality sessions; optional stretching can follow easy/recovery sessions.
Used in: workout preparation · companion modulesWhich additional signals PACE does not merely display but actually interprets in decisions.
Sleep, HRV, resting heart rate, subjective state and training context are considered together.
Used in: readiness · recovery state · planningMax HR, resting HR and derived training anchors help individualize easy/LT1/threshold and intensity interpretation.
Used in: targets · analysis · ProgressTemperature/feels-like, humidity, dew point, wind and precipitation can be processed as environmental context.
Used in: workout interpretation · race contextRouteSummary uses elevation gain/loss, gradient, terrain fractions and mean altitude without sending the exact GPS route in the engine payload.
Used in: pace interpretation · analysis · race intelligencePACE does not use a universal weather penalty; heat, wind and terrain can shift how pace is weighed against heart rate/RPE.
Used in: workout analysis · response · replanningMissing or uncertain data lowers analysis confidence; PACE does not treat absent signals as ideal execution.
Used in: analysis · positive progressionWhat the athlete directly sees and controls in the app.
Core screens connect today's decision, workout details, weekly plan, analysis history and performance development.
Used in: daily app experiencePACE explains purpose, focus, common mistakes and relevant rationale instead of showing only numbers.
Used in: Today · WorkoutProfile, goal, training days, HR anchors, automatic volume capacity, strength, integrations and help are centralized.
Used in: profile & settingsWorkout cards for story, 4:5 and 1:1 plus route, metrics, intervals and transparent PNG can be saved or shared.
Used in: analysis · social sharingStart and finish can be protected with privacy zones; exact route does not need backend storage for export.
Used in: share exportThe app and dynamic coaching copy are currently maintained in German and English with localization contracts.
Used in: entire appThe unit system can be switched between kilometers and miles and is applied consistently across plan, workout, analysis, history and progress.
Used in: entire app · account settingName, birth year, race goal/date, availability, Apple Health and first-plan bootstrap are implemented; public multiuser activation remains gated.
Used in: new account · first planAccount-isolated runtime state and restore on another device are technically prepared, while production multiuser remains deliberately OFF.
Used in: accounts · device changesAuthentication flows including password reset are implemented and remain feature-gated until production cutover.
Used in: multiuser sign-inSeparate opt-in, pseudonymized research facts and holdout validation are technically prepared; collection remains OFF by default.
Used in: later engine validation · not required for normal app useRoadmap items are deliberately separated from current capabilities. Versions show the currently documented target window and can still change before implementation.
Authentic pre-race forecasts are planned to be evaluated against verified HM outcomes using separate development, calibration and holdout cohorts.
Planned for: forecast calibration · evidenceFalse alarms and missed fatigue signals are planned to be evaluated on real athlete histories beyond synthetic tests.
Planned for: recovery intelligence · evidenceRun count, distance, time, weekly/monthly volume, trends and traceable personal bests with source and date.
Planned for: ProgressOpt-in iOS notifications for relevant plan/analysis events with deduplication and deep links.
Planned for: plan · analysisDynamic training, analysis and coaching copy that appears in the closed alpha will be systematically checked for complete German/English coverage.
Planned for: entire appAdditional wearables are planned through provider-neutral contracts; Garmin is the first candidate after technical/API validation.
Planned for: workouts · health/training dataStaged integration where reliable structured workout and data paths are available.
Planned for: wearable expansionPACE is planned to support additional race distances beyond the half marathon with their own periodization and workout logic.
Planned for: training breadthBeginner-specific progression instead of assuming an established running base.
Planned for: onboarding & periodizationRunning shoes with mileage, rotation and workout/history assignment as optional gear context.
Planned for: gearMajor half marathons and marathons are planned as structured race context with yearly editions, course/elevation profiles, goal selection, race strategy, environmental context and race intelligence loop.
Planned for: race setup · strategy · intelligenceSocial features around shared training and community activity.
Planned for: communityOptional community, competition and event features linked to participation/interest and training goals.
Planned for: communityStore actual load, completed reps and RIR; build execution history for later adaptive strength progression.
Planned for: strength · progressionA native Android client built on the same platform-neutral PACE Engine contracts.
Planned for: platform expansionAdditional languages and data/wearable providers after consolidated DE/EN and platform QA.
Planned for: internationalization · integrationsApp/Play Store productization, subscriptions plus support, operations and observability for public scale.
Planned for: public scale