Skip to content
OptiPin app icon OptiPin
Download
Practice guide · How to track a stack

Tracking a multi-compound protocol

One compound is a notes app. Three to five, TRT plus an AI, a GLP-1, a healing peptide, a GH secretagogue, running on different schedules and landing on the same labs, is where spreadsheets quietly fall apart. This is the practice guide: why multi-compound tracking is hard, and the principles that keep it legible. It's about method, not molecules, and it contains no doses or protocols.

The failure mode
Fragmentation
The fix
One timeline
Hardest part
Overlapping labs
Read doses in
Phase context
TL;DR

Why multi-compound tracking breaks the usual tools

A single compound is easy: one schedule, a handful of notes. The difficulty scales non-linearly because a real stack combines things that do not share a rhythm and do not stay in their lanes. Four problems compound at once:

Spreadsheets and notes apps fail not because people are careless but because those tools hold one of these dimensions at a time, never all four together.

The principles that keep it legible

1. One timeline, no exceptions

The single highest-leverage habit is refusing to fragment. Every compound, every injection, and every lab value belongs on one dated timeline. The payoff is automatic context: a blood result is always read against which compounds were active, at what point in a phase, when it was drawn. Fragmented data, doses here, labs there, inventory in your head, is not just inconvenient, it is uninterpretable, because the connections that make the numbers mean anything are exactly what fragmentation destroys.

2. Per-compound schedules, not one calendar

Each compound needs its own schedule logic, daily, every-N-days, weekly, cycled, with its own reminders, rolled up into a single day view. That way "what do I take today" is answered without you mentally reconstructing five separate cadences.

3. Labs read in context, trended over time

Because markers overlap, isolated snapshots mislead. Draw labs at consistent times relative to your injections, record them on the shared timeline, and look at trends. When a value moves, the timeline shows which compounds were on and how far into a phase you were, turning "why is my hematocrit up?" from a guess into a readable answer.

4. Inventory as part of the protocol

Track each vial's remaining amount and expiry so a runout is predicted, not discovered. On a multi-vial stack this is the difference between a smooth protocol and an improvised gap.

5. Phase tagging

Tag the windows, on, off, blast, cruise, titration, so every data point is read against the phase it happened in. This is the same logic as the cycle-structure guide: phases exist so your data means something.

What good tracking actually prevents

Common failureWhat one-timeline tracking does instead
"Which one caused this?" side-effect confusionSide effect lines up against the compound/step that preceded it
A lab misread out of contextValue shown with active compounds + phase + timing
Running out of a vial mid-protocolRunout predicted with a reorder warning
Off-week dip misread as failurePhase tag makes the dip expected, not alarming

This is the problem OptiPin was built for

Everything above is a description of a design brief, and it is OptiPin's. It handles per-compound schedules (daily, every-few-days, weekly, cycled), forecasts blood levels for the compounds it models, keeps per-vial inventory with runout warnings, tags cycle phases so off-week dips are not misread, and puts labs and doses on one timeline, with insight summaries that connect dosing, symptoms, and bloodwork. The explicit design goal is that adding a fourth or fifth compound does not multiply the overhead, which is exactly where spreadsheets give up. Concrete stacks this applies to include the BPC-157 + TB-500 recovery stack and the retatrutide + TRT recomposition combination.

The honest part

This is a guide to tracking, not to what to run. It contains no doses or protocols, and good record-keeping is a harm-reduction step, not a substitute for medical supervision. Running multiple active compounds multiplies interactions, side-effect sources, and monitoring needs; several of the compounds people stack are unapproved or investigational, and some (like TRT) are prescription therapies that require a clinician. Track well and bring the data to a professional, don't let a tidy log substitute for one.

Add the fifth compound without the fifth spreadsheet

OptiPin holds every compound, schedule, vial, lab, and phase on one on-device timeline, and forecasts levels for the ones it models, so a complex stack stays legible instead of scattered. iOS, no account.

Download OptiPin

Frequently asked questions

Why is tracking multiple compounds so hard?

Each compound runs on a different clock (daily, every-few-days, weekly, cycled) and they all hit the same body: overlapping labs, inventory across many vials, and dose meaning that changes by phase. Spreadsheets and notes apps hold one of those dimensions at a time, not all together.

What's the most important principle?

One timeline. Fragmentation - doses, labs, and inventory in separate places - is the main failure mode. When everything shares one dated timeline, a lab result is automatically read against what you were taking and how far into a phase you were.

How do you track bloodwork on a stack?

Draw labs at consistent times relative to injections, record them on the same timeline as doses, note the context, and read trends not snapshots. Because multiple compounds move the same markers, you need to see which were active when a value changed.

Can one app track TRT, GLP-1, and peptides together?

Yes - that's what OptiPin is built for: per-compound schedules, level forecasting, per-vial inventory with runout warnings, cycle-phase tagging, and labs plus doses on one timeline, so a fourth or fifth compound doesn't multiply the overhead.

Related

BPC-157 + TB-500 stack · Retatrutide + TRT stack · Cycle structure & tracking · Bloodwork to monitor · Feature guide · Peptides guide