I am not sure, how the WHOOP 5.0 steps & calories tracking algorithm works.
What I have observed is that the steps & calories count seem to be more than double of what my apple watch used to indicate for the same use case, before my switch to WHOOP 5.0.
I believe its a over estimating the steps taken / calories burnt (e.g. for a normal daily commute / office / home walks).
Please could you check and kindly suggest best way forward on this topic & obtain realistic step/calorie count as my diet calorie consumption is quite dependent on the same.
Whoop data is a disaster! Totally unrealistic and unreliable. Various problems are known for months or even years and nothing happens. Instead of solving issues they keep on releasing new features that are in turned based on inaccurate data and metrics. Whoop there it is (not).
I’ve had my Whoop for 5 days and was hoping the calorie burn would calibrate. It hasn’t. It’s averaging ~1,500 kcal/day for me.
I consume ~2,600 kcal/day (logged in MyFitnessPal). If Whoop were right, that’s a surplus of ~1,100 kcal/day → ~7,700 kcal/week → over 2 lb/week of weight gain. That’s obviously not what’s happening.
Any basic BMR calculator puts my BMR around 1,500–1,600 kcal/day, which is further proof your estimate is way too low.
This is a shame because accurate calorie burn was the primary reason I bought Whoop—to maintain a slight deficit while still fueling my training. And it’s frustrating to keep getting the same canned responses from your team. This is a critical metric for people paying good money to monitor calories and performance. Whoop needs to fix this.
Since I did not hear from you on the above topic, I continued to use the device to check on device calibration / inaccuracy comments from other users across this forum. Below would be my thoughts/observations on the device / application performance, based 2 weeks + use case:
I do note that some background server based calibration is taking place in terms of step count & associated calories consumed. (though very hard to point out when & based on what factors)
One aspect I have noted is that any steps counted & processed after 12:00 AM at my location / time zone still gets clocked into previous day, until some switch over time threshold… Assuming the data is processed in the back end server (& not within the app / device), I am suspecting the switch over time threshold is defined by the backend WHOOP data processing server’s time zone (data & time) independent of the user’s device / app location / time zone (date & time). Hence some days show way too many steps and some other days show way few steps, which I believe may be further adding to the potential data inaccuracy.
Also Steps / Calories captured within WHOOP source data file feeding into Apple’s Health data app generally is either above or below the steps actually clocked in / processed by WHOOP application / server. (I did check the WHOOP source data entries within Apple’s health app)
There seems to be a huge impact on step count when the wristband is worn on the dominant wrist/hand vs the non dominant one. I believe, when worn on a dominant wrist/hand then devices seem to pick up all movements (even the ones not associated with walks/runs) e.g. movement captured while brushing teeth etc. I am not sure, if WHOOP’s backend data processing engine is actively differentiating / discounting for such normal functional movements when worn on a dominant / non-dominant wrist/hand.
I would very much appreciate WHOOP 5.0 teams comments/feedback on the above.