Guide
Time blocking means assigning every working hour a specific task on your calendar, then checking the plan against what happened. A calendar is enough to plan. For the review, Toggl suits freelancers who bill by the hour. Timely suits teams that turn tracked time into timesheets. Rize records app use automatically on Mac or Windows. Dayflow writes a free, local timeline of your Mac day.
Time blocking is a way of planning your day by giving every working hour a specific job on your calendar before the day starts. Instead of a list of things to do, you end up with a schedule of when you will do them.
People get it wrong in two ways. Some treat the plan as a promise, so the first meeting that runs long breaks the whole day and they give up on the method. Others never check the plan against what actually happened, so they repeat the same estimating mistakes week after week. Planning is half the method. Reviewing against reality is the other half, and it is the half most guides skip.
A note before we start: Dayflow, the Mac app behind this blog, is our product. It appears once, in the tools section near the end. That section is a comparison of vendor documentation as published on October 4, 2026, and nothing more.
A time-blocked day is a calendar where nothing is unassigned. Every stretch from start to finish has a label: “Draft proposal,” “Email and Slack,” “Team standup,” “Lunch,” “Buffer.” When one block ends, you already know what the next one is for.
Blocks come in a few common types:
The idea has been around in planners and calendars for a long time. It became widely discussed through Cal Newport, who describes a version he calls time-block planning in his writing on deep work. If you want the background on that wider idea, see our deep work review.
The key mental shift is that time blocking turns a vague intention (“I’ll work on the proposal today”) into a concrete appointment with yourself (“Proposal, 9:00 to 11:00”). Once work has a time attached, you can see whether the day actually has room for it.
These four ideas are often used interchangeably. They answer different questions.
| Method | Question it answers | When you decide | What it misses on its own |
|---|---|---|---|
| To-do list | What needs doing? | Any time | When it will happen, and whether it fits |
| Time blocking | When will each thing happen? | Before the day or week | Whether the plan was realistic |
| Timeboxing | How long may this task take? | At the start of a task | Where the task sits in the day |
| Time tracking | Where did the time actually go? | During or after the work | What you intended to do |
A to-do list is the input to time blocking. You pick items from the list and place them on the calendar.
Timeboxing is a rule you can apply inside a block. If your “Proposal” block ends at 11:00, a timeboxing mindset says you stop at 11:00 and move on, even if the draft is rough.
Time tracking is the mirror image of time blocking. Blocking is the forecast. Tracking is the record. You need both to know whether your forecasts are any good.
The mechanics are simple. You open a calendar, look at the day or week ahead, and fill the open space with labeled blocks. Most people use their normal work calendar so meetings and blocks live in one place. Some prefer a paper planner because it is harder to over-schedule when you have to write each block by hand.
A few practical choices shape how it feels:
Planning horizon. Some people block the next day at the end of each workday. Others sketch the whole week on Sunday or Monday and fill in details each morning. A weekly sketch helps protect focus time before meetings fill the calendar.
Block size. Blocks of 30 to 120 minutes are typical. Focused work usually needs longer blocks because getting started costs time. Shallow tasks fit shorter ones.
Visibility. Putting blocks on a shared calendar signals that the time is taken. Keeping them private avoids awkward conversations but makes it easier for others to book over them.
Flexibility. The plan is a draft. When something urgent arrives, you do not abandon blocking. You stop, look at the remaining hours, and redraw them. The aim is not to obey the morning’s schedule. It is to always have a deliberate plan for the time that is left.
This is a simple loop you can start tomorrow. It has eight steps, and the last one is the one that makes the others improve over time.
Steps one through seven are planning and running. Step eight is the feedback loop. Without it, you are making the same forecast every day with no way to tell whether it is accurate.
This is an invented example to show the method, not a real person or real data.
Sam is a freelance developer working on a client app. On Tuesday evening, Sam plans Wednesday. The outcome for the day is “checkout bug fixed and deployed, and the estimate for the next feature sent to the client.”
| Time | Planned block | What actually happened |
|---|---|---|
| 9:00 - 9:30 | Email and Slack | Email and Slack, ran to 9:50 after a client question |
| 9:30 - 11:30 | Fix checkout bug | Started 9:50, reproduced bug, found cause at 11:15 |
| 11:30 - 12:00 | Client call | Client call, on time |
| 12:00 - 12:45 | Lunch | Lunch |
| 12:45 - 14:15 | Deploy fix, write tests | Tests took longer than expected, deployed at 14:40 |
| 14:15 - 15:00 | Buffer | Used up by the deploy overrun |
| 15:00 - 16:30 | Write feature estimate | Started 15:00, interrupted twice by Slack, finished 16:45 |
| 16:30 - 17:00 | Daily review | Review at 16:45, ten minutes |
A few things stand out when Sam reviews this.
The morning email block overran because Sam answered a question that could have waited. That one decision delayed the focus block by twenty minutes. Next time, the email block ends on time and the reply goes in the afternoon shallow block.
The bug fix itself fit roughly inside its planned time once it started. The estimate was fine. The start time was the problem.
Writing tests was underestimated. A single day cannot prove a pattern, but if it shows up again on Thursday and Friday, Sam should pad test-writing blocks by default.
The buffer did its job. Without it, the overrun would have eaten the estimate block and the second outcome would have slipped to Thursday.
The afternoon interruptions came from Slack being open during a focus block. That is a habit problem, not a planning problem, and it is only visible because Sam compared the plan with what happened.
None of this needs a complicated system. It needs an honest record of the day next to the plan.
This is the angle most time blocking advice skips, and it is where the method either gets better or quietly fails. There are three ways to get the “actual” column.
From memory. At the end of the day, you write down what you think happened. It costs nothing, but memory smooths things out. Interruptions, quick detours and context switches tend to disappear, and the day looks closer to the plan than it was.
With a timer. You start and stop a timer as you switch tasks. This is accurate when you remember to do it, and it fits well with blocks, because each block is a natural moment to start a timer. The weakness is the switching you do without noticing, which is exactly what a review is supposed to catch.
With an automatic record. Software records what you worked on in the background, and you read it back later. You do not have to remember to start anything, so unplanned switches show up. The trade-offs are privacy, cost and setup. Our guide to Mac time trackers covers the main options.
Whichever source you use, look at the same few things during a review:
A daily review can be five minutes with a simple daily work log. A weekly review is where patterns show up. If you want a rough picture before you start, the where does my week go calculator lets you sketch how your hours split across meetings, focus work and everything else.
Planning the ideal day instead of the real one. If your days usually include an hour of unplanned messages, a plan without that hour is fiction. Plan for the day you actually have.
No buffers. A calendar packed edge to edge breaks at the first overrun. One or two empty blocks make the rest of the plan survivable.
Blocks that are too vague. “Work” or “Project X” is not a block. “Write the intro and outline for Project X proposal” is. Vague blocks invite drifting.
Treating a broken plan as failure. Plans break. The method is to redraw the rest of the day on purpose. People who quit after a bad Monday usually expected the plan to be a contract.
Blocking focus work into your worst hours. If afternoons are when you are tired and interruptible, a three-hour writing block at 15:00 is likely to fail no matter how well you plan it.
Never reviewing. Without comparing plan to reality, your estimates never improve. This is the most common reason time blocking feels like it stopped working after a few weeks.
Over-engineering the system. Color codes, nested categories and complex templates can become a way of avoiding the work. A plain calendar and a short daily review are enough to start.
You can plan blocks in any calendar. The tools below help mostly with the review side: recording where the time actually went so you can compare it with the plan. This article covers Toggl (formerly Toggl Track), Rize and Timely, plus Dayflow. For more detail, see our comparisons of Toggl for Mac, Rize alternatives and Timely alternatives. If you are choosing a general time tracker for Mac, our Mac time trackers guide covers more options.
| Tool | What it does for this | Price |
|---|---|---|
| Toggl (formerly Toggl Track) | Manual and real-time timers, timesheets and calendar integrations. The vendor also lists automated background tracking and a timeline in the desktop app, plus project planning with timelines, tasks and capacity management. Cloud-based, on Web, Mac, Windows, iOS, Android and browser extensions. | Free plan for up to 3 users. Starter $9 per user per month billed annually, or $12 per user per month billed monthly. Premium $16 per user per month billed annually, or $24 per user per month billed monthly. Enterprise: contact vendor. 30-day trial on paid plans. |
| Rize | Automatic app and website tracking with AI auto-categorization and tagging. Google Calendar can be connected to capture meeting time. Mac and Windows. The vendor states data is hosted on Amazon Web Services. | No free tier. Basic $9.99/mo billed annually, or $12.99/month billed monthly. Pro $23.99/mo billed annually. Max $39.99/mo billed annually. Team $29.99/seat/month with annual billing, or $39.99/seat/month billed monthly. 7-day trial. |
| Timely | A Memory tracker records work in the background into a private timeline, and AI drafts timesheet entries for you to approve. Manual timer included. Cloud-based. | No free tier. Starter $9 per user per month billed yearly, or $11 per user per month billed monthly. Premium $16 per user per month billed yearly, or $20 per user per month billed monthly. Unlimited $22 per user per month billed yearly, or $28 per user per month billed monthly. Enterprise: contact sales. 14-day trial. |
| Dayflow | Records the screen at one frame every 10 seconds and has AI write the day into a readable timeline, so you can set it next to your planned blocks. Recordings and the timeline are stored on your Mac. Mac only, macOS 14 or later. | $0, MIT licensed. Optional Pro plan at $20 a month. |
Dayflow is our product, so weigh this section accordingly. It fits the review half of time blocking for one person on a Mac who wants a written record of the day without starting timers. It does not plan blocks, and it has no invoicing, payroll approvals, team reports or website blocking.
A note on Dayflow’s data: analysis can run with local AI on your Mac, through your own cloud provider, or through Dayflow Pro. With Pro, screenshots are deleted after processing under the privacy policy, and activity data may be retained for sync. AI summaries can miss or misread work, so check them before relying on them.
Time blocking is simple: give every hour a job before the day starts, and redraw the plan whenever it breaks. The part that makes it work long term is the review. Put the plan next to what actually happened, look for overruns, late starts and interruptions, and adjust your estimates.
You need nothing more than a calendar to begin. Add a tracker only when you notice your end-of-day memory is too fuzzy to review honestly, and pick it based on what you need the record for: billing, team reporting, or simply seeing where your own day went.
They overlap but are not the same. Time blocking decides when each piece of work happens by placing it on your calendar. Timeboxing sets a fixed limit on how long a task may take, and you stop or ship when the limit hits. Many people combine them. They block a slot on the calendar and treat its end time as a hard box rather than a suggestion.
There is no correct length, but most people use 30 to 120 minutes. Focused work like writing, coding or design usually needs a longer block because getting started takes time. Admin, email and quick calls fit shorter blocks, often batched together. If you keep failing to finish a block, the length is probably wrong for that kind of task, so adjust it during your weekly review.
Re-plan the rest of the day instead of abandoning it. Take five minutes, look at what is left, and move or drop blocks so the remaining hours are realistic. Do not squeeze the missed work into evening hours by default. A broken plan is normal. The point is to make a fresh decision about the hours you still have rather than drifting.
Yes, and it is often more useful then. Meetings are fixed blocks you place first. The gaps between them become visible, and you can decide which gaps are long enough for focused work and which are only good for email or prep. Some people also block a recurring focus slot several days ahead so meeting invites cannot take it.
Yes. A paper planner with the day split into half-hour lines works, and so does any calendar app. The method only needs a place to write the plan and a way to note what really happened. Apps help mostly with the review side, because recording actual time from memory at the end of a day tends to be vague and flattering.
Compare planned blocks with what actually happened for a week or two. Look for tasks that always overrun, blocks that get eaten by interruptions, and times of day when you rarely do what you planned. Those patterns tell you how much padding to add. A quick exercise that compares your sense of time with a clock can also show whether you tend to under- or overestimate.
Toggl or Timely beats Dayflow here. Toggl offers billable rates on paid plans and timesheet approvals and profitability reports on Premium. Timely uses AI to draft timesheet entries for you to approve and is aimed at teams that bill hours. Dayflow has no invoicing, payroll approvals or team reports, so it helps you see your own day, not bill it.
No. Dayflow is a Mac app that records the screen at one frame every 10 seconds and has AI write a timeline of what you did. It covers the review half of time blocking, not the planning half, and it does not block websites. You still plan blocks in your calendar or planner, then compare them with the timeline.
Task batching groups similar small tasks, like replying to email or approving pull requests, so you do them together instead of scattered through the day. Time blocking is the wider method of giving every hour a job. Batching usually lives inside a time-blocked day as one or two shallow-work blocks, which keeps small tasks from interrupting focused blocks.
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