Readiness — Target Events

Answers:

"Am I progressing toward the required state for my target event?"

Readiness applies event-specific context to the Intelligence Stack.

It considers information such as:

• event priority;
• days to event;
• projected form;
• TSB;
• taper state;
• event demands;
• limiting factors;
• phase alignment.

---

The Readiness view evaluates whether your current training state is aligned with an upcoming target event.

It combines:

• the target event stored in Intervals.icu;
• projected fitness and fatigue at the event;
• event-specific form targets where available;
• current training phase and planned load direction;
• taper governance;
• durability and performance limitations;
• the Montis Adaptive Decision Engine (ADE).

Readiness is therefore not simply today's Wellness status or today's TSB.

It asks:

"Given where I am now, the training I have planned, and the demands of this event, am I progressing toward an appropriate race state?"

---

How Race Readiness Is Evaluated

The Race Readiness Dashboard evaluates the athlete relative to the specific target event rather than applying one universal readiness threshold.

Different race types can require different target states for freshness, neural load, anaerobic priming, durability and energy-system alignment.

The same underlying athlete metrics may therefore produce different readiness interpretations for different events.

Data Inputs — The Signal Stack

Race Readiness combines several layers of evidence:

• Event Metadata — target load, expected intensity, duration, distance and event priority;
• Forecast Series — projected CTL, ATL and TSB leading into race day;
• Future Trajectory — forward load and form context used for validation and fallback;
• Performance Intelligence (PI) — recent durability, intensity density and anaerobic-repeatability evidence;
• Energy System Progression (ESPE) — current energy-system profile and adaptation state;
• Block History — phase and load history used to interpret taper magnitude and training trajectory;
• Taper State — ADE-resolved taper state.

The dashboard prioritises the athlete's projected state at race start rather than relying only on today's training status.

---

The Readiness Core

The Readiness Score (0–100) summarises the athlete's event-specific readiness evidence.

The score is interpreted together with the event profile and limiting factors rather than treated as a standalone percentage.

The dashboard maps the score into readiness states such as:

• Near Peak — optimal freshness and strong event specificity;
• Ready — appropriate freshness and event preparation;
• Risky — residual fatigue, poor taper execution or another meaningful limitation;
• Poor — significant fatigue, detraining or substantial event-preparation constraints.

The dashboard also exposes the limiting factors responsible for reducing readiness.

Examples can include:

• neural load clustering;
• durability drift;
• projected form outside the event target;
• taper conflict;
• event-specific energy-system mismatch.

---

Diagnostic Verdicts

Race Readiness also evaluates several individual dimensions.

Form — Freshness

Evaluates projected TSB at race start relative to the event-specific target.

Durability — Stability

Evaluates evidence of performance fade and cardiovascular / power decoupling.

Neural — Sharpness

Evaluates whether recent high-intensity work indicates appropriate priming or excessive neural load.

Alignment — Specificity

Compares the athlete's current ESPE profile with the physiological demands of the target event.

Taper — Execution

Evaluates whether the planned load reduction and remaining intensity are consistent with arriving at the event in the required state.

These diagnostic verdicts explain why the overall readiness score has been produced.

---

Target Events from Intervals.icu

Montis reads Race A, Race B and Race C events from your Intervals.icu calendar.

Race priority matters. Montis does not treat Race A, Race B and Race C events equally.

• Race A is the primary target event, and the only one that gets taper governance. ADE marks pre-taper from 21 days before the event, but that is only a note. From 10 days out (taper), ADE protects the race from conflicting load and phase decisions.
• Race B is an important secondary target. Montis shows it as context (readiness and countdown), but it does not trigger pre-taper or taper governance, so it doesn't constrain ADE decisions.
• Race C is a lower-priority event or training race. Like Race B, it doesn't trigger taper governance, so normal training progression takes precedence.

Only A races constrain the Adaptive Decision Engine's taper decisions. The same projected form or fatigue state can therefore lead to a different coaching response when the event is marked A rather than B or C.

Events may be:

• events you create yourself;
• shared events added from the Intervals.icu Races & Events directory;
• shared events that contain additional course information.

The event record can provide Montis with context such as:

• event date;
• priority;
• sport;
• planned load where available;
• expected duration and distance where available;
• projected CTL and ATL;
• event-specific training demand;
• shared event information.

Managing target races

Montis reads Race A, B and C events from your Intervals.icu calendar. You can add, change or remove them in Intervals.icu, or from the app:

• Change or delete a race: on the Readiness page, press the gear icon (Modify Event) next to the race name. The race opens in the Workout Builder, where you can edit it or delete it. Delete asks you to confirm.
• Delete a race directly: open Workflow and find Target Event Profiling & Readiness Governance. Press the bin icon on the race, then press it again to confirm.
• Add a race: save an event as Race A, B or C from the forecast calendar or the Workout Builder.

After you save or delete a race, Montis refreshes your calendar and the readiness sources. Changes made in the Builder also refresh the weekly and season reports.

The race picker cards on the Readiness page only select a race. They have no edit or delete buttons.

