Planned times that add up
Understand how planned time behaves when a task rolls over, and choose the right fix: timebox it again, give subtasks planned times, duplicate it, or plan it from a weekly objective.
To play videos here, allow cookies in your cookie settings. Or watch this one on Loom.
In this video
How to do it
- If a task rolls over with the wrong planned time, timebox it again on today's calendar and resize the block to the time left.
- For tasks with parts, add subtasks with their own planned times so the task's planned time is the sum of what's left.
- Delete a working session from a day you never got to, so the task drops off that day's list.
- Or duplicate the task with Cmd D (Ctrl D on Windows) and move the copy to the next day you'll work on it.
- For work you know spans several days, create a weekly objective and set a planned time on each day you'll work on it.
Transcript
Show the full transcript
Hey everyone, Alex here with a pro-tip video and I want to get into uh, the issue of multi-day tasks. This is probably one of the more common questions and confusions, uh, I get in support, uh, and there are sort of complex and maybe unintuitive behaviors and logics to tasks that I think are worth, clarifying and explaining here, as well as techniques and workarounds to handle the situations, the different types of situations,
when you have a task that you work on for multiple days. Since I'ma can handle these multi-day tasks, but there are some, some behaviors that are worth knowing and, and knowing how to handle. Um, so I wanted to set up a few different types of examples of multiple- Thank very much. We'll multi-day tasks, explain how they work, how you can handle them best, and advise what I think are, are some of the best practices here. So I've set up some examples and I'm gonna work through them one at a time, kinda isolating our view here,
and just talk through each one of them. Let's look at this first one. This is, I've just called this single task, and this is a very simple example of a-of a simple syn- Thank you. A single task that doesn't have sub-tasks, wasn't scheduled to the calendar, uh, and you can see in this example, I planned to work on this task for two hours yesterday. I only worked on it for one hour, but I didn't complete it, so I-I didn't mark it complete, and at midnight, as all incomplete tasks do, it rolled over to the th-the next day,
today, Wednesday. Uh, and this may be sufficient- enough solution for you to-to know about that. If you don't finish working on something, it'll roll over, and I could keep working on this task today, and ultimately check it off. The big downside that users face with this behavior is the task's plan time. As you can see today, Wednesday, the task is showing a plan time of two hours. It's not taking into account- account. The time that you've logged on a previous day, ah, and that's not always ideal.
That's not always what you want. This is just sort of a quirk of the logic of how tasks planned times work. Which is that they can really only have one true plan time. These are not two different tasks. They're the same task, so yesterday when it had a plan time of two hours today, it has a plan time of two hours because it is- This is the same. Same task. Umm, if that's something you want to solve, keep watching because I'll go through techniques to- to get around that. But if that's not super important,
in fact, a better example would be if you had a really small task. Like, it happens to me often where I might have a ten minute task, uh, and I'm- I do a part of it, but I'm blocked by someone's response or waiting for someone- someone's response, so I work for- work on it for five minutes, but I don't complete it, I let it roll over. I'm okay having, like, an incorrect plan time on the next day of ten minutes because that's kind of small enough that it doesn't matter. But something like a two-hour task where you're only gonna work on it for another hour.
If your plan time estimate was accurate, this isn't- this isn't always a great solution. Um, but I just wanted to explain the- basic behavior here of a task that rolls over is incomplete, not taking into account the previous day's actual time you logged. So let's go through another situation. Tasks with working sessions, and by working session I mean a task that you scheduled onto the calendar. Um, when tasks are pinned or time boxed to-
through the calendar and you create a working session on the calendar for that task, the tasks plan time logic changes to now be a sum of all the working sessions for that task. I'll show you what I mean. Um, let's say I took this task yesterday, let me say I just worked on it for, uh, 15 minutes, but I scheduled it to the calendar for one hour because I was planning to work on it for one hour. But I only worked on it for 15 minutes. I didn't complete the task, so it has rolled over to the next day, today,
and it still shows a plan time of one hour. Um, but if, if my, if I'm certain that my plan time is pretty accurate here, that I'm gonna spend just the remaining 45 minutes on it, how do I handle this? Well, a nice little trick you can do here is time box the task again, because, When you time box the task, uh, it's plan time for that day, will be respective to the working sessions you've planned for that day. I'll show you what I mean. I'm gonna schedule this task to
the calendar today. I'm just gonna drag the projection to pin it, but then I'm going to adjust the project, or the, the working session to, uh, 45 minutes here. Here. And we'll see if I show both days. Now I am seeing two different plan times. It's not really taking into account the time I worked on it yesterday. It's taking into account how long I've planned for it on the calendar. So this could be a nice workaround where you say, actually, I just, I know I won't only work on this for 45 minutes today. Schedule to the calendar and adjust the block on the calendar to the-
time you want. And now, when you're looking at your home view, at least, you will see the plan times respective to each day that you planned. I planned one hour for this task yesterday, 45 minutes today. That could be a good solution. The downside with this approach is that, like I mentioned, once you schedule a task to the calendar like this, it's overall plan time is a sum of all the workings of working so. So you'll see when I click into this task, it's overall cumulative plan time is an hour and 45 minutes,
because it is the sum of these two working sessions. Uh, the one hour yesterday and the 45 minutes today. Um, so that may or may not be ideal either, but if you're focused on your plan times being correct each day, rather than the overall task. I'm going ask. This could be a good solution. I quickly want to show one more thing. Let's say that, let me remove this block from the calendar. Um, oops. Let's say that I worked on this task,
uh, or I planned to work on this task yesterday, but I didn't even get to it. Um, now I have a situation where the task's plan time is two hours. Uh, the one hour block from yesterday and then the remaining, the, the overall. over a plan time is still carried over to today. In this situation where you didn't even get to it, the best thing to do might be to just delete this working session, to get it off yesterday's task list and get you back to that original plan time. So you'll see if I delete this working block from yesterday, the plan time drops down to one hour, it's off yesterday's task list and
I just have the, it's like nothing happened like I'm restarting. Um, so that could work. Let me get to, uh, uh, solution that I think is, is a little bit more elegant, um, especially with tasks that have multiple parts, um, or you know in advance are going to take multiple days, subtasks, and not just subtasks, but subtasks with planned times. If a task has subtasks, and those subtasks have planned
time, which they don't need to, you can create subtasks without planned times, like this. But if you do add planned times to your subtasks, the tasks overall planned time is the sum of the subtasks planned time. So you can see here, 10, 10, 30, 30, that makes up the, um, tasks overall planned time. And now when I look at a task that I worked on parts of yesterday and have parts remaining today, I see much more accurate planned times because I'm just,
I'm, I'm dealing with subtasks, really, not one big task. Um, I'm not focused on how long the overall task will take, but it's pieces. So I completed those two 10-minute subtasks yesterday. I, I have a plan time yesterday of the 20 minutes I worked on it, or planned. So those two pieces and worked on it. And today I just have the remaining bits. So, uh, a plan time of one hour, just representing the incomplete parts of that task. Um, I think this could be a nice solution.
Especially if it has multiple parts. Or even you could sort of proactively do this by, um, creating a subtask, just name a, The day that you're working on it. So I could create a new task and create subtasks for Wednesday and Thursday. Oops. Can't spell. And if I add, they already have a plan times there. If I were to work on just the Wednesday part of this, tomorrow when this task rolls over, again, I'll have, uh, just the 30 remaining minutes of it.
That could be a nice way to break it up. Proactively. Let me get to one last solution, and this is my preference, uhm, because it's just the cleanest, and it's, it may not fit your mindset of how you want tasks to work, but with, for me, I want to avoid all that complicated stuff with plan times when tasks, roll over. If I, whether or not I know in advance that a task is going to take multiple days, I like to just create tasks
for each day that I work on it. Um, so if I, if I work on this task today, um, you know, for 45 minutes and I don't complete it, I will probably do the following. I'm going to duplicate the task. Yes. And move the copy to tomorrow. And that way I can check off the task today. And tomorrow, I have not the same task, but a, a totally unique task, although it is a, an exact duplicate. But this way I can manage this one independently and not
worry about this complicated business of, of, you know, multiple days, plan times. I can just mess with this one. Uh. . And the nice part about duplicating is that it'll carry over all my notes and links that I've put in here, um, the channel. Uh, if it's coming from an integration, that works too, this, to duplicate the task. Um, I will do that. I'll do that if I, uh, am not planning to work on it multiple days, but that's what ends up happening. And I'll do it if I know in
advance that. Yeah. A task is going to take multiple days. And in fact, if I know in advance, a task is going to take multiple days. If I know that I have a task, I'm going to work on, partially on Wednesday, Thursday, and Friday. Honestly, my favorite thing to do is to create a very simple, weekly objective. Let's just call this big task. And I can either just drag this on, or I can click into here and say I'm gonna work on this for 20 minutes Wednesday. one. Thursday, 45 minutes fr- uh, Thursday, and 15 minutes Friday.
And what this has done is create three tasks very quickly with that same name. Um, and what's nice is they're all linked back to an objective where I can sort of see a bird's eye view at a glance of this, this bigger than normal task. Um, it's not like a big project, it's just something I'm chipping away. with. Add over a few days. If I know in advance, it's gonna take a few days, I'll probably do this approach. Um, so, I know that's a lot to take in. Uh, I just wanted to acknowledge all the sort of sometimes
unintuitive logic with tasks plan time and how it works when the task rolls over or is moved to the next day is incomplete. Um, and the different- approaches you can take to sort of manage that logic, uh, either by sub-tasks or scheduling it to the calendar or, uh, taking the simplest approach, um, in my opinion, just duplicating the task and- and- and having tasks specific to each day. Uh, I think that's a nice sort of peace-of-mind solution.
Um, and your analytics, your time tracking, all that stuff. stuff. will be, um, spot on. So, I hope this helps. Sorry for the very long video. Um, I know there's a lot of things going on here. Um, thank you so much for watching. Bye.
Questions
Why doesn't a rolled-over task's planned time subtract the time I already worked?
A task has one planned time, and it doesn't account for actual time logged on earlier days. A task that rolls over is the same task, so it keeps its original planned time.
How do I give a task a different planned time on each day?
Timebox it on each day's calendar. Once a task is timeboxed, each day shows the length of that day's working session, and the task's overall planned time becomes the sum of all its sessions.
Do subtask planned times change the task's planned time?
Yes. If subtasks have planned times, the parent task's planned time is their sum, so completing some subtasks leaves only the remaining time on the next day.