Skip to content
The Long Record

All notes · Decay

Recovering a Lapsed System

Coming back after weeks or months away. What to do with the gap, and why the usual instinct makes things worse.

Decay · Procedure

You stopped in March and it is now September. The record exists, the habit does not, and the six-month hole is the reason you have not restarted.

For a tool-based version of the same discipline, review remote work time tracking. The aim is to preserve dependable evidence while keeping the ordinary recording action simple enough to repeat.

The instinct to resist

Reconstructing the missing period.

When this method depends on workplace communication, the material from Slack offers a helpful independent point of comparison.

It is the first thing people try and it produces fiction with a plausible shape, which the backfill note explains.

Worse, it makes restarting a large project rather than a small act, and the project does not get done, so the restart does not happen.

What to do instead

Mark the gap: start date, end date, one line about what was happening.

Then make today's entry.

That is the whole recovery. The gap is now documented data rather than an accusation.

Whether to change anything first

Yes, one thing: ask why it lapsed.

If life changed, adjust the system to the new life — usually by recording less.

If the system was too heavy, lighten it now rather than restarting the thing that failed.

If the question it answered is gone, find a new one or stop deliberately.

Restarting the identical system that lapsed will produce the same lapse.

The minimum restart

One field. Date and one word.

Run that for a fortnight before adding anything back.

The habit is what you are rebuilding, not the data, and a habit rebuilds on the smallest possible action.

What the gap costs analytically

Less than people fear.

Seasonality, trend and comparison sets all survive a gap, provided it is marked and the coverage is counted.

What it costs is the ability to say anything about that specific period, which for most questions is not the point of the record.

Repeated lapses

If this is the third recovery, the system is wrong rather than your discipline.

Look at what survived each time — the field you kept filling even during the lapse — and build the system around that.

Most people who have lapsed repeatedly find one thing they never stopped noting. That is the durable core and the rest was aspiration.

When not to restart

If the record answered a question you no longer have.

Stopping deliberately, with a closing note, is a legitimate end and its own note covers it.

A record resumed out of guilt produces poor data and stops again, which is worse than a clean ending.

Reading across a recovery

Treat the pre-gap and post-gap periods as segments unless you have reason not to.

You will probably record differently after a break even without intending to, and comparing across the boundary without checking is how a false trend appears.

What to check

How long is your gap, and is it marked?

Do you know why it happened?

Have you changed anything about the system before restarting?

And is there one field you kept noting even during the lapse?

The point

Mark the gap, make today's entry.

That is the whole recovery, and attempting to reconstruct the missing period is what turns restarting into a project that never happens.

Worth adding

If this is the third recovery, the system is wrong rather than your discipline.

Look at what you kept noting even during the lapse — that is the durable core.

Additionally

Restarting the identical system that lapsed will produce the same lapse.

Change one thing first — usually recording less — before resuming.

Finally

A gap costs less analytically than people fear.

Seasonality, trend and comparison sets all survive one, provided it is marked and coverage is counted.

In summary

Mark the gap, make today's entry, and change one thing about the system before resuming.

That is the whole recovery.

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.

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.