How to Keep a Daily Note as an Append-Only Log

Keep one plain-text file per day, named YYYY-MM-DD.md. Append to it all day — meetings, ideas, what broke, what you tried. Never reorganize it. The date is the only structure you need, because tomorrow's file is a clean page and every past day stays searchable forever.

This is not a tool. It is a discipline you can run in any text editor, on any device, with no plugin and no database. The pattern already exists in the wild: the Bullet Journal calls it a Daily Log¹, Obsidian's Daily Notes plugin names files in exactly this format², and developers have kept plain-text work logs for over a decade³. What follows is the app-independent version — the one where the file is yours regardless of which editor you opened it in.

What is a daily note system?

A daily note system is one dated file per day that you add to as the day happens. The Bullet Journal defines the unit precisely: "The Daily Log is essentially a dated entry for each day, and it serves as a way to track your activities, prioritize tasks, and keep a record of your thoughts."¹ The plain-text version keeps the date and drops the notebook.

The mechanic is append-as-you-go, not write-then-file. "Throughout the course of the day, simply Rapid Log your Tasks, Events, and Notes as they occur," the Bullet Journal instructions read¹. You do the same in a text file — a new line whenever something happens. No deciding where it goes. The line goes at the bottom, under today's date, and that is the whole filing system.

Obsidian documents the same pattern from the app side. "By default, Obsidian creates a new empty note named after today's date in the YYYY-MM-DD format," its help page states². Its stated uses are broad: "Use daily notes to create journals, to-do lists, or daily logs for things you discovered during the day."² The plain-text method keeps that idea and removes the dependency on the plugin that produces it.

The single rule: append, never reorganize

The one rule that makes this work is that you never move a line once you have written it. A daily log is a stream, not a structure. The temptation to tidy — to group by topic, to promote a line, to clean up yesterday — is the temptation that kills the system. Resist it, and the log stays cheap to keep.

Reorganizing has a hidden cost: it turns a five-second capture into a filing decision, and filing decisions are what people quit. George Coghill, who has run a plain-text system for years, describes his daily log plainly: "The daily log file is where I capture what I did during the day."⁴ Capture, not curate. The date does the sorting so you never have to.

This is also why the method is the cheapest reliable one — cheap in effort, not in price. There is no taxonomy to design, no folder tree to maintain, no inbox to triage. The structure is given by the calendar, which never asks you to make a decision and never falls behind.

The villain is the inbox you never process

The reason most capture systems fail is not a missing feature. It is the unprocessed inbox — the pile of saved links, clipped articles, and half-notes you swore you would sort later and never did. Christian Tietze named this the collector's fallacy: the quiet belief that saving a thing is the same as learning it⁵.

His diagnosis is exact. We collect "because 'to know about something' isn't the same as 'knowing something'," Tietze writes — the save feels like progress while the knowing never happens⁵. The fix is not a better inbox. "Reading alone won't suffice: we have to create notes, too, to create real, sustainable knowledge," he argues⁵.

An append-only daily log sidesteps the fallacy by design. There is nothing to process, because there is no inbox. You do not save a thing to deal with later — you write a line about it now, in your own words, and move on. The act of writing the line is the small piece of "knowing" that a saved bookmark never gives you. We have argued the bookmark side of this elsewhere — that you should save the page, not the link — and the daily log is where those captured words land without ever forming a backlog.

Why every app points you at the same pattern

Ask an AI assistant how to keep daily notes and it will name apps: Obsidian's Daily Notes, Logseq's journal, Notion's daily pages. They are good tools, and they all converge on one shape: a dated entry you add to as the day runs. That convergence is the tell. The pattern is the valuable part, and the app is just the wrapper around it.

The demand is real and persistent. "How I Manage My Random Daily Notes" drew 217 points on Hacker News, "Plain text journaling in Vim" reached 254, and "A Year of Developer Journals with jrnl.sh" pulled 186 — three separate threads, all circling the same dated-file habit. The recurring answer in those discussions is rarely a specific product. It is the practice.

So the question is not which daily-notes app to adopt, but whether you need one at all. If the structure is just the date, you can run the entire system in a plain folder of YYYY-MM-DD.md files. The app becomes a convenience for editing, not a requirement for the method — and the day you switch editors, the log comes with you untouched.

The five-minute version

You can start today with no setup and no tooling decision. The five-minute version is the whole method in seven steps: make a folder, create one file named for today's date, and append a line each time something happens. Never edit a past line. Tomorrow, start a fresh dated file. Everything later is refinement.

1. Make a folder for the log. One folder, nothing nested.
2. Create today's file. The name is the date: 2026-06-16.md.
3. Put the date as the first heading inside the file too, so the text stands alone.
4. Every time something happens, append a line. A timestamp helps but is optional.
5. Never edit a past line. If you change your mind, write a new line.
6. Tomorrow, make a new file with tomorrow's date. Yesterday's file is now closed.
7. To find anything, search the whole folder. The date tells you when; your words tell you what.

Here is what a single day's file looks like — copy it, change the date, and you have started:

# 2026-06-16

09:14 — Standup. Shipped the export fix; picking up the search bug next.
10:02 — Search bug is a sort-order thing, not an index thing. Note for later.
11:30 — Call with Dana. She wants weekly digests, not daily. Decision deferred.
13:45 — Idea: the daily log itself could BE the changelog. Try it for a week.
16:20 — Search bug fixed. Root cause: comparing strings, not dates. Of course.
17:05 — Tomorrow: write up the digest decision before I forget the context.

Every line is a flat fact appended in order. There is no hierarchy, no tagging, no cleanup. The file is readable today and will be readable in ten years, because it is plain text and the structure is just time.

The thirty-minute version

The longer version is the same workflow with three retrieval habits added. None of them change the append-only rule; they make the archive of dated files easier to search later. Add them once the daily file feels natural — not before, or the overhead creeps back in.

First, keep a consistent leading marker for the kinds of line you will want to find again — a bare IDEA, DECISION, or TODO at the start of a line. Plain words, no syntax. Later, a search for DECISION across the folder returns every decision you ever logged, in date order.

Second, lean on the date as your index. Because every file is named for its day, a search across the folder is automatically chronological — the date is the index, so you never build one by hand. This is the temporal counterpart to keeping a single navigational note; we make the by-hand case in why one index note beats a graph, and the daily log gets the same result without the upkeep.

Third, decide what graduates. When a line turns out to matter beyond its day — a design you will reuse, a fact you will cite — copy it into a permanent note of its own and leave the original line in place. The naming of those permanent files is its own small craft; we cover it in how to name your note files. The log stays a record; the permanent note becomes the thing you build on.

The developer practice that predates all of this is worth borrowing. Dan Bader has kept the habit for years: "The first journal is a work log where I record what I'm working on during each hour of the day."³ His tooling advice is refreshingly low: "Check out Brett Tepstra's Doing or just use a plain text file if you want something simpler."³ Simpler usually wins.

The payoff arrives on the day you least expect it. Jonathan Búcaro, who keeps a work log, recalls reaching for his exactly once it mattered: "During a company restructure, when I was asked for a detailed report of my achievements, the obstacles I faced, and the steps I took to overcome them."⁶ A searchable folder of dated files answered a question that memory could not. The log is insurance you write a line at a time, and the premium is five seconds a day.

Common mistakes

The method is easy to start and easy to quietly sabotage. Four mistakes account for most abandoned logs — and all four come from the same root: treating the log as something it is not.

• Reorganizing yesterday. The instant you start moving old lines into topics, you have re-created the filing problem the date was supposed to solve. Leave the past alone.
• Trying to make it the whole system. A log captures flow. It is poor at durable, atomic ideas you will reference for years — those deserve their own files. Pair the log with permanent notes; do not ask one dated file to be both stream and library.
• Mixing in your task list. A running log and an actionable task list pull in different directions. The to-do side belongs in its own plain-text file; keep the daily note for what happened, not what must happen.
• Over-formatting. Tables, nested bullets, and tags turn a thirty-second append into a small layout project. A flat list of timestamped lines is faster to write and just as easy to grep.

How this works in MNMNOTE

In MNMNOTE, a daily log is exactly what the method describes: a plain Markdown file named for the date, kept locally on your own device, that you append to through the day. There is no plugin to install and no database to configure. You open a dated file, add a line, and the folder of files stays plain text you own.

That ownership is the point, and it is not ours to claim alone. Steph Ango, Obsidian's CEO, put it best: "File over app is a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read."⁷ A daily note that lives as a plain .md file passes that test. "Apps are ephemeral, but your files have a chance to last," Ango writes⁷ — and a decade of dated text files is about as durable as a log can get.

Frequently asked questions

What is a daily note system?

A daily note system is one dated file per day that you add to as things happen. Each file is named for its date — 2026-06-16.md — and you append lines all day: meetings, ideas, observations, what you tried. The date supplies all the structure, so there is nothing to organize and nothing to file.

How do I keep a plain text work log?

Make a folder, create a file named with today's date, and append a line every time something happens at work. Never edit past lines. Tomorrow, start a fresh dated file. To retrieve anything, search the folder — results come back in date order automatically, because every filename is a date.

Why append-only instead of editing and reorganizing?

Reorganizing turns a fast capture into a filing decision, and filing decisions are what people abandon. Append-only keeps the cost near zero: every line goes at the bottom under today's date. The date does the sorting, so the log stays cheap enough to actually keep for years.

Isn't a daily log just Obsidian Daily Notes or a Bullet Journal?

It shares the lineage. The Bullet Journal's Daily Log and Obsidian's YYYY-MM-DD daily notes are the documented pattern¹². The plain-text, append-only version keeps that idea and removes the dependency: the file is ordinary Markdown you own, readable in any editor, with or without the app that created it.

Can a daily log be my entire note system?

No, and that is the honest limit. A log is built for flow — the running record of a day. It is weak at durable, atomic ideas you will reference for years. Pair it with permanent notes: when a logged line matters beyond its day, copy it into its own file. The log records; the permanent note compounds.

How do I find something in a year of daily files?

Search the folder. Because every file is named for its date, results are chronological by default — the date is the index. A consistent leading marker like DECISION or IDEA makes targeted retrieval sharper: one search returns every decision you ever logged, oldest to newest.

Does keeping a daily log help beyond record-keeping?

It can. Writing about your day, rather than only saving things, is the small act of processing that a pile of captures never gives you. There is even evidence that regular expressive writing aids cognition; the well-being side of that story lives in our piece on writing to feel better.⁸

A note system you will actually keep beats a better one you will abandon, and nothing is cheaper to keep than a dated file you append to and never reorganize.

This method borrows its lineage openly — the Bullet Journal's Daily Log, Obsidian's dated notes, and Christian Tietze's warning about the collector's fallacy. To keep your own dated log as plain Markdown you own, mnmnote.com opens a new file in a tab.