Dependencies show which tasks must finish before others can start. Link waiting on and blocked tasks, choose dependency types, and accept suggestions from your Process Map.
Who this is for
Workspace members who can edit tasks. Process Map suggestions appear when a task is linked to a duty with defined order.
Before you start
Tasks created in your workspace.
Edit access on the tasks you want to link.
Steps
Open a task from list, board, or timeline view.
Find Waiting on / Unlocks in the detail panel or side panel (the second list shows tasks that cannot start until this one finishes).
Waiting on lists tasks that must complete before this one. Click Add waiting task and search by title.
In the second list under that heading, click Add task that blocks to link downstream work.
Choose a dependency type: Finish → start, Start → start, Finish → finish, or Start → finish. Add optional lag days (for example +2d). Set soft to warn only or hard to block auto-schedule.
When your Process Map defines order, open Suggested from Process Map and click Link to accept a suggestion.
What you should see
Linked tasks show in both dependency lists with type and lag labels. List view may show blocked-by hints on affected rows. Hard dependencies prevent auto-schedule from placing work out of order.
Troubleshooting
Auto-schedule skipped a dependent task Hard dependencies block placement until predecessors complete. Finish or remove blocking tasks, or change the dependency to soft.
Suggested from Process Map is empty The task needs a source duty linked to your Process Map with defined handoffs. Link the task to a duty or add order in Process Map.
I cannot add a dependency Circular links are rejected. Pick a different predecessor or remove an existing link that creates a loop.
Common questions
How are dependencies different from subtasks?
Subtasks are a parent/child tree on one piece of work. Dependencies link separate tasks across lists with finish or start rules.
What does soft vs hard mean?
Soft dependencies warn when dates clash. Hard dependencies block auto-schedule from placing the successor too early.
What is lag?
Lag adds delay days after the predecessor date before the dependent task can start. For example +2d waits two days.