Readiness and daily check-in

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.