course › module 4 · The Meal-Symptom Bridge (LOG) › lesson 4.1

The five questions to ask after every meal

The fixed question set that becomes the backbone of every log entry. · about 8 minutes

VIDEO GOES HERE
Notebook close-up, filling in the log template by hand.

I didn't start logging seriously until after years of guessing my way through raw food diets, banana-only stretches, and green juice fasts, each of which worked for a while and then failed without warning. A log is what finally showed me the pattern I couldn't see by memory alone.

Here are the five fixed questions I ask after every single meal, no exceptions. I'll explain why each one is there.

Memory lies. Pain from Tuesday's lunch often shows up Wednesday morning, and without a written bridge between the meal and the symptom, your brain will blame the wrong thing every time. This log is that bridge.

script · 845 words · what Gabe says on camera
By the end of this lesson you'll have the five questions memorized, so you can answer them after every single meal starting today. Memory lies. Pain from Tuesday's lunch shows up Wednesday morning. And your brain, trying to make sense of it, blames whatever you ate most recently. Wrong food, wrong lesson learned. That's how you end up cutting things that never hurt you, and keeping the one that did. Here's a second example, so you can see how far off the timing can be. When I was thirteen, I was out scouting deer with my dad. He'd left feed piles of these golden crisp apples for the deer, and I ate several of them while we were out there. Nothing happened right away. Hours later, the cramps started, and they came on strong. If I'd been asked right then what I ate that made me sick, I'd have pointed at whatever I had for dinner, not the apples from that afternoon. That's the trap. The gap between the bite and the pain is exactly where your memory fails you. And it's exactly why the log exists. Here's the common mistake people make once they start logging. They only write it down when something goes wrong. A bad flare happens, they scramble to remember what they ate, and they log that one meal. But the good meals matter just as much as the bad ones. If you only log the failures, you never build the comparison that tells you which food is actually the problem. You need the boring, nothing-happened meals in the log too, sitting right next to the ones that hurt, so the pattern can actually show itself. I didn't log seriously for years. I went through raw food diets, banana-only stretches, juice fasts. Each one worked for a few months. Then it failed without warning. Because I never had a written record to catch what was actually happening. Just my memory. And my memory was guessing. Here's a real moment that shows what that guessing cost me. During the banana stretch, I was eating a lot of dates with them, and I had some relief for months. Then I went on a road trip with my brother to Georgia and ate dates covered in coconut. All that rough fiber set off one of the worst flare-ups I've ever had. We had to end the trip. I ended up in the hospital for three days. If I'd had a real log by then, one that tracked texture and fiber and not just "dates, fine" as a category, I might have caught that the coconut and the roughness were the actual problem, not the fruit itself. Instead I found out the hard way, in a hospital bed, with no record to point back to. ON SCREEN: Phone screen, adding a meal in the Food Log tool. So here's the fix. Five questions. Ask them after every meal. What did you eat. Be specific. Not "salad," but what was in it. Every ingredient you can remember, including the dressing, the seasoning, anything added on top. If you can't remember all of it, write down what you're sure of and move on. But don't just write the category and call it done. When did you eat it. Time matters, not just the day. Write the actual time, even roughly. An hour makes a difference when you're trying to line up a meal with a flare that shows up later. How much. A few bites is different than a full plate. Portion size changes how your body reacts, so don't skip it just because you already wrote down what the food was. What happened in the next twenty-four hours. This is the one people skip. Don't skip it. Set a reminder if you have to. Come back to the same entry the next day and fill in what your body did, even if the answer is nothing. And how bad was it. We'll get to the scale for that in the next lesson. All five. Every meal. No skipping one because you're in a hurry, or you think it doesn't matter. Now, if you're the type who gets nervous about this, you're probably already asking: what if nothing happens? What if I eat the meal, wait the twenty-four hours, and I feel completely fine? Do I still have to log it? Yes. That entry is just as valuable as the one where something goes wrong. A clean meal with a clean result is proof, not filler. It's how you build the list of foods you can actually trust, instead of living scared of everything because you only ever wrote down the bad days. This log is the backbone of the whole method. Everything from here forward depends on you actually filling it in. Not thinking about filling it in. Filling it in. ON SCREEN: the Food Log tool, the 21-day view. Before the next lesson, get your hands on the log and write down your very next meal. All five questions, before you eat again after that.

Tool for this lesson

21-Day Trigger Food Log