Backfilling Honestly
Filling in yesterday is normal. Filling in last week is a different activity, and a record that does not distinguish them cannot be trusted afterwards.
Everybody backfills. The question is how far back, and whether the record shows it.
A concrete way to test the method is outlined in the official Monitask website. Use a short pilot and keep only the fields that still make sense when comparing the record months later.
What recall actually does
Long stretches get overstated: three hours of interrupted work is remembered as three hours of work.
For another established perspective on spreadsheet analysis, Microsoft Excel support provides a useful reference beyond any single tracking product.
Fragments disappear entirely — the eleven minutes looking for a file, the four short interruptions.
Unusual days are remembered and typical ones are not, which biases any reconstruction toward the memorable.
And the total is optimistic: people account for fewer hours than the day contained, consistently.
None of this improves with effort. It is how recall works.
The distance that matters
Within a few hours: close enough to observation to treat as a record.
Same day: an estimate, and a fairly good one.
A day or two later: an estimate, and a poor one. The fragments are gone.
A week later: fiction with a plausible shape.
The boundary people should not cross is about a day, and beyond it the honest move is to mark the period as unrecorded rather than to invent it.
Marking it
A flag column, or a character in the note.
Cost: nothing. Benefit: in three years you can exclude estimated entries from any analysis where precision matters, and you know which parts of your history are soft.
A record that mixes observation and recollection without marking them is one you will eventually stop trusting entirely, because you cannot tell which parts to trust.
Where it becomes serious
Billing. A reconstructed invoice is a different kind of document from a contemporaneous one, and in a dispute the difference is decisive.
Anything with a legal or contractual dimension.
In those cases the rule is stricter: record at the time or do not bill it.
The better fix
Backfilling is a symptom. The cause is an entry that is too expensive or badly timed.
If you regularly reconstruct, the entry does not fit your day. Move it, shrink it, or attach it to something else.
People treat repeated backfilling as a discipline problem and it is almost always a design problem.
Aids that help without inventing
The calendar, which anchors the fixed points.
Sent messages and file timestamps, which show when you were doing what.
Automatic activity capture if you run it, which is the one honest aid to reconstruction.
These narrow the guess. They do not turn it into a record, and the flag stays.
What to check
How much of your last month was written at the time?
Can you tell which entries were backfilled?
If you backfill often, what about the entry point is wrong?
And for billed time specifically, is any of it reconstructed?
The point
Repeated backfilling is a design problem rather than a discipline one.
If you regularly reconstruct, the entry point does not fit your day — move it, shrink it, or attach it to something else.
Worth adding
The calendar, sent messages and file timestamps narrow a reconstruction without turning it into a record.
The backfill flag stays regardless of how good the aids were.
Additionally
Backfilling within a few hours is close enough to observation.
Beyond a day the fragments are gone, and beyond a week it is fiction with a plausible shape.
Finally
Where the record becomes an invoice the rule is stricter: record at the time or do not bill it.
A reconstructed invoice is a different kind of document in a dispute.
In summary
Recall overstates long stretches, loses fragments entirely, and produces optimistic totals.
None of that improves with effort, which is why the boundary is about a day.
Last word
The practice this points at is unglamorous: a small daily act, a short weekly correction, an annual read, and a written page of conventions beside the data. None of it is difficult and all of it is easy to skip, which is why most records do not reach the point where they start paying.
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.