Guide

How to keep a plain Markdown work log that will still open in ten years

Updated November 2026 · by Jerry Liu, Dayflow's founder

Keep one folder of plain .md files, one per day, named YYYY-MM-DD, using only headings, lists and links. Any text editor will open them. Obsidian wins if you want a free app on Mac, Windows, Linux, iOS and Android that keeps notes as Markdown files in a local folder. Dayflow fits Mac users who forget to write: it exports a recorded day as Markdown.

You open the notes app you used two jobs ago, and it asks for a login you no longer have. Or the export hands you one huge file of tagged fragments with no dates. Or the notes are fine, but there are only eleven of them, all from one hopeful week in March, and then nothing.

Then someone asks what you shipped last quarter. You end up scrolling through sent mail and old calendar invites, trying to rebuild months of work from scraps.

This guide covers a plain kind of work log that tends to survive: Markdown text files in one folder, a habit small enough to keep, and a way to check after a week whether it’s holding. Most of it needs only a text editor, paper and a timer. If you want the bigger picture first, the work journal guide covers why people keep one at all.

Disclosure: Dayflow is our product, and this blog is published by Dayflow. It appears in one section below and in a section on when it’s the wrong pick. The method here is a comparison of vendor documentation: Obsidian facts come from its own pages as checked on October 4, 2026, and Dayflow facts come from its published documentation for version 2.2.0.

The short version

Why do work logs keep disappearing?

Most logs don’t fail because the person lacked discipline. They fail for a few ordinary reasons.

The tool outlives the habit, or the habit outlives the tool. Apps change their pricing, change their formats, or close. If your notes live inside one app’s own database, you need that app, or its export button, to read your own past. A plain text file has no such dependency. You can open it with whatever editor exists at the time.

The setup is too ambitious. Tags, properties, status fields, linked databases. Building the system is fun for a weekend. Feeding it every evening is a chore, and chores get skipped.

The cue is vague. “I’ll write it up at the end of the day” has no end. Many people find the day ends whenever the last meeting runs over, and by then the log has lost.

Memory has already smoothed the day over. By 6pm the morning is a blur. Rebuilding it feels like homework, so you write “worked on the report” and move on. If that blank feeling is familiar, where did my day go covers it in more depth.

Plain Markdown helps with the first two problems. It is ordinary text with a few punctuation conventions: # for a heading, - for a list item, [text](link) for a link. Even if nothing ever renders it again, ## Done still reads as a heading to a human. The other two problems are about habit, and most of the fixes below are about habit too.

Seven things to try this week

1. Make one folder and name files by date

What to do: Create a single folder, for example Documents/worklog. Each workday gets one file named with the date in year-month-day order and the .md extension. That order sorts correctly in any file list, so the folder doubles as a calendar. Keep the names free of words. The topic belongs inside the file.

Illustration: On Monday, October 12, you save 2026-10-12.md. On Tuesday, 2026-10-13.md. When you need “the week the migration broke”, you scroll the list instead of searching.

After a week: Open the folder. Can you find Wednesday in a few seconds without searching? If the files are scattered across folders or have names like notes final 2.md, fix the naming before you add anything else.

2. Use a three-heading template and nothing else

What to do: Paste the same skeleton into every new file. Three headings is enough:

## Done

## Open

## Tomorrow

“Done” is what you finished. “Open” is what’s half-finished and where you stopped. “Tomorrow” is the one thing you’ll want to remember when you sit down in the morning. If you’d like a starting point with prompts, the daily work log template is laid out the same way.

Illustration: A filled entry might look like this:

## Done
- Sent revised quote to the Harbor account
- Reviewed onboarding copy, left 6 comments

## Open
- Pricing page draft: stuck on the FAQ
- Draft lives in the shared drive under Pricing / Q4

## Tomorrow
- Ask Sam whether the discount applies to renewals

After a week: If entries take more than a few minutes, the template is too big or you’re writing prose. If one heading is always empty, delete it. A smaller template you keep using beats a complete one you skip.

3. Catch the day on paper, type it once

What to do: Keep an index card or a sticky note next to the keyboard. When you switch tasks, write the time and three or four words. Don’t open the log file during the day. At the end, type the card into the file and throw the card away.

This works because writing on paper takes almost no effort, so you don’t put it off, and typing it up becomes copying rather than remembering.

Illustration: The card reads: “9:40 quote Harbor. 11:15 copy review. 2:00 pricing FAQ, stuck. 4:30 call w/ Sam.” At 5:30 that turns into four bullets in under two minutes.

After a week: Look at the cards before you throw them out, or just think back. Were they mostly full, or mostly blank by noon? If they go blank after lunch, put a second card somewhere you’ll see it in the afternoon, such as under your coffee mug.

4. Tie the entry to a cue you can hear

What to do: Choose a fixed time and make it physical. A kitchen timer set when you sit down after lunch works. So does a recurring calendar event called “log” that blocks ten minutes. Or tie the log to an action you already do, like closing the laptop lid: the lid doesn’t close until today’s file exists.

Illustration: You set a calendar event for 5:15 every weekday. On Thursday a meeting runs until 5:40. The event stays on your screen, and you write a three-bullet entry before you leave instead of planning to “do it tonight”.

After a week: Count the files. If there were five workdays, how many files are there? If you’re short, look at which days you missed and what happened at the cue time. Move the cue to a calmer part of the day rather than trying harder at the same one.

5. Keep the formatting boring

What to do: Use headings, bullet lists, plain links, and dates written as 2026-10-12. Skip features that only one app understands, such as special embed syntax, custom callout blocks or plugin-generated tables. Those may display beautifully today and show up as clutter in a plain editor later.

If you’d like an app on top of the folder, look for one that keeps your notes as ordinary files. Obsidian is one example. Its documentation describes notes as Markdown-formatted plain text files in a vault, which is a folder on your local file system, so other editors can open the same files. The app is free with no sign-up required, including for work use, on Mac, Windows, Linux, iOS and Android. Its Daily notes core plugin opens or creates a note for today’s date, with a default name format of YYYY-MM-DD, and supports a template, which matches the setup above.

Syncing between devices through Obsidian’s own service is a paid add-on. Sync Standard costs $4 USD per user, per month billed annually, or $5 USD per user, per month billed monthly. It is limited to 1 synced vault, 1 GB total storage, a 5 MB maximum file size and 1 month of version history. A commercial license at $50 USD per user, per year is optional.

Illustration: You’re tempted to add a status property and a query that lists all open items across the month. Instead, you keep writing plain bullets under “Open”. On Friday you search the folder for the word you need.

After a week: Open one of your files in the plainest editor you have. Does it read like a tidy note, or like code? If it reads like code, strip it back.

6. Read it back on Friday and roll it up

What to do: Set aside fifteen minutes on Friday. Read the week’s five files and write one weekly file, for example 2026-W42.md, with three headings: shipped, still open, and what got in the way. The weekly work log template has a ready-made layout.

You can also do this out loud. Read your week to a friend or a coworker who keeps their own log, and listen to theirs. Saying it to another person makes gaps obvious, and it gives you both a reason to keep writing.

Illustration: Reading the week back, you notice “pricing FAQ, stuck” sits under “Open” for four days in a row. Your weekly file says: “Blocked on renewal discount question since Tuesday. Need a decision from Sam.” That sentence is more useful than anything you’d have remembered unprompted.

After a week: Can you answer “what did you do this week?” without opening email or your calendar? When a performance review comes around, a stack of weekly files is most of the preparation.

7. Keep a second copy somewhere else

What to do: On the same Friday, copy the whole folder to a second place: an external drive, a USB stick in a drawer, or wherever you already keep backups. Text files are small, so a whole year fits almost anywhere. Some people also print each month’s weekly files and keep them in a binder, which no software change can touch.

Illustration: On the first Friday of each month you plug in a drive, drag worklog across, and replace the old copy. It takes less time than making coffee.

After a week: Check that the copy opens. Pick a random file on the second drive and read it. A backup you’ve never opened is only a hope.

Where seeing your actual day helps

Every step above depends on you remembering what you did. On a scattered day, the index card goes blank by ten and the 5:15 entry turns into guesswork. That gap is where an automatic record helps, because you don’t have to start a timer or rebuild the day from memory.

Dayflow is a free, MIT-licensed Mac app for macOS 14 or later. It records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Recordings and the timeline are stored on your Mac. You can keep screenshot analysis on-device with Local AI through Ollama or LM Studio. If you choose your own cloud provider or the optional Pro plan at $20 a month, selected screenshots are processed off-device. The local and cloud processing page explains the difference.

