A protocol tracker is most useful when it records decisions without silently changing history. The goal is not to decide what someone should take. The goal is to preserve the user-defined plan and create a separate record of completed, skipped, or changed actions.
Record the plan in clear fields
- A user-defined protocol name and peptide label
- The user-entered amount and its unit
- The intended recurrence or selected days
- The planned start date and optional end date
- Any user-entered timing or administration notes
- Whether the protocol is active, paused, or ended
Structured fields make a record easier to review than one long note. Keep units attached to values and avoid abbreviations that may be unclear later.
Separate the plan from the history
A scheduled action says what was planned. A completed record says what the user logged as having happened. These are different facts. Marking an item complete should create a timestamped record rather than rewriting the original schedule.
- Due means the action is scheduled but has not been logged as completed.
- Taken means the user recorded a completed action.
- Skipped means the user intentionally recorded that the scheduled action did not occur.
- Missed means the scheduled time passed without a completed or skipped record.
Preserve changes instead of erasing them
When a user changes a schedule, the new plan should apply going forward while completed history remains attached to its original timestamps. Pausing or ending a protocol should not delete prior records. Corrections should be visible as corrections rather than indistinguishable replacements.
Keep vial and administration-site context auditable
A tracker can associate a completed entry with a user-selected vial and administration site. That context helps the user review inventory and rotation history, but it does not establish that a particular vial, route, site, or technique is appropriate.
Treat reminders as prompts, not proof
A delivered notification only shows that a reminder was sent to a supported subscribed device. It does not prove that the user saw it or completed the scheduled action. Completion should require an explicit user record.
Review the record with visible coverage
A weekly review should identify how many days or scheduled actions contain data. Percentages are easier to interpret when the underlying coverage is visible. Missing records should remain missing rather than being treated as positive or negative outcomes.
- Review completed, skipped, missed, and upcoming actions separately.
- Check whether units and timestamps are consistent.
- Keep observations separate from conclusions about effectiveness.
- Export or share records with a qualified professional when appropriate.