How to Log Fasting Days

Logging fasting days correctly prevents the most common fasting-tracker error: a day that shows 0 kcal logged because you “didn’t eat” when you actually consumed 600–800 kcal in your eating window. Zero is not accurate. Zero corrupts your weekly average. And a corrupted weekly average makes your calorie data useless for assessing whether your fasting protocol is working. This guide covers the correct CalEye workflow for intermittent fasting (16:8, 5:2, OMAD) and extended fasting protocols.

The tracking goal on a fasting day is the same as any other day: log everything you consume that has calories. The difference is that fasting days compress consumption into a narrower window and may include a planned restriction day (5:2 protocols). CalEye’s fasting mode handles the timing automatically — you set your eating window, and the app marks anything consumed outside it as outside the fasting window for your records.

Setting Up Your Fasting Protocol in CalEye

Before logging your first fasting day, configure your fasting protocol. This takes 2 minutes and changes how CalEye displays your daily log.

1. Tap Profile → Nutrition Setup → Fasting Protocol

2. Select your protocol type:

   • Intermittent Fasting (16:8, 14:10, 18:6): Set your eating window start and end times
   • 5:2 Protocol: Designate which two days of the week are restriction days; set your restriction calorie target (typically 500–600 kcal)
   • OMAD (One Meal a Day): Set a 1-hour eating window
   • Custom: Set any window you’re using

3. Toggle Show Fasting Timer ON — this displays a countdown to your next eating window opening on the home screen

Once configured, CalEye’s daily log view shows a visual fasting/eating window timeline. Meals logged within the eating window appear in green. Anything logged outside the window appears in amber (CalEye still counts the calories — it just marks them as outside-window for your review). For a deeper look at structuring your eating window, our guide on setting macros inside an intermittent fasting window covers the per-meal protein minimums that matter most in a compressed schedule.

This visual separation matters more than it sounds. The most common fasting data corruption comes from pre-eating-window coffees with milk, post-window late-night snacks, and “just a few bites” that get mentally categorized as “not eating” but are visibly outside the window in the app. The amber flag makes these exceptions impossible to ignore — and ignorance is how fasting protocols silently fail without you realizing it.¹

The choice of eating window start time has metabolic implications beyond simple calorie tracking. Research on time-restricted eating consistently shows that earlier eating windows — 8 AM to 4 PM or 7 AM to 3 PM — produce better glycaemic and insulin outcomes than equivalent windows shifted later in the day, even when total calorie intake is identical. If you currently fast from noon to 8 PM, consider whether shifting your window two to three hours earlier would align better with the circadian peak in insulin sensitivity that occurs in the morning hours.²

What to Log During the Fasting Window

Not everything consumed during a fast is calorically significant. Here is what to log and what to skip, with the reasoning behind each category.

Log these:

• Coffee with milk or creamer (any dairy addition has calories — 30 ml of whole milk adds approximately 19 kcal)
• Bulletproof coffee (butter and MCT oil in coffee — a tablespoon of each adds 230–270 kcal, which is nutritionally equivalent to a small meal)
• Any sweetened beverage, including those sweetened with sugar alcohols, which carry 2–2.6 kcal/g depending on the polyol type
• Bone broth (30–50 kcal per cup, plus sodium; marketed as a fasting aid but technically caloric)
• Any food, even small amounts — a handful of 20 almonds adds approximately 140 kcal and contains fat and protein that stimulate insulin secretion

Skip logging (no meaningful calories):

• Black coffee with no additions (fewer than 5 kcal per cup)
• Plain tea (herbal, green, black) with no additions
• Plain sparkling or still water
• Electrolyte tablets with no sugar (check label for 0 g carbohydrates — many electrolyte products contain small amounts of dextrose)

The metabolic question of what “breaks” a fast — whether anything that raises insulin, however slightly, interrupts the fasting state — is separate from the calorie-tracking question. For calorie-tracking purposes the rule is simpler: if the label shows calories, log it. The precise threshold at which a caloric intake interrupts autophagy or ketosis is not something a calorie tracker can or should assess.¹

Logging the Eating Window

Log meals in the eating window exactly as you would on a non-fasting day — photo log, barcode scan, or recipe entry. There is no difference in the logging method. The fasting window changes the timing structure; the eating-window logging is identical to standard daily logging.

For 16:8 and similar protocols: You are typically logging 2–3 meals within the eating window. Log each meal as it happens. CalEye’s daily total accumulates as normal. The practical challenge with 16:8 is preventing the compressed window from becoming an excuse for larger portions — research has consistently shown that some people unconsciously compensate for the shorter eating period by eating more calorie-dense food during it, partially or fully erasing the calorie deficit the fasting window was intended to create.³ Tracking is the check on that compensation. Our 16:8 fasting calorie tracker view shows exactly how CalEye displays the eating window timeline.

