Quick Reference
This is the quick-reference companion to How to Track Your Peptide Cycles, which covers why tracking matters and how to build a full system, and to How Do You Know If Your Peptide Protocol Is Working?, which covers how to evaluate what you've recorded. This guide is narrower on purpose: exactly which fields to write down, whether you're using a plain notebook, a spreadsheet, or a purpose-built tool.
| Category | What to record | How often |
|---|---|---|
| Dosing and site | Compound, dose, time of administration, and injection/application site | Every dose |
| Immediate effects | Any effect or side effect noticed within hours | Every dose |
| Subjective check-in | Energy, sleep, mood, recovery (1-10 scales) | Weekly |
| Body measurements | Weight, and relevant measurements if tracked | Weekly to every 2-4 weeks |
| Bloodwork | Panel results plus draw conditions | Baseline, then periodic |
Daily Log Fields
Fields worth writing down every time you dose. Keep each entry short; the goal is capturing it accurately in the moment.
- Compound and dose: exactly what you took and how much, in the same units every time, so entries stay comparable week to week.
- Time of administration: the actual clock time, not just "morning" or "evening." Timing relative to meals or training can matter for how a compound is felt.
- Injection or application site: which site you used, if the compound is injected or applied topically. Rotation matters for compounds where repeated use of the same spot can cause local irritation, so a quick site note is worth the few seconds it takes.
- Any immediately noticeable effect or side effect: anything you notice within hours of dosing, good or bad. One line is enough; the point is catching it while it's fresh.
Weekly and Periodic Subjective Fields
These don't need a daily entry. A weekly check-in is enough to catch the trend without turning tracking into a second job: energy level and sleep quality on simple 1-10 scales, recovery from training and mood in a sentence each, appetite or digestion if relevant to the compound you're running, and any new or resolving symptom, something that showed up, or something that went away.
Objective Measurement Fields
Not every field applies to every protocol; use judgment about which matter for what you're running. Body weight, measured under the same conditions each time, relevant body measurements like waist or other circumference if body composition is part of the goal, sleep tracker data summarized weekly if you already use a wearable, and training performance metrics such as load or reps for the thing you're trying to improve.
Bloodwork Checkpoints
Bloodwork is the objective layer that subjective and daily fields can't replace on their own. Take a full baseline panel before you start, then periodic follow-ups tied to the compound's typical timeline, plus a fresh checkpoint at any dose change or added compound. See How Long Should You Track a Peptide Before Evaluating Results? for how to time those follow-ups, and the peptide bloodwork guide for which markers pair with which goals. Record the draw conditions alongside the results themselves, time of day, whether you were fasted, and how far into the protocol you were: that context is what makes a later comparison meaningful rather than misleading. See Baseline vs Follow-Up Bloodwork: When Does Comparison Matter? for why draw conditions matter as much as the numbers.
What Not to Skip
Two easy things to leave out, and shouldn't: a side-effect log is just as important as a benefit log, even when the side effect is minor and fades quickly. And recording "nothing notable happened" at a given checkpoint is itself useful data, not a blank to leave empty. A string of unremarkable entries tells you the absence of a signal was real, not a missed log.
Related Reading
Comparing tools for logging all of this? See the peptide tracker comparison. For the terms used on lab reports and vials, the peptide glossary has plain-language definitions.
For the fuller system, including spreadsheet templates and how a purpose-built tool handles this, see How to Track Your Peptide Cycles. For how to weigh what you've recorded once you have it, see How Do You Know If Your Peptide Protocol Is Working?. For how long to wait before your first real evaluation, see How Long Should You Track a Peptide Before Evaluating Results?. For making sure a before-and-after bloodwork comparison is meaningful, see Baseline vs Follow-Up Bloodwork. Once you have a log going, BioStackIQ's Rate My Stack and Build Protocol can help you put it to use.
Frequently Asked Questions
What's the minimum I should track for any peptide protocol?
At minimum, log the compound and dose, the time you took it, and anything you notice within hours of dosing. That short daily entry alone is enough to reconstruct what you actually ran if you need to troubleshoot later. Everything else in this guide, weekly subjective scores, measurements, and bloodwork, builds on top of that baseline habit.
Should I record side effects even if they're minor?
Yes. A minor irritation or a mild digestive change that fades in a day is still worth a one-line note. A side-effect log is just as important as a benefit log, and a pattern of small effects is often the first sign of something worth paying attention to, whether that's a site that needs to be rotated out or a dose worth reconsidering.
Do I need a spreadsheet or app to track this?
No. This guide covers what to record, not what tool to use. A notebook works fine as long as you're consistent. If you want a fuller system, including spreadsheet templates and how a purpose-built tool like BioStackIQ's protocol builder handles this, see how to track your peptide cycles for that side of things.
What bloodwork context should I record besides the results themselves?
Record the draw conditions alongside the numbers: time of day, whether you were fasted, and how far into the protocol you were. A follow-up panel drawn at a different time of day or under different fasting conditions than your baseline is harder to compare cleanly. See baseline versus follow-up bloodwork for why that context matters so much for a fair comparison.
Is it worth logging days when nothing seemed to happen?
Yes. Recording that nothing notable happened at a given checkpoint is itself useful data, not a blank to leave empty. It tells you later that the absence of a signal wasn't a missed entry, and a string of unremarkable days is exactly what you want to see next to the entries where something did change.