Why I Put Everything on My Calendar

Look at a normal calendar and you'll see the same three kinds of thing:

10:00  Team meeting
14:00  Dentist
19:00  Dinner

Appointments. Commitments to other people. Things with a fixed time that would cost me something if I forgot them.

That's what I used a calendar for, for years. And it's a strangely narrow slice of a day.

A day has far more than meetings in it

Between those three events, a lot actually happened. I did focused work. I went for a run. I read for twenty minutes. An idea showed up in the shower. I felt good after lunch and flat by 4 p.m. I finished something I'd been putting off.

None of that was on my calendar. It was scattered across other places:

Focused work   → a task app
The run        → a fitness app
The book       → a notes app
The idea       → wherever I could type fastest
The mood       → nowhere, usually

Each of those apps is fine on its own. But my day was shattered into pieces, and no single place held it. If I wanted to know what a given Tuesday was actually like, I couldn't — I'd have to reassemble it from five sources, and I never did.

Everything I record has one thing in common

Here's the observation that changed how I think about all of it.

I went for a run — when? I read a book — when? I worked on a project — when? I had that idea — when? I felt great — when?

Every one of those has a time attached. Not a due date, not a reminder — an actual moment when it happened.

Everything happens in time.

That sounds obvious to the point of being useless. But sit with it, because it has a consequence: if everything I might want to record already happens at a time, then a timeline is the one structure that can hold all of it. And I already have a timeline I check every single day.

The calendar isn't a schedule. It's a timeline of my life

The reframe is small and it changes everything:

Calendar = my future schedule
→
Calendar = the timeline of my life

Once it's a timeline instead of a schedule, the tense opens up. The future holds what I plan to do. The present holds what I'm doing right now. And — the part we almost never use — the past holds what I actually did.

Most people's calendars are write-once: you put a future event in, it happens, and then it's dead weight you scroll past. But the past of a calendar is the most honest record of your life you own. You just have to start treating it as something worth keeping.

Why the calendar is unusually good at this

Once I started recording more than meetings, I noticed the calendar is quietly better at it than the dedicated apps:

• every entry gets a time automatically — no field to fill in
• it has a built-in structure: day, week, month
• it's a place I already open dozens of times a day
• the past is right there, in order, whenever I want to reread it
• it's a standard format (Google Calendar), so the data is portable, not trapped

The last two matter most. A journal answers what did I write? A calendar answers something richer, almost for free:

What did I do · when I did it · and how long it took.

That's already most of a life log, and I didn't have to build a habit around a blank page to get it.

But a calendar event is too thin

This is where I hit the wall — and where, if you've read why your calendar is really a database with two columns, you know what's coming.

Say I want to record a run. On a normal calendar I get:

Running
7:00 PM – 8:00 PM

Time and a title. That's the whole schema. But what I actually want to keep is:

Running
Distance:   5.2 km
Condition:  Good
Location:   Han River
Rating:     ★★★★☆

The calendar nailed the hard part — when, for how long — and then gave me nowhere to put what it actually was. The timeline is excellent. The data model behind a single event is almost empty.

A calendar has a beautiful x-axis and no other columns.

Every kind of record hit the same wall. A work block wanted a project and a status. A journal entry wanted a mood and a highlight. A meeting wanted an outcome. The time was always easy; the meaning had nowhere to go.

What if events could carry more?

That gap is the whole reason Velprium exists.

The question I couldn't stop asking was simple: what if a calendar event could have properties, the way a Notion page does? What if "Running" could carry distance and condition, and "Deep work" could carry a project and a rating, without leaving the calendar?

So that's what I built — a layer on top of Google Calendar that lets any event hold its own properties, and then lets me filter and review across them. Not a new place to record my life. The one I already used, finally able to hold more than a title.

If it happened in time, put it on the calendar

I've stopped thinking a calendar's job is to tell me what I'm supposed to do.

A calendar can also tell you what you did, what you thought, how you felt, and — over enough time — how you actually lived.

Meetings and appointments were never the point. They were just the only things thin enough to fit in two columns. Give an event room to hold what it meant, and there's no reason to keep the rest of your life in five other apps.

Everything happens in time. So if something happened, why not put it on the calendar?

Put more than meetings on your calendar. Try Velprium →