Splitting tasks
Letting long work spread across days, and why the smallest piece is thirty minutes.
Updated 8 September 2026
By default a task is placed as one block, which means it needs one free gap as long as the task. A three-hour piece of work on a day of back-to-back meetings will wait for a day that has three clear hours.
Tick Can be split on the task and it may be placed in pieces. Each piece is at least thirty minutes. The scheduler takes the first gap of at least that length, fills as much of the gap as the task needs, and continues in the next gap, on the same day or the next.
An example
A fifty-minute follow-up, marked splittable, on a day that is booked solid until 4:30 pm with a 5 pm finish. It takes 4:30 to 5:00 today and the remaining twenty minutes at 9:00 tomorrow. Without splitting, it would have waited for tomorrow entirely.
No slivers
The scheduler will not leave a final piece that is too short to be useful. If a split would leave, say, ten minutes at the end, the previous piece is shortened so the last one is a usable size.
What should not split
Anything continuous: a meeting, a workshop, a flight, a call. When you describe a task in plain words, the draft guesses this for you, and you can change it in the form.