Missed dose log: what to record when you miss an entry

A missed dose log is still a log. When you skip an entry, or an entry covers something that did not happen, write down the gap itself, the time you are writing it, and which details you know versus which you are estimating. Do not leave a blank, and do not reconstruct the day from memory and present it as fact.

This article is about record-keeping only. What to do about the item you missed is a question for your prescriber or pharmacist. A log cannot answer it, and nothing here should change what you do.

Keep the gap visible#

A blank row is ambiguous. Six months later, you cannot tell whether it means "nothing happened," "I forgot to write it down," or "I skipped it on purpose." Three different facts.

So add an entry for the missing day. Give it a short status in plain words:

• No entry made: you do not know what happened, or you did not write it down at the time.
• Not done: you know the planned item did not happen.
• Unknown: you are not sure which of the two it was.

Pick your wording once and reuse it. Consistent labels matter more than clever ones, a point the piece on tracking less, more consistently makes about the whole habit. A short, honest gap entry beats a long entry you had to invent.

Two times, not one#

Every late entry has two timestamps. The event time is when the thing happened, if you know. The writing time is when you typed it. Keep both, because only the second one is certain.

| Field | What to write | Example | | --- | --- | --- | | Event date | The day it applies to | Tuesday, Oct 21 | | Event time | Your best knowledge, or "unknown" | "Morning, exact time unknown" | | Written on | The real date and time you are typing | Thursday, Oct 23, 8:10 PM | | Status | One of your three labels | Not done |

If you travel, the writing time should carry a time zone. The note on timestamps that survive travel covers why a bare clock time can mislead you later.

Mark what you know and what you estimate#

Inside a late entry, label each detail as known, estimated or unknown. A short prefix is enough: "known," "est." or "unknown."

Use "unknown" instead of a plausible guess. A guess that looks like data is harder to spot than an empty field. If you recorded a number at the time, it is known. If you are recalling it two days later, it is an estimate, even when you feel sure.

And don't overwrite the original gap. Add the late entry next to it, so the history shows that the gap existed and when it was filled. The principles in a peptide log you can actually trust apply here: the value of a log is that you can tell what was written when.

Why memory is a weak substitute#

It's tempting to fill in a missed entry from memory. The research on diaries says memory is useful, but not exact.

One study compared daily adherence diaries with a recall report three months later. Agreement was substantial, with a weighted kappa of 0.64, yet about one in four participants reported inconsistently. Agreement was lowest, 46.2%, among people whose diary showed exactly one missed item. A single gap is the hardest thing to reconstruct from memory. The same paper notes that some participants may have completed their diaries in batches, which the authors name as a source of misclassification.

A second study followed 95 women who rated symptoms daily for four weeks. Their seven-day recall ratings ran higher than the average of their daily ratings, and the gap widened in weeks when symptoms were changing.

These are different populations and different questions from a personal protocol log, so read them as a reason for caution, not a measurement of your own memory. Individual variation is real. The practical point is narrow: the sooner you write an entry, the less your memory has to do.

How gaps change the way you read the log later#

Gaps are not random noise. In a 30-day online diary study with 371 participants, completion dipped on Fridays and Saturdays and declined over the month. The authors concluded the missing days did not meet the standard of being missing completely at random, and that missingness related to the behavior being tracked in one of the measures.

For a personal log, that suggests two habits:

• Note the reason, if you know it. "Traveling," "busy week," "phone died" is enough. It lets you see later whether gaps cluster around certain days or situations.
• Do not read a trend straight across a gap. If three days are missing, a line connecting day 4 and day 8 draws a smooth slope that you never observed. Mark the break instead. The approach in turning daily check-ins into signal is to read a sparse log as sparse, not as a smooth curve.

A log with honest gaps is more useful than one that looks complete but is partly reconstructed. When you review your history, the labeled gaps tell you exactly which stretches to trust and which to read with care.

What to actually record#

When you notice a missed entry, write this, in this order:

1. A gap entry for the day, with one of your three status labels.
2. The real date and time you are writing it, with time zone.
3. The details you know, marked known, and the details you are recalling, marked est.
4. "Unknown" for anything you cannot support.
5. A short reason, if you have one.
6. A note to raise the item itself with your prescriber or pharmacist, if that applies to you.

Keep it short. A two-line gap entry that you actually write is worth more than a detailed form you avoid filling in. If a template makes this feel heavy, simplify the template, not the habit. OptimizedTracker can hold these fields, but a notes app works too. For a wider view of keeping a record you can check months later, see how to organize a protocol you can actually audit.