What this page owns
This page is not the generic symptom log and not the full protocol manager. Its job is narrower: help you correlate a side-effect pattern with the exact routine version that surrounded it.
Build one timeline out of four event types
Most messy logs fail because everything gets crammed into one note. Keep these as separate entries that can be read together later.
1. Dose or injection event
Log the exact timestamp, compound, route, site, and anything unusual about administration.
2. Symptom event
Log what you felt, when it started, when it peaked, how long it lasted, and how severe it was.
3. Protocol version change
Log the rule change itself: schedule shift, stack change, pause, restart, lot switch, or routine drift.
4. GLP-1 injection history
If this is mainly an obesity-medication workflow, keep injection recurrence and reminders separate from symptom interpretation.
High-signal peptide side-effect timeline template
This is the minimum structure that usually makes later review possible.
| Window | What to capture | Useful fields | Why it matters |
|---|---|---|---|
| At administration | Date/time, compound, route, injection site if relevant, protocol version, and whether timing was on-plan, late, or unusual. | Timestamp, route/site, version label, planned vs actual time. | Gives you the anchor event the rest of the timeline hangs from. |
| 0-24 hours | First symptoms, immediate site reactions, appetite changes, energy shifts, nausea, reflux, headache, or “nothing notable.” | Onset time, peak time, severity 0-10, duration. | Separates same-day effects from next-day effects instead of mixing them. |
| Day 1-3 | Carryover symptoms, bowel pattern, hydration issues, sleep disruption, fatigue, appetite suppression, or rebound hunger. | One daily symptom score plus one short context note. | This is where many obesity-medication patterns become easier to compare week to week. |
| Day 3-7 | Recovery trend, recurring pattern, quiet days, training tolerance, travel effects, or batch/lot notes. | Better / same / worse, plus top confounder. | Helps you tell a true weekly pattern from a one-off rough day. |
| Weekly review | What changed in the routine, what stayed stable, and whether the pattern repeated after the same trigger. | Version comparison, confounders, questions for next week. | Turns logging into learning instead of passive note collection. |
Questions this page should answer
- Did the symptom start after the dose event, before it, or on an off-pattern day?
- Did the symptom appear after a routine change such as timing drift, missed dose, restart, or new vial?
- Did the same pattern repeat at the same point in the cycle?
- Were there obvious confounders like travel, poor sleep, illness, alcohol, or heavy training?
- Was this a peptide-wide issue, or mainly a GLP-1 / obesity-medication injection pattern?
Route to the right tracker page
If the main question is more specific than “what happened when?”, jump to the page built for that job.
| Real question | Best next page | Why |
|---|---|---|
| I need the routine, version history, and reminders in one place. | Peptide protocol tracker | Best fit for schedule anchors, stack changes, and versioned protocol notes. |
| I need clean administration history first. | Peptide dose log | Best fit for precise timestamped entries before symptom review. |
| I mainly need symptom detail and severity. | Peptide side-effect log | Best fit for symptom-by-symptom entries with severity and duration. |
| This is really a GLP-1 or obesity-medication injection workflow. | GLP-1 injection tracker | Best fit for recurring injection logging, reminders, and consistency. |
Good timeline habits
- Use timestamps, not vague phrases like “later” or “that evening.”
- Log “no symptoms” when nothing happened. Quiet days matter.
- Record schedule drift as its own event instead of burying it in notes.
- Keep lot, storage, and travel changes visible when they might matter.
- Review the week as a pattern, not as a single bad moment.