How to Keep a Food and Symptom Diary That Actually Finds Your Triggers

Almost everyone with unexplained digestive symptoms has tried keeping a food diary. Almost nobody finishes one. And the people who do finish often end up with pages of notes that prove nothing, because the diary was missing the fields that make analysis possible.

Here's what a diary needs to contain in order to work, and why each field earns its place.

The six fields that make a diary usable

• Time stamp on the meal. Not the date, the clock time. Reactions land one to four hours later, so without times you can't line symptoms up with the right meal.
• Ingredients, not dish names. "Chicken curry" tells you nothing. Onion, garlic, cream, chili, and stock powder tells you everything.
• Hidden ingredients: stock, marinades, infused oils, thickeners, emulsifiers, and sweeteners. This is where most missed triggers live.
• Symptom severity as a number. A 2 and an 8 are different events. Without a scale, every entry reads as a bad day and no pattern emerges.
• Stool form, using the Bristol Stool Form Scale. It's the standard clinicians use, published by Lewis and Heaton in 1997, and it turns a vague description into a comparable number.
• Sleep and stress, once a day. These shift your threshold, and they let you set aside the days where life, not food, caused the flare.

The four reasons diaries fail

• Too much friction. If logging a meal takes three minutes, you'll stop by day four. Fast capture beats complete capture every time.
• Recording after the fact. Filling in Tuesday on Thursday produces fiction. Log at the table or not at all.
• Only logging bad days. A trigger is only provable if you also captured the days you ate it and felt fine.
• Stopping too early. Under 10 days there isn't enough repetition for a pattern to separate from coincidence.

How to read your own diary

Once you have 10 to 14 days, resist the urge to scan for the food you already suspect. That's how confirmation bias ends up producing a permanent and unnecessary ban on tomatoes.

Do it in this order instead.

• For each flare-up of severity 5 or above, list every ingredient eaten in the four hours beforehand.
• Count how often each ingredient appears across all those windows.
• Then count how often that same ingredient appears on calm days. This step is the one everybody skips, and it is the one that matters.
• A real trigger appears frequently before flares and rarely on calm days. An ingredient that shows up everywhere is just something you eat a lot of.
• Test the top candidate by removing it alone for two weeks, then reintroducing it deliberately.

Bring it to a clinician, not just to yourself

A structured diary is also the most useful thing you can put in front of a doctor or dietitian. Both the ACG guideline and NICE guidance treat diet and symptom history as a first-line part of assessment, and what a clinician wants is dated entries, severity scores, stool form and your shortlist of suspected ingredients. Not a narrative.

FoodTrigger AI is built around exactly this method: fast time-stamped capture, an ingredient breakdown including hidden ones, a severity scale, Bristol stool classification, sleep and stress markers, and an automatic cross-examination of the one-to-four hour window before every flare. Logging is free and works without an account, and Pro exports a dated summary for your appointment.