Task Dependencies

Setting Dependencies Between Tasks

Task Dependencies help identify which Tasks will be directly affected by a delay elsewhere in the project.


In Taskfeed, the scheduling of any Task that has a dependency on another task (the ‘Predecessor’ task) can be determined when the Predecessor has an End Date and the dependent task has a predefined Lead or Lag number of days in relation to End Date of its Predecessor task.

In other words, the task dependencies are always set as Finish to Start.


A Finish to Start dependency means Task A must finish before Task B can begin" (or "B can't start until A has finished"). (1)


In the example below, the Task ‘Product Implementation’ is directly dependent on another Task - ‘PM to Review Signed Contract’.

Product Implementation is should always start 2 working days after the contract is reviewed by the Project Manager. In Taskfeed, this is defined as a Lag of 2 days in the Product Implementation task.

The task ‘PM to Review Signed Contract’ is dependent on ‘Client to Return Signed Contract’. In other words, the Project Manager can only review the contract once the client returns it. They have defined a 1-day Lag on PM to Review Signed Contract in relation to Client to Return Signed Contract.

Once these have been defined on a template, it will be applicable every time a project is created using these tasks.

If a client takes longer than the expected 4 days to return the signed contract, we should update the Board to reflect that delay, so that Product Implementation can be pushed back as a result of the delay in both its direct predecessor task (PM to Review Signed Contract) and the task that its predecessor is dependent on.

💡See Also:

What if a Predecessor Task is completed sooner than planned?

In Taskfeed, a Task’s Complete Date and the Task’s End Date are 2 different fields and can have different values. This is important to remember when setting and using Task dependencies.

The End Date of a Task can be manually entered, rescheduled and edited as needed. It can also be automatically predefined from a template when you set a Start Date and Duration for a task or set a Duration and a dependency on another task (a combination of Predecessor Reference and Lead/Lag value).


The task Complete Date is a separate field. It is a timestamp automatically generated when someone marks a task as Complete.

If someone completes a Task any time before or after its End Date, the End Date does not change by default but the Task’s Complete Date will show the date and time when the task was marked as complete.


Therefore, if a predecessor Task is completed earlier than its End Date, the Start Date of its dependent tasks won’t be recalculated, but they will be considered Ready to work.

Update the End Date to the Complete Date Automatically

💡There are 2 options in the Taskfeed Scheduling Settings for your Organization which can be optionally enabled if you wish to have dependent tasks recalculated when predecessors are completed early or late:

Either or both options can be enabled to:

  • Recalculate the Task’s End Date to reflect the Complete Date when a Task is completed early and/or

  • Recalculate the Task’s End Date to reflect the Complete Date when a Task is completed late.

If one or both of these settings are enabled, it can affect the Start Date of dependent tasks because the Complete Date and the End Date will essentially become the same thing.

As a consequence, dependent Tasks may also have their Start Dates recalculated.


Feedback and Knowledge Base