RISE's Energy Schedule guide says it uses recent sleep timing from phone-based tracking, a connected wearable through Apple Health on iPhone or Health Connect on Android, or manual entries. It describes a model that updates its estimated circadian timing as sleep records accumulate. Those are the provider's model and data-source descriptions, not a sensor-accuracy or alertness test by this review.
In the documented Energy tab, you can view and edit last night's sleep alongside today's energy schedule. Start there: check sleep and wake times and their source, correct an inaccurate entry, then inspect that date's predicted peak or dip. This identifies the native entry point; it is not a before-and-after chart observed in this review. The guide distinguishes timing from how energetic you feel: inaccurate sleep records and factors such as caffeine or medication can make the experience differ from the prediction. A peak label is not a measurement of your present alertness or clearance to drive or exercise.
For an older incorrect record, the reset guide gives Progress → Sleep Times → select the night; the editing guide then describes adjusting sleep time, adding awake time where needed and choosing Save. Editing is limited to the past fourteen days. Check the intended date and entered times after saving, then review the sleep-debt view and energy schedule separately. Correcting a record does not prove that the resulting prediction matches how you feel. These are documented routes, not before-and-after results observed here.
For travel, RISE's separate help article warns that the Energy Schedule can temporarily differ from the new local clock while its estimate adjusts. Keep the trip date and time zone with any comparison; changing a clock label is not evidence that the body has adapted. A manual target-difference worksheet below cannot recreate that circadian model.
Diagnose a surprising schedule before trusting it
| Check | Why it matters | What it cannot establish |
|---|
| Last night's sleep and wake times | A wrong imported or manually entered interval changes the model input. | Whether the corrected forecast matches actual alertness. |
| Older record within the past fourteen days | The documented edit route can correct a specific night. | That nights outside the edit window can be changed there. |
| Travel time zone and local date | Clock changes can shift the displayed schedule while adaptation continues. | That a predicted peak makes driving or exertion safe. |
Record the original and corrected times if you compare views. We did not connect a wearable or observe the before-and-after schedule, so this is a verification route rather than an accuracy result.