A step-by-step walkthrough of setting up complex task dependency chains, auto-blocking rules, and critical path visualisation.
Task dependencies are one of the most powerful — and most underused — features in PMT. This guide will take you from zero to confident with the full dependency system.
The basics: linking tasks
Every task in PMT can be linked to one or more other tasks with a dependency relationship. The two types are:
- Finish-to-start (default): Task B can't start until Task A is finished.
- Finish-to-finish: Task B can't finish until Task A is finished.
To add a dependency, open any task and click "Add dependency" in the right panel. Search for the blocking task and select the relationship type.
Auto-blocking rules
Auto-blocking rules let you define dependency logic at the project level so you don't have to manually link every task. Example: any task tagged "QA" should automatically block the "Deploy" task in the same milestone.
Critical path visualisation
Enable Critical Path view from the timeline header. PMT will highlight the longest path of dependent tasks — the sequence that determines your earliest possible completion date. Any delay on the critical path delays your milestone. Tasks not on the critical path have "float" — they can slip without affecting the deadline.
Common mistakes
The most common mistake is creating circular dependencies. PMT will warn you, but they can be subtle in large dependency graphs. Check the dependency graph view (Cmd+Shift+D) to visualise all relationships in a project.