SlopeReady

Training planning · 8 min read

Adaptive training plan: why the next seven days stay stable

An adaptive plan should not swap tomorrow's session every morning. In SlopeReady, populated days from today through today + 6 are protected from automatic regeneration. System-generated days from today + 7 through today + 27 can use new information unless you changed them yourself or approved a Coach proposal.

Twenty-eight planning cards in four rows in an alpine room: the first seven sit under a fixed clear rail, while later cards hang from movable magnets. A small ski-trip marker is attached to the final card.
On this page

The coming week needs enough stability for you to reserve time around it. The later plan needs room to move because new training and recovery information will arrive before you reach those dates.

Seven days is not a magic training rule. It is a clear SlopeReady product boundary: the nearby calendar stays predictable while the more distant, system-owned part of the plan can adapt.

One plan, two time zones

The SlopeReady plan covers 28 days. This boundary governs automatic regeneration only. You can still make an explicit change to any current or future day.

Today through +6

Stable week

A populated day survives refreshes and daily rollover unchanged. Tomorrow still shows the session you made time for.

A genuinely empty day that was not set as rest may be filled.

+7 through +27

Adaptive horizon

System-generated days may be rebuilt during daily rollover using current training and recovery context.

A day you edited or applied through a Coach proposal stays as you set it.

Sources: How SlopeReady works, SlopeReady data sheet.

How the same 28-day plan behaves

These four cases expose the details that broad promises about an “adaptive plan” tend to skip.

Strength is scheduled tomorrow.

Automatic update
New sleep or readiness data arrive.
Result
The saved session stays. A daily view may explain today's context without rewriting the plan.

A system-planned endurance session sits 12 days away.

Automatic update
The calendar rolls forward the next day.
Result
That distant day may be rebuilt using the context available then.

You move a session 18 days away to Friday.

Automatic update
The adaptive horizon is rebuilt later.
Result
Your explicit Friday edit remains.

A day in the coming week is empty after a long absence.

Automatic update
SlopeReady rebuilds the current window.
Result
The empty, unauthored day may be filled while existing commitments remain untouched.

Four distinctions worth checking

A useful adaptive plan answers these questions without hiding the rules.

Refresh or change?

New data can update an explanation and the distant plan. Replacing a saved near-term session is a separate action.

Automatic or explicit?

A refresh comes from the system. Moving, replacing, or applying a Coach proposal is a deliberate edit.

Empty or rest?

An unfilled day may be a gap. A rest day you set on purpose is a decision that should survive.

Suggestion or saved plan?

An explanation or easier option for today does not alter the lasting calendar. A plan mutation needs a visible action.

Audit any adaptive training plan in four steps

Use these questions with any training app.

  1. Mark the protected dates

    Find which sessions cannot change merely because you open the app, sync data, or receive a new measurement.

  2. Find the adaptation boundary

    Check the first date the system may rebuild and whether it shows a reason.

  3. Test one manual edit

    Move a distant session, refresh the plan later, and confirm that your chosen date remains.

  4. Check consent

    A lasting Coach change should show the exact edit before it reaches the plan.

What the research supports, and what it does not

A systematic review and meta-analysis of 13 randomized trials found a small overall effect in favour of reinforced implementation intentions for physical activity. This supports the practical idea of connecting an intention with a time and situation.

The study populations varied widely. The review did not test adaptive training software, calendar stability, or ski preparation. It therefore does not identify seven days as an optimal buffer or show that more automatic changes produce better training.

Sources: Silva et al. (2018).

What SlopeReady does

SlopeReady keeps a rolling plan from today through today + 27. During daily rollover, populated days from today through today + 6 remain unchanged. Only system-generated days from today + 7 through today + 27 may be recalculated.

Your edits and Coach changes you approve are stored as explicitly authored. That includes a rest day you chose. Automatic regeneration cannot replace those decisions.

SlopeReady does not record workouts, live heart rate, GPS, or ski runs. With your permission, it reads available Apple Health data, interprets the context, and helps you manage the plan.

Take the next decision further

Feedback or a static plan See when adaptation adds more value than an unchanged PDF. Read the comparison Readiness with incomplete data Separate today's estimate from the completeness of its inputs. Understand confidence Training load without jargon See what the number compares and what it cannot predict. Interpret training load Start with a short history Choose a cautious starting point when training or sleep data are thin. Choose a starting point First questions for the AI Coach Begin with one concrete session or planning decision. Choose a question How SlopeReady works Follow the data path, 28-day plan, and confirmation step. Open the product guide

Discuss a change without giving up control of the calendar.

SlopeReady reads permitted Apple Health data and keeps a visible 28-day plan. The AI Coach can use your saved plan, recent sessions, and available recovery context to propose a change. It becomes part of the plan only after you approve it.

See how SlopeReady works

The seven-day buffer is a SlopeReady product decision, not a universal physiological threshold. Training data do not replace assessment of pain, acute symptoms, or medical concerns.