Sleep
Recovery context
Read the day before rewriting the week.
Capture how the client feels, keep readiness beside its evidence, and turn a changing pattern into a coach-owned next step.
Directional context. Coach-controlled decisions.
One evidence line
Recovery context that stays connected to action.
A daily log should be quick for the client, legible for the coach, and honest about what it can support. Keep the input, interpretation, trend, and follow-up in one line.
- 01
Capture
Make the daily check-in small enough to finish.
Log sleep, energy, soreness, stress, fatigue, hydration, and notes without turning Recovery into a long questionnaire.
- 02
Interpret
Show what shaped today’s readiness.
Keep the score beside its available signals, freshness, and missing context so the number never stands alone.
- 03
Trend
Separate one rough day from a direction.
Compare recent logs, sleep, and the weekly digest while treating sparse or stale data as incomplete evidence.
- 04
Respond
Bring the decision back to the coach.
Review the exact recovery day, save a date-specific note, send a manual nudge, or carry the concern into Daily Review.
Readiness with receipts
A score is useful only when its evidence stays visible.
Fitflux keeps the aggregate beside the signals that shaped it. Freshness, missing inputs, and degraded sources stay part of the reading instead of disappearing behind a confident number.
Self-report
How the client feels today.
Energy, soreness, stress, fatigue, hydration, and notes keep the client’s own experience in the picture.Training load
Recent work, not a generic warning.
Recent workout effort and time since training help frame recovery without claiming to prescribe the next session.Confidence
Fresh, stale, or partially available.
When a source fails or a signal is missing, the surface says so and keeps manual Recovery available.- Current-week Recovery log count
- Sleep, energy, stress, and soreness direction
- Previous-week comparison when enough data exists
- A building-baseline state when fewer than three logs exist
- Cautious guidance that never converts a trend into an automatic edit
Read the direction
One hard day is not automatically a new plan.
Compare recent logs with the previous week only when enough evidence exists. Missing days stay missing, sparse data builds a baseline, and the digest remains a prompt for review.
Recovery does not predict injury, diagnose a condition, or rewrite training by itself.
Coach-owned response
Turn the signal into the right size of follow-up.
Not every change needs a program edit. Review the exact day, preserve the coach’s reasoning, and choose between a light nudge and a broader Daily Review action.
Review the day
Keep the evidence attached to its date.
Open the recovery log that raised attention and compare its signals before writing a conclusion.Save a coach note
Preserve the thinking behind the next decision.
Draft, discard, and save a note against the selected recovery date without leaking it across clients or trainers.Follow up
Use a nudge when the next step is simple.
Send a manual recovery nudge or carry the concern into Daily Review when a broader coaching response is needed.Connected when useful
Bring wearable context in without taking manual Recovery away.
Oura can add recent sleep and recovery signals for supported clients. Connection failures stay local, retries stay explicit, and the core Recovery log remains available.
Connected data can enrich the picture. It does not become a silent prerequisite for logging or coach review.
Connected
Show recent wearable sleep and recovery context beside the client’s manual Recovery data.
Degraded
Keep available signals visible, explain what is missing, and offer a scoped retry.
Reconnect required
Name the connection problem without blocking manual logging or historical Recovery review.
Keep context close
See what changed. Decide what changes next.
Choose the platform plan that fits your active-client roster and bring Recovery into the same system as training, client follow-up, and Daily Review.
Join the waitlist