How to Log a Peptide or GLP-1 Dose So You Can Trust the Record

A dose log becomes trustworthy when it records the injection you actually gave, in enough detail to reconstruct the arithmetic. Six fields do that work: compound, vial concentration, volume drawn, milligrams delivered, timestamp, and site. Add them at the moment of injection and the record answers questions months later.

Most logs fail not because people lack discipline but because the entry captures a conclusion ("0.25 mg") without the inputs that produced it.

The six fields that make a log auditable

An auditable entry lets a second person verify it without asking you anything. That means it contains both the measurement you made and the context that gives the measurement meaning.

Two optional fields pull more weight than expected: needle gauge and length, which affect comfort and depth, and a free-text note field for anything unusual. Notes are where the useful surprises end up.

Volume and concentration, not milligrams alone

Recording only milligrams throws away the ability to catch a mistake. Milligrams are derived, and the derivation depends on a concentration that lives nowhere but your record.

Consider a 5 mg vial reconstituted with 2 mL of water, giving 2.5 mg/mL. Drawing 10 units on a U-100 syringe is 0.10 mL, which is 0.25 mg. Now suppose the next vial was mixed with 1 mL instead, giving 5 mg/mL. The same 10 units is still 0.10 mL, but now it is 0.5 mg. A log that says "0.25 mg" for both weeks looks perfectly consistent and is wrong for one of them. A log that says "10 units from a 2.5 mg/mL vial" and "10 units from a 5 mg/mL vial" makes the discrepancy visible in one glance.

Write numbers the way medication safety guidance recommends: a leading zero before a decimal point, no trailing zero after one, and units spelled out rather than abbreviated in ambiguous ways. "0.25 mg" is unambiguous; ".25 mg" reads as 25 mg to a tired eye, and "250 ug" invites a misread of the microgram symbol.

Timestamp the event, not the intention

The timestamp should be created by the injection, not by your plan for the day. Apps that let you pre-schedule a dose and then mark it complete later drift, because "complete" gets tapped during a commute or at bedtime, and the recorded time becomes fiction.

Interval matters for anything taken on a fixed cadence. If your record shows a dose on Sunday morning and the next on Friday evening, that is a five-day interval, and only an accurate timestamp reveals it. When you truly cannot log at the moment, log later but correct the time field to the actual event rather than accepting the default.

The fields people skip

Site, vial identity, and lot number get skipped because they feel like paperwork. Each one answers a specific question you will eventually ask.

• Site. Without it you cannot rotate deliberately, and you cannot correlate a lump or persistent redness with how often that area was used.
• Vial identity. When you have two vials of the same compound at different concentrations, or one nearly empty, the entry needs to say which one you drew from.
• Lot number and expiration. If a supplier issues a recall or a batch behaves differently, lot is the only field that lets you find the affected doses.
• Diluent and first-puncture date. These belong on the vial record rather than every dose, but the dose entry should point at a vial that carries them.

Partial doses, misses, and waste

Log what happened, including the unflattering version. Three cases come up repeatedly and each has a clean way to record it.

A partial delivery, where the needle backs out or solution leaks at the site, should be recorded as the volume delivered plus a note. Estimating "about 7 of 10 units" is more useful than rounding to 10 and quietly overstating the dose.

A missed dose should be an explicit entry with a reason: travel, illness, out of solution, clinician instruction. An empty day in a log is ambiguous, and ambiguity is what makes people distrust their own records.

Waste, such as a syringe primed and then dropped, matters for inventory rather than dose. Recording it keeps your remaining-volume math honest so a vial does not "mysteriously" run out early.

Fast enough to survive a bad week

A log only works if it takes less effort than skipping it. Fifteen seconds is a workable target, and reaching it means removing typing rather than adding discipline.

Practical ways to get there: default the compound and vial to your last entry, default the volume to your usual draw, suggest the next site from your rotation instead of asking you to pick, timestamp automatically, and put the whole thing on one screen. Vitadel Protocol is built around that shape, and it holds concentration at the vial level so the milligram figure is computed rather than retyped. Whatever tool you use, the test is the same: can you complete an entry one-handed, in a bathroom, at 6 AM?

Reviewing a month of entries

Read your log periodically, or the fields are collected for nothing. A monthly review takes a few minutes and looks for four patterns.

1. Interval drift. Are doses landing where you intended, or has the cadence slid by a day or two?
2. Site concentration. Is one area absorbing most of the injections while another goes unused?
3. Concentration changes. Did a new vial change the units you draw, and did the log capture that at the time?
4. Note clusters. Do the free-text notes cluster around a particular site, vial, or time of day?

None of that interprets whether your protocol is right for you, which is a clinical question. It does tell you whether the record is describing reality.

Export and hand-off

Assume someone else will read your log. A clinician, a pharmacist, or you in eighteen months will need dose, dates, and any interruptions without a decoder key, which means avoiding personal shorthand, keeping units explicit, and being able to export a date range as a document rather than a screenshot. If a tool cannot produce that, the data is trapped, and trapped data is only slightly better than no data.