Guide

Time blocking vs time tracking: plan the day or record it?

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

Use both, in order. Time blocking plans the day. Time tracking shows what actually happened, and without that record, blocks keep overrunning in the same way. Track a few days first, on paper or with an automatic record such as Dayflow on a Mac. Then block one or two anchors a day in a calendar. A calendar wins for planning. A record wins for learning.

It is Monday, 8:40am, and the calendar looks good. Writing from 9 to 11. Email at 11. The report after lunch. A walk at 5. By 10:15 a message has eaten the writing block, the report has slid to Wednesday, and the color-coded week reads more like a wish list than a plan.

Or it goes the other way. You have never planned your day in blocks. You just work. On Friday someone asks what you did on Tuesday, and you know you were busy, but you cannot say what you were busy with.

This article compares the two habits people usually try. Time blocking plans the day ahead of time. Time tracking records what actually happened. It covers why each one tends to fail on its own, six things to try this week (most need only paper, a calendar or a timer), and where an automatic record fits. Dayflow, the Mac app that publishes this blog, is one of those records, so we say plainly where it belongs and where it does not. The Dayflow details below come from its own documentation and published policy for version 2.2.0, reviewed on 2026-09-06. Nothing here comes from lab testing.

The short version

What is the difference, and why does each one fail on its own?

Time blocking means you give each part of the day a job before the day starts. 9 to 11 is writing. 2 to 3 is the budget. The appeal is obvious: you decide once, in a calm moment, instead of deciding all day while messages keep arriving.

Time tracking means you note what you actually spent time on, either as you go or afterward. The appeal there is honesty. A record does not care what you meant to do.

Each one has a familiar way of falling apart.

Blocks are built from optimistic memories. When you estimate a task, you tend to picture the smooth version: the file opens, the idea comes, you are done. The real version includes a slow export, a question from a colleague and ten minutes looking for a login. Many people find their estimates are off in the same direction every time, which is why a plan built without data repeats the same overrun week after week. If this sounds familiar, why we underestimate how long things take goes deeper.

Interruptions are not in the plan. A blocked calendar usually lists the work you chose. It rarely lists the work that chooses you: replies, small fixes, someone stopping by. Those hours have to come from somewhere, and they come out of your blocks.

Manual tracking depends on remembering. A timer only works if you start it, switch it and stop it. That is easy on a calm day and close to impossible on a busy one, which happens to be the day you most want a record of. When you are absorbed in work, you forget the timer. When you are scattered, you forget it more.

End-of-day memory is a poor witness. Reconstructing the day at 6pm tends to favor whatever was memorable: the meeting that went badly, the task you finished. The forty minutes spread across small detours disappear.

So a plan without a record keeps making the same mistakes, and a record without a plan just describes drift. Together, the record tells you how to plan, and the plan gives the record something to be compared against.

Should you track before you block?

Yes, if you can spare a few days. Before you set up a single block, keep a plain log for three to five ordinary workdays.

What to do: Every 30 minutes, write one line on a sheet of paper: the time and what you were mostly doing. Set a quiet repeating alarm if you need the reminder. Do not judge the entries and do not tidy them up. “Inbox, then the invoice question, then reading something unrelated” is a perfectly good line. The time audit template gives you a ready-made sheet if you would rather not draw one.

Illustration: Someone logs four days and notices that their best writing happens between 8 and 10, that “quick” admin tasks take most of the hour after lunch, and that Thursday afternoons are always interrupted by a recurring call that runs long.

How to tell after a week: You can answer three questions without guessing. When do you do your most focused work? How long do your recurring tasks actually take? Where does the unplanned time go? If you cannot answer them yet, log a couple more days. For a longer version of this exercise, see how to do a time audit on a Mac.

How many blocks should a day have?

Fewer than you think. A day planned in solid blocks from 8 to 6 has no room for anything to go wrong, and something always does. When one block slips, the whole plan collapses, and a collapsed plan is easy to abandon.

What to do: Choose one or two anchor blocks a day for the work that matters most and protect them. Put them where your log showed you focus best. Leave the rest of the day loosely planned or unplanned. If you use a calendar, mark the anchors as busy. If you use paper, draw a box around them.

Illustration: Instead of seven blocks, a person sets one: 8:30 to 10:30, draft the proposal. Everything else that day is a short list of things to do “after the anchor.”

