A Clinician-Ready Symptom Log

The difference between a vague appointment and a useful one is usually a piece of paper. Two weeks of structured symptom entries — time, food, medicines, position, and symptom pattern — let a clinician see the shape of your reflux instead of your recollection of it, and they make the questions you bring sharper. This page is the log itself: the five fields, how long to keep it, how to keep it honest, and how to hand it over.

Why the Log Beats Recollection

Human memory compresses two weeks of symptoms into a few vivid nights, and the vivid nights are usually the worst ones — a bias clinicians know well. Structured instruments exist because of this: the GerdQ, a six-question tool developed for primary care, captures reflux symptoms well enough to guide diagnosis and management (Jones, Alimentary Pharmacology & Therapeutics, 2009). The log below borrows the same logic — small, fixed fields, recorded daily — so the appointment starts from data rather than from the three nights you remember best.

• 🧠 Memory flatters and betrays — bad nights loom, quiet nights vanish, and the average drifts.
• 📏 Fixed fields beat free prose — the same five questions every day make entries comparable, which is what patterns are made of.
• 🔎 Clinicians can read patterns fast — a two-week grid answers in seconds what five minutes of questioning approximates.

The Five Fields

Each entry is one line with five pieces of information, recorded once a day for the evening meal and any symptoms around it. The fields are chosen because each one maps to a question a clinician will actually ask: when did it happen, what was around it, what were you taking, where were you, and how bad was it.

Severity and the One-to-Ten Trap

A 1–10 severity number is useful, but only alongside the other four fields. The trap is treating the number as the whole entry: "6/10" on its own tells a clinician nothing about what caused it, when it happened, or whether anything helped. The number's real job is comparability — it lets you and the clinician see whether symptoms are trending across the two weeks, which is exactly the question the evaluation and any treatment trial will hinge on. Record the number, and record the context that gives it meaning.

• 📈 Trend beats snapshot — a 5 that was a 7 last week is information; two weeks of 5s is a different story.
• 📝 Context gives the number meaning — severity plus time, food, medicine, and position is a complete datum.
• ✅ Symptom-free entries still count — a 0 with "no symptoms" is data; it is what makes the trend readable.

How Long to Log, and How to Keep It Honest

Two weeks is the working standard: long enough for a pattern to emerge, short enough that nobody abandons it. Start at least two weeks before the appointment, log once a day — about a minute — and resist the urge to "fix" your diet mid-log; the point is to record your ordinary pattern, not your improved one. The honest version of the log includes the nights you ate late anyway, the restaurant meal you did not plan, and the evening you skipped logging until morning. Missing a day is fine; rewriting a day is not.

• 📅 Two weeks before the appointment — start early enough that the log is full when you walk in.
• ⏰ One minute a day — five fields at the same time each evening; the whole project costs under half an hour.
• 🚫 Don't diet for the diary — record the ordinary pattern; an idealized log hides the very pattern the clinician needs to see.
• 🧾 Include medicines and supplements — the full list, with timing; the medications and supplements during fasting page explains why timing matters for absorption and side effects.

The Patterns a Clinician Can Actually Use

Two weeks of the five fields resolve into a handful of patterns that change management. Postprandial-only symptoms point at meal content and timing — the dials this series covers. Nocturnal symptoms add the position and elevation conversation, where a small trial found real relief from raising the head of the bed (Khan, J Gastroenterol Hepatol, 2012). Symptoms that ignore every meal-related pattern raise the question of whether reflux is the right diagnosis at all — which is precisely the kind of observation the guidelines say deserves evaluation (Katz, Am J Gastroenterol, 2022). The log's job is to make which pattern you have visible on one page.

• 🍽️ Postprandial pattern — symptoms 30–90 minutes after meals; the timing, portion, and content dials apply.
• 🌙 Nocturnal pattern — symptoms lying down or waking you; position, elevation, and the dinner-to-bed gap apply.
• 💊 Medication-timing pattern — symptoms clustered around a dose; the clinician needs the log to see it.
• ❓ No pattern at all — diffuse or meal-independent symptoms are themselves information; they change the diagnostic question.

What to Bring to the Appointment

The log is the centerpiece, and it travels with three companions. Bring the full list of medicines and supplements with doses and timing — not the names you can remember. Bring any prior test results or imaging reports, even from other clinicians. And bring the questions you wrote down while logging, because the moments that raised them will be gone by appointment day. The alarm-symptom list on symptoms that need evaluation is the one thing that outranks the log: if any of those symptoms is present, the appointment should happen sooner, and the log is a bonus rather than a gate.

• 📋 The two-week log — one page, printed or on your phone, readable in seconds.
• 💊 The complete medicine list — names, doses, timing, including supplements and anything over-the-counter.
• 🗂️ Prior results — blood work, imaging, or endoscopy reports from any clinician, even years back.
• ✍️ Your written questions — captured while they were real, not reconstructed in the waiting room.

The Questions Worth Asking

A good appointment ends with you knowing what the next step is and why. The questions below fit most reflux evaluations; write your own versions into the log before you go, so the answers land on the same page as the data that prompted them.

• ❓ "What pattern do you see in this log?" — the clinician reads the grid; you learn what your data say.
• ❓ "Do I need any tests before we decide on treatment?" — endoscopy, pH monitoring, or blood work, and why.
• ❓ "What should my medicine timing be relative to meals?" — the interaction between dosing and eating, made explicit.
• ❓ "What symptom would mean I should come back sooner?" — the return-to-clinic threshold, defined in advance.

Related Topics