I travel a lot and am often in other time zones. While I can answer the question of whether I was on a plane, is there a travel mode to take into account time zone changes? For example, going from New York to Madrid is a 6 hour time zone shift. How does that get figured into the metrics or is there a way to effectively reset the time zone?
1 Like
Hi @astroman, the WHOOP app doesn’t have a dedicated “travel mode,” but it does factor in time zone changes automatically by analyzing your local device time and your sleep/activity patterns.
Here’s how it works: When you travel and your phone’s time zone updates, WHOOP uses your new local time to log sleep, strain, and recovery. So if you fly from New York to Madrid, your metrics will shift to Madrid time as soon as your phone does.
We’re continuously working to improve this experience across all WHOOP metrics. If you have any specific feedback to share from a personal travel experience, definitely let us know!
Does this mean that if i have my country of residence in my profile but live in a different time zone, my whoop will use the time zone where i currently reside in my sleeps and other time-related functions?
I believe it syncs with your phone. The only time it gets a bit screwy is during active travel.
Hi, it would be nice, if one can add in the log / journal, that one was travelling and went into different timezone as this has an impact on sleep etc.
Also would be nice, if one could record how long flight was as an activity.
Will you bring such features in the future?
Thanks, Annike
2 Likes
I’ve had the same issue. I live in Norway and traveled to Bali for three weeks in June. Despite the time zone change, my WHOOP device stayed on Norway time the entire trip. As a result, my data—especially sleep consistency—was completely thrown off. It dropped to 44%, and I didn’t realize it happed until last week. Unfortunately, there’s no way to correct the data, it sucks. Even tried to make a ticket.
WHOOP team @Durkin, please consider introducing a dedicated travel feature. Frequent travelers like me are a big part of your target audience, but every time I change time zones, my data gets disrupted. For example, last month I traveled from NYC to London twice, and my metrics became inaccurate for days. This undermines the core value of WHOOP (accurate, consistent insights) and makes it harder to justify the subscription. Fixing this would greatly improve the experience for members who travel often and help keep us engaged long-term. Thanks for the consideration.
3 Likes
Couldn’t agree with this more - I also travel frequently and this messes up my data, especially sleep consistency. If I travel to a different time zone for five days it nukes my sleep consistency for 5-6 days on each end of the trip, so my data are impacted for nearly two weeks. There needs to be a smarter way for the app to handle time zone changes…
2 Likes
First off, hey Durkin! Second, glad this is getting some attention. While what you describe is exactly how the app should handle time zone changes, it doesn’t correct for the change when calculating sleep consistency because it applies the new time zone to all historical sleep and wake times. For example, if I normally go to bed at 10pm and I fly to a new time zone, say +6 hours, and keep my bedtime consistent at 10pm, the app thinks my usual bedtime based on previous data is 4am and calculates sleep consistency based on that. This seems like it would be so simple to fix!
2 Likes
Hi, I’m having the same problem. I’ve returned from US to Europe and have been awake for about 36 hours. I’m actually not jetlagged, but Whoop is totally out of sync - it tells me I had a nap of 7 hours and a sleep of 1.5 - so completely the other way around. My recovery is red, despite feeling quite well rested and ok. Now it tells me to go to bed a 7:30 PM… I thought it will eventually re-syncronize, but it look like he’s totally astray. How did you solve for such things? I have Whoop Life since about a month ago. Thanks
1 Like
Exactly this! Also I did not sleep on the plane so it just didn’t log my arrival day as separate day (no sleep debt etc.).
Yeah second this. This is the exact problem