Skip to main content
All CollectionsGeneral
Creating or Editing an Event or Task
Creating or Editing an Event or Task

Everything you need to know about how to set up events, tasks, auto-scheduled tasks, repeat rules, etc.

Updated over 4 months ago

If you're looking for a tutorial on how to use the event/task page, you've come to the right place. I'll walk you through every section of the event/task page in detail. The interface is designed to be as simple as possible while still being customizable enough to support many, many use cases. Sometimes, those use cases can be very complex, so this guide exists to help you understand all of the tools at your disposal.


Events

Events are things on your schedule that never move and aren't necessarily something you'd put on a Todo list. They're just regular old calendar events. I won't go into every detail since most of the event settings are pretty normal and self-explanatory, but here are some FlowSavvy-specific tips for event settings:

All day

All-day events default to "not busy", meaning FlowSavvy will schedule tasks on these days. If you don't want tasks scheduled during an all-day event, turn "Busy" on. This is a great way to block off time for long events like vacations where you won't be working on your tasks.

Busy

When an event is "Busy", that means FlowSavvy will not schedule tasks during that event. Turn off "Busy" if you want FlowSavvy to schedule tasks over the event.

Buffer/travel time

Set buffer/travel time on events so FlowSavvy doesn't schedule tasks immediately before or after your event. For example, if it takes you 30 minutes to get to work, you won't want FlowSavvy scheduling tasks during those 30 minutes, so set 30 minutes of travel time on your work event. Or perhaps you'd like some time to decompress after an important meeting. Set some buffer time after the meeting so FlowSavvy doesn't schedule any tasks during that time.

If you want events and tasks to have buffer/travel time by default, head over to Settings > Events and Tasks to change your default buffer times. You'll still be able to override the default on each event/task.

Color

To change the color of an event, use the color option under the calendar option. Read more about color customization here.


Tasks

Tasks are things you put on a todo list. They'll appear on your calendar with a checkmark circle (unless you're zoomed out too far or the task is too small to fit the circle), so you can check off tasks directly from your calendar.

Tasks have a lot more fancy options than events, so let's dive into each setting:

Auto-schedule

When the "Auto-schedule" setting is on, FlowSavvy will automatically find time for your task. In most cases, you'll want to leave this on to take advantage of FlowSavvy's auto scheduling features.

Turn "Auto-schedule" off if you want to put a task at a specific time instead of letting FlowSavvy schedule it for you. For example, if you want your workout to always be 7-8 in the morning but still want to check it off like a task, turn off Auto-schedule and set the start/end times manually. If you'd rather FlowSavvy find a time for your workout instead, leave Auto-schedule turned on.

Dragging and dropping auto-scheduled tasks on the calendar will also turn off auto scheduling for that task so FlowSavvy won't move it after you move it manually.

Since non-auto-scheduled tasks behave more similarly to events, most of the settings below are only relevant for auto-scheduled tasks.


Duration

(Only applicable to auto-scheduled tasks)

I need 2 hrs

Give an estimate of how long you think the task will take. Ex: "I need 2 hours"


Scheduling Hours

(Only applicable to auto-scheduled tasks)

during "Personal hours"

Choose which scheduling hours to use for this task (Ex: "During personal hours", "During work hours", etc). If tasks aren't being scheduled where you want them, make sure you've selected the correct scheduling hours when creating the task, and that your scheduling hours are set up correctly. You can customize your scheduling hours in Settings > Scheduling Hours.

The free plan includes one scheduling hours profile, which you can customize as much as you like. If you need multiple scheduling hours like one for personal and one for work, upgrade to the pro plan for unlimited scheduling hours.


Due date

due date

Enter the day/time that the task must be completed by. If your task doesn't have a hard deadline, it's good to set a deadline for yourself, even if it's 3 weeks out. This date also helps FlowSavvy know which order to schedule your tasks in. Learn more about FlowSavvy prioritization here.

If this task has "Auto-schedule" turned on, FlowSavvy will find time somewhere before the due date for your task. Note that this is not a reminder time or the time you want to do the task. This is the due date, the day and time the task must be completed by.

On non-auto-scheduled tasks, due date has no effect and is for your reference only.


Priority (Pro feature)

Choose between "Do ASAP", High, Normal, and Low. FlowSavvy will auto-schedule your tasks according to their priorities. You can learn more about prioritizing (including how to prioritize on the free plan) by clicking here.

On non-auto-scheduled tasks, due date has no effect and is for your reference only.


Can be started... / Each occurrence can be started...

(Only applicable to auto-scheduled tasks)

Choose when the task can be started. These options change based on whether the task is repeating or not. Here are your options for each:

Non-repeating tasks

For one-off, non-repeating tasks, your options are This task can be started...

  • Now - Choose this option if the task can be started immediately. This is the default, and most of the time, you'll probably just leave it unless there's a reason you can't start the task right now.

  • On [date] at [time] - Choose this option if the task can't be started until a specific date and time. For example, I might want to schedule a task for setting up my new kitchen, but it has to be sometime after I move into the new apartment on July 1st.

