A task dependency shows that one task relies on another task ahead of it in the workflow being completed first.
Dependencies help you:
Keep work moving in the right order
Set due dates that reflect how long each step really takes
Make it clear what's holding a task up
Where you can set task dependencies
You can set dependencies on a template or on a series. Changes only apply to work that hasn't been started yet.
Template: Applies to all client work created from that template that is not started. Use this when the workflow is the same for every client using the template.
Series: Applies to all work in that series (one client) that is not started. Use this when one client needs a different order or timeline.
Important: If you customize dependencies on a series and the template is updated later, the template's settings overwrite the series customization. Re-apply any series changes after updating the template.
To find the settings, go to the template or series you want to update and select the Task Dependencies tab.
Work counts as not started when its project status is not In Progress or Completed.
Choose how due dates are calculated
At the top of the Task Dependencies tab, pick one of two methods. Both count in weekdays.
By Project Due Date: Every task is set a number of weekdays before the project due date. Best when each step has a fixed deadline tied to the final due date.
By Task Due Date: The first task is set a number of weekdays before the project due date. Each later task is set a number of weekdays after the task before it. Best when each step takes a set amount of time after the last one finishes.
You can add blocking tasks with either method.
Important: Switching between methods erases the due dates you've entered, so you'll start over on the new method. Choose your method before you enter your numbers.
Set up dependencies by project due date
Go to the template or series and select the Task Dependencies tab.
Select By Project Due Date.
Drag tasks by the handle to put them in the order they should be done.
For each task, enter the number of weekdays before the project due date it should be due.
(Optional) Add a blocking task in the Blocked by column. See Add a blocking task below.
Select Save.
Example: The project is due Friday, March 27.
Task A is due 15 weekdays before the project due date: Friday, March 6.
Task B is due 10 weekdays before the project due date: Friday, March 13. It's blocked by Task A.
Task C is due 5 weekdays before the project due date: Friday, March 20.
With this method, each due date is fixed to the project due date. Moving one task's date doesn't change the others.
Set up dependencies by task due date
Go to the template or series and select the Task Dependencies tab.
Select By Task Due Date.
Drag tasks by the handle to put them in order. The first task is marked with a flag.
For the first task, enter the number of weekdays before the project due date it should be due.
For each task after it, enter the number of weekdays after the previous task's due date.
(Optional) Add a blocking task in the Blocked by column.
Select Save.
Example: The project is due Friday, March 27.
Task A (first task) is due 15 weekdays before the project due date: Friday, March 6.
Task B is due 10 weekdays after Task A: Friday, March 20. It's blocked by Task A.
Task C is due 5 weekdays after Task B: Friday, March 27, the project due date.
Below the list, a note shows how the last task lines up with the project due date. In this example, the latest task is due on the project due date.
Fixing errors
The first task must be due early enough that the last task is due on or before the project due date. If it isn't, a red message tells you the minimum number of weekdays to enter, for example "Please enter a BEFORE project due date value of at least 5 weekdays."
Rows missing a number are marked in red, and Save stays unavailable until every number is entered. If you drag a different task into the first spot, enter new numbers for the tasks that moved.
Add a blocking task
A blocking task is one that should be completed before the task it blocks is started. Blocking is a visual guide for your workflow. It doesn't stop anyone from completing a blocked task, even if the blocking task isn't done yet. Due dates and blocking are separate: a due date says when a task is due, and blocking says what should finish first.
In the Blocked by column, select the task's row.
Choose the task or tasks that should be completed first. A task can be blocked by more than one task.
Select Save.
The blocking task appears in red in the Blocked by column (for example, Task B is blocked by Task A).
Good to know
Will my changes affect work that's already in progress? No. Dependency changes only apply to work whose project status is not In Progress.
Do the day counts include weekends? No. All relative due dates are counted in weekdays. Holidays are not skipped, so a holiday that falls on a weekday counts as a day.
Can I use blocking tasks with both methods? Yes. You can mark a task as blocked by another task whether you schedule by project due date or by task due date.
What's the difference between a template and a series? A template change applies to every client's unstarted work created from that template. A series change applies only to that one client's unstarted work in the series.
Will a template update overwrite my series customization? Yes. If you update the template after customizing a series, the template's settings replace the series settings for work that is not In Progress.
Can a task be blocked by more than one task? Yes. Add each task that should be completed first in the Blocked by column.
Can someone complete a blocked task before the blocking task is done? Yes. Blocking shows the intended order of work but doesn't prevent anyone from marking a task complete.
What happens if I switch methods? Your entries are erased and you start over on the new method.
Which plans include task dependencies? Task dependencies are available on the Premium plan.