How to Keep a Daily Work Log (2026 Guide)

Keep one dated file, add a line at each break, write outcomes rather than activities, and close the day with a five-minute review. A plain Markdown file is enough. Add Toggl if you bill clients by timer, Timing for automatic billable records on a Mac, ActivityWatch for a free open-source raw record, or Dayflow if you want AI to draft the day's timeline for free.

A daily work log is a short, dated record of what you did each workday, kept somewhere you can search later. The payoff comes weeks after you start. You can answer a standup without scrolling Slack. You have real examples for a performance review. You can back up an invoice. On Friday, you can say where the week went.

It usually goes wrong at the same point. You plan to write it all up at 6 p.m. By then you remember the big meeting and the main task, and the rest is gone: the small fixes, the thread that turned into a spec, the hour lost to an urgent bug. After a week of thin entries, the log feels like homework that proves nothing, and you stop.

This guide gives you a method that works with a text file and nothing else. It then shows where software can fill the gaps memory leaves.

Disclosure: Dayflow, one of the apps covered here, is our product. The method behind the app comparisons is a review of each vendor’s own documentation as checked on October 4, 2026. Dayflow details come from its published 2.2.0 documentation.

The short version

1. Pick one file or note and one fixed format.
2. Add a line at each natural break, not at the end of the day.
3. Write the outcome and a rough time block, not just the activity.
4. Fill the gaps from a record (calendar, git, or a tracking app) instead of from memory.
5. Close the day with a five-minute review and tomorrow’s first task.
6. Roll the week’s outcome lines into a short weekly summary.

What you need before you start

• One place to write. A Markdown file, a notes app or a doc. It should be searchable, and you should still have access to it in a year.
• A fixed format. You will set this up in step 1. Same headings every day.
• A few seconds at each break and five minutes at the end of the day. That is the whole time budget.
• A decision about the reader. A log for yourself can be blunt. One that goes to a manager or client needs cleaner wording and should leave out anything private.
• Optional: an app that records in the background. If you work on a Mac and want one, our roundup of Mac time trackers covers the options. You do not need one to start.

Step 1: Where should you keep the log?

Pick one location and one format, and keep both for at least a month.

Plain text or Markdown is the safest choice. It opens in any editor, survives app switches, and can be searched in seconds. One file per month works well: long enough to scroll back through, short enough to stay fast.

Use the same headings every day so a scan takes seconds. The daily work log template gives you a ready layout to copy into your file or notes app.

Illustration: a single day in a Markdown file might look like this.

## 2026-10-05 Mon
Plan: ship invoice export fix, review Sam's PR
Done:
- 09:10-10:40 Fixed rounding bug in invoice export, PR #412 open
- 10:40-11:15 Standup + sprint planning, agreed to cut CSV import from v2
- 13:00-14:30 Reviewed Sam's PR, two change requests
Blocked: waiting on API key from finance
Tomorrow first: merge #412 after CI

Mistake to avoid: spreading the log across a notes app, Slack messages to yourself and sticky notes. If you have to assemble the log before you can read it, you won’t read it.

Step 2: When should you write entries?

Write at natural breaks, not at the end of the day. A break is any point where your attention switches: a meeting ends, you finish a task, you go to lunch, you change projects, you close the laptop.

One line is enough. You are leaving a marker for later, not writing a report.

The reason is simple. At a break, the thing you just did is still in front of you, with the ticket number, the file name and the person you talked to. By evening, the morning has blurred into one item.

Illustration: you finish a call with a client. Before opening email, you type: “11:20 Call with Acme, they want launch moved to Nov 3, I owe them a revised timeline by Thu.” That takes a few seconds and captures a deadline you would otherwise have to hunt for.

Mistake to avoid: logging every few minutes. If the log interrupts the work, you will drop it within a week. Aim for a handful of entries a day, not dozens.

Step 3: What should each entry say?

Each line should answer four questions: what changed, on what, roughly when, and where the evidence lives.

Activities like “worked on API” are easy to write and useless to read later. Outcomes like “fixed pagination on /orders, PR #418” tell future you what happened and where to look.

A good line has four parts:

• Outcome: done, decided, sent, blocked or abandoned.
• Object: the ticket, document, client or feature.
• Time block: start and end. Rounding to the nearest 15 minutes is fine.
• Link or ID: a PR, a doc URL or an email subject.

Include work that produced nothing visible. That means dead-end investigations, a long debug that ended in “not our bug,” and slow code reviews. These are the hours that vanish from memory. They are also the ones you most need when someone asks why something took so long.

If you are unsure how good your sense of elapsed time is, try the time estimation test. It is a short exercise that compares your guess with a clock. It is not a diagnostic, just a quick way to see whether your time blocks need a clock’s help.

Illustration: compare “Research, meetings, emails” with “14:00-15:45 Traced checkout timeout to Redis config (not our code), filed INFRA-221.” The second line still makes sense in three months.

Mistake to avoid: writing to look busy. A log full of “meetings” and “emails” is just a list of verbs. If a meeting produced a decision, write down the decision.

Step 4: How do you capture the hours you forget?

Even with entries at each break, some hours slip through. Interruptions chain together, a quick question becomes an afternoon, and the log has a hole from 1 to 3.

You can fill holes by hand from records you already have: your calendar, sent mail, git commits and browser history. That is free and often enough.

The alternative is an app that keeps a record while you work, so you fill the gap from evidence instead of guessing. On a Mac, there are three distinct approaches.

A timer you start and stop

Toggl (formerly Toggl Track) is built around manual and real-time timers, timesheets and calendar integrations. The vendor also lists automated background tracking and a timeline in the desktop app. It states that it does not take screenshots or record keystrokes. Data lives in the cloud and syncs across web, desktop and mobile.

The Free plan covers up to 3 users. Starter is $9 per user per month billed annually, or $12 billed monthly. See our Toggl for Mac comparison.

A timer only works if you remember to start it. That is the same habit problem as the log itself.

An automatic app and window tracker

Timing records time automatically across apps, websites and documents on the Mac, down to specific URLs and Mail threads. It lists AI activity summaries and AI-powered suggestions for time entries. Tracked times stay on your Mac unless you opt into sync.

There is no free tier. Professional is $9 per month billed annually, or $11 billed monthly. There is a 30-day trial with no credit card required. More in our Timing comparison.

ActivityWatch is free and open source (MPL-2.0). It records the active app, the window title and whether you are away from the keyboard. Browser extensions add tab titles and URLs, and editor plugins add coding time. Data stays on your device.

ActivityWatch lists no AI summaries, so you read its charts and write the log lines yourself. See ActivityWatch vs Dayflow.

A screen-based timeline

Dayflow records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. It is free and MIT licensed, with an optional Pro plan at $20 a month. It runs on macOS 14 or later.

Recordings and the timeline are stored on your Mac. Analysis can run in three places:

• on-device, through Ollama or LM Studio
• through a cloud provider you configure
• through Dayflow Pro

The local and cloud processing page spells out what leaves your Mac in each mode.

You can export a date range as Markdown from Settings → Export and paste it into your log. The export work history workflow walks through it.

Illustration: at 5 p.m., your log jumps from “13:00 lunch” to “15:30 sent revised timeline to Acme.” The record for that window shows a spreadsheet, the Acme folder and a long doc session. That is enough to write: “13:45-15:20 rebuilt Acme launch timeline around new Nov 3 date.”

Mistake to avoid: pasting raw tracker output and calling it a log. “Google Chrome, 47 minutes” is evidence, not an entry. Turn it into what you actually did. Check AI summaries before you share them, because they can miss or misread work.

Step 5: How should you close out the day?

Spend five minutes before you stop. Read the day’s entries and fill any gap longer than about an hour. Then add three things:

• the one to three outcomes that mattered
• anything blocked, and who it waits on
• the first task for tomorrow

The “tomorrow first” line does more than it looks like. The next morning starts with a decision already made, not with a scan of your inbox.

Illustration:

Mattered: #412 ready to merge, Acme timeline sent
Blocked: finance API key (asked Priya, follow up Wed)
Tomorrow first: merge #412, then start CSV import spike

