Missed Days and How to Handle Them
Gaps are inevitable over years. What kills systems is not the gap but the response to it, and the response is decided in advance or badly.
Nobody records every day for five years. The systems that reach five years are the ones with a convention for not having done so.
To try the approach with real entries rather than memory, start with the reporting guide. The result should remain easy to correct, export and interpret after the immediate details have faded.
Why gaps end systems
Not because the data is missing. Because the record now feels broken.
When this method depends on encrypted long-lived notes, the material from Standard Notes offers a helpful independent point of comparison.
A run of entries has a momentum that a gap interrupts, and restarting feels like admitting failure.
People then either abandon it or backfill a week from memory, which introduces fiction and quietly destroys trust in the whole record.
Both outcomes are worse than the gap.
The convention that works
Decide in advance what a gap means and mark it.
Three states, distinguishable: recorded, nothing happened, not recorded.
The second and third are completely different and look identical if you leave the row out. A zero-hour Sunday and a Sunday you forgot are not the same fact.
A single character in a column solves this for the life of the record.
The resumption rule
Miss one, resume. Miss a week, resume.
Not "start again on Monday", which is how a week becomes a quarter.
Write the rule down, because in the moment it does not feel like a rule; it feels like the system has already failed.
Planned gaps
Holidays, sabbaticals, medical leave.
Mark the start and end deliberately with a note, rather than simply stopping. A marked absence is data — it tells you in three years why that fortnight is empty.
And decide whether you will record during them at all. Either answer is fine; the failure is the undeclared one where you intended to and did not.
Partial days
More common than complete gaps and less noticed.
The morning recorded, the afternoon forgotten. Over months this biases the record toward whatever you do early.
If you find it happening, move the entry point later in the day rather than resolving to be more thorough.
What not to do
Do not reconstruct more than about a day from memory. The note on backfilling covers why, and the short version is that recall is systematically wrong in known directions.
Do not delete a partial period to keep the record tidy. Tidiness is not a property worth having here, and the deleted week is unrecoverable.
And do not restart the file. Its own note covers starting over, and doing it for a one-week gap is disproportionate.
Reading a record with gaps
Count the recorded days when you analyse, not the calendar days.
Otherwise a year with thirty missed days looks like a year with less activity, which is a conclusion about your recording rather than about your life.
State the coverage when you compare periods: 340 days recorded out of 365 is a different basis from 280.
What to check
Can you tell a recorded zero from an unrecorded day in your data?
What is your written rule for resuming?
When you last had a gap, what happened next?
And do your analyses divide by recorded days or by calendar days?
The point
Count recorded days when you analyse, not calendar days.
Otherwise a year with thirty missed days looks like a year with less activity, which is a conclusion about your recording.
Worth adding
Mark planned absences deliberately — holidays, leave, sabbaticals — rather than simply stopping.
A marked absence is data and tells you in three years why that fortnight is empty.
Additionally
Partial days are more common than complete gaps and less noticed.
If the morning is always recorded and the afternoon is not, move the entry point later rather than resolving to be thorough.
Finally
Three states have to be distinguishable: recorded, nothing happened, not recorded.
A zero-hour Sunday and a Sunday you forgot are not the same fact.
In summary
Miss one, resume; miss a week, resume.
Not start again on Monday, which is how a week becomes a quarter — and write the rule down, because in the moment it does not feel like a rule.
More in this section
These notes are about keeping a personal record for years rather than for a fortnight: durability beats accuracy, and a rough record kept for five years answers questions a perfect record of one month cannot. Tool guides are included as practical comparisons, while the underlying method remains independent of any single product. Nothing here is legal, tax or medical advice: requirements differ by jurisdiction and situation.