I build Pinwise, which imports labs and charts them, so I am not neutral. This page is about keeping your results organized and comparable. It does not tell you what any number means for you, or what to change because of it. That conversation belongs with whoever ordered the test.
Why one result tells you less than you think
A single draw is one moment. Plenty of markers move around from day to day for ordinary reasons, so one high or low number on its own is hard to read. Three or four draws taken under similar conditions are a different thing. Now you can see a direction, and you can line it up with what was going on in your log at the time.
That is the whole idea of this page. Make each draw as comparable to the last one as you can, write down the context, and lay the results out so the trend is easy to see.
Reference ranges belong to the lab, not to you
The range printed next to each result is the lab's range. It usually comes from a reference population the lab tested, and it can differ from one lab to another for the same marker. A few things follow from that.
- An H or L flag means outside that lab's range. It is a prompt to ask a question, not an answer by itself.
- Inside the range is not a verdict either. Ranges are wide, and your clinician may care more about where you sit inside it, or how far you moved since last time.
- Switching labs can shift the range. If you change labs, copy the new range down with the new result instead of reusing the old one.
The practical rule: always log the range that was printed on that report, next to the number, every time. A result without its range is half a record.
Watch the units
This one catches people. Two labs can report the same marker in different units, and the numbers look nothing alike. A couple of common examples:
| Marker | One lab reports | Another reports | To convert |
|---|---|---|---|
| Total testosterone | ng/dL | nmol/L | ng/dL divided by 28.84 gives nmol/L |
| Glucose | mg/dL | mmol/L | mg/dL divided by 18 gives mmol/L |
| Cholesterol | mg/dL | mmol/L | mg/dL divided by 38.67 gives mmol/L |
Conversion factors are marker specific. Use the one for the exact marker, and when in doubt, keep each result in the units the lab printed and note the unit beside it.
If a result suddenly looks wildly different from last time, check the unit before you check anything else. Nine times out of ten that is the whole story.
Make each draw comparable
You cannot control everything, but you can keep the easy things the same from draw to draw.
- Same lab when you can. Fewer changes in method, range and units.
- Same time of day. Some markers are known to vary across the day. Early morning every time is the simple habit.
- Same fasting state. Fasted or not, pick one and stick to it, and write down which.
- Same point in your schedule. Note how many days it had been since your last injection, and where you were in a cycle. Drawing on day 2 one time and day 6 the next makes the two hard to compare.
Which of these matter most depends on the panel, so it is worth asking whoever orders your labs what they want held constant.
What to write down at every draw
The numbers come on the report. The context does not, and it is the part you will not remember in three months.
- Date and time of the draw, and which lab.
- Fasted or not.
- Days since your last injection, and the day of the cycle if you run one.
- What your protocol was at the time, and when it last changed.
- Anything out of the ordinary that week. Sick, a hard training block, travel, bad sleep, a new supplement or medication.
- Who ordered it and why, if it was a specific question.
Lay it out so the trend is visible
The format that works for me is one row per marker and one column per draw, with the context rows across the top. Something like this, with your own numbers filled in:
| Draw 1 | Draw 2 | Draw 3 | |
|---|---|---|---|
| Date, time, lab | Mar 4, 7:40am, Lab A | Jun 2, 7:55am, Lab A | Sep 1, 7:30am, Lab A |
| Fasted | Yes | Yes | Yes |
| Where in schedule | Before starting | Week 8, 3 days after last pin | Week 4 off |
| Protocol note | Baseline | Changed May 10 | Run ended Aug 4 |
| Marker, unit | value (range) | value (range) | value (range) |
| Marker, unit | value (range) | value (range) | value (range) |
The dates and notes are placeholders to show the layout. They are not a suggested schedule.
Read it left to right. Look for a direction across several draws rather than one jump. And keep the protocol notes on the same page, because a trend with no timeline next to it is just a list of numbers.
One caution I try to hold myself to: lining a change up with a date is not the same as knowing what caused it. The timeline is something to bring to your clinician, not a conclusion to draw on your own.
A baseline is the draw you will wish you had
If you are about to start something new, the most useful result you can have later is the one from before you started. Without it every later number has nothing to be compared to. If you missed it, the next best thing is to start the habit now and keep the conditions steady from here.
What to bring to the appointment
- The trend layout above, with ranges and units on every result.
- Your protocol history with the dates it changed.
- The specific questions you want answered, written down before you walk in.
A clinician can do a lot more with a clean timeline than with a stack of PDFs and a rough memory of when things changed.
How Pinwise does it
I built lab imports with trends into Pinwise because my own results lived in a pile of PDFs with no link to what I was running at the time. In the app they sit next to your dose history and your cycles, so the timeline is already there when you look at a trend. Lab imports are part of the free tier, along with all the tracking, and it all stays on the device. There is no account, and the App Store privacy label reads Data Not Collected.
If you use the AI advisor in Pro, it can read your own records back to you, with your own key. I wrote more about what that means for your data. It is iPhone only for now. If you run cycles, the cycle tracking guide covers how to keep the protocol side of this timeline straight.