How Dependencies Work Across Different Levels

This quick reference provides an overview of how dependency relationships can be structured within a project.

Dependencies are relationships you create between various work breakdown structure (WBS) levels in a project. You cannot create dependencies with the top-level project. Also, you cannot create relationships between parent and child levels because they already have an inherent relationship. Outside of these constraints, you can create multiple dependency relationships (even between the same predecessor and successor) as shown in the illustrations below.

The first item you select in each relationship is considered the predecessor - it leads the relationship. The second level you select in the relationship is considered the successor - it is impacted by the predecessor.

You can create relationships between any levels except the project level. You can create a dependency relationship between a task and a phase or between a phase and a labor code, as long as they are not in the same parent/child branch. The illustrations below show the allowed dependency relationships for a selected predecessor in each WBS level under a project: