Keep a running log of your day (Daily Log)

TL;DR

Start each day with a reflection template inside a single “Daily note,” then append entries as the day progresses.

Briefing Cornell Notes

Briefing

A practical daily-note system centers on keeping a running log of what happens throughout the day—capturing reflections, ideas, messages, meetings, personal moments, and tasks in one continuously linked page. The payoff is simple: it turns everyday activity into a searchable timeline that can be revisited months later to understand patterns, track where ideas came from, and quickly reconstruct what mattered.

The workflow starts with a “Daily note” template that begins in the morning with a daily reflection section. From there, new entries get added as the day unfolds. When an idea strikes—like a great side-project concept during a dog walk—the system records it as a dedicated “side project idea” note. Because the idea note is linked back to the daily log, it becomes easy to trace the origin of that thought. Over time, the growing list of linked ideas lets someone look back and see how often inspiration arrived during specific moments (for example, dog walks).

As the day continues, routine work gets captured in the same structure. Slack checks and message responses can be logged as a straightforward entry. Meetings are handled with extra care: instead of cluttering the daily note with attendee details, the log can create a separate “backbench” note tied to the meeting. That meeting note includes the calendar invite and becomes the place for live notes—discussion points, follow-ups, and action items. If the meeting involves particular people, those linked notes also let the user pull up everything connected to an individual later.

Social and personal details follow the same logic. A lunch with Alex McCall at Black Belly Butcher can be saved as a restaurant note, marked with location context (Boulder, Colorado) and a quick recommendation (a “10 out of 10” prime rib sandwich). The result is a personal knowledge base that makes future recommendations effortless.

Finally, the system closes with a to-do list. Simple items can stay inline, while complex tasks—like starting taxes—can be broken out into their own linked notes. The overall structure emphasizes a “bottom-up” approach: build the day as a sequence of linked notes rather than forcing everything into one static page. Instead of tracking exact timestamps, the method favors a running log that still preserves enough context to recall what was happening—so a year later, today’s entries provide a clear snapshot of where time went and what decisions or ideas emerged.

Cornell Notes

The core idea is to maintain a single daily log that grows throughout the day, with entries linked to separate notes when they deserve their own space. Morning starts with a daily reflection template. As events happen—dog walks, Slack work, meetings, meals, and tasks—each item becomes either an inline entry or a linked note (like a side project idea or a meeting backbench note). Meetings can store action items and discussion details without cluttering attendee lists, and linked notes make it easy to revisit everything tied to a person. The system matters because it creates a searchable timeline: months later, it’s possible to reconstruct what happened and trace where ideas came from, even without exact timestamps.

How does a running daily log help someone capture ideas in a way that’s useful later?

When an idea appears during a specific moment (for example, a dog walk), it gets recorded as its own “side project idea” note and linked back to the daily log. Over time, the daily log accumulates multiple idea notes, each tied to when and where inspiration occurred. That linkage makes it possible to look back a year later and see patterns—such as how many side-project ideas were sparked during walks—rather than having scattered, untraceable notes.

What’s the advantage of creating a separate note for meetings instead of stuffing everything into the daily page?

Meetings can be logged by clearing attendee details from the daily note while creating a “backbench” meeting note linked to the calendar invite. That meeting note becomes the workspace for live notes: discussion topics (such as growth related to Reflect), follow-ups, and action lists (like following up with Alex and Kyle about a growth idea). Linked meeting notes also let someone pull up all related notes for a specific individual later.

How does the system turn everyday personal recommendations into reusable information?

A lunch can become a structured restaurant note. For example, a meal at Black Belly Butcher can be saved with metadata like “restaurant,” the location (Boulder, Colorado), and a quick recommendation (“prime rib sandwich” rated “10 out of 10”). Later, returning to that note or sharing it with someone provides immediate, context-rich suggestions without rewriting details from scratch.

When should tasks be kept inline versus split into linked notes?

Simple items can remain in a general to-do list at the end of the day. More complex work—like starting taxes—can be split into its own linked note. This keeps the daily log readable while still giving complicated tasks a dedicated space for deeper planning and tracking.

Why does the approach work even without tracking exact times for each event?

The method favors a running log that records events in sequence rather than requiring precise timestamps. Even if exact timing isn’t captured, the linked structure preserves enough context to reconstruct the day later—what happened, what was discussed, what ideas emerged, and what actions were planned.

Review Questions

In what ways does linking a “side project idea” note to the daily log improve recall compared with writing the idea in a standalone document?
How would you structure a meeting entry so it supports both action tracking and later retrieval by person?
What criteria would you use to decide whether a task belongs in the end-of-day to-do list or in its own linked note?

Key Points

1
Start each day with a reflection template inside a single “Daily note,” then append entries as the day progresses.
2
Record spontaneous ideas as dedicated notes (e.g., “side project idea”) and link them back to the daily log for later tracing.
3
Log routine work like Slack responses as simple entries, keeping the daily page readable.
4
For meetings, create a linked “backbench” note tied to the calendar invite and store discussion details, follow-ups, and action lists there.
5
Save personal moments (like meals) as structured linked notes with location and a short recommendation to make future suggestions effortless.
6
Keep simple tasks in an inline to-do list, but split complex tasks (like taxes) into linked notes for deeper follow-through.
7
Use a running, sequential log rather than exact timestamps to preserve context while reducing overhead.

Highlights

A dog-walk idea becomes a linked “side project idea” note, letting future-you trace inspiration back to the moment it happened.

Meeting notes can live in a separate backbench note tied to the calendar invite, keeping the daily page clean while preserving action items.

Lunches can be converted into restaurant notes with location and a quick rating, turning personal preferences into reusable recommendations.

Complex tasks get their own linked notes (like taxes), while small tasks stay in the end-of-day to-do list.

The system’s timeline-style structure makes it possible to reconstruct a day months or even a year later without relying on exact timestamps.

Topics

Daily Logging
Linked Notes
Meeting Backbench Notes
Idea Capture
Task Management

Mentioned

Alex McCall
Alex
Kyle