Task Dependencies
Define relationships between tasks to ensure proper sequencing and automated scheduling.
Overview
Dependencies link tasks that must occur in a specific order. By defining these relationships, you enable the system to automatically adjust due dates when previous tasks are delayed and identify the critical path of your project.
Dependency Types
| Type | Name | Logic |
|---|---|---|
| FS | Finish-to-Start | Task B cannot start until Task A finishes. (Most common) |
| SS | Start-to-Start | Task B starts when Task A starts. Used for parallel work. |
| FF | Finish-to-Finish | Task B finishes when Task A finishes. Used for synchronized completion. |
| SF | Start-to-Finish | Task B finishes when Task A starts. (Rarely used) |
Lag and Lead Time
- Lag Time: A required delay after a predecessor completes (e.g., "Wait 3 days for concrete to cure" = FS + 3 days).
- Lead Time: An early start before a predecessor finishes (e.g., "Start ordering materials 5 days before the design finishes" = FS - 5 days).
Managing Dependencies
In Task Catalogs (Templates)
- Open a Catalog Item.
- Go to the Dependencies tab.
- Click Add Dependency and select a predecessor item.
- Choose the relationship type and optional lag.
The Dependencies tab displays a badge showing the total number of dependencies configured.
Predecessors vs. Successors
- Predecessors: Tasks that must happen before the current task.
- Successors: Tasks that are waiting on the current task to proceed.
Related:
- Task Management - Working with tasks
- Catalog Items - Setting template dependencies
- Tasks Overview - Module overview