Baxnet Ideas · Founder note
Your Calendar Is a Diary Written in Advance
TL;DR: A calendar can tell you where you expected to be. It cannot tell you whether you went, what happened there, or why the plan changed.
Take an ordinary week from a few years ago.
Monday morning contains a run. Wednesday has a dentist appointment. Thursday evening is dinner with somebody whose name you have not seen for a while. Friday begins with a flight.
On the calendar, all four events look equally real. Each has a title, a time and a rectangle of colour.
But perhaps the run was slept through. The dentist moved the appointment by a week. The dinner happened and changed the course of the month. The flight remained in the calendar after the trip was cancelled.
The old week looks like a record of what happened. It is actually a record of what, at various moments, somebody thought was going to happen.
That makes the calendar a peculiar kind of autobiography. Most diaries are written after the event. A calendar is written before it.
The Accidental Autobiography. This is a series about the partial biographies hidden inside ordinary personal data.
The future tense of a life
We put things in calendars because memory is unreliable and the future requires coordination. A calendar carries obligations, invitations, hopes, travel buffers, birthdays, deadlines and recurring instructions to become a slightly more organised person next Monday.
Researchers call part of this prospective memory: remembering an intention at the appropriate moment. In a survey and diary study of reminder use, people described using digital calendars for appointments, medication and other future activities. They also described the obvious failure mode. Sometimes they forgot to look at the calendar. Notifications could be ignored when life was busy.
This sounds mundane, but it fixes the meaning of the record. Dentist — 11:00 is first an attempt to help a future person arrive somewhere. It is not a receipt issued afterwards to prove that they did.
The difference is easy to lose once the date has passed. A calendar interface keeps moving forward. Future plans become old blocks, and old blocks acquire the visual authority of history. There is rarely anything on the screen to distinguish the meeting that happened from the meeting everybody forgot.
Even a confirmed event is not a completed event.
The underlying calendar standard is more careful than our memories of the interface. RFC 5545 allows an event to be tentative, confirmed or cancelled. It also defines when calendar information was created or last modified, and a sequence number for significant revisions made by an organiser.
Those distinctions are useful, but still narrow. A last-modified date says that the stored information changed, not what the previous plan was. A revision number helps calendar systems recognise a newer version; it does not explain why the dinner moved. And a confirmed event was definite when scheduled. The standard does not claim that everybody arrived, stayed, enjoyed it or left as the person they had been before.
Recurrence is not repetition
Recurring events create an even better accidental portrait.
Every Tuesday at seven: gym. Sunday evening: call Mum. The first working day of the month: review finances. Friday afternoon: two hours marked FOCUS with an optimism that deserves some respect.
Read carelessly, this is a list of habits. Read accurately, it is a list of recurring intentions.
Some will have become real routines. Others were ignored for six months because deleting the series would have felt too much like admitting defeat. The gym slot may describe a disciplined athlete, an aspirational athlete, or somebody who attended regularly until an injury they never wrote in the calendar.
The recurrence still tells us something. It shows what a person wanted to protect from the rest of the week. It may reveal the version of themselves they were repeatedly trying to make room for. That is meaningful evidence, just not evidence of attendance.
Absence is equally slippery. A nearly empty calendar might belong to somebody with a quiet life. It might also belong to somebody whose days are governed by childcare, shift work, caring for a parent or constant requests that never arrive as formal invitations. A crowded calendar can indicate opportunity, obligation, bureaucracy or an inability to say no.
The blocks are real. The biography we attach to them remains provisional.
The record needs another verb
A personal intelligence engine should not flatten all of this into a timeline headed Things You Did.
It needs more verbs: planned, invited, accepted, moved, cancelled, perhaps attended, perhaps remembered. Some of those can come from the calendar. Others may be supported by another trace, such as a ticket, photograph or message, where the person has chosen to connect them. The most important may need a simple question: did this happen, and did it matter?
That is not a demand to preserve every revision of every dentist appointment forever. Most changes are ordinary administration. It is a design principle: do not silently promote an intention into a fact just because its start time is now in the past.
The more interesting possibilities begin once that distinction is protected. A person might notice that the work they claim to value is always the first thing moved. They might rediscover a monthly dinner that quietly held a friendship together. They might see that a frightening appointment occupied three rescheduled blocks before it became one lived morning.
Those are not insights a calendar can declare on its own. They appear when the plan is allowed to meet the person’s account of what happened.
An old calendar can answer a question that most diaries cannot: what did I believe my life was going to be?
Sometimes the answer is close to what occurred. Sometimes it is a record of optimism, avoidance, duty and contingency. Both versions belong to the autobiography. They just should not be mistaken for the same one.
Further reading: RFC 5545: Internet Calendaring and Scheduling Core Object Specification and How to Remember What to Remember: Exploring Possibilities for Digital Reminder Systems.