The high-signal fields
You do not need an endless spreadsheet. You need enough structure to answer four questions later: what was planned, what actually happened, what changed around it, and what happened afterward?
| Field | Why it matters | When it becomes critical |
|---|---|---|
| Planned schedule + actual timestamp | Lets you separate normal weeks from late, early, or missed-dose weeks. | Any time you are comparing symptoms, energy, appetite, or recovery patterns. |
| Compound + amount exactly as logged | Prevents fuzzy recall when reviewing cycles, stacks, or changes over time. | When you have dose changes, multiple compounds, or restarts. |
| Route and site | Keeps injection-site issues and administration notes attached to the entry. | When rotation, irritation, or technique questions show up. |
| Symptoms with timing | Turns “felt off” into a real timeline you can review later. | When nausea, sleep disruption, anxiety, GI issues, or wearable changes show up. |
| One short context note | Captures confounders like travel, illness, bad sleep, training, alcohol, or stress. | When the week looked unusual and you need to explain the noise. |
| Lot, batch, reconstitution, or storage note | Useful for consistency checks and later recall or handling reviews. | When you mixed a vial, changed batches, or suspect handling differences. |
Practical rule: if the log cannot tell you whether the week was on schedule, late, missed, or mixed with another change, it will be hard to interpret later.
What to track every time
- Date and time of the actual dose or the missed dose note.
- Compound name and the amount exactly as you recorded it elsewhere.
- Route/site if relevant.
- Schedule status: on time, early, late, skipped, restarted, or intentionally changed.
- One-line note about what changed afterward.
What to track only when it adds signal
- Side-effect timing if the question is about symptom patterns. Use the peptide side-effect timeline when timing matters more than the dose record.
- Routine drift if the real problem is adherence or inconsistent timing. Use the routine drift log when the week stopped following the plan.
- Batch, lot, or vendor details if consistency or recall questions matter. Use the batch, lot, and vendor notes log.
- Morning versus night timing if time-of-day is the actual question. Use the morning vs night injection log.
Simple peptide tracking template
| Date | Time | Compound | Amount | Schedule | Symptoms / context note |
|---|---|---|---|---|---|
| ____ / ____ / ____ | ____ : ____ | ____________ | ____________ | On time / late / skipped | ______________________________ |
| ____ / ____ / ____ | ____ : ____ | ____________ | ____________ | On time / late / skipped | ______________________________ |
| ____ / ____ / ____ | ____ : ____ | ____________ | ____________ | On time / late / skipped | ______________________________ |
When a simple note stops being enough
A plain note is fine when nothing changed. Move up to a broader tracker when you start asking timeline questions instead of memory questions.
Peptide dose log
Best if you mainly want a clean dose history with a few notes.
Peptide protocol tracker
Best if you need missed doses, schedule drift, stacks, and context in one view.
Peptide tracker
Best if you want the broadest app-style route into logging, symptoms, and reminders.
GLP-1 injection tracker
Best if your peptide logging overlaps with obesity-medication tracking.
Use Jabbit when the protocol no longer fits in screenshots and notes
Jabbit fits this query because the real need is not “read a peptide article.” It is keeping dose timing, symptoms, missed-dose weeks, and protocol notes in one private timeline. Compared with GLP-1-first apps like Shotsy, the fit is broader when you are logging peptides, stacks, or non-standard protocol context.
Three review questions that make the log better
- Did the week follow the plan, or was it really a missed-dose or schedule-drift week?
- Did the symptoms follow the dose timing, or did they line up better with sleep, stress, travel, meals, training, or illness?
- Would another person understand what happened from the log without asking you to reconstruct it from memory?