Task dependencies in Rocketlane that help you manage project timelines effectively by linking tasks with logical relationships. By establishing dependencies, you ensure that changes to one task automatically adjust the schedules of related tasks, maintaining consistency in your project plan.

By default, new Rocketlane accounts include only the Finish-to-Start dependency. 

However, users on Premium plans and above can unlock additional dependency types by enabling them in Settings → Workflow Management. Toggle Enable Additional Dependencies.

What Are Task Dependencies?

Dependencies define relationships between tasks in a project. For example, if Task B requires the completion of Task A to proceed, these tasks are connected by a dependency. When changes are made to the completion date of Task A, they indirectly affect the start or due dates of Task B, ensuring that the relationship between tasks is preserved.

Types of Dependencies in Rocketlane

When additional dependencies are enabled, you can choose from the following options:

1. Finish-to-Start (default): Task B starts only after Task A finishes.

2. Start-to-Start: Task B starts only after Task A starts.

3. Finish-to-Finish: Task B finishes only after Task A finishes.

4. Start-to-Finish: Task B finishes only after Task A starts.

Adding and Managing Dependencies

To set up dependencies and manage lags:

1. Navigate to the Project Plan:
   Open your project in the Project Plan view.

2. Set a Predecessor:

   • Click on the Predecessor button for a task.

   • In the dialog box, select:

     • The Predecessor Task.

     • The Dependency Type (e.g., Finish-to-Start).

     • The Lag (number of days required between tasks).

How Dependencies Work

Example Scenario 1: Two Tasks with a Finish-to-Start Dependency

Let’s define Task A as the parent and Task B as the child with a Finish-to-Start dependency and a lag of 3 days.

• Parent Task Moves Forward:
  If Task A is delayed by 3 days, Task B will also shift forward by 3 days to maintain the 3-day lag. 

• Parent Task Moves Backward:
  If Task A is preponed by 3 days, Task B will also move back by 3 days to preserve the dependency.

• Child Task Adjustment:
  If you attempt to move Task B backward without moving Task A, a dialog box will warn you that the dependency will be broken. However, you can move Task B beyond the 3-day lag without violating the dependency.

Example Scenario 2: Adjusting Artificial Lags

If an artificial lag is introduced to Task B (e.g., setting a start delay greater than 3 days), the following rules apply:

• If Task A is delayed further, Task B will adjust as long as the dependency is not violated.

• If Task A is preponed, the lag for Task B resets to the predefined 3-day gap.

Handling Multiple Dependencies for a Task

A task can have multiple dependencies, with each specifying different lags. For example:

• Task B has a 3-day Finish-to-Start dependency on Task A.

• Task B also has a 6-day Finish-to-Start dependency on Task C.

If Task A is delayed, Task B will adjust accordingly. However, Task B will also honor the 6-day gap required by Task C. In such cases, Task B maintains the largest lag (6 days in this example) to satisfy all dependencies.

Key Dependency Rules in Rocketlane

1. Predecessor Can Move the Successor:
   Changes to a predecessor task’s timeline will affect its successor.

2. Successor Cannot Move the Predecessor:
   Adjusting the successor task does not impact the predecessor, preserving the dependency flow.

Dependency Violations:
If you attempt to move a task in a way that violates its dependencies, Rocketlane prompts you with a warning, ensuring logical consistency.