Mistake to avoid: turning the review into a planning session or a verdict on your productivity. Fill the gaps, note what is next, close the file. If this regularly takes more than ten minutes, the format is too heavy.

Step 6: How do you turn daily logs into a weekly report?

On Friday, or whenever your team expects an update, read the week’s entries. Copy the outcome lines into a short summary with four parts: shipped, in progress, blocked and next week.

Because the daily lines already name outcomes and link evidence, this is editing, not remembering. The weekly status report template gives you a structure. The same daily lines can also feed your standup updates.

You may want a rough sense of how your week splits between meetings, focused work and everything else. The where does my week go calculator lets you compare your guess with what the log says.

Illustration: from five days of entries, you pull: “Shipped invoice rounding fix (#412). Sent Acme revised launch timeline for Nov 3. Blocked on finance API key since Mon. Next: CSV import spike.” Four lines, all traceable.

Mistake to avoid: writing the weekly report from memory and checking the log afterward. Start from the log. Otherwise the last two days and the most stressful task crowd out everything else.

Doing it by hand vs with a tool

Approach	Effort	What you get	Cost
Manual (text file + template)	A line at each break, five minutes at day end	Exactly what you choose to write, with gaps where you forgot	$0
Toggl (formerly Toggl Track), timer	Start and stop timers, or edit timesheets	Timed entries per project, cloud sync; billable rates on paid plans	Free for up to 3 users; Starter $9 per user per month billed annually or $12 billed monthly
Timing (automatic)	Review and assign recorded time	App, website, document and URL time on the Mac, plus AI activity summaries	No free tier; Professional $9 per month billed annually or $11 billed monthly; 30-day trial
ActivityWatch (automatic)	Install, read charts, write entries yourself	Active app, window title, away time, optional URLs, stored locally	Free, MPL-2.0
Dayflow	Read and correct the AI timeline, export to your log	AI-written timeline from a screen frame every 10 seconds, Markdown export	$0 (MIT); optional Pro $20 a month

Again, Dayflow is our product, so weigh our description accordingly. It is built for the “what did I actually do” half of a work log. It does not do invoicing, payroll, team reports or website blocking. The manual method in steps 1 to 6 works the same whether you use it or not.

Common mistakes

• Starting with too much structure. Ten fields per entry will not survive a busy week. Start with Done, Blocked and Tomorrow first, and add fields only when you miss them.
• Logging only what shipped. Investigations, reviews and help you gave colleagues are real work. If they are missing from the log, they are missing from your review too.
• Backfilling a whole week on Friday. That is reconstruction, not logging. If you have to do it, rebuild from your calendar, commits or a tracker’s record, and mark those entries as reconstructed. Our guide on how to remember what you worked on covers that recovery job in more detail.
• Keeping it only where you could lose it. A log that lives only in a work account goes away with the job. Check your employer’s policy on keeping personal notes before you make a copy elsewhere.
• Writing for an audience you do not have yet. Polishing every line for a manager makes the log slow and you will stop. Keep the daily file rough and polish only the weekly summary.
• Treating the record as the log. App time and AI summaries are inputs. The log is your account of what happened and why.

Where Dayflow is the wrong pick

• You bill clients by the hour and need invoices. Dayflow has no invoicing, billing status or billable rates. Timing does better here. It tracks billing status, offers report rounding and integrates with GrandTotal for invoicing, depending on plan. Toggl is the other option, with billable rates on paid plans and profitability reports on Premium.
• You manage a team and need shared reports or approvals. Dayflow has no team reports or timesheet approvals. Toggl lists timesheet approvals on Premium, which is $16 per user per month billed annually or $24 billed monthly. Timing’s Connect plan adds shared projects at $16 per user per month billed annually, or $20 billed monthly.
• You work on Windows, Linux or an older Mac. Dayflow needs macOS 14 or later. ActivityWatch runs on Windows, Linux and Android as well as Mac. Toggl runs on the web, Windows, iOS and Android.
• You do not want your screen captured at all. Even with local storage and on-device analysis, some people or employers rule out screen frames entirely. Toggl states it takes no screenshots, ActivityWatch records app and window titles rather than screen images, and a plain text log records only what you type. For more on that trade-off, see time tracking without surveillance.
• You want a free automatic record with no AI involved. ActivityWatch is free, open source and lists no AI features, so nothing is summarized or interpreted for you.

The bottom line

A daily work log is a habit problem, not a software problem. Keep one file in one format, write a line at each break, describe outcomes instead of activities, and close each day with five minutes and a first task for tomorrow. On Friday, the weekly report mostly writes itself from those lines.

Software helps with one specific failure: the hours you forget. Toggl fits if you bill clients and will run timers. Timing fits if you want automatic, billable-ready records on a Mac and are fine with a subscription. ActivityWatch fits if you want a free, local, open-source record and will write the summaries yourself. Dayflow fits if you want AI to draft the day’s timeline for free and are comfortable with screen frames stored on your Mac.

If you are still choosing a time tracker for Mac, start with the daily work log template this week, see where the gaps show up, and pick a tool for those gaps.

Frequently asked questions

What should a daily work log include?

Each entry should name the outcome, the thing it applies to, a rough start and end time, and a link or ID such as a ticket or document. At the end of the day, add what mattered most, anything blocked and who it waits on, and the first task for tomorrow. Leave out play-by-play detail you would never reread.

How long does keeping a daily work log take?

With the method in this guide, it takes a few seconds at each natural break plus about five minutes at the end of the day. If it regularly takes longer than ten minutes, the format is too detailed. Cut fields until the log is easy to keep on a bad day. A short log you keep beats a thorough one you abandon.

Is a daily work log the same as a timesheet?

No. A timesheet records hours against projects, usually for billing or payroll. A work log records what you did and what came of it, in your own words. The two overlap when you add time blocks to log entries, and a good log makes a timesheet faster to fill. A timesheet alone rarely tells you what was achieved.

Can I keep a daily work log in a plain text file?

Yes, and it is often the best choice. A Markdown or text file opens in any editor, is easy to search, and does not depend on an app staying in business. Use one file per month, with a dated heading for each day and the same sections every time. The free Dayflow daily work log template gives you a layout to copy.

What is the best work log app if I bill clients by the hour?

Not Dayflow, which has no invoicing, billing status or billable rates. Timing is a strong fit on a Mac. It has billing status tracking, report rounding and GrandTotal invoicing integration depending on plan, from $9 per month billed annually. Toggl (formerly Toggl Track) offers billable rates and team reports on paid plans, from $9 per user per month billed annually, and also runs on Windows and the web.

Is there a free way to log work automatically on a Mac?

Yes. ActivityWatch is free and open source under MPL-2.0. It records your active app, window title and away time and stores them locally, though it lists no AI summaries. Dayflow is free and MIT licensed. It records the screen at one frame every 10 seconds and has AI write a timeline, with an optional Pro plan at $20 a month. With either one, you still need to check the result.

Does Dayflow work on Windows or Linux?

No. Dayflow runs only on macOS 14 or later. On Windows or Linux, ActivityWatch is a free, open-source option that records your active app and window title locally, and it also runs on Android. If you prefer a timer that syncs across devices, Toggl runs on the web, Windows, Mac, iOS and Android.

Should I share my daily work log with my manager?

Share summaries, not the raw log. The daily file is a working document that can include half-formed notes and personal reminders. Pull the outcome lines into a weekly update or standup instead. That keeps the useful part and leaves out what does not need an audience. If you use an AI-written timeline, check it before sending, since summaries can miss or misread work.

Can AI write my daily work log for me?

AI can draft it, but you should edit the draft. Timing lists AI activity summaries, and Dayflow has AI write a timeline from screen frames that you can export as Markdown. Either gives you a record to work from. Neither knows why a task mattered or what was decided on a call, so add outcomes and decisions yourself and correct anything the summary got wrong.

Does Dayflow send my screen recordings to the cloud?

Recordings and the timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis stays on-device. If you configure your own provider, selected screenshots go to that provider under its terms. With Dayflow Pro, Dayflow handles cloud analysis. Under its privacy policy, Pro deletes screenshots after processing and may retain activity data for sync.