How to Adjust Nutrition Based on HRV for Recovery
Why the disconnect between wearable data and nutrition tracking hinders recovery, and how a closed-loop system automates your fuelling based on real-time physiological strain.
Why the disconnect between wearable data and nutrition tracking hinders recovery, and how a closed-loop system automates your fuelling based on real-time physiological strain.
Look at your phone's home screen. In one folder, you have an intelligence engine built on millions of data points, tracking your heart rate variability, respiratory rate, and sleep architecture down to the minute. In another folder, you have a digital ledger from 2014 asking you to scan a barcode.
This is the structural deficit in modern endurance training. We measure the strain with absolute precision. We fuel the engine using static math.
Recovery is the rate-limiting feature of human performance. You cannot out-train your ability to adapt, and you cannot adapt without matching substrate to strain.
A modern wearable produces more physiological data in a single day than most athletes generated in an entire career a decade ago. The sensors are medical-grade. The algorithms are trained on millions of nights. The problem is not the signal.
The problem is where the signal ends up.
Apple Health, Whoop, Oura, Garmin, and Polar all expose this data. They all ship beautiful dashboards. None of them can tell your kitchen what to do about it. The signal ends in a graph.
Every control system is either open loop or closed loop. An open loop produces a reading and stops. A closed loop takes the reading, acts on it, and measures the response. Most consumer health tech is open loop by design. You are supposed to be the controller.
In the open loop, the signal dies in your dashboard. You scroll, nod, and decide to "take it easy today." What that means for your protein distribution, your carb timing, or your evening hydration is left entirely to intuition. That is not a system. That is a mood.
The flaw in a calorie-first model is that every session is treated as a single lumpy number. It isn't. Two sessions that burn the same total energy can leave behind completely different biochemical debts.
The Zone 2 ride leaves a 12-hour recovery window. It is forgiving. A modest protein meal, normal carbs, and you are ready again. The threshold session leaves a 48-hour window. It demands immediate carbohydrate replenishment, elevated protein through the day, and a pre-sleep casein dose to arrest the overnight drift into negative nitrogen balance.
Your food log treats both identically. Your wearable can already tell the difference in the first ten minutes of the session.
Of the ten or so channels a modern wearable produces, three move the plan every single day. Each one maps to a concrete kitchen decision.
None of these adjustments require a human to read a graph. None of them require you to know what cortisol is doing. The engine reads the overnight numbers, does the math, and the plan updates before you finish your coffee.
Fluid replacement is the cleanest example of the gap. The clinical consensus for post-exercise rehydration is 1.5× the fluid volume lost (Shirreffs et al., 1996), because the kidneys keep excreting urine while you drink. If you lose 1 kg of water weight in a hot session, you need roughly 1.5 litres to restore homeostasis.
Static nutrition apps give you an arbitrary daily goal, usually around 2.5 litres. They don't know you ran in 28°C heat. They don't know your sweat rate. They don't know you finished at 19:00, which means that 1.5 litres needs to land between 19:00 and 21:00 if you want to protect deep sleep. Drink it at 22:00 instead and the nocturia wrecks the recovery you just trained for.
This is not complicated math. It is simply math that nobody has bothered to automate, because the two apps that would need to talk to each other do not.
Picture a Tuesday. You log a 55-minute threshold ride at 17:30, finishing at 430 watts average, burning 780 kcal. Your Whoop flags it as a strain score of 17.2. You wake up Wednesday and HRV is 14% below baseline. Sleep efficiency came in at 82%.
A standard nutrition app sees: yesterday you earned 780 extra calories, today you have your normal 2,400 kcal target.
KEXBI sees the same data and runs three responses in parallel. Tuesday's post-session window gets a 70g fast carbohydrate plus 30g whey top-up. Dinner carbs get lifted by 40g and front-loaded to low-GI to pull cortisol down. A 40g casein dose lands 90 minutes before bed. Wednesday's breakfast swaps the oats for a protein-and-fat combination to blunt the insulin resistance spike that always follows fragmented sleep. Hydration targets rise by 600 ml for the day and finish by 20:30.
Same athlete. Same wearable. Same calorie target. A completely different recovery trajectory by Thursday morning.
The wearable industry solved sensing. It did not solve acting. Every major consumer device now produces data of a fidelity that would have required a sleep lab twenty years ago, and every consumer nutrition app treats that data as if it did not exist.
Every wearable on the market has solved sensing. KEXBI solves what to do about it.