Topics

Search and search views

Dependency types

In This Article

Finish to start - FS
Finish to finish - FF
Start to start - SS
Start to finish - SF
Dependency types and auto-shifting dates
Relevant dates for each dependency type
Default dependency type

Dependencies show the relationships between tasks and the sequence in which they should be performed. Task dependencies allow you to mark a task as blocking another or being blocked by another task. In this way, we designate one task as the precedent and the other as a dependent; the precedent task is performed before the dependent task.

Previously, Asana offered one type of dependency, called finish to start, or FS. This meant that the dependent task should not be started until the precedent task was completed. We've now added three more dependency types, outlined in this article.

In the examples below, it's helpful to consider two example tasks, Task A and Task B. Task A is the precedent task, and task B is the dependent task.

Finish to start - FS

Task B cannot start until Task A is complete. This is the most common type of dependency.

For example, a writer cannot begin editing a draft until the first draft is complete.

Frame 629769 (1).png

Finish to finish - FF

Task B cannot finish until Task A is complete. This type of finish dependency is useful for tasks which contain subtasks; if the subtasks are not complete, the parent task cannot be completed.

For example, before declaring that the design phase of a project is complete, all user experience research interviews must also be finished.

Frame 629768 (1).png

Start to start - SS

Task B cannot start before Task A starts. This type of dependency is ideal for tasks that are required to run parallel to each other.

For example, drafting a social media announcement should not start until the related web page creation has begun, although neither task needs to be complete before the other may begin.

Frame 629770.png

Start to finish - SF

Task B must start before Task A can be completed. This is important for situations that require overlap.

For example, in shift work, one operator's shift should not end before their replacement has begun their shift to provide uninterrupted coverage.

Frame 629771.png

Jamie's shift does not end until Chris' shift begins.