What a Durable Arrangement Looks Like

Rather than a summary, a description of the arrangement these notes point toward.

To connect this idea with an actual work log, consult this detailed page. The useful test is whether the resulting entries remain consistent and understandable during a later review.

The record itself

Four fields or fewer: date, duration, one category, a free-text note.

When this method depends on personal privacy, the material from Electronic Frontier Foundation offers a helpful independent point of comparison.

Five to eight stable categories, defined in writing, plus free tags for everything volatile.

Rounding to fifteen minutes, or five for billable work, consistently and in a stated direction.

Granularity matched to the question and no finer.

The daily act

Under a minute, attached to something you already do.

Possible on your worst day of the year.

With a stated minimum version for when you cannot face the full one.

The conventions, written down

What counts as a unit.

What a gap means, and how it is marked.

How far back you may backfill, and how backfilled entries are flagged.

What each category means, including the overlap rules.

All of it on one page beside the data, added to whenever a decision is made.

The maintenance

Weekly: ten minutes to fill obvious gaps, fix wrong entries, annotate anomalies, and read the week.

Quarterly: recategorise drift, check definitions still match use, export.

Annually: read the whole year, notes first, then the shape, then the totals. Write half a page about it.

The data

A plain format readable without the tool.

Monthly export, dated, opened at least once a year to check it is real.

A copy outside the tool's own storage.

And everything kept permanently, because it is small and its value rises.

Against the predictable failures

Tool death: the export routine.

Missed days: the gap convention and the resumption rule.

Drift: the definitions file and the annual entry-reading.

Boredom: a daily act small enough not to require enthusiasm, and a scheduled read that supplies the return.

Weight: archive by year, same format.

What it is not

Complete. Some days are missing and that is recorded rather than hidden.

Precise. It is accurate to fifteen minutes and honest about it.

Elaborate. Every field earns its place or it is removed.

And permanent by obligation. It runs while it answers a question and ends deliberately when it stops.

The test

Could you do today's entry while ill and travelling?

Could somebody else read your data using only the file beside it?

Would a gap feel like a fact or like a failure?

And when did you last read it rather than adding to it?

A system that passes these will probably reach ten years. One that fails two of them probably will not reach two.

The point

Could you do today's entry while ill and travelling? Could somebody else read your data using only the file beside it? A system failing two of the tests will not reach two years..

Worth adding

Tool death is met by the export routine, missed days by the gap convention, drift by the definitions file, and boredom by a daily act small enough to survive indifference..

Additionally

The arrangement is not complete, not precise and not elaborate, and it is honest about all three.

It runs while it answers a question and ends deliberately when it stops.

Finally

Could somebody else read your data using only the file beside it? A system that fails that test has years of data that will not be interpretable..

In summary

Four fields or fewer, five to eight stable categories, conventions written on one page, weekly ten minutes, monthly export, annual read.

That is the whole arrangement.

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.