Guide

How to Time Block Your Day and Check It Against Reality (2026 Guide)

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

Put two or three outcomes on your calendar as blocks with buffers, record what you actually do, and compare the two at the end of the day. For the record, Toggl works if you remember to start its timer. Rize and Timely track automatically on paid plans. Dayflow records your Mac for free, but it is Mac only and has no billing features.

Time blocking means giving every piece of work a slot on your calendar instead of a spot on a list. The outcome you want is plain: at the end of the day you know whether it went the way you planned, and if it didn’t, you know why.

The usual failure is just as plain. You build a tidy calendar at 9 a.m. The first block runs long, a few messages eat the gap, and by lunch the plan is fiction. Nobody writes down what happened instead, so the next morning you build the same fiction again.

This guide covers both halves: making the blocks, and checking them against what you actually did. Most advice stops after the first half. The second half is what makes tomorrow’s plan better than today’s.

A note before we start: Dayflow, which comes up below as one way to record your day, is our product. The method works fine without it. Tool details come from a comparison of each vendor’s own documentation, checked on October 4, 2026 for the other tools and against Dayflow 2.2.0 for Dayflow.

The short version

  1. Write down today’s fixed commitments and the two or three outcomes that matter.
  2. Estimate each task, then add a buffer.
  3. Put the blocks on your calendar, including buffer and admin time.
  4. Record what actually happens, by hand, with a timer or with an automatic tracker.
  5. At the end of the day, put the plan and the record side by side and label the gaps.
  6. Once a week, change how you plan based on the gaps that keep repeating.

What you need before you start

Step 1: What actually has to happen today?

Start with what you can’t move: meetings, calls, school pickup, a deadline at 3 p.m. Write those down first. They are the walls your blocks have to fit between.

Then pick two or three outcomes for the day. An outcome is something you could show someone: “draft of the proposal sent to Sam,” not “work on proposal.” Outcomes give each block a finish line, which makes the end-of-day comparison much easier.

Illustration: A product designer’s Tuesday. Fixed points: standup 9:30 to 9:45, client review 2:00 to 3:00. Outcomes: finish the v2 onboarding screens, send written feedback on the pricing page copy, and reply to the two open developer questions.

The mistake to avoid: listing nine outcomes. Your calendar will accept nine blocks without complaint. Your day won’t. If everything on the list is urgent, choose the ones that would hurt most to miss and leave the rest on the list, not the calendar.

Step 2: How long will each task really take?

Write a time estimate next to each outcome before you place it. Then add a buffer. Most people estimate from the version of the task where nothing goes wrong: no unclear brief, no broken file, no question you have to wait on. Our piece on why we underestimate how long things take goes into why this happens even to experienced people.

Pick a padding rule and use it consistently for now. You will correct it with real data in step 6. If you want a quick sense of how your internal clock compares with an actual one, the time estimation test is a short exercise for that. It’s not a diagnostic, just a calibration check.

Illustration: The designer guesses 90 minutes for the onboarding screens. Their notes from last week show a similar set of screens took most of a morning once revisions came in. They block two and a half hours instead and keep the 90-minute guess written beside it, so they can see later which number was closer.

The mistake to avoid: estimating only the “doing” part. Opening files, finding the latest version, writing the handoff note and answering the follow-up question all count as part of the task. If they aren’t in the estimate, they will come out of the next block.

Step 3: How do you lay the blocks out on a calendar?

Now place the blocks. A few rules that hold up across most jobs:

Illustration: The designer’s day ends up like this:

The mistake to avoid: filling every slot. A calendar with no gaps looks productive and fails at the first interruption. If the day doesn’t fit with a buffer, the day doesn’t fit. Move an outcome to tomorrow now, while it’s a choice and not a casualty.

Step 4: How do you record what actually happened?

This is the step most people skip, and it’s why their time blocking never improves. A plan with no record of reality can’t teach you anything. You need something that shows what you did, written down as it happened, not reconstructed at 6 p.m. from memory.

There are three ways to do it.

By hand. Keep a running log. Every time you switch tasks, write the time and what you switched to. It’s free, it works anywhere and it forces you to notice your switches. The cost is that you will forget entries, especially on the busiest days, which are the days you most want a record of. The daily work log template gives you a ready-made layout.

