Morning running intervals: logging breakfast and pre-run context
A practical workflow for recording breakfast, interval timing and missing recovery signals before an early run.
The scenario: intervals before work
Your run starts at 07:00, earlier than your usual breakfast. Record the planned session time first, then log what you actually eat and its time. A meal entered later in the diary is not evidence that it was available before the run.
Use familiar food choices and your established plan. This example does not define a fasting strategy or a universal carbohydrate target; session demands and digestive tolerance differ.
Read the window, not just the daily total
Before Training separates the day’s plan from the available pre-session information. A daily carbohydrate total can include meals eaten after the workout, so inspect the stated time window when reviewing preparation.
Check whether sleep or wearable data has arrived. An unavailable signal means the app lacks that observation; it does not mean you slept zero hours or have no recovery.
After the intervals
Confirm the workout and review the distance, duration and heart-rate information that is actually present. If interval structure or splits are missing, do not treat the workout summary as a complete record of every repetition.
For the next comparable session, record the same meal timing, route and workout format. Several observations are more useful than attributing one strong run to breakfast alone. Food, weather, accumulated training and pacing may all differ.