What Is Timeboxing? The Complete Guide (2026)

Timeboxing means giving a task a fixed amount of time and stopping when it runs out, whether or not it is finished. It differs from time blocking, which reserves calendar slots, and Pomodoro, which repeats 25-minute work intervals. To run boxes, a timer such as Toggl works well; to check boxes against what you actually did, an automatic tracker like RescueTime, Rize or Dayflow on a Mac helps.

Timeboxing is giving a task a fixed amount of time in advance and stopping when that time runs out, finished or not. The time is the fixed part, and the scope of the work is what bends to fit it.

People usually get it wrong in one of two ways. They treat it as another word for putting tasks on a calendar, which is time blocking. Or they set the box and then quietly run over, which turns a timebox into an estimate nobody checks. The stop, and the review afterward, are the whole technique.

One disclosure before going further: Dayflow, a Mac app mentioned in the tools section below, is our product.

The short version

• Timeboxing caps a task at a fixed duration. When the box ends, you stop and decide what happens next.
• Time blocking is different. It reserves calendar slots for kinds of work. It answers “when”, while timeboxing answers “how long, at most”.
• Pomodoro is one specific timebox. It uses 25-minute intervals and short breaks, regardless of the task.
• The useful part is the gap. Comparing the time you planned with the time things actually took is what improves your estimates.
• Tools split into two jobs. Timers help you run a box. Automatic trackers help you check the box against what really happened.

What is timeboxing, exactly?

A timebox has three parts:

1. A task with a defined outcome. Not “work on the report” but “draft the methods section”.
2. A fixed duration. For example, 45 minutes.
3. A stop rule. What you do when time is up: ship it, book another box with a narrower goal, or drop it.

Most planning starts from the work and asks how long it will take. Timeboxing turns that around. It starts from the time you are willing to spend and asks how much useful work fits inside it. That shift matters because task estimates are usually wrong and rarely corrected. A time limit is something you can actually hold.

The term comes from project management. Agile software teams use fixed-length sprints and fixed meeting lengths, and they cut scope instead of extending the deadline. Applied to one person’s day, the same idea becomes: this task gets this much time, and no more without a deliberate decision.

The underlying problem is often summed up as Parkinson’s law, the observation by C. Northcote Parkinson that work expands to fill the time available for it. If a task has no limit, polishing, rereading and side-research will fill whatever time it is given. A box removes that slack.

Timeboxing vs time blocking vs Pomodoro

These three get used interchangeably, but they solve different problems.

	Timeboxing	Time blocking	Pomodoro
Core question	How long may this task take?	When will I do this kind of work?	How do I keep working in short bursts?
Unit	One task with a set outcome	A calendar slot, often for a category	A 25-minute interval plus a short break
Length	You choose it per task	You choose it per slot	Fixed by the method
What happens at the end	Stop and decide: ship, rebox or drop	Move to the next block	Take a break, then start another round
Main risk	Running over without noticing	Blocks fill with whatever shows up	Intervals cut through work that needs longer focus

Time blocking is most associated with Cal Newport, who uses it to protect long stretches of focused work. A block from 9:00 to 11:00 labeled “writing” tells you when to write, but not how much writing should be done or when to stop polishing. If you want more on that side of the idea, our deep work review covers it.

Pomodoro, attributed to Francesco Cirillo, uses 25 minutes of work and 5 minutes of rest, with a longer break after four rounds. It is a timebox with the length already chosen for you. That is helpful for starting tasks you are avoiding. It is less helpful when the work has a long warm-up, because the timer can ring just as you get going.

The three combine well. A common setup is a two-hour time block for project work, divided into two or three timeboxes with specific outcomes. Inside each box, you can run Pomodoro intervals if short bursts help you.

How does timeboxing work in practice?

Timeboxing works by moving decisions earlier. Before starting, you decide what “done enough” looks like and how much the task is worth to you in time. Once the box is running, you are no longer deciding whether to keep going. You only decide at the end.

Three things make that work.

A visible limit. A countdown you can see changes behavior more than a time you wrote in a notebook. Many people use a plain timer, a calendar event with an end alert, or a focus mode.

A defined outcome. “Answer email” has no natural end. “Clear the 12 emails flagged this morning” does. If the outcome is vague, the box ends and you cannot tell whether it worked.

A stop rule chosen in advance. Boxes come in two kinds:

• Hard boxes end at the limit with no exceptions. They suit perfectionism-prone tasks such as editing slides or tweaking a design.
• Soft boxes end at the limit unless you choose to extend by a fixed amount, such as 15 minutes, once. They suit tasks where stopping abruptly would cost more than finishing.

What does not work is a box with no consequence. If you routinely run 20 minutes over and keep going, you are estimating, not timeboxing.

How do you timebox your day? A five-step method

Here is a simple method that keeps the review step built in. Call it plan, box, run, stop, compare.

