Zepbound missed dose tracker (what to log)

When a dose is late or missed, the most helpful thing you can do is keep a clean timeline — so you and a clinician can reason from facts, not vibes.

What to log (minimum viable timeline)

This page is intentionally non-medical. It does not give dose timing instructions. It helps you capture the information that makes a missed-dose situation clearer.

Core fields

  • Scheduled dose day/time (what you intended)
  • Actual injection day/time (if you took it later)
  • Medication name (e.g., Zepbound / tirzepatide)
  • Dose (exactly as prescribed)
  • Reason (travel, refill delay, forgot, nausea, etc.)
  • Symptoms (if any) + context (sleep, meals, stress)
  • Next scheduled dose (the plan you were following)

Missed / late dose log template

Tip: If you only track 3 things, make it: scheduled time, actual time, and why it shifted.
Safety note: Don’t use this page to self-prescribe changes. Use it to capture facts, then follow clinician + labeling guidance for decisions.
Scheduled Actual Dose Reason Notes (symptoms/context)
____ / ____ / ____
____ : ____
____ / ____ / ____
____ : ____
____________ ____________ ____________
____ / ____ / ____
____ : ____
____ / ____ / ____
____ : ____
____________ ____________ ____________
____ / ____ / ____
____ : ____
____ / ____ / ____
____ : ____
____________ ____________ ____________

FAQ

Does this page tell me what to do after a missed dose?
No. This is a tracking template (what to log + a clean timeline). For dose timing decisions, follow your prescriber and the medication’s labeling.
What’s the fastest way to be consistent with tracking?
Use a tiny checklist: scheduled time, actual time, and one sentence about what happened. Consistency beats detail.
Is Jabbit private?
Jabbit is privacy-first: your data syncs via your iCloud account. Jabbit isn’t a server collecting your injection history.
Is this only for Zepbound?
No — you can use the same missed-dose timeline tracking approach for other GLP‑1s too. Start with GLP‑1 injection tracker and adapt the log fields.

Related (keep it in one cluster)

If you’re building a tighter tracking workflow, link these together: