Todoist time blocking: a worked example with the numbers
Todoist itself has no calendar grid, so "time blocking in Todoist" means giving each task a duration and priority inside Todoist, then dragging those tasks into slots on a calendar you pair with it, usually Google Calendar through Todoist's own sync. The blocks live on the calendar; Todoist just supplies the list they're built from.
What "time blocking in Todoist" actually means
Todoist gives you due dates, priorities, labels, and an optional duration field on any task. What it doesn't give you is an hour-by-hour grid. So when someone searches "Todoist time blocking," they usually want a way to turn a Todoist list into blocked time on a calendar. Todoist supplies the list, a calendar app supplies the grid, and the two connect through Todoist's own two-way Google Calendar sync: tasks with a due date and time show up on the calendar, and calendar events can flow back into Todoist as tasks.
Why Todoist needs a calendar to do this at all
Todoist has grown to more than 30 million registered users, according to Wikipedia's entry on the app, so a lot of people are already living inside it for capture and prioritization. But a task list on its own can't lay your day out end to end the way a calendar can. Every task list without a calendar view has that same gap. Pairing the two just hands each tool the one job it's actually built for: Todoist decides what and how urgent, the calendar decides when and for how long.
The numbers behind a Todoist day
Todoist's own Productivity view sets a default daily goal of five completed tasks and a weekly goal of twenty-five, according to Todoist's help documentation, and it awards Karma points for finishing tasks on time. Those defaults are a reasonable anchor for how many blocks a single day can actually hold. Five real blocks, each with a duration attached, is a fuller day than it sounds once you count a lunch break, a commute, and the ten or so minutes it takes to mentally shift from one task to the next.
| Task | Todoist duration | Calendar block |
|---|---|---|
| Reply to priority emails | 25 min | 9:00 to 9:30 |
| Draft the client proposal | 50 min | 9:45 to 10:45 |
| Call the supplier about the delay | 15 min | 11:00 to 11:15 |
| Review the proposal with a coworker | 30 min | 1:00 to 1:30 |
| Update the project tracker | 20 min | 3:30 to 3:50 |
That's five tasks, matching Todoist's own default daily goal, with 15 minutes of built-in gap between most of them for the transition time a back-to-back schedule usually eats silently.
Priority labels do some of the sorting work before a single block gets placed. Marking the proposal and the supplier call as Todoist's top priority level, and leaving the tracker update and email reply lower, means that if only three of the five blocks survive a rough morning, the calendar drag-and-drop naturally favors keeping the two that matter and dropping the two that don't, rather than defending whichever block happened to get placed first.
Where the blocks actually break
The proposal draft, budgeted at 50 minutes, is the one most likely to run long, since writing tasks are notoriously hard to estimate. If it takes 80 minutes instead, the 11 a.m. supplier call still has to happen at 11, because that's when the supplier is reachable, so the proposal review at 1 p.m. either gets pushed or gets rushed. This is the same failure every time-blocked calendar runs into eventually: a duration guessed inside a task list meets a calendar that has no memory of which times were flexible and which weren't. Pushing every remaining block back by the same 30 minutes feels like the natural fix in the moment, but it quietly assumes the rest of the day has 30 spare minutes sitting in it, which it usually doesn't; by 3 p.m. the tracker update has nowhere left to land.
A looser alternative: windows instead of blocks
Guessing durations more precisely doesn't really fix this, since that's a skill that resists getting better with practice for a lot of people. Dropping the idea that every task needs an exact slot does more good. The supplier call genuinely needs a fixed time, since it depends on someone else's hours. The proposal draft needs something looser: an earliest start, once the emails are handled, and a deadline before the 1 p.m. review, with the exact minutes in between left alone. Time windows versus due dates covers that distinction directly, and why classic time blocking breaks down and what a looser version looks like goes further into the same overrun problem from a different angle. Todoist can hold the list of tasks either way; the difference is whether you're forcing all of them into exact slots or letting most of them float inside a window and only pinning the ones the world has already pinned for you.
Setting this up without redoing your whole system
You don't need to abandon Todoist to try the looser version. Keep due dates for anything genuinely fixed, and for everything else, write the earliest sensible start and the real deadline in the task name or a comment until you decide whether you want a tool built around that structure natively. Drifta treats every task that way by default: an earliest start time, a deadline, or both, set once on the task's edit screen, so the day holds together even when the first block of the morning runs over. If you've already tried pairing Todoist with a calendar and it kept collapsing by early afternoon, that's usually why, and it's worth reading a closer look at Google Calendar's own limits for time blocking before assuming the problem is your estimating.
Common questions
Does Todoist have its own time-blocking feature?
Not a calendar grid, no. Todoist has durations, due dates, priorities, and labels, which you use to plan what goes into a block, but the actual blocking happens on a connected calendar app, most commonly through Todoist's built-in Google Calendar two-way sync.
How long should a Todoist task's duration be if I'm not sure?
Round up from your first guess, then add roughly 25 percent. If you guess twenty minutes, block twenty-five. Most time-blocking failures come from underestimating, not overestimating, so the safer error is a block that finishes a little early.
What's a realistic number of blocked tasks per day?
Somewhere between four and six blocks that require real focus is realistic for most days once you count meetings, breaks, and transition time between tasks. Todoist's own default productivity goal is five completed tasks a day, which lines up with that range.
What should I do when a Todoist block runs long?
Let it run and shrink or drop the next block rather than pushing every remaining block later by the same amount. A schedule that shifts everything down the line after one overrun usually collapses by early afternoon; one dropped block is a smaller loss.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.