For 5:2 restriction days: Your target is 500–600 kcal for the day. Log all food carefully. CalEye shows a restriction-day budget bar in a distinct color (orange versus the normal green). When you approach 500 kcal, the bar turns amber. When you hit the limit, it turns red. The psychological discipline required on restriction days is substantial — hunger is real, and the temptation to approximate rather than log precisely is strongest when you are most food-focused. Log before eating, not after, to give yourself real-time visibility into your remaining budget.

For OMAD: You are logging one meal, typically a large one covering a full day’s nutrition in a single sitting. Log this as a multi-item meal session: add each dish as a separate item within the same meal log. Tap + Add item to stack dishes within one meal entry. The challenge with OMAD is that large meals are harder to estimate accurately — a single sitting of 2,000 kcal spread across multiple dishes has more portion-estimation error than three 650-kcal meals logged separately. Use the photo log for each dish rather than trying to recall the full meal after the fact.

Logging Extended Fasts (24+ hours)

For fasts exceeding 24 hours — extended water fasts, dry fasting periods used in some religious practices, or supervised medical fasts — the logging protocol differs from daily intermittent fasting.

1. Set a fasting start marker in CalEye: Log Meal → Start Fast → enter the start time
2. Log only what you consume — water logs (CalEye can track plain water in ml for hydration monitoring), electrolytes, and any accidental or deliberate caloric intake
3. When breaking the fast, tap End Fast — CalEye records the fasting duration and marks the subsequent meals as “fast-break” meals in your log

Extended fasting carries risks that intermittent fasting protocols do not — including electrolyte imbalance, hypoglycemia in people on certain medications, and refeeding syndrome risk after fasts exceeding 72 hours. The logging structure described here should not substitute for medical supervision if you are undertaking extended fasting as a therapeutic intervention. What CalEye provides is a record of fasting duration alongside calorie data, which is useful for sharing with a healthcare provider reviewing your metabolic response.⁴

Refeeding after extended fasts should be gradual. The first meal after a 48+ hour fast should be small and low in refined carbohydrates — high carbohydrate refeeding after extended fasting causes a rapid insulin surge that drives potassium, phosphate, and magnesium into cells, lowering serum levels and potentially triggering cardiac arrhythmias in severe cases. Log the refeeding meals with the same care as the fast itself.

Reading Your Weekly Averages on Fasting Protocols

Weekly averages look low on fasting protocols — this is expected, not a data error. A 16:8 user eating 2,000 kcal in their eating window has the same weekly average as a standard eater consuming 2,000 kcal across three meals. The timing is different; the total is the same. The weekly average for a 5:2 user eating 2,000 kcal on five normal days and 500 kcal on two restriction days is: ((2,000 × 5) + (500 × 2)) / 7 = approximately 1,571 kcal/day — which is exactly the 5:2 design intent.

The most common misreading of fasting-protocol data is comparing daily totals rather than weekly averages. A restriction day showing 500 kcal logged does not mean you are in danger of starvation — it means the protocol is executing as designed. In CalEye, tap Progress → Weekly Summary to see the 7-day average calorie intake alongside a color-coded view of which days were restriction days, normal days, and any days where the eating window was exceeded.

The weekly average is also the metric your body responds to, not the daily number. Metabolic rate, fat mobilization, and hormonal adjustments to dietary intake are driven by multi-day energy balance, not single-day deficits. This is why a bad restriction day that lands at 700 kcal instead of 500 kcal is not a protocol failure — it shifts your weekly average by approximately 29 kcal, which is essentially noise against the variation in energy expenditure.³ Our article on protein shakes during the intermittent fasting window addresses whether a liquid protein source after the window closes counts against the fast.

Fasting Day Logging Checklist

• Fasting protocol configured in CalEye settings
• Fasting timer active on home screen
• During fasting window: log anything with calories (black coffee = skip)
• During eating window: log every meal normally
• On 5:2 days: check restriction budget before each eating decision
• At end of week: check 7-day average (not daily total) in Weekly Summary
• Share weekly average with dietitian or care team if relevant to your protocol review

Log the eating window. Mark the fasting window. Let the weekly average tell the real story.

References

1. Patterson RE, Laughlin GA, LaCroix AZ, et al. “Intermittent Fasting and Human Metabolic Health.” Journal of the Academy of Nutrition and Dietetics 115, no. 8 (2015): 1203–1212.

2. Sutton EF, Beyl R, Early KS, et al. “Early Time-Restricted Feeding Improves Insulin Sensitivity, Blood Pressure, and Oxidative Stress Even Without Weight Loss in Men with Prediabetes.” Cell Metabolism 27, no. 6 (2018): 1212–1221.

3. Lowe DA, Wu N, Rohdin-Bibby L, et al. “Effects of Time-Restricted Eating on Weight Loss and Other Metabolic Parameters in Women and Men With Overweight and Obesity.” JAMA Internal Medicine 180, no. 11 (2020): 1491–1499.

4. Cahill GF Jr. “Fuel Metabolism in Starvation.” Annual Review of Nutrition 26 (2006): 1–22.