# What a TRT log actually records, and what a TRT tracker app should keep

By The Optimized Team (Product). Published: 2026-07-05T10:00:00+00:00. Updated: 2026-10-27T21:58:27.431727+00:00.
Canonical: https://optimizedtracker.com/blog/what-a-trt-log-actually-records

A TRT log is a record, not a plan. It holds each entry as prescribed, the site, short check-ins, and lab results with the date and time of the draw, so you and your prescriber can read it later.

## What a TRT log is for

A TRT log records what happened and when: each entry as your prescriber wrote it, where it was given, how you felt, and the lab results with the date and time of the draw. It is a record, not a plan. It doesn't tell you what to do, and it never replaces a conversation with the person who prescribes your therapy.

That distinction shapes everything below. A good log is something you and your prescriber can read months later and agree on what happened. If you are comparing a TRT tracker app with a spreadsheet or a notebook, the question is the same: does it hold the right fields, in a form you can trust later?

## The core entry: what, when, and as prescribed

Every entry needs three things: the date, the time, and the product as it is labeled. Record the product name and the form exactly as printed on the label. Copy the prescriber's instructions as written, in a separate field, rather than paraphrasing them from memory. That way the log shows what you were told and what you actually did, side by side.

A few details are easy to skip and costly to lose:

- **The exact time.** A date alone hides patterns that a time stamp reveals.
- **Changes.** When the prescriber changes an instruction, add a new dated note. Do not overwrite the old one.
- **Missed or late entries.** Log them with a short reason. A gap you can explain is more useful than a gap you have to guess about.

The log's job is to show the gap between the plan and what really happened. Nobody is grading it.

## Site and administration record

If your log includes a site, record where each entry went: the site, the side, and any skin reaction you noticed. This is bookkeeping, not technique. The point is that you can look back and see which sites you have used and how often, which is the idea behind [site rotation as a data problem](/blog/injection-site-rotation-is-a-data-problem). Keep the field short, a picker or a few words, so it doesn't become a chore.

## Symptoms and check-ins

Most logs also carry a short check-in: energy, mood, sleep, appetite, or whatever you and your prescriber agreed to watch. Keep it small and keep it identical from day to day. Use the same scale every time (for example 1 to 5), and write down the question you answered.

Be clear about what this data is. Self-reported check-ins are noisy. A single bad day tells you little, and two things moving together in a personal log does not show that one caused the other. The value of a check-in is in the long run of entries, not in any one of them.

## Lab results over time

Lab results are the part of the log most worth getting right, because they are the part most likely to be compared across months.

### Record the date, the draw time, and the lab

For each result, store the date, the time of day the blood was drawn, the lab name, and the value with its unit. The time matters more than most people expect. In a study of 66 men aged 30 to 80, [testosterone peaked between about 05:30 and 08:00](https://pmc.ncbi.nlm.nih.gov/articles/PMC2681273/), and in men aged 30 to 40 the level at 16:00 was about 20 to 25% lower than at 08:00. The authors concluded that measurements should be restricted to morning hours. They also noted that their findings may not apply to people on replacement therapy who are adjusting their regimen. For a log, the takeaway is practical: two values from different times of day may not be directly comparable, and you can only tell if you wrote the time down.

The same study found that isolated low readings could reflect measurement variability, which is why more than one measurement is commonly used. One number is a data point. A series with consistent timing starts to look like a trend. For more on this, see [reading your own lab trends without fooling yourself](/blog/reading-lab-trends-without-fooling-yourself).

### Which results tend to show up

Published monitoring reviews name several results that are tracked during therapy. A [narrative review of adverse-effect management](https://pmc.ncbi.nlm.nih.gov/articles/PMC12052019/) discusses hematocrit (checked every 3 to 6 months early on, then yearly, in that review), PSA, estradiol, blood pressure, and liver enzymes. A [pre-therapy checklist](https://pmc.ncbi.nlm.nih.gov/articles/PMC10233410/) suggests hematocrit at least every 6 months while on therapy. The two sources do not agree on every interval, and neither gives a standard for what a patient's own record should contain.

Put plainly: these are clinical documents about monitoring, not about record-keeping, so what you log is your own choice. Your clinic decides which labs you get and when, and what any result means. The log only stores the dates and the values so that the history is there when you sit down with them.

| Field | Why it is recorded |
|---|---|
| Date of draw | Orders results in time |
| Time of draw | Lets you compare like with like |
| Lab name | Different labs can report differently |
| Value and unit | The number, with its unit, exactly as printed |
| Reference range as printed | Context from the lab, not your own judgment |
| Note | Anything unusual about the day |

## Baseline entries

Before the first regular entry, record where you started. The same pre-therapy checklist describes documenting items such as confirming low testosterone with two morning values, a baseline hematocrit, a PSA where relevant, a sleep apnea screening result, cardiovascular and clotting history, and fertility interest. You don't need all of these in your log. But whatever baseline your clinic collected, copy those values and their dates in once, at the start, so later results have something to be compared with.

## What a TRT tracker app should do with all this

Whether you use a notebook, a spreadsheet, or a TRT tracker app, the requirements come out the same. Entries need a date and a time. Every number needs a unit. Lab values need a draw time. Changes should add to the history, never rewrite it. And you should be able to pull up the whole timeline, or export it, to bring to an appointment.

[OptimizedTracker](/) is built around that idea: a protocol log, lab-trend charts, and check-ins on one timeline, kept as a record you can audit. It does not suggest what to take or how much, and it is not a substitute for medical advice.

## What to actually record

For the short version, keep these fields and nothing more at first:

1. Date and time of each entry
2. The product as labeled, plus the prescriber's instruction copied as written
3. The site, if relevant
4. A short, identical check-in
5. Lab date, draw time, lab name, value and unit
6. A dated note whenever anything changes

A small log that you actually keep beats an elaborate one you abandon, which is the argument in [tracking less, more consistently](/blog/the-case-for-tracking-less-more-consistently). Start with the fields above, and add one only when you find yourself wishing you had it.