What readiness is — and why we ask
Readiness is a short, daily snapshot of how prepared your body and mind are for training. N+One combines subjective check-ins with objective signals (when you connect a wearable) and your recent training-load profile to produce a readiness score and trend. That score is used by the AI Coach and the app’s planning logic to adapt the next session — not to punish a missed ride. The goal: make the next session the right session.
What goes into a readiness score
N+One blends two inputs:
- Subjective check-in answers you enter each day (simple, quick inputs about how you feel).
- Physiological and behavioural data from connected devices when available (sleep, HRV, resting heart rate, strain/recovery metrics).
On the technical side the Readiness page uses recent readiness and training-load time series (roughly the last ~90 days in page code paths) and your training-load profile (CTL / ATL / TSB) to put a single day’s score in context.
How to complete a daily check-in (what to expect)
- Aim to complete the check-in once per day, ideally soon after waking and before your first ride. This gives the cleanest baseline for HRV and resting heart rate comparisons.
- The check-in is intentionally short. Typical entries ask about how you slept and how you feel (energy/fatigue), plus any acute illness or soreness that might affect training.
- If you use a compatible wearable, physiological metrics (sleep duration/quality, HRV, resting heart rate, strain/recovery) will be combined with your answers automatically when the wearable has recently synced.
Note: N+One’s exact form layout may change in the Beta app. The important rule is consistency — try to answer the same way each morning so trends are meaningful.
Wearables and integrations: WHOOP and Garmin
N+One supports several device integrations. For readiness specifically:
- WHOOP: WHOOP sync can supply strain, recovery, and sleep data that N+One uses to shape readiness scores.
- Garmin: Garmin sync provides activities plus health metrics (sleep, HRV, resting heart rate) that contribute to readiness and the app’s training-load model.
Connect devices from Settings → Integrations (Device Integrations) at /settings/integrations. On that page you can see connect/disconnect controls, sync status, and last-sync times.
Important notes about other integrations:
- Oura Ring is visible on the integrations page with "full integration coming soon" — it is not yet active for full sync.
- Zwift appears in a workout-upload card; the page copy says "full integration coming soon" for structured indoor workout upload intent.
- Wahoo and Garmin both support uploading planned workouts back to device platforms when you enable that behaviour; that feature is listed on the Integrations page.
If an OAuth connection fails, the integrations page can surface return query messages (for example: oauth_failed or whoop_profile_failed). Reconnect or check the message shown after the OAuth flow.
Where readiness appears in the app
- Readiness page (/readiness): daily scores, history, and the readiness time series. Use this page to review trends and how the app interprets recent sleep, HRV, and load.
- Training calendar (/training): readiness context is used behind the scenes to adapt planned sessions. The calendar still shows scheduled and completed workouts; when a planned session matches a completed ride the UI deduplicates the entries so you see the completed activity with its planned context.
- AI Coach (/coach): the conversational coach uses your profile, recent data, and readiness to give session-level advice and adjustments in real time.
If you’re early in setup and haven’t finished onboarding, opening the app will redirect you to /onboarding where the chat-based profile capture and integrations step help get readiness and device sync configured.
Best practices to get reliable readiness signals
- Sync daily: open the app or force a sync from the wearable app before checking in. Connected WHOOP or Garmin data will populate without manual entry when sync is current.
- Be consistent with timing: answer the check-in at a similar time each day (morning is best) to reduce noise in HRV and resting heart rate comparisons.
- Keep a short note of acute events: illness, travel, heavy alcohol, or injury — these explain sudden drops and help the AI coach adapt.
- Don’t overreact to single-day swings: readiness is more useful as a pattern across several days; N+One uses ~90 days of recent history to put short-term scores in context.
How readiness changes your plan (plain language)
- If readiness is low, the coaching logic will favor lower-intensity or recovery-focused options that still preserve progression. The plan adapts; it doesn’t mark sessions as failures.
- If readiness is high, the coach can keep or increase stimulus in a controlled way that respects your training-load profile (CTL / ATL / TSB).
This is the practical expression of N+One’s adaptive approach: the plan is dynamic so your training dose follows biology, not a rigid calendar.
Troubleshooting and common questions
- My wearable isn’t showing data: confirm the device is connected at /settings/integrations and check the wearable app’s last-sync time. OAuth errors sometimes appear after a failed return; try reconnecting.
- I answered the check-in but the score didn’t update: the app requires network to record new syncs and to run the cloud model. See /offline for cached behavior — previously viewed pages may work, but new sync needs a connection.
- What if I miss a day? Missing one check-in won’t break your plan. The coach uses recent trends and will adapt once new data arrives.
Privacy and data
Readiness inputs and device data are part of your training profile. For details on how we handle personal data see /privacy.
Learn more
- Integrations and device setup: /settings/integrations
- See your readiness dashboard: /readiness
- How HRV and readiness fit together: /knowledge-base/heart-rate-variability-for-cyclists-a-complete-guide-to-hrv-monitoring-and-interpretation
- Practical training-readiness guidance: /knowledge-base/training-readiness-optimize-performance
- How N+One uses load and readiness to adapt plans: /knowledge-base/understanding-training-load-ctl-atl-tsb
If something still looks off after checking connections, open Settings → Help & Support (/settings/support) to file a report or read the FAQ entries related to integrations and profile setup.
The N+One Beta tag in the header means we’re refining this flow. Your consistent check-ins and device syncs help the AI Coach give the right next session — because the most important ride is always the next one.