Race names and training focus

Montis reads certain words in a race's name to set the training focus for that race. Upper or lower case doesn't matter, and the letters also count inside a longer word.

For rides, a name with tt or time trial also marks the race as a time trial, which sets a fresher form target on race day (Event TSB 8 to 18). Ride names with crit, circuit or loop, or fondo, sportive or etape, and the run distance also set the race profile.

---

Shared Course Map

The Readiness page can also display a detailed course map and route forecast.

However, an event location is not the same thing as a course route.

An Intervals.icu event can contain latitude and longitude describing where the event takes place without containing the actual race course.

Montis requires an attached course file to perform route analysis.

Supported course sources include an attached:

• GPX
• FIT
• TCX

course.

Event location only

An event may contain:

• venue;
• address;
• latitude;
• longitude;
• event map location.

This is enough for Intervals.icu to show where the event takes place.

It is not enough for Montis to reconstruct the race route.

In this case the Readiness page will display:

the pin location of the event

because no route stream is attached to the shared event. However, if you attach a GPX file manually to the calendar event in intervals, it will use this to reconstruct the race route.

Event with an attached course

If the Intervals.icu event includes a GPX, FIT or TCX course, Montis can obtain the actual sequence of route coordinates.

This enables the Shared Course Map and allows route-level analysis such as:

• total course distance;
• elevation gain;
• maximum altitude;
• terrain profile;
• route segments;
• climbs and descents;
• estimated course demand;
• course-specific pacing or completion modelling where supported.

The important distinction is:

Event coordinates = where the race is

Course coordinates = the route you will race

Montis requires the second one for the Shared Course Map.

---

Adding a course in Intervals.icu

You can use an existing shared race from the Intervals.icu Races & Events directory or create/share your own event.

For Montis route analysis, verify that the event contains an attached course.

In Intervals.icu this can be added through the event's Add Courses function by uploading a GPX, FIT or TCX file.

Simply adding an event address or map location does not create a course.

Finish-time forecast

When your target race has a course, the Readiness page shows a ROUTE FORECAST under the course map. It predicts your finish time from your own training history and current settings, and shows how hard the course is.

What you see

The Coaching Perspective — Model Anchor panel shows the evidence behind the times: your closest matching ride or run (distance, gain or time), the climb used, your power model, or the threshold pace cap.

The numbers come from the Montis engine. The AI Coach explains them and is told not to recalculate them.

Which course Montis uses

1. The course on the shared event (GPX, FIT or TCX added in Intervals.icu). This gives the full forecast described below.
2. A GPX file attached to your calendar event. This gives a simpler estimate (see Calendar GPX estimate).
3. The event location only. You get a pin on the map and no forecast.

How rides are forecast

Rides include road, gravel, MTB, cyclocross, track and handcycle courses. Montis tries these in order and uses the first one that works:

If none of these has enough data, there's no forecast.

How runs are forecast

Runs include road and trail runs. Montis uses:

Both are capped by the threshold pace in your Intervals.icu Run settings, so a forecast is never faster than your threshold allows. The cap is lifted when one of the matched runs was a race. Power is not used for runs.

Calendar GPX estimate

A GPX attached to the calendar event gets a simpler estimate. Montis splits the route into 500 m pieces and times each one from your threshold pace (runs) or FTP (rides), adjusted for gradient and distance. Optimistic and Conservative are a fixed range either side of Realistic. This estimate does not use your two-year history, so for the best forecast use a course on the shared event.

Set it up

1. In Intervals.icu, open your race and add the course with Add Courses (GPX, FIT or TCX). Or attach a GPX to the calendar event.
2. Check your sport settings in Intervals.icu: threshold pace for running, FTP and a power curve for cycling.
3. Open Readiness and pick the race. The forecast appears under the course map once the course has loaded.

---

Race Readiness Governance

Montis separates the underlying race metrics from the final readiness judgement.

The Readiness Governance block determines how event form and taper constraints should modify the interpretation of the athlete's current state.

The main fields are:

Event TSB

Montis estimates CTL and ATL at the target event and derives:

Event TSB = projected CTL − projected ATL

This represents projected form at the event rather than today's form.

The ADE uses the projected event state rather than blindly relying on raw calendar CTL/ATL values.

For example:

Projected CTL: 67.15
Projected ATL: 66.83

Event TSB = +0.32

---

Target TSB Range

Some event profiles define an expected TSB range.

For example, an FTP / TT-oriented event may use:

Target TSB: +8 to +18

The event profile can also define other desired conditions such as:

NDLI: low
WDRM: low

and durability expectations.

These targets describe the desired race-state context, not universal thresholds for every event.

---

Form Status

Projected Event TSB is compared with the event's target range.

Montis resolves one of three form states.

too_fatigued

Event TSB is below the target range.

Example:

Event TSB: +0.32
Target:    +8 to +18

→ too_fatigued

This can add:

TSB below event target

as a limiting factor.

target_range

Projected Event TSB is inside the event target range.

This indicates that projected form is aligned with the target.