How to tell after a week: Count how many anchor blocks actually happened as planned. If most did, add a second anchor. If few did, the anchor is in the wrong spot or is too long. Move it or shorten it before adding more.

How do you stop blocks from overrunning?

Use your own numbers. A generic rule of thumb for padding estimates is still a guess. Your log is not.

What to do: For a week, write a quick estimate next to each block before you start, then write the actual time beside it when you finish. At the end of the week, divide actual by estimate for each kind of task. That gives you a personal multiplier. Use it next week, and leave 15 to 30 minutes of empty buffer between blocks for the things nobody planned. If you are curious how your sense of time compares with a clock in the first place, the time estimation test is a short exercise for that. It is not a diagnostic.

Illustration: Someone finds that writing tasks take about 1.5 times their estimate and admin tasks take about double. Next week, a “one-hour” writing block gets 90 minutes and a “30-minute” admin block gets an hour.

How to tell after a week: Your blocks end closer to when you said they would. They will not be exact, and they do not need to be. The goal is fewer days where everything slides by two hours.

What happens when you put plan and actual side by side?

You see the gap, and the gap is the most useful information either habit produces.

What to do: Draw a line down a page. On the left, write the blocks you planned this morning. On the right, as the day goes, write what actually happened in the same time slots. Do not erase the left side when plans change. Cross things out and keep going. The daily work log template works for this if you prefer a printed version.

Illustration: Left column, 2 to 3pm: budget review. Right column, 2 to 3pm: budget review for 20 minutes, then a client question, then back to the budget at 2:45. The plan was not wrong. It just did not include the client.

How to tell after a week: Look at the right-hand column across all five days. If the same kind of interruption shows up three or more times, it is not an interruption anymore. It is part of the job, and it deserves its own block.

Can a kitchen timer help without becoming another chore?

It can, if you use it at the edges of a block instead of inside it. Starting and stopping a timer for every small switch is the part that wears people out. Marking the end of a block is much lighter.

What to do: When a block starts, set a kitchen timer (or any timer) for when it should end. Then forget it. When it rings, stop for one minute and write a single line: what you did in the block and whether you are done. Then decide whether to continue, switch or take a break.

Illustration: A 90-minute timer rings during a design review. The line reads: “Got through half the screens. Continue 30 more, then lunch.” That one line is both a tracking record and a small replan.

How to tell after a week: You have a short, honest note for most blocks, and you did not have to remember to start anything mid-task. If the timer ringing feels jarring, try a softer sound or a slightly longer block.

Does reviewing the day actually change anything?

Yes, if it is short and you do it every day. A long weekly review is easy to skip. Five minutes at the end of each day is easier to keep.

What to do: Before you stop working, look at the plan and the record and answer three questions in writing. What got done? What slipped, and why? What is the first block tomorrow? The end-of-day report template has space for these. If it helps to say it out loud, text the three answers to a friend or colleague who is doing the same thing. Knowing someone will see it makes it easier to keep doing.

Illustration: “Done: proposal draft. Slipped: invoices, because the client call ran 40 minutes. Tomorrow first: invoices, 9 to 10.”

How to tell after a week: Mornings start faster, because tomorrow’s first block was decided yesterday. You may also find the same reason for slipping shows up several times, which tells you what to change next. To see the whole week in rough categories, the where does my week go calculator gives a quick estimate to compare against your notes.

Where seeing your actual day helps

Every step above depends on a record. For many people, the record is what breaks first: the half-hour alarm gets dismissed, the right-hand column stays empty after lunch, and the review becomes a guess. If that is what keeps happening, an automatic record means you do not have to remember to start a timer or rebuild the day from memory. That is the whole idea behind where did my day go.

Dayflow is a free, open-source Mac app (MIT license, macOS 14 or later) that records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Full screen recordings and the timeline are stored on your Mac. You choose how the analysis runs: a local AI model on your Mac, which keeps screenshot analysis on-device; your own cloud provider, which receives selected screenshots under its own terms; or Dayflow Pro at $20 a month, which manages cloud analysis and, under the privacy policy, deletes screenshots after processing and may retain Activity Data for sync. You can export a date range as Markdown from Settings → Export, which makes it easy to paste the actual side next to your planned blocks.

The AI summaries can miss or misinterpret work, so treat the timeline as a draft to check, not a verdict.