With a timer. Start a timer when you begin a block and stop it when you leave. Toggl (formerly Toggl Track) is the best-known example. The vendor lists manual and real-time timers, timesheets and calendar integrations, and also mentions automated background tracking and a timeline in its desktop app. It runs on web, Mac, Windows, iOS, Android and browser extensions. See our Toggl for Mac comparison for how it fits a Mac setup. Timers are precise when you remember them. Like a paper log, they rely on you noticing the moment you switch.

With an automatic tracker. These record your computer activity in the background, so the record exists even when you forget. Rize tracks apps and websites automatically, categorizes them with AI, and can connect to Google Calendar to capture meeting time. That last part is handy for this method, since your blocks live on a calendar too. More in our Rize alternative page. Timely uses a Memory tracker that records work across web and desktop apps into a private timeline, then has AI draft timesheet entries for you to approve. Our Timely alternative page covers the details.

Dayflow is another automatic option. It captures your Mac 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. Analysis can run on local AI through Ollama or LM Studio, through a cloud provider you configure, or through Dayflow Pro. How local and cloud processing work explains what leaves your Mac in each mode. The AI summaries can miss or misread work, so treat the timeline as a draft you check, not a verdict.

If you’re weighing more options, our roundup of the best time tracker for Mac picks compares more tools side by side.

Illustration: A hand-written log for the designer’s morning might read: “9:45 onboarding screens. 10:20 Slack, dev asked about modal spacing. 10:35 back to screens. 11:10 client emailed new logo, swapped assets. 11:40 screens. 12:30 stopped, two screens left.” That log already explains why the block ran 15 minutes past lunch.

The mistake to avoid: filling the record in from memory at the end of the day. Memory rounds everything toward the plan. You will “remember” a clean two-and-a-half-hour block, not the three interruptions that broke it up. Our page on where your day went is about exactly that gap.

Step 5: How do you compare the plan with reality?

At the end of the day, put the calendar and the record next to each other. For every block, mark one of four results:

Then write one short reason for each result that isn’t “kept.” Don’t grade yourself. You are collecting evidence, not a score. The end-of-day report template has a layout that works for this, and it doubles as a note you can send to a manager or client if you need to.

Illustration:

BlockPlanActualResultWhy
Onboarding screens9:45 to 12:159:45 to 12:30, 2 screens leftOverranThree interruptions, new client assets
Pricing copy feedback1:00 to 1:451:00 to 1:30Kept
Buffer3:00 to 3:45Finished onboarding screensUsed as intendedAbsorbed the morning overrun
Developer questions3:45 to 4:303:45 to 4:00, then a callSwappedUnplanned call with PM

The mistake to avoid: only checking the blocks that went well, or skipping the comparison on bad days. The bad days carry the most information. A two-minute comparison on a chaotic day is worth more than a careful one on a calm day.

Step 6: How should you change next week’s plan?

Once a week, read back over your daily comparisons and look for repeats. One overrun is noise. The same overrun on three days out of five is a planning rule you got wrong.

Common patterns and what to change:

If you want a fuller picture than your daily notes give you, a week-long time audit is the next step. Our guide to doing a time audit on a Mac walks through it, the time audit template gives you a sheet to fill in, and the where does my week go calculator is a quick way to see how your hours divide up before you start.

Illustration: Over a week, the designer’s comparisons show the morning focus block overran four times, each time after a Slack question around 10:15. They change two things: Slack goes to “do not disturb” until 11:30, and the focus block gets a 30-minute tail of buffer built in. Everything else stays the same.

The mistake to avoid: redesigning your whole system after one bad week. Change one or two rules, run the next week, compare again. If you change everything at once, you won’t know which change helped.

Doing it by hand vs with a tool

ApproachEffortWhat you getCost
Manual log (paper or notes file)High. You write every switch yourselfA record exactly as detailed as your discipline on a given day$0
Toggl (timer-based)Medium. Start and stop timers, or use timesheets and calendar integrationsPrecise entries for tracked time; billable rates and team reports on paid plansFree plan for up to 3 users; Starter $9 per user per month billed annually, or $12 billed monthly
Rize (automatic)Low. Runs in the background on Mac or WindowsApp and website activity with AI categories; Google Calendar meetingsNo free tier; 7-day trial; Basic $9.99/mo billed annually, or $12.99/month billed monthly
Timely (automatic)Low. Background Memory tracker, you approve AI-drafted entriesPrivate timeline plus AI-drafted timesheets, aimed at teams that bill hoursNo free tier; 14-day trial; Starter $9 per user per month billed yearly, or $11 billed monthly
Dayflow (automatic)Low. Records your Mac screen in the backgroundAn AI-written timeline of your day stored on your Mac, exportable as Markdown$0, MIT licensed; optional Pro plan at $20 a month; macOS 14 or later

