Guide
Timeboxing means giving each task a fixed block of time and stopping when the block ends. Start with three boxes a day, each with a clear finish line, and use a kitchen timer you can see and hear. A paper plan and a friend for accountability cover most needs. On a Mac, Dayflow can add an automatic record of where each box actually went.
You open the calendar at 9:00 and the day looks reasonable. Report draft until 11, then email, a call at 2, then the slide deck. By 4:30 the report is half done, the deck has not been opened, and you could not say where the morning went. The plan was fine on paper. It just had little to do with the day you lived.
Timeboxing is the usual fix: give each task a fixed block of time, work on it only inside that block, and stop when the block ends. It sounds simple, and for many people it falls apart by Wednesday. This guide covers why that happens, seven small changes that make boxes hold up, and how to tell after a week whether any of them are working. One disclosure up front: Dayflow, a Mac app mentioned near the end, is our product.
Timeboxing itself is not complicated. A to-do list says what to do. A timebox also says how long the task is allowed to take and what you will have to show at the end. That limit is the useful part, and it is also where things go wrong.
The first problem is estimates. Most people plan from their best day, the one where nothing interrupted them and the task was as easy as it looked. Real days have a slow start, a question from a colleague and a file that will not open. So the boxes are too small from the beginning, and every box that runs over pushes the next one. If this sounds familiar, our piece on why we underestimate how long things take goes into it further.
The second problem is that boxes without a finish line expand. “Work on the report, 9 to 11” has no natural end. You can always polish one more paragraph, so the box ends whenever something else forces it to, usually the next meeting.
The third problem is that the end of a box is easy to miss. When you are absorbed, or when you have slid into something easier, the clock in the corner of the screen does not register. The box is technically over, but nothing tells you so.
The last problem is memory. At the end of the week you remember the plan clearly and the actual day only vaguely. You cannot fix estimates you never compare against reality, so next week’s plan repeats the same mistakes. None of this means you are bad at planning. It means the plan never got any feedback.
What to do. The night before, or first thing in the morning, choose three tasks that matter and give each one a box. Write them on paper or put them on the calendar. Leave everything else unboxed. Three is small enough to protect and big enough to move real work forward.
Boxing every hour feels thorough, but it means one late meeting breaks the whole plan, and a broken plan is easy to abandon. Three boxes can survive a messy day.
Illustration: a designer writes on an index card: “9:30 to 10:30, homepage hero, two directions. 1:00 to 1:45, reply to client feedback. 3:00 to 4:00, export icon set.” Everything else, including email and small requests, fits around those.
How to tell after a week. Count how many of your fifteen or so boxes actually happened at roughly the planned time. If most did, try adding a fourth. If fewer than half did, the problem is probably box size or placement, which the next two sections cover.
What to do. Size each box from what similar work actually took last time, not from what you hope it takes. If you have no record, take your gut estimate and add half again. Many people find 25 to 90 minutes is a workable range: short enough to see the end, long enough to get past the warm-up.
It also helps to know how your sense of time compares with a clock. The time estimation test is a short exercise that does exactly that. It is not a diagnostic, just a quick way to see whether you tend to run fast or slow.
Illustration: someone guesses that a weekly report takes 30 minutes. They look back and remember it usually runs into lunch. They box it for 60 minutes and finish with ten to spare, which feels better than running 30 minutes over.
How to tell after a week. Next to each box, write the minutes it actually took. If most boxes ran over, your sizing is still optimistic. If most finished early with room left, you can tighten them a little.
What to do. For each box, write one sentence that describes the output, not the activity. “Work on the proposal” is an activity. “Proposal sections 1 and 2 drafted, rough is fine” is an output. When the box ends, you can check whether you got there.
The finish line also makes stopping easier. If you reached it early, you can stop with a clear conscience. If you did not, you know exactly what is left.
Illustration: a developer changes “fix the login bug” to “reproduce the login bug and write down the cause, no fix yet.” The box is 45 minutes. The smaller target is reachable, and the fix gets its own box tomorrow.
How to tell after a week. Count how many boxes ended with the finish line met. If the number is low, the targets are too big for the box. Cut them in half, not the time.
What to do. Put a physical kitchen timer on the desk, set it when the box starts, and let it ring when the box ends. A visible countdown is easier to notice than a clock in the menu bar, and a sound you cannot ignore marks the end of the box even when you are absorbed.
When it rings, stop. Write one line about where you left off, so the next session starts quickly. Then decide on purpose: schedule another box, or accept what you have as good enough. The habit that breaks timeboxing is quietly running over, because every later box pays for it.
Illustration: a writer sets a 50 minute timer, gets interrupted by the ring mid-sentence, and writes “next: finish the bit about onboarding, then add the example” on a sticky note. The next morning she starts in under a minute.
How to tell after a week. Note how often you stopped when the timer rang versus how often you kept going. You are not aiming for perfect. You are checking whether the end of a box is now something you notice.
What to do. Between focused boxes, add 15 to 30 minutes of buffer. That is where messages, small requests and overruns go. At the end of the day, add a short closing box: check what got done, write down what did not, and sketch tomorrow’s three boxes.
The buffer is not wasted time. It is the honest acknowledgment that interruptions happen. When something lands mid-box, write it on a scrap of paper and deal with it in the buffer. A simple daily work log works well for the closing box.
Illustration: a project manager’s day reads “focus box, buffer, call, buffer, focus box, closing box.” When a stakeholder emails at 10:15, she jots it down and replies at 10:45 in the buffer.
How to tell after a week. Look at whether your focused boxes started on time more often than before. If buffers keep overflowing, your days have more interruptions than the plan allows, and you might need fewer focused boxes, not more discipline.
What to do. For the box you are most likely to avoid, work alongside someone. Sit together in a café, or share a video call with cameras on and microphones off. Say what your box is at the start, and say whether you hit the finish line at the end. This is often called body doubling, and our guide to body doubling covers how to set it up.
The other person does not need to help with the task. Their presence makes it harder to drift, and saying the finish line out loud makes it more concrete.
Illustration: two friends who both work from home meet on a call at 9:00 three mornings a week. Each says one line, “taxes, gather receipts into one folder,” then they mute and work for 50 minutes.
How to tell after a week. Compare the boxes you did with company against the ones you did alone. If the shared boxes land more often, keep them for the work you dread most.
What to do. Once a week, set aside 20 minutes. Put the plan next to what actually happened and look for patterns: which boxes ran over, which ones never started, what kind of work kept leaking into the day. Then size next week’s boxes from that. A time audit template gives the review a simple structure, and the where does my week go calculator helps if you want a rough picture of how the hours divide.
This is the step that makes timeboxing improve over time. Without it, you keep planning from your best day.
Illustration: after one week, a consultant notices that every Monday morning box was eaten by email from the weekend. Next Monday she plans a 45 minute email box at 9:00 and starts the focused work at 10:00.
How to tell after a week. You are on track if you can point to one concrete change you made for next week based on what you saw. If the review is mostly guessing because you cannot remember what happened, that is the gap the next section is about.
The weekly review depends on knowing what really happened, and memory is usually the weakest part. Paper logs work, but only if you remember to fill them in, and on busy days you won’t. If you have ever asked where did my day go, this is the part of timeboxing that answers it.
Dayflow is a free Mac app that records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. There is no timer to start, so a box that drifted into something else still shows up. Full screen recordings and the local timeline are stored on your Mac. You can choose local AI, which runs a supported model on your Mac through Ollama or LM Studio and keeps screenshot analysis on-device, or send selected screenshots to your own cloud provider or to Dayflow Pro. The details are on our local and cloud processing page. You can export a date range as Markdown from Settings → Export and put it next to your plan.
The app is $0 and MIT licensed, with an optional Pro plan at $20 a month (see pricing). It needs macOS 14 or later. AI summaries can miss or misinterpret work, so treat the timeline as a starting point. The facts here come from Dayflow’s own documentation as of September 2026.
Dayflow publishes this article.
For running the box itself, a kitchen timer beats Dayflow. A timebox needs a visible countdown and a signal at the end, and a cheap physical timer does that better than any screen record.
Dayflow is Mac only. If your boxes happen on a Windows machine, a phone or a tablet, it will not see them.
It sees only the screen. Phone calls, whiteboard sessions, reading on paper and meetings away from the desk will not appear in the timeline unless something on screen reflects them.
It is a record, not a coach. It will not plan your boxes, tell you when one is over or push you back on task. It does not provide website blocking, so if what you need during a box is a hard stop on certain sites, you need a separate blocker.
It has no invoicing, payroll approvals or team reports. If your boxes also need to become client invoices or team timesheets, look at our roundup of Mac time trackers for tools built around billing.
And if you would rather not have your screen recorded at all, even locally, a paper log and an honest Friday review will do the job.
Timeboxing works when the boxes are few, sized from real experience, and given a clear finish line. Start with three boxes tomorrow, a kitchen timer on the desk and a one-line target for each. Leave buffers, stop when the timer rings, and bring in a friend for the box you would otherwise avoid.
Then, once a week, compare the plan with what actually happened. That review is what turns a nice-looking calendar into estimates you can trust. Paper is enough for most people. If you are on a Mac and keep finding that you cannot remember the day well enough to review it, an automatic record like Dayflow can fill that gap.
Timeboxing is a planning method where you give a task a fixed amount of time in advance, work on it only during that window, and stop when the time is up. The box has a start, an end and a definition of what you will have to show for it. It differs from a to-do list, which says what to do but never says how much time each item is allowed to take.
Many people find that 25 to 90 minutes is a workable range, but the right length depends on the task and on you. Shorter boxes suit work you tend to avoid, because the end is always in sight. Longer boxes suit work that needs a warm-up, like writing or debugging. Try one length for a week, note which boxes you finished, and adjust from there.
The terms overlap and people use them loosely. Time blocking usually means reserving calendar time for a kind of work, such as email from 9 to 10. Timeboxing adds a hard stop and a defined output for a specific task, such as a first draft of section two in 45 minutes. You can use both: blocks shape the week, boxes shape the hours inside them.
Stop anyway, then decide on purpose. Write one line about where you left off, and either schedule a new box for the rest or accept the current version as good enough. Quietly running over is what breaks the method, because every later box gets squeezed. An unfinished box is also useful data: it tells you the next estimate for similar work should be longer.
It can, if the plan expects interruptions instead of pretending they will not happen. Box less of the day, leave buffer boxes between focused ones, and keep a short box for messages and requests. When an interruption lands mid-box, note it on paper and return to it in the buffer. Over a week you will see roughly how much of each day interruptions really take.
No. A sheet of paper with three boxes written on it and a kitchen timer cover the core of the method. A calendar helps if other people need to see when you are busy. Software becomes useful mainly at review time, when you want to compare the plan with what actually happened without relying on memory.
Not really, and a plain kitchen timer beats it for this job. A timebox needs a visible countdown and a clear signal when time is up, and a cheap physical timer does that well. Dayflow is a record of what was on your Mac screen, written up by AI into a timeline. It is useful for reviewing where boxes went afterward, not for running the box itself.
No. Dayflow does not provide website blocking. It records the screen at one frame every 10 seconds and has AI write a timeline of the day, so it can show you afterward that a writing box drifted into browsing. If you want something that stops you from opening a site during a box, you need a separate blocking tool.
Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month that manages cloud analysis. It runs only on Macs with macOS 14 or later, so it does not run on Windows or on a phone. The free app can use local AI through Ollama or LM Studio, or your own cloud provider, whose charges and terms apply.
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