# Multi-day tasks

A 6:57 Sunsama Pro Tips video in Multi-day tasks.

- Page: https://www.sunsama.com/pro-tips/multi-day-tasks
- Video on Loom: https://www.loom.com/share/2817210ff12d4f4c91b6fbbd32eaa864
- Topics: multi-day tasks, planned time, timeboxing, weekly objectives

## Summary

Timebox one task on several days to give each day its own planned time, or, when you know work will take days, create a separate task for each day and link them with a weekly objective.

## Steps

1. Timebox the task on today's calendar and resize the block to today's planned time.
2. Click the task's time stamp to open the mini calendar, move to another day, and click to add a second working session.
3. For work you know will take several days, duplicate the task with Cmd D (Ctrl D on Windows) and move the copy to the next day.
4. Align each day's task to the same weekly objective with R, so you can see them together.
5. Check off each day's task when that day's part is done.

## Chapters

- 0:00 Revisiting multi-day tasks
- 1:01 Why planned time doesn't shrink
- 2:07 Timeboxing across days
- 4:11 One task per day
- 5:15 Linking days with an objective

## Questions

### Why doesn't my task's planned time reflect what I already worked on?

Planned time doesn't take actual time into account, from today or any earlier day. If you want a different planned time per day, timebox the task on each day or create separate tasks.

### Is a task timeboxed on two days one task or two?

It's one task with two working sessions. Each day shows that session's length, and the task's overall planned time is the sum of its sessions.

### What's the best way to handle a task I know will take several days?

Create a distinct task for each day, by duplicating it or creating it from a weekly objective. Then you can check off each day's part without worrying about rollover.

## Transcript

[0:00] Hey everyone, uh, I think this video will be a refresher to many folks, especially longer term users and customers, but it's something that comes up regularly enough that I want to revisit it again and make a little refresher video on multi-day tasks or tasks that take multiple days to complete. But this time I'm going to sort of re-emphasize what I would recommend as an approach philosophically to these types of tasks. So let me get into it here. I filtered my workspace view to a single channel so I can just sort

[0:30] of show you some, some, uh, examples without cluttering, uh, what I'm showing you too much. And today I'm working on this task, Pro Tips, right now, that as you can see, I actually planned to do on Wednesday, but I didn't finish it. Um, you can see I barely got into it just for a few minutes, and then what I did is realized I wasn't going to get to it, and I didn't touch it. I let it roll over to Thursday when I also didn't get to it, and I let it roll over to today when finally I have the time to complete this task. And I'm showing you this because one

[1:01] of the questions I get asked is, hey, I worked on this task on one day, why doesn't my planned time on the next day reflect what I already worked on it? So, here you can see I worked on it for seven minutes. Why doesn't the task's planned time today show as 45 minutes minus the seven minutes I already worked on it? And the short answer is that that's not how planned time works on Sinsama tasks. It doesn't take into account actual time, whether you worked on it today or any previous day. And in general, it's an Sinsama tasks are not designed to be worked

[1:33] on multiple days, though you can totally do that. It's not something that they're designed to, to have, you know, distinct planned times on separate days. I'll get into how you can do that. But I wanted to show this example because this is an example where it's not like I worked on this task for 40 minutes on Wednesday and I didn't quite finish it, and then I let it roll over. It's that I barely got into it. So, I'm okay with my task, personally, having its full potential.

[2:07] You can have a task that spans multiple days that has distinct planned times for each day. Let me show you how you could do that. In order to do that, you would timebox your task. So let me create a multi-day task here, and let's set it for, whatever, 45 minutes today. If I timebox this task to the calendar today, As soon as I timebox the task, I'm any task, its planned time is derived from its working session's duration on the calendar. So you'll see as I change the duration here,

[2:40] the task's planned time will change. And now that I've timeboxed the task to the calendar, I can actually timebox it to the calendar again, whether today or on a future day. So let's say that this task I got into for, uh, 45 minutes today, and I I was gonna work on it tomorrow for another 15 minutes. What else? What I could do is, uh, timebox it again. The quick way to do that is click on the timestamp where it shows when you've timeboxed it. And here you can click in the calendar and even move to future days

[3:11] to timebox it again. So I could click here and make another little 15 minute working session for it. And now I have the same task timeboxed across two days and you'll see that actually it does display separate planned times. Uh, these are not separate tasks, they are the same task, but they have separate looking points. Planned times because I've timeboxed it and it's those working sessions durations that are, uh, determining how long, uh, the task is going to be worked on that day.

[3:41] If I click on it, I will still see sort of the cumulative history in view here. The planned time is the sum of all those working sessions. But that's one way that you can sort of get around this limitation, uh, of, of planned time not being specific to that day, uh, is timeboxing the task on, on each day for or how long you plan to work on it that day. Now, what I want to emphasize is, is a recommended workflow for when you know in advance that a task is going to take multiple days, which is not the case here.

[4:11] I didn't plan to not complete this task on Wednesday, um, but if I knew in advance that I was going to work on it Wednesday and not finish it and then work on it again Friday and so on and so forth, What I'd actually recommend is making multiple tasks. It's just a cleaner situation when you don't have to worry about rollover, or worry about these planned times, um, that I'm talking about and not worry about not completing the task today. If I know in advance that I have a big task that,

[4:44] uh, I'm, uh, going to work on maybe two days or maybe five days or whatever, I would highly recommend making multiple tasks for it for each day. That way, I could complete the task today and then move on to the next day where I have the next distinct task for them. So, um, this would be useful, for example, if you had a big task that maybe had a bunch of notes in it, really detailed notes, what you could do is, uh, duplicate the task. Now I have two copies of it, and I can take the second instance of it,

[5:15] put it on the next day I plan to work on it. That way, today, I can just check off this instance. I don't need to worry about rollover. I don't need to worry about distinct planned times. These are distinct tasks, so tomorrow's can have a totally different plan time, and so on. So for a test that might take two days. And you know in advance it'll take two days, this is a decent approach. Another approach, which I've shown to a lot of folks, is weekly objectives. This is where weekly objectives can really come in handy, where you make, um,

[5:47] some sort of objective that you use to link these distinct tasks to, so they're bound to each other in some way. So I could align this task to this objective, and this one too, and that way, um, I see all those aligned tasks under this objective, I can sort of track and see when I've planned to work on this. Again, that would be useful if I knew in advance that this task was going to take multiple days, I can just manage it one day at a time, one task at a time. Complete it here,

[6:17] add notes to it, whatever, and then whether you duplicate the task or you just create it again the next day with some distinct part, maybe the next day's part has slightly different, different, you know, notes or subtasks around it. Whatever. Now at least I have these two separate tasks that I don't need to worry about rollover and their plan time, all that stuff. So, uhm, just wanted to refresh on multi-day tasks here, uh, and, and re-emphasize that, in my opinion, if you know in advance a task is going to take

[6:47] multiple days, I would recommend creating multiple tasks for it and managing it one day, one task at a time. Uhm, hope that helps. Thanks so much for watching.
