Back to Help Centre

Task Dependencies

Link tasks together so they follow a logical order. Dependencies help you manage complex workflows where one task must finish before another can begin.

By Byte Size Labs · Updated 13 April 2026

What Are Dependencies?

A dependency means one task relies on another. For example, "Review design mockups" must finish before "Implement the UI" can start. Dependencies ensure work happens in the right order.

Dependency Types

FS

Finish-to-Start

Task B cannot start until Task A finishes. This is the most common type.

SS

Start-to-Start

Task B cannot start until Task A starts. Both can run in parallel after that.

FF

Finish-to-Finish

Task B cannot finish until Task A finishes. They can overlap but must end together.

SF

Start-to-Finish

Task B cannot finish until Task A starts. Rarely used, but useful for just-in-time scheduling.

Adding Dependencies

How to Link Tasks

  1. Open a task and scroll to the Dependencies section
  2. Search for the task you want to link
  3. Choose the dependency type (Finish-to-Start is the default)
  4. Optionally set a lag in days (e.g., a 2-day gap between tasks)
  5. Click "Add"

Removing Dependencies

In the Dependencies section, click the remove button next to any dependency to unlink it. This does not delete either task — it only removes the relationship between them.

Predecessors & Successors

Predecessors (Blocked By)

Tasks that must be completed (or started) before the current task. If any predecessor is incomplete, the current task shows a "blocked" indicator.

Successors (Blocking)

Tasks that depend on the current task. Completing this task may unblock its successors and allow them to be scheduled.

Circular Dependencies

A circular dependency occurs when Task A depends on Task B, and Task B depends on Task A (directly or through a chain). The system detects circular dependencies and prevents you from creating them. If you see a warning, review your dependency chain and remove the link that creates the loop.

Tips for Using Dependencies:
  • Use Finish-to-Start for most workflows — it's the simplest and most intuitive
  • Add lag days when you need a buffer between dependent tasks (e.g., waiting for approval)
  • Check the Timeline view to visualise your dependency chains
  • Keep chains short — deeply nested dependencies become hard to manage

Need more help? Contact support or return to help centre