Turn your to-do list into a timeboxed schedule — a start & end time for every task
% added to each estimate (planning fallacy). 0 = none.
Minutes of transition / reset time.
Minutes. Longer tasks split into multiple focus blocks with a recovery break between — set this to your focus endurance.
Meetings/calls are pinned. Flexible tasks route around them.
Add a task to build your schedule.
A flat to-do list tells you what to do but never when — so the day fills with context-switching and reactive work and your real priorities slip. This time blocking planner fixes that. You enter your day's start and end, then each task with an estimated duration and priority. It inflates each estimate by a buffer to counter the planning fallacy, splits long tasks into focus blocks, routes flexible work around your fixed appointments, and lays it all out on a timeline with a start and end time for every block. If the day overflows, the lowest-priority tasks are flagged — never silently dropped.
Day: 09:00–17:00 (480 minutes available). Buffer 25%, break 10 min, max block 90 min. Tasks:
With a fixed 11:00 standup (30 min) pinned, the planner fills High-priority work first, drops a break between blocks, and routes around the standup. Total scheduled work = 75 + 38 + 150 = 263 min; with transitions and the fixed 30 min the day load is well under 480, so utilization lands around ~70% and the last block ends with comfortable slack. If you'd piled on three more hour-long tasks, the lowest-priority one would move to “Unscheduled — won't fit today.”
This is a planning aid, not a prediction. Block lengths are estimates inflated by a generic buffer; real durations vary, so treat the timeline as a default to defend, not a guarantee. The 25% default sits inside the research-backed 25–50% planning-fallacy range (measured mean underestimation ≈ 27%) — track your actual vs planned for ~2 weeks and recalibrate your own buffer. The 90-minute split cap reflects ultradian focus decay; it's a guideline, not a hard law. Context-switching costs (15–25 minutes of reduced performance per switch) are only partly absorbed by transition gaps. Everything runs locally in your browser — nothing is saved or sent, the tool doesn't sync with calendars or send reminders, and refreshing clears the plan. Reported productivity gains for time blocking come from studies of the method in general and aren't a promise about your individual results.
It assigns each task a real start and end time. You enter your day window and tasks; the planner buffers each estimate, splits long tasks at the max-block cap, routes around fixed appointments, and lays it on a timeline. Overflow is flagged, not dropped.
People underestimate task time by ~27% (the planning fallacy). A 25% buffer turns optimistic estimates into realistic blocks. Set it to 0% to ignore the effect, or higher if you tend to overrun.
Focus decays after ~90 minutes (ultradian rhythm). Tasks longer than your max-block length split into multiple focus blocks with a recovery break between. It's a guideline — lighter tasks tolerate 45–60 min.
The lowest-priority, latest tasks move to an “Unscheduled — won't fit today” list and you're told by how much you're overcommitted. High-priority work is protected and flagged, never silently dropped.
No — aim for ~70–85% utilization. Slack absorbs the inevitable overrun. Near or above 100% means one delay cascades through the whole day.
No. It runs privately in your browser, doesn't sync or remind, and refreshing clears the plan. Copy the text schedule to paste into your calendar yourself.
Yes — 100% free. Everything is calculated privately in your browser; nothing is stored or sold.
🔒 Everything is calculated in your browser. We don't store or sell your data. Planning aid, not a prediction.