A delayed tennis match: updating meal timing before play
How to keep the planned match time, actual meals and pre-session context consistent when a tennis start is delayed.
The scenario: a 14:00 match moves to 16:30
A tournament delay changes the relationship between lunch and warm-up. Update the planned session time when you have reliable information, then check the meals recorded around the new start.
Keep the real lunch time intact. Moving an entry to make a readiness indicator look better would erase information about what happened. If you eat again during the delay, log that separately.
Separate the meal checkpoint from the match window
A daily plan may show progress up to a meal such as lunch, while pre-session metrics use a different time window. Read the label and the window before interpreting a shortfall. They are not interchangeable targets.
Use food you tolerate and a plan appropriate to the circumstances. This scenario does not specify what every player should eat while waiting or how much fluid to consume.
After play: confirm the actual session
Review the actual match duration and available heart-rate or intensity data. Wearable summaries do not necessarily contain point-by-point work, court conditions or rally duration.
Record the delay as context when comparing matches. A long wait, changed warm-up and different opponent can alter the experience. A correlation between the extra meal and a result is not proof that the meal determined performance.