Hunger & Energy Management

This content is for informational purposes only and does not constitute medical or nutritional advice. Speak with your health professional before starting this protocol.

Note: Hunger and low energy are expected during an active sprint. The tactics in this article address the most common protocol-related causes. If you experience severe dizziness, fainting, chest pain, or symptoms that feel disproportionate to the protocol, stop and seek medical attention.

This page also covers energy management — both hunger and low energy arise from the same adaptation process and are addressed together here.

If You're Hungry Right Now

Hunger during a sprint is expected. It is not a signal that something is wrong or that you should stop — it is a normal part of the protocol.

But there are things you can do in the next ten minutes.

Immediate tactics:

  • Drink water — a full glass, now. Thirst and hunger signals overlap in the hypothalamus. Hunger that disappears after water was never food hunger.
  • Have a bouillon or broth. Hot, salty liquid is one of the most effective acute hunger suppressants during a low-carb sprint — warmth, sodium, and volume together.
  • Eat your vegetables first. If a meal is coming in the next hour, eat a large volume of raw or cooked vegetables immediately. Physical stomach distension triggers satiety signals before the food has been absorbed.
  • Wait 20 minutes. Ghrelin (the hunger hormone) rises in waves. The peak of a wave lasts roughly 20 minutes before it subsides — even without eating. If you can outlast the wave, the urge often drops significantly on its own.
  • Distract deliberately. Go outside, begin a task that requires focus, call someone. Hunger is significantly amplified when you are sitting still with nothing to do.
  • Coffee or tea. Caffeine is a real appetite suppressant. A black coffee during a hunger spike is a protocol-consistent tool. Limit caffeine after 2 PM to protect sleep.

Why You're Hungry: The Ghrelin Wave

Ghrelin is your primary hunger hormone. It rises in anticipation of your usual mealtimes, peaks for approximately 20 minutes, then falls — regardless of whether you have eaten. This is why hunger is worst before your usual meal times and why waiting it out works.

During caloric restriction, baseline ghrelin is chronically elevated. Your body produces more of it to signal urgency. But the wave pattern persists. The peak is survivable. It will pass.

What blunts ghrelin long-term:

  • Adequate protein at every meal (protein suppresses ghrelin more effectively than carbohydrates or fat)
  • Adequate sleep (sleep deprivation elevates ghrelin significantly — see Sleep & Recovery)
  • Electrolytes (sodium in particular — see Hydration & Electrolytes)

Hunger That Isn't Going Away: Diagnose Before You Eat

Persistent, intense hunger that doesn't respond to the tactics above is usually one of four things:

1. You're under-eating protein Protein is the most satiating macronutrient. If your protein target isn't being met — whether from skipping meals, choosing lower-protein options, or misjudging portions — hunger will be disproportionately high. Check your protein log.

2. You're dehydrated Three litres of water per day during an FLS sprint is the protocol target. Many people manage 1–1.5 litres in practice. At that level, persistent "hunger" is often dehydration. The signals are indistinguishable without awareness.

3. You're sleep-deprived One night of poor sleep measurably increases ghrelin and reduces leptin. If you're getting less than 6 hours, hunger will be significantly harder to manage than the protocol assumes. Sleep fixes the problem better than any food strategy.

4. It's refeed timing The FLS protocol includes scheduled refeed days specifically because cumulative hunger becomes unmanageable for many people without them. If your next refeed is several days away and today is genuinely difficult, check whether an earlier refeed is appropriate (use the app's guidance, or refer to Refeeds for early-refeed criteria).

If You're Low on Energy Right Now

Low energy on the Habits scale (1–2, or exhausted) during a sprint has a specific pattern. Knowing where you are in it helps.

Days 3–7 of your first sprint: the adaptation dip

If you're in the first week of your sprint, low energy is very likely carbohydrate adaptation. Your body has been running on glucose. It is now transitioning to fat oxidation. This transition takes 3–7 days. During this window, energy will feel unreliable — sometimes flat for hours, sometimes normal. This is temporary and does not require intervention beyond electrolytes and patience.

What makes the adaptation dip worse: not enough sodium. The single most common cause of severe early-sprint fatigue is sodium depletion from the low-carb-driven insulin drop. Increase sodium immediately — bouillon, salt on your food, electrolyte drink. Most people feel better within 2 hours.

Beyond Day 7: energy should stabilise

If energy remains consistently low after the first week, investigate:

  • Electrolytes. Sodium, potassium, and magnesium — all three matter. Magnesium deficiency causes fatigue and poor sleep independently of the caloric deficit.
  • Sleep. Caloric restriction directly reduces sleep quality for some people, particularly in weeks 1–2. See Sleep & Recovery for protocol-specific strategies.
  • Training volume. If you've maintained pre-sprint training intensity and frequency (HIIT, heavy lifting, long runs), this is the likely cause. The FLS protocol recommends 2–3 resistance sessions per week at moderate intensity, plus daily walking. Anything beyond that without sufficient fuel will produce exactly this kind of fatigue.
  • Protein. Amino acids are also a fuel source. Insufficient protein leads to more muscle breakdown for energy, which is metabolically inefficient and exhausting.

What Low Energy Doesn't Mean

It does not mean the protocol has stopped working. It does not mean you need to eat more carbohydrates. It does not mean you should end the sprint.

The most common cause of persistent low energy beyond day 7 is an electrolyte problem or a training problem, not a calorie problem. Solve those first.

One practical check: Log the last three days in the app. Look at whether protein targets are being met, whether you've hit your water target, and what your sleep score has been. The answer to most persistent energy problems is visible in that data.

When to Consider an Unplanned Refeed

The protocol's guidance for an unplanned refeed includes:

  • Energy consistently 1 on the scale for 3+ days after week 1
  • Training performance down more than 15–20% from baseline
  • Persistent sleep disruption correlated with the sprint
  • Inability to function at work or in daily tasks

If these apply, an unplanned refeed is the correct response — not pushing through. Refer to Refeeds for how to execute it.