Dayflow publishes this article, so weigh that when reading this section.

Where Dayflow is the wrong pick

It does not plan. Dayflow records what happened, but it does not schedule blocks, remind you when one starts or move things around when the day changes. For the planning half, a calendar or a paper planner is the better tool, and for many people paper is all they need.

It does not block anything. Dayflow has no website blocking. If what keeps breaking your blocks is drifting to a feed or a news site, a dedicated website blocker will do more for you.

It sees only your Mac screen. Phone calls, in-person meetings, a whiteboard session, thinking on a walk and anything done on paper will not appear. If much of your work happens away from the screen, a paper log captures more. It is also Mac only, so if you work on Windows or mostly on a phone, it is not an option.

It is not a billing or team tool. There are no invoices, payroll approvals or team reports. If you need those, look at another time tracker for Mac built around billing.

It is a record, not a coach. It will not tell you what to change. The daily review is still yours to do.

And if a rough paper log already gives you enough to plan with, you do not need any app.

The bottom line

Time blocking and time tracking are not rivals. Blocking is a guess about the day, and tracking is how you check the guess. Plans built without a record keep overrunning in the same ways, and records kept without a plan only tell you where the day drifted.

Start with a few days of honest tracking, on paper if that works for you. Then protect one or two anchor blocks, pad them with your own numbers, and spend five minutes each evening looking at the gap between plan and actual. If the record is the part that keeps slipping, make it automatic. If the plan is the part that keeps slipping, make it smaller.

Frequently asked questions

Is time blocking or time tracking better?

Neither is better on its own because they answer different questions. Time blocking decides in advance what the day is for. Time tracking shows what the day was actually spent on. A plan without a record tends to repeat the same overruns. A record without a plan only describes drift. Most people get more from tracking first, then blocking with what they learned.

Can you do time blocking and time tracking at the same time?

Yes, and they work well together. Plan your blocks in the morning, let the day happen, and compare the plan with the record at the end. The gap between the two is the useful part. It shows which tasks you underestimate, which hours get interrupted, and which blocks you never protect. A two-column page with planned on the left and actual on the right is enough to start.

Why do my time blocks always run over?

Estimates usually come from remembering the smoothest version of a task, not the version with a slow file, a question from a colleague and a detour to find a password. Interruptions are rarely written into the plan either. The fix is to measure your own overrun for a week, then pad future blocks by that ratio and leave empty buffer time between them.

How long should I track my time before I start time blocking?

Three to five ordinary workdays is usually enough to see a pattern. Pick days that are typical, not a holiday week or a launch week. You are looking for rough answers: when you do your best focused work, how long recurring tasks really take, and where the unplanned time goes. You can keep tracking afterward to check how your blocks hold up.

Do I need an app for time blocking?

No. A paper planner, a printed day sheet or the calendar you already use is enough. Time blocking is a planning habit, and the tool matters less than whether you protect the blocks you set. An app can help with tracking, because remembering to log time by hand is the part that tends to slip, but blocking itself works fine on paper.

Is Dayflow a good tool for planning time blocks?

No. Dayflow records what was on your Mac screen and writes it into a timeline, but it does not schedule your day. For the planning half, a calendar or a paper planner beats it. Dayflow also has no website blocking, so if distractions are what break your blocks, a dedicated website blocker is the better pick. Dayflow fits the record half, not the plan.

Is Dayflow free?

Yes. Dayflow is $0 and open source under the MIT license, and it runs on macOS 14 or later. There is an optional Dayflow Pro plan at $20 a month, which handles cloud analysis for you. You can also run screenshot analysis with a local AI model on your Mac or with your own cloud provider, whose charges and terms apply separately.

Does Dayflow send my screen to the cloud?

It depends on the mode you choose. Recordings and the timeline are stored on your Mac. With local AI, screenshot analysis stays on-device. With your own provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Dayflow Pro deletes screenshots after processing and may retain Activity Data for sync. Your own provider has its own terms.

What should I do when a time block gets interrupted?

Do not try to rescue the whole schedule. Write one line noting what interrupted you and roughly when, then decide whether the block resumes, shrinks or moves to tomorrow. Over a week, those notes show whether the interruptions are random or predictable. Predictable ones, like a daily check-in that always runs long, belong in the plan as their own block.

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