Dayflow is our product, so weigh that row with that in mind. For full plan details, see each vendor’s pricing page, and our pricing page for Dayflow.

Common mistakes

Where Dayflow is the wrong pick

Dayflow handles one step of this method: the record of what happened on your Mac. Several situations call for something else.

The bottom line

Time blocking works when it’s a loop, not a ritual: plan the blocks, record what happened, compare the two, change one rule, repeat. The planning part is the easy part. The record is what makes the loop work.

Pick whichever recording method you will actually keep up. A paper log is fine if you’re disciplined about it. Toggl suits people who like starting a timer and need billing or cross-platform apps. Rize and Timely give you a background record on paid plans, with Timely leaning toward teams that bill hours. Dayflow gives you a free, automatic record of your Mac with the data stored locally, as long as you don’t need billing, team reports or anything outside macOS.

Whatever you choose, do the ten-minute comparison tonight. One day of plan-versus-reality data will tell you more about how to block tomorrow than any template.

Frequently asked questions

What is time blocking?

Time blocking is planning your day by giving each task a specific slot on your calendar instead of keeping it on an open-ended list. A block says what you will work on and when. The calendar then shows how much of the day is already spoken for, so you see an overloaded day in the morning instead of discovering it at 6 p.m.

How many hours of my day should I time block?

There is no correct number, and anyone quoting one is guessing about your job. Start by blocking only your two or three most important outcomes plus your fixed meetings, and leave the rest open as buffer. After a week of comparing plan with reality, you will see how much unplanned work your days actually absorb, and you can size your blocks from that.

Is time blocking the same as timeboxing?

They overlap. Time blocking means reserving calendar slots for work. Timeboxing usually adds a hard limit: when the box ends, you stop and move on, even if the task isn't finished. Many people use both, blocking the day out and then treating a few blocks as strict boxes for tasks that tend to expand, such as email or polishing a draft.

What should I do when a time block runs over?

Decide on purpose instead of drifting. Either stop and move the rest of the task to a later block, or keep going and explicitly drop or shrink something later in the day. Then write down that the block overran and why. That one note is what lets you fix your estimates next week, which matters more than rescuing today's schedule.

How do I check whether I actually followed my time blocks?

You need a record of what happened that doesn't depend on end-of-day memory. That can be a running log where you jot the time whenever you switch tasks, a timer app you start and stop, or an automatic tracker that records your computer activity. Put that record next to your calendar, then mark each block as kept, overran, swapped or never started.

Can Dayflow create time blocks on my calendar?

No. Dayflow is a record of what you did, not a planner. It captures your Mac screen at one frame every 10 seconds and has AI write the day into a timeline. You plan your blocks in whatever calendar you already use, then use the Dayflow timeline as the reality side when you compare. Its AI summaries can miss or misread work, so check them.

What is the best way to track time blocks on Windows?

Dayflow won't help here, because it runs only on macOS 14 or later. Toggl is the stronger pick: the vendor lists web, Mac, Windows, iOS, Android and browser extension apps, plus a free plan for up to 3 users. If you want automatic tracking on Windows instead of timers, Rize supports Mac and Windows, with a 7-day trial and no free tier.

Is there a free way to compare my time blocks with what I actually did?

Yes. A paper notebook or a plain text log costs nothing and works if you write the time down whenever you switch tasks. Toggl's Free plan covers up to 3 users with timers and calendar integrations. Dayflow is $0 and MIT licensed on Macs running macOS 14 or later, with an optional Pro plan at $20 a month for managed cloud analysis.

Should I use a billing tool if I time block client work?

If you invoice by the hour, yes, and that tool should not be Dayflow, which has no invoicing, payroll or team reports. Toggl offers billable rates on paid plans and profitability reports on Premium. Timely drafts timesheet entries from a background timeline for you to approve. Either can sit alongside your calendar blocks as the record you compare against.

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