too_fresh

Event TSB is above the target range.

This does not automatically mean "better".

Excessive unloading can leave the athlete very fresh while reducing useful race-specific stimulus.

This is why Montis can recommend controlled sharpening rather than simply continuing to reduce load.

---

Taper Governance

Only A races get taper governance.

When an A race is inside the active taper window, ADE compares its projected race-day form with that race's own form target, together with the direction of the planned training load. A race with no form target (for example a run with no distance set) gets no form check.

This produces a separate taper_governance state.

Too fatigued + increasing load

Form: too_fatigued
Load trend: increasing

Montis can resolve:

taper_load_conflict

Meaning:

The athlete is projected to arrive below the desired form range while the calendar is still adding load.

Recommended response:

reduce planned load and prioritise recovery.

Target form + increasing load

Form: target_range
Load trend: increasing

Montis can resolve:

taper_load_risk

The athlete is already projected to reach the desired form range, so additional load risks creating unnecessary fatigue.

Recommended response:

retain only short race-specific openers and avoid adding fatigue.

Too fresh + increasing load

Form: too_fresh
Load trend: increasing

Montis can resolve:

taper_sharpening_required

This is an important exception.

If projected freshness is above the target range, controlled race-specific work may be appropriate rather than further unloading.

Recommended response:

retain controlled sharpening while avoiding excess endurance volume.

Too fresh without increasing load

Montis can resolve:

freshness_above_target

Recommended response:

retain controlled openers rather than continuing to unload.

---

Phase Governance

Race readiness is also checked against the phase Montis believes is required.

The governance output therefore contains:

phase_required
phase_alignment
resolution

phase_required

The phase that should currently govern the plan, such as:

• Build
• Base
• Recovery
• Taper

phase_alignment

Whether the current/planned training direction agrees with that requirement.

Typical states can include:

aligned
misaligned
aligned_with_sharpening
underload_watch

For example, increasing load during a required Recovery or Taper phase is normally considered misaligned.

There can be a taper exception when controlled sharpening is justified by excessive projected freshness.

resolution

This indicates whether the original ADE directive was allowed to stand or whether higher-level phase/event governance constrained it.

A useful way to think about this is:

ADE = what the athlete can tolerate

Phase/Event Governance = what the athlete should do

Phase and event governance therefore sit downstream of the base ADE decision.

---

Limiting Factors

Montis exposes the reasons preventing a completely clean race-readiness state.

Examples include:

• TSB below event target;
• TSB above event target;
• taper load conflict;
• durability drift;
• event-specific system mismatch;
• insufficient planned volume.

These are intentionally shown separately so that a readiness result can be explained rather than presented as an unexplained percentage.

---

Readiness Labels

The governance layer can return several final labels.

READY

No higher-level taper conflict requires the readiness label to be qualified.

CONDITIONALLY_READY

The athlete may have acceptable underlying capability, but a current taper/load conflict means the plan is not fully aligned.

READY_WITH_SHARPENING

The athlete is broadly ready, but projected freshness is above the desired event range and controlled race-specific sharpening is appropriate.

The UI must not reduce this to plain READY.

The readiness score itself remains unchanged; the governance label explains how that score should be interpreted.

---

Example

For the Granfondo San Gottardo example:

Event: Granfondo San Gottardo
Priority: A
Days to event: 5
Training bias: FTP
Taper state: taper

Projected CTL: 67.15
Projected ATL: 66.83
Projected Event TSB: +0.32

Target Event TSB: +8 to +18

Therefore:

Form status: too_fatigued
Limiting factor: TSB below event target

Montis also detects:

Durability drift

as another limiting factor.

The complete readiness assessment therefore does not say simply:

"TSB is +0.32, therefore you are not ready."

It says:

Projected form is below this event's target range, durability is also a limiting factor, and those constraints must be interpreted together with current phase, planned load and taper governance.

---

Readiness Score vs Readiness Governance

These should not be confused.

Readiness Score   summarises the underlying event-readiness dimensions shown on the page.

Readiness Governance   determines whether projected form or taper conditions require that readiness to be qualified or constrained.

This is why Montis can legitimately show strong individual components such as:

• Neural Readiness: READY
• Durability: ADEQUATE

while the overall event assessment remains constrained by:

• projected form;
• insufficient planned volume;
• taper quality;
• event-specific system alignment.

The final question answered by Readiness Governance is therefore:

"Even if the athlete has the capability to race, is the current training trajectory actually preparing them to arrive at the event in the right state?"

---

Important implementation note

A readiness governance label such as READY should not be interpreted as meaning that every event-form target has been met.

The event object can still expose unresolved constraints through:

• form_status;
• limiting_factors;
• projected Event TSB;
• target TSB range;
• phase alignment;
• taper governance.

For example, an event may currently show:

readiness_label: READY
form_status: too_fatigued
event_tsb: +0.32
target_tsb_range: +8 to +18

In that case, the readiness label and the event-form constraints must be read together.

The limiting factors are part of the explanation of the readiness state, not secondary information to ignore.