# Pro-tips for dealing with multi-day tasks

A 5:22 Sunsama Pro Tips video in Multi-day tasks.

- Page: https://www.sunsama.com/pro-tips/pro-tips-for-dealing-with-multi-day-tasks
- Video on Loom: https://www.loom.com/share/cd0658ac09c349bb811d904dc1e09a0a
- Topics: multi-day tasks, rollover, breadcrumbs, weekly objectives

## Summary

Let unfinished tasks roll over with credit for the time or subtasks you completed, or create one task per day from a weekly objective when you know the work will take several days.

## Steps

1. Log actual time on the task, or check off the subtasks you finished today.
2. Leave the task incomplete to roll it over at midnight, or drag it to tomorrow's column now.
3. For work you know spans days, create a weekly objective for it.
4. Click the objective, click a day of the week, and set a planned time to create that day's task.
5. Check off each day's task when its part is done, and click the objective to see all its linked tasks.

## Chapters

- 0:00 Handling multi-day tasks
- 0:30 Rolling over with a breadcrumb
- 1:34 Subtasks that carry over
- 3:11 Daily tasks from an objective
- 4:45 Tracking progress on the objective

## Questions

### What happens if I don't finish a task today in Sunsama?

If you leave it incomplete it rolls over to tomorrow automatically. If you logged actual time or completed subtasks, a breadcrumb stays on today to show you worked on it.

### Do incomplete subtasks roll over too?

Yes. The parent task moves to the next day with only its incomplete subtasks left to do, and today keeps credit for the ones you finished.

### How do I create a task for each day from a weekly objective?

Drag the objective into a day's task list, or click the objective, click a day of the week and set a planned time. Each day gets its own task aligned to the objective.

## Transcript

[0:00] Hey everyone, let's talk about a few ways that you can handle multi-day tasks, or tasks that take more than one day to complete. Sansama has some handling built in for this, so I just want to show some basic use cases, common things that people may run into, to show you the behaviors to expect in advance so you can manage these and not be too worried. We'll just go through a few different scenarios, there's no right or wrong way here, I just want to show some common techniques. Let's take this first task, let's say I plan to work on it

[0:30] today. But in actuality, I only was able to work on it for an hour and a half, and more importantly, I didn't actually finish the task. How do I handle this task, knowing it's not done, and I want to continue working on it tomorrow? Well at this point, I don't actually have to do anything. Because I leave this task incomplete, it will automatically roll over to tomorrow, and I'll see it in tomorrow's task list. If that leaves you feeling uneasy for any reason, you can preemptively do this and just drag it the task

[1:01] to the next day. Because I logged actual time on the task today, I still see it and I get credit for having worked on it. We call this a breadcrumb in Sansama. This is the same task, you see there's no completion circle here, so I can come tomorrow, continue working on this task, and check it off. But because I logged actual time, I'm getting credit for having worked on it, as you can see here. And I don't need to worry about losing the task because of Let's take another scenario where the same

[1:34] sort of behavior manifests. Maybe you have a slightly more complex task that has subtasks. Well, completion credit or breadcrumbs sort of act the same way here. Let's say instead of, or in addition to, logging actual time, I just complete certain parts of the task. So let's say I completed subtasks 1 and 2 today, but I'm not done with the entire task yet. Again, just leave the task in completion. And it will automatically roll over to the next day with the incomplete parts

[2:06] only. Or, again, preemptively you could do this and just drag this to the next day. And you'll see the incomplete parts, the subtasks, and more importantly the main parent task are left incomplete on the next day. So, again, tomorrow I could continue working on this, check this off, and I'll get credit on it on the days that I worked on it. These are good techniques and good things to remember for the those tasks that you don't necessarily plan will take multiple days. Tasks maybe you expect to complete in one day but don't.

[2:39] Or maybe for tasks that you think might take two, maybe three days at most. I say that because this is all well and good and this works well, but if your tasks are more complex than this, or we're talking about several days of breadcrumbs, things can get a little complicated. Everything works, but it's a lot to sort of manage and juggle when it's warm. One single task spread across multiple days. If you know in advance that a task is going to take multiple days to complete, there are other ways you can handle this and I'll show a

[3:11] technique that I personally like to use. If I know I'm going to work on a task, let's say Thursday and Friday, I'd rather just have individual tasks on each of those days so that I can check them off and feel good about completing that day's part of it, and know that I have another task, an individual task the next day. One way that I like to do this is with weekly objectives. Objectives don't need to be these grand, huge, big level things like big projects.

[3:41] They can be just things that are bigger tasks, tasks that take a couple days, and objectives are a good way to sort of link these things together and get the best of both worlds. So you could create an objective for your task and create tasks from that objective. You could do this by dragging the objective into the task list or a technique I like. I like to use click on the objective, and then click on the day of the week you want to create a task for it, and you can set a plan time. So I could say I want to work on this for 90 minutes on

[4:13] Thursday, and on Friday, 45 minutes. And if we come back out here, we'll see I've actually created two distinct tasks. These are not the same task, but they are both aligned to the same objective. So, on Thursday I could work on this task, and whether they're not a complete. The whole task, the entire overarching task, whatever it is, I'll check this off at the end of the day, because I've completed Thursday's portion of it, I guess. And then come Friday, I have a new task to work on

[4:45] that, and I don't need to worry about this this rollover situation, or these breadcrumbs, I just have sort of two distinct tasks here that's that may be a little easier to manage. What's nice about this too, again these are linked to the same objective, So if it is some larger task, some larger objective, I can call click on this and sort of track all the linked tasks to this and sort of see my progress throughout the week. So, just a few very basic techniques and concepts for understanding how tasks can work on multiple days,

[5:16] and techniques for approaching that. Hope this helps, and thanks for watching!
