Keep a useful record of an existing protocol

A useful log answers a small set of questions: what was recorded, when it happened, and what context was saved alongside it. The record can be useful even when it cannot tell you why something changed.

Separate the plan from the actual entry

Your schedule describes a plan you already have. Your history describes what actually happened. Recording a different time or amount does not make the log less useful. It makes the difference visible.

• Keep the compound name and amount exactly as entered, with its unit.
• Record the actual date and time, including when an entry is added later.
• Keep an injection site with the entry when relevant.
• Leave a value missing when it is not known, rather than filling it from a community reference.

Give each kind of data its own context

A saved dose, a wearable measurement and a laboratory result are different records. Their source, date and unit matter. Keep a lab's reference range with its result instead of treating a number without context as a conclusion.

Read a timeline as a timeline

Placing a wearable reading beside a logged entry helps you find dates and observations. It does not isolate a cause. Changes in sleep, training, measurement conditions and other factors may occur at the same time.

A useful question for the log is, 'What did I record during this period?' A different question is, 'What caused this change?' A personal tracking chart cannot settle the second question on its own.

Keep a copy you can use

Periodically export your records and check that dates and units are understandable outside the app. When sharing a report, include enough context for the reader and choose deliberately who receives access.