How to Build Notion Relation for Multi-Phase Project Dependency

Managing a project with multiple phases often means tracking how each phase depends on the previous one. Without proper database relations, you might lose sight of task handoffs, milestone blockers, or resource allocation across phases. Notion’s relation property allows you to link databases so that each phase record can reference its predecessor or successor directly. This article explains how to set up a multi-phase project dependency using Notion relations, including the required database structure and the exact steps to connect phases.

Understanding Multi-Phase Project Dependency in Notion

A multi-phase project dependency means that the start or completion of one phase relies on the output of another phase. In Notion, you model this by creating a single database for all phases and then using a Relation property to link records within that same database. This is called a self-referencing relation. The relation allows you to select a phase record and point it to another phase record that must finish first.

Before you begin, ensure you have a Notion workspace where you can create databases. You will need edit permissions on the page where the database will live. No third-party tools or integrations are required. The process uses only built-in Notion properties: Relation, Rollup, and Select.

Database Structure for Multi-Phase Dependencies

Create one database named “Project Phases” or similar. Each row represents a single phase. Add the following properties:

• Name (Title property): The phase name, for example “Phase 1: Research” or “Phase 2: Design.”
• Phase Number (Select property): A single-select list with values like “1”, “2”, “3” to enforce order.
• Status (Select property): Options such as “Not Started”, “In Progress”, “Complete.”
• Depends On (Relation property): Links to the same database (self-referencing). This will hold the predecessor phase.
• Depends On Status (Rollup property): Shows the Status value of the linked phase.

Steps to Build the Self-Referencing Relation

1. Create the Phase Database
   On a Notion page, type /database and select Table. Name the database “Project Phases.” Add at least three sample rows: “Phase 1”, “Phase 2”, and “Phase 3.”
2. Add the Phase Number Select Property
   Click + Add a property in the table header. Choose Select. Name it “Phase Number.” Add options: “1”, “2”, “3.” Assign each row its corresponding number.
3. Add the Status Select Property
   Add another Select property named “Status.” Add options: “Not Started”, “In Progress”, “Complete.” Set all rows to “Not Started” for now.
4. Create the Self-Referencing Relation
   Click + Add a property and choose Relation. Name it “Depends On.” In the relation setup dialog, select the same database: Project Phases. Choose Show on both databases so that the linked phase also shows the reverse relation. Click Create relation.
5. Link Phase 2 to Phase 1
   In the “Depends On” column for the Phase 2 row, click the empty cell. A menu appears showing all records from the same database. Select “Phase 1.” Repeat for Phase 3: select “Phase 2” as its dependency.
6. Add a Rollup to Show Dependency Status
   Click + Add a property and choose Rollup. Name it “Depends On Status.” In the Rollup configuration, set Relation to “Depends On.” Set Property to “Status.” Choose Show original as the calculation. This displays the status of the linked phase.
7. Test the Dependency Tracking
   Change the Status of Phase 1 to “Complete.” The Rollup column for Phase 2 now shows “Complete.” This confirms that the dependency link works and updates in real time.

Common Mistakes and Limitations

Creating a Relation to a Different Database by Mistake

When setting up the Relation property, you must select the same database name. If you accidentally pick a different database, the relation will not link phases within the same project. To fix this, delete the relation property and recreate it, making sure to choose the same database from the dropdown.

Rollup Shows No Value Even After Linking

The Rollup property depends on the Relation property being correctly configured. If the Rollup cell is empty, check that the Relation column has a linked record. Also verify that the Rollup property is set to the correct related property (Status) and that the calculation is set to “Show original.” If the linked phase has no Status value, the Rollup will also be empty.

Cannot Link More Than One Predecessor

A single Relation property can hold multiple linked records. If Phase 3 depends on both Phase 1 and Phase 2, you can select multiple records in the Depends On cell. The Rollup will then show the first selected record’s status by default. To aggregate multiple dependencies, use a Rollup calculation like “Show original” for each separate Rollup property, or use a formula to combine statuses.

Notion Relation Types: Self-Referencing vs Cross-Database

Item	Self-Referencing Relation	Cross-Database Relation
Database used	Same database for all records	Two separate databases
Use case	Multi-phase dependencies, task hierarchies, org charts	Linking projects to tasks, clients to invoices
Setup complexity	Simple: one relation property	Requires both databases to be created and linked
Rollup behavior	Pulls data from the same database	Pulls data from the related database
Reverse relation	Automatic: shows in the linked record	Automatic: shows in the linked record

For multi-phase dependency tracking, the self-referencing relation is the correct choice. It keeps all phase data in one place and makes it easy to visualize the sequence of phases.

You can now build a Notion relation that maps dependencies across multiple project phases. Start by creating the Project Phases database with the required properties. Then apply the self-referencing relation and rollup to display dependency status. For complex workflows, consider adding a Formula property that flags blocked phases when a dependency is not yet complete.