If you want to start a task after another task, add a task dependency instead.

Repeating tasks

For repeating tasks, your options are Each occurrence can be started...

  • The day of its due date - Choose this option if you want the task to be done the same day as its due date. For example, if you want to walk your dog every day sometime between 8 and 12, you would make the task due at 12 and say each occurrence can be started the day of its due date at 8.

  • [number] days before its due date - Choose this option if you want to give your repeating tasks a more flexible window for when they can be completed. This option exists to support a ridiculous amount of use cases, and it's a careful balance between customizability and ease-of-use. Here are a few examples of how you might use this option:

    • "Write my report by Friday every week": Set your due date to repeat every week on Friday, and then say each occurrence can be started 4 days before its due date. FlowSavvy will find time for your report every week sometime between Monday and Friday.

    • "Exercise 2 times a week but I don't care which days": One way you might accomplish this is by making the due date repeat every Wednesday and Saturday, and then saying, "each occurrence can be started 2 days before its due date".

    • "Change air filters every 3 months-ish": Make the due date repeat every 3 months, and then say each occurrence can be started 14 days before its due date. This way, you'll have a 14-day window every 3 months to change the filters.


Repeating

The repeat rules are pretty self-explanatory, but remember that for auto-scheduled tasks, you're making the due date repeat. So, if you have a task that you want to complete every weekend, you'd make the due date repeat every week on Sunday since that is when each occurrence will be due. You can lengthen the window the task can be scheduled in by using the "Each occurrence can be started..." option explained above.


Splittable

Only applicable to auto-scheduled tasks

"Splittable" means the task can be split into multiple parts, meaning if you have an hour-long task but you have 15 minutes here and there throughout your day, FlowSavvy will schedule parts of the task where it can. If it doesn't make sense to split your task into multiple parts, turn "splittable" off.

To make auto-scheduled tasks splittable by default, head over to Settings > Events and Tasks. You'll still be able to override the default on each task.

Min block duration

When "Splittable" is on, you can decide the minimum amount of uninterrupted time you need for part of the task by setting the "min block duration". For example, if you have to work on a huge 10-hour project but you don't want to work on it if you can't sit down for at least 30 minutes, set the min block duration to 30 minutes.

Task still not splitting?

The "splittable" and "min block duration" settings allow a task to be split, but they do not force a task to be split. If this is what you're trying to do, here are your current options:

  1. Create a repeating task with a smaller duration to break up the task over a few days. (example)

  2. Create separate tasks with smaller durations. You can adjust the due dates and "can be started" dates to spread them out.

  3. Some users have requested a feature to specify a "max block duration" as well as a minimum break length between sessions. If this sounds like it would work for you, please submit a feature request for it using the in-app help center.


Buffer/travel time

Buffer/travel time on tasks works similarly to buffer/travel time on events. FlowSavvy will not schedule other tasks during buffer/travel time, so if you need a few minutes to wind down after a difficult task, add some buffer time to it. You can add buffer time both before and after a task.

If you want tasks and events to have buffer/travel time by default, head over to Settings > Events and Tasks to change your default buffer times. You'll still be able to override the default on each event/task.


Progress

After creating a task, the progress bar will appear in the task's page. You can record your progress through a task, and then the next time FlowSavvy recalculates, it will only schedule the remaining time. For example, if I have completed 1 hour of a 4-hour task, when I recalculate, FlowSavvy will only schedule the remaining 3 hours.

On non-auto-scheduled tasks, progress has no effect and is for your reference only.


Task dependencies (Pro feature)

Task dependencies are a way to tell FlowSavvy that "Task A must be done before Task B" or "Task C must be done after Task A and Task B". When adding a task dependency, tasks will not show up as options if they are completed, repeating, or if they would create a loop of tasks that reference each other. Fixed-time tasks that are in the past will also not show up as options for dependencies.

Why aren't dependencies supported for repeating tasks?

The nature of repeating tasks introduces uncertainty in how dependencies should behave across multiple occurrences. For example, if "Task A every other day" depended on "Task B every Friday", which occurrences of Task A would depend on which occurrences of Task B? Dependencies involving repeating tasks are not supported in order to keep the dependencies feature straightforward and intuitive.

However, task occurrences are scheduled in order of due date, so you can influence order by adjusting the due dates and repeat rules. For routines involving many back to back tasks, we recommend just creating one repeating task for the routine and optionally use the notes section to create a checklist of subtasks.

Task dependencies are only available on the Pro plan.


Color

Tasks are automatically color coded according to how close they are scheduled to their respective due dates. Learn more about automatic color-coding here.

To change the color of a task manually, click the option that says "Smart color-coding" and select a custom color. Read more about color customization here.


💡If this article did not answer your question, please feel free to message us! We'd be happy to answer your question and would love to know how we can improve this article.


Did this answer your question?