Glossary
Food Diary
Updated April 2, 2026
Food Diary records what you eat and drink alongside the context that explains why the intake happened. That is the difference between a diary and a plain log. A log can tell you that dinner ran high in calories. A diary can show that the same pattern appears after late meetings, skipped lunches, travel days, or high-friction weekends.
Practical logging rhythm
Set rhythm first, then method.
| Rhythm | Structure |
|---|---|
| Daily | capture each meal within 2 hours |
| Weekly review | inspect trend around triggers and mood |
| Bi-weekly cleanup | compress messy entries and fix missing fields |
Model log entries
Use repeatable examples to reduce drift.
| Entry type | Minimum fields | Value |
|---|---|---|
| Planned meal | name, portion, ingredients | best for trend stability |
| Missed context meal | skip reason and replacement | reveals adherence drift |
| Trigger meal | location, companions, emotion | clarifies repeat risk |
What a diary catches that macro totals miss
| Hidden pattern | Why standard logging misses it | What the diary adds |
|---|---|---|
| Weeknight overeating | macros only show the outcome | notes on stress, time pressure, and meal timing |
| Weekend drift | averages hide the timing and social trigger | event context and repetition across similar days |
| Low-protein mornings | daily totals can still look acceptable by bedtime | meal-sequence pattern that predicts later hunger |
| Restaurant underlogging | calorie total looks random | location, companion, and decision context |
| Repeated appetite spikes | macros do not show the lead-up | sleep, training, and skipped-meal notes around event |
Review rules
Use the diary to find repeatable situations, not to create guilt loops.
- Review 7 to 14 days at a time instead of single bad meals.
- Circle situations that repeat more than once before changing the plan.
- Fix the earliest break in the chain, such as skipped lunch, poor prep, or commute hunger.
- Keep one sentence of context per entry so the pattern stays readable.
Interpretation patterns
| Pattern | Likely signal | Suggested adjustment |
|---|---|---|
| Repeated late hunger windows | low protein or low fiber in prior meal | adjust evening structure |
| High weekend drift | social context effect | set weekend-specific defaults |
| Trigger meals with high density | behavior-linked risk zones | add pre-plan alternatives |
Pair this with food logging and macro tracking workflows for stronger trend context. If a normal food log tells you what happened, the diary should tell you what keeps causing it.