14 months on tirzepatide, A1C down from 10.4 to 5.9, logging everything against my Dexcom G7 data. the data side has been solid. the correlation side has been annoying. here’s the gap I can’t close: my GI symptoms don’t cluster the way I expected in the standard day-1-to-3 post-injection window. some weeks I have nothing early then get a rough day-5 or day-6. used to think it was random noise until I started reading how MCAS researchers categorize symptoms by position within a cyclical window rather than absolute date. the insight is that “had nausea on May 4th” is almost useless. “had nausea on day-5 of injection cycle” is actually informative. this is directly transferable to a weekly dosing cycle. the variable that matters isn’t the calendar date, it’s days-since-last-dose. day-5 and day-2 symptoms can fall on the same day of the week in back-to-back cycles but they’re structurally different events. peak absorption side effects look different from mid-cycle flares, which look different from trough effects as the drug wears off. what I actually want to track: symptom severity + timestamp + days-since-injection as a derived field, auto-calculated from my last logged dose. rn I log symptoms and injections separately then manually calculate relative timing in a spreadsheet. it works but I’m two weeks behind and definitely missing patterns. anyone found a health tracker that auto-generates a “days since last dose” field when you’re entering a symptom log? or at least lets you anchor symptom entries to a recurring event rather than just the calendar? I’ve tried a few and they all seem to assume absolute time is the only useful dimension. for anyone on a weekly injection schedule it really isn’t.
Sulfur burp timing relative to injection day is exactly what I’ve been logging, so I understand the pull toward this. The catch is that “days-since-last-dose” only holds as a clean anchor if your injection timing is consistent week to week. If shots drift 12-18 hours across cycles, a day-5 in one week and a day-5 three weeks later aren’t the same pharmacokinetic event, and the derived field starts obscuring the pattern you’re trying to find rather than revealing it.
the case for that holds if you’re anchoring to day-of-week rather than actual injection time. but a timestamp-derived hours-since-dose field already absorbs the drift by design. 9pm thursday one week, 11am friday the next, both timestamps are logged, day-5 still means ~120h post-dose in both cycles. the 12-18h variance doesn’t collapse the window, it just shifts it on the calendar, which is exactly what the derived field tracks.
the “12-18h variance doesn’t collapse the window” part is right and that’s a solid design. the caveat i’d add: it only holds if you’re logging injection time to the hour consistently, not just the date. most people log the date and call it done, which reintroduces exactly the drift you’re trying to eliminate.
the cyclical-window framing is the right one and the MCAS analogy actually holds up better than most cross-domain transfers, so no pushback on the core idea. where i’d push is “days-since-injection as a derived field” being the variable that matters. with a ~5 day half-life you’re not at a clean trough by day 6-7, you’re at roughly 60-65% of peak at steady state, so the “trough effects as the drug wears off” framing is doing more work than the PK supports unless you’ve actually missed a dose or just titrated up. day 5-6 GI flares at steady state are more likely a second-order effect (motility resetting, bile timing, whatever you ate two days prior) than residual drug clearance. the better derived field is probably days-since-injection AND week-in-current-dose, because tolerance windows shift for ~3-4 weeks after each titration and a day-5 symptom in week 1 of a new dose is structurally different from a day-5 symptom in week 4. spreadsheet will let you do that, most trackers won’t. ymmv.
The “day-5 and day-2 symptoms can fall on the same day of the week” observation is exactly what breaks standard symptom logging for weekly injections, and you’ve framed it more clearly than most threads do. Where I’d add a layer: if you’re also cycling hormonally, there’s a second cycle overlaid on the injection one. Day-5 post-injection during the luteal phase is a different physiological state than day-5 mid-follicular. Progesterone slows gastric emptying, so the GI burden on that same injection-cycle day can look completely different depending on where your menstrual cycle sits. Single-axis tracking misses that interaction for anyone on tiz with a functional cycle. Also worth flagging for compounded tiz specifically: days-since-dose math assumes consistent absorption, but batch-to-batch reconstitution variance means actual peak timing can shift. Some of those unexpected day-5 flares might reflect when the drug actually peaked rather than when you expected it to based on the label concentration. On the tracking side, logging injection events and symptoms as separate record types and pulling correlations in the chart view has helped me get closer to what you’re describing. The dark mode chart colors in the app I use are unusually readable for multi-variable overlays, which matters when you’re trying to visually pattern-match across two cycles at once rather than just one.
The MCAS framing actually transfers well here, and the case for injection-relative timing rather than calendar date is the right reframe.
Where I’d gently push back: if you’re also running a hormonal cycle underneath the injection cycle, position in the dosing window is only one of two relevant axes. Day-5 post-injection in the follicular phase is a meaningfully different physiological state than day-5 late-luteal, even at identical doses and concentrations. I track both overlays, and the interaction is where the interesting patterns actually live rather than in either cycle individually. On the app side, I’ve found CareClinic useful for exactly this reason bc the injection-day column and cycle-day column sit in the same log view, which is the only setup where I’ve actually been able to see when the two cycles are amplifying versus cancelling each other out.