1. Plan the outcomes. List three to six tasks for the day, each written as an outcome you can check. “Send revised quote to client” rather than “quote stuff”.
2. Box each one. Give each task a duration based on what it is worth, not just what you guess it needs. Add a buffer box of 30 to 60 minutes for interruptions that will come anyway.
3. Run with a visible limit. Start a timer or calendar event for each box. Close or mute what is unrelated to the task if you can.
4. Stop and decide. When time is up, choose one of three: ship what you have, book a new box with a narrower goal, or drop it. Write a one-line note on which you chose.
5. Compare plan with reality. At the end of the day, put planned durations next to what actually happened. Note where you ran over, where you drifted to other work, and which estimates were far off.

Step 5 is the one most guides leave out, and it is the one that makes the next day’s boxes more accurate.

A worked example (made-up)

This is an illustration, not a real person’s data.

Maya is a freelance designer. On Tuesday she plans four boxes:

Box	Planned	Outcome
Client logo revisions	60 min	Three revised options exported
Invoice and email	30 min	Last month’s invoice sent, inbox under 10
Portfolio case study	90 min	First draft of the text
Buffer	45 min	Whatever comes up

What happens:

• Logo revisions take 60 minutes, but she exports only two options. At the stop, she ships two and books a 20-minute box for the third tomorrow. That is the method working.
• Invoice and email ends at 30 minutes on the clock, but looking back, about half of it went to reading a long newsletter thread. The box was kept, the outcome was not.
• Portfolio case study runs 40 minutes over because she never set a stop rule and kept rewriting the first paragraph.
• Buffer gets used by a client call that was not on the plan.

Her takeaways for Wednesday: the case study needs a hard box with a smaller outcome (“outline plus first section”), email boxes need the newsletter closed, and the buffer was the right call.

Notice that two of those lessons came from things she would not have remembered without a record. A timer would have shown that the email box lasted 30 minutes. It would not have shown what she did during it.

How do you check a timebox against what actually happened?

Planning is easy to feel good about. The review is where timeboxing earns its keep, and it depends on having an honest record of the day. There are three common ways to get one.

A manual log. At the end of each box, write what you did and how long it really took. It is free and makes you reflect, but it relies on memory, and memory tends to smooth over the 10-minute detours. A daily work log template gives you a structure for this.

A timer per box. Start a timer when the box starts and stop it when you stop. This tells you whether you ran over. It does not tell you what happened inside the box, and it misses anything you forgot to time.

An automatic record. Software that tracks app and website use, or the screen itself, in the background. You do nothing during the day, and at review time you see where the minutes went, including switches you would not have noticed.

Whichever you use, the review itself is short:

• Put planned and actual time side by side for each box.
• Mark each box as kept, overrun, or drifted (on time but spent partly on other work).
• Look for the same task type running over again and again. That is an estimate problem, not a discipline problem.
• Adjust tomorrow’s boxes, not your opinion of yourself.

If you want a rough sense of where a typical week goes before you start boxing, the where does my week go calculator gives you a starting picture to compare against.

What are the most common timeboxing mistakes?

Boxing activities instead of outcomes. “Two hours on the proposal” invites drift. “Pricing section of the proposal” gives you a finish line and a way to judge the box.

Planning with no slack. A day packed edge to edge with boxes breaks at the first unplanned call. A buffer box is part of the plan, not a sign of weakness.

Treating overruns as failures to hide. Running over is information. If you never record it, you never learn that “quick” code reviews actually take 50 minutes.

Ignoring your own estimation bias. Most people are consistently off in one direction. The time estimation test is a short exercise that compares your sense of time with a clock. It is not a diagnostic, just a way to see your own pattern. For people who struggle with time blindness, our piece on apps for ADHD time blindness covers the problem in more depth.

Using one box length for everything. Pomodoro’s fixed 25 minutes suits some tasks and fights others. Size the box to the work.

Skipping the review. Without step 5, timeboxing is a to-do list with timers attached. The comparison is what turns it into a feedback loop.

Tools that help with timeboxing

You do not need software to timebox. A kitchen timer and a notebook will do. Tools help with two separate jobs: running the box, and checking it afterward. The tool details below come from a comparison of each vendor’s own documentation, checked on October 4, 2026. For a wider list, see our roundup of Mac time trackers.

Tool	What it does for this	Price
Toggl (formerly Toggl Track) (Toggl for Mac compared)	Manual and real-time timers to run each box, plus timesheets and calendar integrations. The vendor also lists automated background tracking and a timeline in the desktop app, and a focus mode on the free plan. Cloud sync across web, desktop and mobile.	Free 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 (Rize alternative)	Automatic app and website tracking with AI categorization, useful for the review step. Google Calendar can be connected to capture meeting time. Mac and Windows, data hosted in the cloud.	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. 7-day trial, no credit card.
RescueTime (RescueTime alternative)	Background tracking of apps and websites, plus distraction blocking, focus sessions, goals and alerts that can help protect a box while it runs. Data is processed in the cloud.	Free Lite plan exists (limits not listed on the pricing page). Focus (Solo) $7/month billed annually ($84), or $9/month billed monthly. Solo+ $12/month billed annually ($144), or $15/month billed monthly. 14-day trial on paid plans.
Dayflow	Records your Mac screen at one frame every 10 seconds and has AI write the day into a readable timeline, for comparing planned boxes with what happened. Recordings and the timeline are stored on your Mac. Exports a date range as Markdown.	$0, MIT licensed. Optional Pro plan at $20 a month. macOS 14 or later.

