What Dependency Types are supported?

The purpose of this article is to explain what a Dependency Type is and how it is used to categorise relationships between different entities involved in delivering outcomes across projects, business units, and suppliers.

Understanding dependency types helps ensure that interdependencies are clearly identified, owned, and managed to prevent delivery delays and improve coordination across the organisation.

A Dependency Type describes the direction or nature of a dependency — that is, who provides the deliverable and who receives it.

Each type defines the relationship between the Provider (the party responsible for delivering something) and the Receiver (the party depending on that delivery).=

Supported Dependency Types

Dependency Type: Project → Project

Description: One project depends on another project to provide a deliverable, input, or milestone.

Example: Project A must complete design work before Project B can start development.

Dependency Type: Project → Business Unit

Description: A project delivers something that a business unit will use or adopt.

Example: Project Alpha provides a new reporting dashboard to Finance Business Unit.

Dependency Type: Project → Supplier

Description: A project provides requirements, data, or specifications that a supplier needs to perform their work.

Example: Project Beta provides technical specifications to an external supplier.

Dependency Type: Supplier → Project

Description: A project depends on a supplier to deliver goods, services, or resources.

Example: A supplier delivers hardware to Project Delta before testing can begin.

Dependency Type: Business Unit → Project

Description: A business unit must provide input, approval, or resources before a project can progress.

Example: The People & Culture Business Unit must confirm workforce requirements before Project Epsilon can proceed with system configuration.