How to plan and record a peptide cycle

A cycle is a protocol with an end date. Whatever the compound, the structure is the same: a defined on period, a defined off period, and a set of things you agreed to watch while it ran. The discipline that makes a cycle worth anything is not the schedule itself: it is having decided, before you start, what would count as it having worked.

Write the plan down before it starts

A plan that exists only in your head is a plan that will be quietly revised whenever it becomes inconvenient. Five fields, written once:

Start and end date

The end date is the important half. A cycle without one is just a habit.

Compounds and doses

In the same units you will log in. If two compounds are running together, both, with their own frequencies.

Frequency

Daily, twice daily, weekly, every third day. Frequencies inside one stack do not have to match, and usually do not.

What you are watching

Two or three specific measures, chosen in advance: a lift, a lab value, sleep, a symptom score. Named before you start, so you cannot pick the flattering one afterwards.

The off period

How long, and what you expect to happen during it. Decided now, while you are not attached to the result.

Stacks: different clocks running at once

The reason stacks get confusing is not the number of compounds, it is that they run on different clocks. Something daily and something weekly share a calendar but never line up the same way twice, and after a fortnight nobody can say from memory which days had both.

Two things make this tractable. Group the compounds into a named schedule ("morning stack", "evening protocol") so you are tracking two or three objects rather than seven separate threads. And keep an eye on where the schedules overlap, because that is where side effects, if there are any, will be hardest to attribute. The overlap is also where a level estimate earns its keep: seeing two curves on one axis answers "what was I actually on last Tuesday" in a way a list of log entries does not. There is more on reading those curves in peptide half-life, explained.

Change one thing at a time

The most common way a cycle produces no usable information is that three things started on the same Monday: a new compound, a new training block and a new diet. Something changed, and nothing is attributable. If the point of the cycle is to learn whether the compound does anything for you, then it has to be the only new variable, and if it cannot be, that is worth writing down at the start rather than discovering at the end.

What to log while it runs

• Every dose, with date, amount and site. See injection site rotation for why the site field is the one worth protecting.
• The named measures, on a fixed cadence. Weekly beats daily here: daily numbers on a noisy measure produce a graph nobody can read.
• Anything unexpected, on the day it happens. Retrospective side-effect reporting is close to worthless: the memory reshapes itself around whatever conclusion you have since reached.
• Deviations. A missed week, a dose taken late, a batch that ran out. The deviations are usually the most informative part of the record.

Ending it properly

An off period is part of the protocol, not the absence of one. Two things are worth doing at the end of a cycle. First, remember that stopping is not the same as clearing: a compound with a long half-life is still present, at falling levels, for weeks. Five half-lives is the usual rule of thumb, so anything around a week of half-life is a month or more before it is negligible. Second, write the verdict down while it is fresh, against the measures you named at the start, including the honest answer "no detectable difference". That entry is what makes the next decision better than the last one.

A year of cycles recorded that way is genuinely useful to you and to any clinician you show it to. A year of cycles recorded from memory is a story, and the story always improves in the telling.