Which of the following is not a good use case for the dependency column?

• A. When a status can only change when the date of the task has started
• B. When tasks are independent
• C. When a task must finish before another starts
• D. When it's used to enforce dates

Answer: (A)

The dependency column is about linking tasks so timing and sequencing flow from predecessors to successors. It controls when work can start or finish relative to another task, and can be used to enforce date relationships between tasks. Gating a status change on the task’s date starting isn’t something a dependency relationship provides—it doesn’t govern when a status can be updated. That’s handled by other logic or automations, not by dependencies. So this scenario isn’t a good use case for the dependency column. In contrast, using dependencies to ensure one task finishes before another starts or to drive or enforce dates fits how the feature is intended to work, and you generally wouldn’t apply dependencies when tasks are independent.