As noted at the top, Dayflow is our product. It fits the review step: the timeline shows what you were doing inside each box, and with local AI through Ollama or LM Studio, the screenshot analysis stays on your Mac (details in local and cloud processing). It does not run, enforce or block anything during a box, and its AI summaries can miss or misread work, so check the timeline before relying on it.

When Dayflow is the wrong choice

• You want a timer to start and stop each box. Toggl (formerly Toggl Track) is built around timers and is free for up to 3 users.
• You want distractions blocked while a box runs. Dayflow has no website blocking. RescueTime lists distraction blocking and focus sessions.
• You work on Windows, or need team reports. Dayflow is Mac only and has no team reports, invoicing or payroll. Toggl covers Windows, mobile and team reporting, and Rize runs on Mac and Windows with team plans.
• You bill clients from your timeboxes. Dayflow does not produce invoices. Toggl’s paid plans include billable rates, and RescueTime’s Solo+ plan adds timesheets with billable rates.

The bottom line

Timeboxing is a limit, not a schedule. You decide how much time a task is worth, stop when that time is up, and choose on purpose what happens next. Time blocking decides when work happens, and Pomodoro is one fixed-length way of boxing it. They work well together.

Most of the value comes after the box ends. Comparing what you planned with what actually happened shows which estimates are always wrong and where your attention drifts. Do that with a notebook, a timer, or an automatic record, but do it. A week of honest reviews will teach you more about your boxes than any amount of planning.

Frequently asked questions

What is timeboxing in simple terms?

Timeboxing is deciding in advance how much time a task gets, then stopping when that time is up. The time limit is fixed and the amount of work is what flexes. If the box ends before the task does, you ship what you have, schedule another box, or cut scope. The point is to make time the constraint instead of letting a task run as long as it wants.

What is the difference between timeboxing and time blocking?

Time blocking reserves a slot on your calendar for a type of work, such as 9 to 11 for writing. Timeboxing puts a hard limit on a specific task, such as 45 minutes to draft the intro, and you stop when it ends. A time block says when you will work. A timebox says how long a task is allowed to take. Many people put several timeboxes inside one time block.

Is Pomodoro the same as timeboxing?

Pomodoro is one fixed form of timeboxing. It uses 25-minute work intervals with 5-minute breaks and a longer break after four rounds, attributed to Francesco Cirillo. General timeboxing lets you pick any length and ties the box to a task and an outcome. Pomodoro is built around the interval itself, so a long task becomes several pomodoros rather than one box sized to the work.

How long should a timebox be?

Size the box to the outcome and to how long you can hold attention on it. A common range is 25 to 90 minutes for focused work and 10 to 20 minutes for small admin tasks. Shorter boxes force decisions and expose drift sooner. Longer boxes suit work with a high warm-up cost, such as writing or debugging. Adjust after reviewing a week of planned versus actual times.

What should I do when a timebox runs out before the task is done?

Stop and choose one of three things on purpose: ship the current version, book a new box with a narrower goal, or drop the task. The worst option is quietly running over, because the next box then starts late and the whole plan slips. Write down how far over you would have gone, since that gap is the most useful number for estimating the next box.

How can I check whether I actually stuck to my timeboxes?

Compare the plan with a record of what happened. You can keep a manual log, run a timer for each box, or use an automatic tracker that records app and screen activity in the background. A timer shows how long you ran it. An automatic record also shows what you did inside the box, including switches to email or chat you would not remember.

Is Dayflow a good app for running timeboxes?

Not on its own if you want something to start, stop or protect each box. Toggl (formerly Toggl Track) is built around timers, and RescueTime lists distraction blocking and focus sessions, which Dayflow does not offer. Dayflow is better suited to the review step: it records your Mac screen at one frame every 10 seconds and writes a timeline you can compare against the plan.

Does timeboxing work for people with ADHD?

Some people with ADHD find external time limits helpful because they make time visible, and others find hard stops stressful. It is a technique to try, not a treatment. Short boxes, a visible countdown and an honest check of planned versus actual time tend to matter more than the exact method. If time blindness is the main issue, a record of where time went can make the gap concrete.

What is the difference between a hard and a soft timebox?

A hard timebox ends when the time ends, no exceptions. You stop mid-sentence if needed. A soft timebox ends at the time limit unless you make a deliberate decision to extend it by a set amount. Hard boxes suit tasks prone to perfectionism, such as polishing slides. Soft boxes suit tasks where stopping abruptly would cost more to restart than to finish.