Weeks on, weeks off: tracking peptide cycles

Many peptide protocols aren't continuous — they run in cycles: a stretch of weeks on, then a deliberate break. The structure is simple. Keeping count across months, two compounds, and a vacation is not.

Why protocols cycle at all

Cycling exists for reasons your protocol's designer cares about: giving receptors a break to maintain sensitivity, bounding long-term exposure, cost control, and creating clean “off” windows to judge what the compound is actually doing. Which pattern (if any) applies to a given compound is a clinician conversation — this guide is about not fumbling the execution.

Where cycle tracking falls apart

1. The count drifts. “Week 5, I think” becomes week 6-or-maybe-7 after any interruption.
2. Off-weeks don't announce themselves. Nothing reminds you to stop — so on-autopilot dosing bleeds into the break.
3. Restarts get lost. The off-phase ends on a date nobody wrote down, and the break quietly stretches from four weeks to seven.
4. Stacked compounds desynchronize. Two cycles with different lengths need two counters, not one memory.

What correct cycle execution needs

• A start date — every count derives from it, so it must be recorded, not recalled.
• A current-position readout: “week 3 of 8 on” or “off week 1 of 4.”
• Schedules that mute themselves in off-weeks — no due doses, no reminders, no willpower required.
• A resume date stated as a date (“resumes Mon, Sep 14”), not an offset you compute in your head.

That's the whole system. On paper it's a calendar and discipline; in an app it's a one-time setup that survives skipped days, travel, and stacked protocols without a single recount.

Cycles that count themselves

Set 8-on/4-off once. PepShot schedules doses only in on-weeks, shows “Week 3 of 8” on today's card, and tells you the exact date the next phase starts.

Download PepShot

Related: GLP-1 tracking · site rotation