The part that fits a Markdown log is export. Settings → Export saves a date range as Markdown, so you can paste a day’s timeline into that day’s file, trim it, and add the reasons that a screen never shows. AI summaries can miss or misinterpret work, so read it before you keep it. The export work history workflow walks through it.

Once more, plainly: Dayflow publishes this article, and it’s our product.

Where Dayflow is the wrong pick

The bottom line

A work log that lasts is mostly a matter of being boring. Use one folder, one file per day named by date, three headings, and plain formatting that any editor can read. Write it at a fixed cue, catch the day on paper as it happens, read it back on Fridays, and keep a second copy you’ve actually opened.

If you’d like an app over the folder, choose one that leaves your files as files. Obsidian does that across desktop and mobile. If your problem is remembering the day in the first place and you work on a Mac, a Dayflow Markdown export can give you a draft to edit. Either way, the file is what lasts, so start with today’s.

Frequently asked questions

What file format is best for a work log you want to keep for years?

Plain text is the safest choice. Markdown is plain text with a few conventions, such as # for headings and - for list items. A file saved as .md opens in any text editor on any operating system, and it stays readable even when nothing renders the formatting. Avoid formats that live inside one app's database, because then you need that app, or its export, to read your own notes.

How should I name daily work log files?

Put the date in year-month-day order, such as 2026-10-12.md. That order sorts correctly in any file list, so the folder doubles as a calendar. It also matches YYYY-MM-DD, the default name format of Obsidian's Daily notes plugin, if you ever use the folder there. Leave spaces and descriptions out of the name. The topic belongs inside the file.

Is Obsidian free to use for work?

Yes. Obsidian's pricing page lists the app as free with no sign-up required, including for work use. A commercial license costs $50 USD per user, per year. The vendor calls it optional: you are not required to pay, though it encourages organizations that use Obsidian for work to buy one. Sync and Publish are separate paid add-ons. These are the terms as checked on October 4, 2026. See the vendor's pricing page for current details.

What does Obsidian Sync cost?

Sync Standard is $4 USD per user, per month billed annually, or $5 billed monthly. It covers 1 synced vault, 1 GB total storage, a 5 MB maximum file size and 1 month of version history. Sync Plus is $8 USD per user, per month billed annually, or $10 billed monthly, with 10 vaults, 10 GB, 200 MB files and 12 months of history. The vendor says Sync is end-to-end encrypted.

Can Dayflow write my daily work log for me?

It can write a first draft. Dayflow records your Mac screen at one frame every 10 seconds, has AI turn the day into a timeline, and exports a date range as Markdown from Settings → Export. Treat that export as notes, not the finished entry. AI summaries can miss or misinterpret work, and the screen doesn't show why you made a decision. Read it and add context before you keep it.

Should I use Obsidian or Dayflow for a work log I write myself?

Obsidian. If you want to type the log by hand and read it on more than one device, Obsidian fits better. It is free, runs on Mac, Windows, Linux, iOS and Android, and stores notes as Markdown files in a local folder. Dayflow is Mac only and is a recorder, not an editor. Some people use both and paste a Dayflow Markdown export into the day's note.

What should a daily work log include?

Write down what you will want later: what you finished, what is still open and where you stopped, and anything tomorrow-you needs, such as a blocker or a decision and the reason for it. Links to the pull request, document or ticket save the most time when you look back. A short entry you keep writing is worth more than a thorough one you give up on.

How long should a daily work log take to write?

Short enough that skipping it feels silly. For most people that means a few minutes and a handful of bullets. If entries keep growing until you dread them, cut the template down to one heading for a week. What you want is an unbroken run of small files, because a missing day is much harder to rebuild later than a thin one.

Does Dayflow work on Windows or on my phone?

No. Dayflow runs only on macOS 14 or later, and it records what is on your Mac screen. Work done on a phone, a tablet or another computer won't appear in its timeline. If your log has to live across Windows, Linux or mobile, use a plain Markdown folder in a cross-platform notes app. Obsidian, for example, lists Mac, Windows, Linux, iOS and Android.

Can a Markdown work log replace a time tracker for billing clients?

Not on its own. A log records what happened, but billing usually needs hours per client and invoices, and a folder of text files gives you neither. Dayflow doesn't create invoices or payroll approvals either. If you bill by the hour, use a time tracker built for invoicing alongside your log, and keep the Markdown files as the readable record behind the numbers.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required