Tracking does not prove causation. It can preserve timing, reduce recall bias, and give you and a clinician a cleaner record to evaluate.
The four-line entry
A practical daily note can fit in four lines:
- Context: date, time, sleep, meals, exercise, illness, travel, or another meaningful condition.
- Event: what was taken, changed, skipped, or scheduled, copied from the actual instruction.
- Observation: what you noticed, stated without a diagnosis.
- Action: what you did next, including contacting a clinician or making no change.
"Headache, moderate, began around 3 PM, lasted two hours" is an observation. "The product caused dehydration" is an interpretation. Keep both if useful, but label them differently.
Write the baseline before the change
A before-and-after comparison needs a before. Record the relevant measure for several days before a planned change when practical. Use the same time, device, units, and conditions so the comparison is less noisy.
Choose a small set of outcomes that matter. More fields do not automatically create better evidence; they can create more opportunities to find a pattern that is not real.
Make subjective ratings concrete
If you use a rating scale, define its anchors once and keep them stable:
- 0 = absent
- 3 = noticeable but did not change the day
- 5 = changed an activity or required a response
- 7 = severe enough to stop normal activity
- 10 = worst imaginable or emergency-level concern
The exact scale matters less than using it consistently. Do not let the number replace the written description when the details are important.
Timing is information, not proof
Record when an event happened, when an observation began, how long it lasted, and whether it repeated. A close time relationship can be worth investigating, but it does not rule out other causes.
Context can matter: a new prescription, infection, sleep loss, alcohol, strenuous exercise, dietary change, or a different batch or product may all belong in the same timeline.
Avoid changing five things at once
When several variables change together, the record becomes harder to interpret. Do not change prescribed treatment to improve an experiment; discuss changes with the prescriber. When a clinician directs a change, record exactly what changed and when.
Use a scheduled review
A daily log captures detail. A weekly review finds missing entries, confirms whether reminders match current instructions, and turns repeated observations into concise questions. It is also a good time to archive stale calculator results or superseded source cards.
Useful review prompts include:
- Did the planned event actually happen?
- Did the relevant measure change before the event?
- Was the observation repeated or isolated?
- What other variables changed?
- Does this need routine follow-up, prompt clinical advice, or urgent care?
Know when a journal is not enough
Severe, rapidly worsening, or emergency symptoms need appropriate medical help, not another data point. For suspected product problems or adverse events, a clinician can advise on care and reporting. FDA's MedWatch program explains how safety information and adverse-event reports are collected.
Health and planning notes can be sensitive. Use device security, review what is synchronized, and export or delete records intentionally. PepPlanner provides in-app export and account deletion controls.
The bottom line
A clean log protects the facts from your memory's urge to tell a tidy story. Record the date, the event, the observation, and the action. Let the interpretation stay provisional until the evidence is stronger.