How to Use Notion Relations and Rollups for Project Tracking

If you’re tracking projects in Notion but manually copying data between databases, you’re working too hard. Relations and rollups connect your databases automatically, pulling in the information you need and calculating totals, averages, and progress without lifting a finger.

This tutorial walks you through setting up relations and rollups step by step, with examples you can use in your own project workspace today.

What Are Notion Relations and Why Use Them for Projects?

A relation is a property that links entries in one database to entries in another. Think of it as a connection between two lists—like linking individual tasks to the project they belong to, or connecting team members to the tasks they own.

Relations replace manual tagging and let you view related information in both directions. When you link a task to a project, you can see all tasks inside that project’s page, and you can see the project from the task’s page.

For project tracking, relations help you organize work across multiple databases without duplicating data. You might link tasks to projects, projects to clients, or bugs to sprints—all depending on how your team works.

What Are Rollups and How Do They Work?

A rollup is a property that pulls data from a related database and performs a calculation on it. Once you’ve created a relation, you can add a rollup to count, sum, average, or find the earliest or latest value from the linked entries.

For example, if your Tasks database is related to a Projects database, you can add a rollup in Projects to automatically count how many tasks belong to each project, or sum up the hours estimated for all tasks in that project.

Rollups save you from writing complex formulas and keep your dashboards up to date as you add or edit entries. They’re especially useful for tracking budgets, time spent, completion percentages, and workload distribution.

How to Create a Relation Between Two Databases

Before you can use rollups, you need a relation. Here’s how to set one up between a Tasks database and a Projects database.

Step 1: Open your Tasks database (either as a full page or inline).

Step 2: Click the + icon in the top-right corner of the table view to add a new property.

Step 3: Name the property something like “Project” and select Relation from the property type dropdown.

Step 4: Choose the database you want to link to—in this case, your Projects database. Notion will show you a list of all databases in your workspace.

Step 5: Decide whether to show the relation in both databases. Toggle “Show on Projects” if you want a two-way relation. This adds a property in the Projects database that lists all linked tasks. Most of the time, you’ll want this on.

Step 6: Click Create relation and you’re done. You’ll now see a new property in your Tasks database where you can select one or more projects.

To link a task to a project, click inside the relation cell, search for or select the project name, and press Enter. You can link a task to multiple projects if needed, though for most project tracking setups, one-to-many works best.

How to Add a Rollup to Calculate Data from Related Entries

Now that your tasks are linked to projects, you can use a rollup in the Projects database to pull in task data automatically.

Step 1: Open your Projects database.

Step 2: Add a new property by clicking the + icon.

Step 3: Name it (e.g., “Total Tasks”) and select Rollup from the property type list.

Step 4: Choose the relation you want to roll up. Notion will show you all relations in this database—select the one pointing to your Tasks database.

Step 5: Select the property from the related database you want to calculate. For example, choose “Name” if you want to count tasks, or “Time Estimate” if you want to sum hours.

Step 6: Pick a calculation. Common options include:

• Count all: Total number of related entries (e.g., total tasks per project)
• Sum: Add up numbers (e.g., total estimated hours)
• Average: Mean value (e.g., average task priority)
• Percent empty / not empty: Completion tracking
• Earliest date / Latest date: Deadlines or start dates

Step 7: Click Done and your rollup will populate automatically. As you add, edit, or remove tasks, the rollup updates in real time.

Real-World Examples of Relations and Rollups for Project Tracking

Here are four setups you can build today to make your project tracking more powerful.

1. Count Completed Tasks per Project

In your Projects database, create a rollup on the Tasks relation. Choose the “Status” property and set the calculation to Show original, then add a filter (if your Notion plan supports it) or use Count values and filter manually in a view.

Alternatively, create a checkbox property in Tasks called “Done,” then roll it up with Percent checked to see completion percentage per project.

2. Sum Time Estimates to Track Project Hours

Add a number property in your Tasks database called “Hours” (or “Time Estimate”). In Projects, create a rollup on the Tasks relation, select “Hours,” and choose Sum.

Now each project shows the total estimated time for all its tasks. You can compare this to actual hours tracked if you’re using Notion for time tracking.

3. Track Budget Spent Across Tasks

If you assign a cost or budget to each task (e.g., contractor fees, software spend), add a number property called “Cost” in your Tasks database. Roll it up in Projects with Sum to see total spend per project.

This works well for agencies, consultants, and product teams managing multiple work streams. If you also track AI tool costs, you can build a unified cost tracker across all resources.

4. Show the Nearest Deadline from Related Tasks

Add a date property called “Due Date” in your Tasks database. In Projects, create a rollup on Tasks, select “Due Date,” and choose Earliest date.

This gives you the next upcoming deadline for each project, so you can prioritize work at a glance. Pair this with a Notion project management template to keep everything organized.

How to Link More Than Two Databases with Relations

You’re not limited to one relation per database. You can chain relations together to build multi-layered systems—like linking Projects to Clients, Tasks to Projects, and Tasks to Team Members.

Example setup:

• Create a Clients database.
• Relate Projects to Clients.
• Relate Tasks to Projects (already done above).
• In Projects, add a rollup to count tasks. In Clients, add a rollup to count projects.

Now you can see how many projects each client has, and how many tasks belong to each project—all updated automatically. This structure works especially well if you’re managing client work with a Notion CRM or client onboarding system.

Common Mistakes to Avoid with Notion Relations and Rollups

Relating the Wrong Property

Make sure your relation points to the correct database. If you accidentally link Tasks to Team Members instead of Projects, your rollups won’t make sense. Double-check the database name when creating the relation.

Using the Wrong Calculation

If you want to count tasks but choose “Sum” on the Name property, you’ll get an error or zero. Use Count all for counting entries, Sum for adding numbers, and Percent checked for completion tracking.

Forgetting to Enable Two-Way Relations

If you don’t toggle “Show on [Other Database],” the relation only appears in one place. For project tracking, you almost always want two-way relations so you can view and edit links from either side.

Overcomplicating Your Database Structure

Don’t create relations just because you can. Start simple: Tasks ↔ Projects is enough for most teams. Add Clients, Sprints, or Team Members only when you actually need to track that dimension.

How to Use Relations and Rollups in Different Project Views

Once your relations and rollups are set up, you can filter, sort, and group by them in any Notion view.

Board view: Group tasks by the “Project” relation to see a Kanban board with one column per project. This works well if you’re comparing Notion to other Kanban tools.

Timeline view: Use the rollup “Earliest Date” as the start date for projects, then visualize project timelines with task deadlines nested inside.

Calendar view: Show tasks on a calendar, colored by the related project, so you can see workload distribution across time.

Gallery view: Display projects as cards, with rollups (task count, total hours, completion %) shown as card previews for a high-level dashboard.

Using Relations and Rollups in Agile and Sprint Planning

If your team follows agile or scrum, relations and rollups are essential for tracking sprint progress and backlog health.

Create a Sprints database and relate it to Tasks. Add rollups to count total tasks, sum story points, and calculate the percentage of tasks marked “Done.” This gives you a live burndown view without manual updates.

You can also relate Tasks to a Bugs database or a Features database, then roll up bug counts per sprint or feature progress per release. If you want a ready-made setup, the Scrum Board PRO template includes pre-configured relations and rollups for sprint tracking, backlogs, and burndown charts—all set up in under 10 minutes.

For teams building roadmaps, you can link tasks to releases using a Notion roadmap template and roll up completion status to see which features are on track.

When to Use Formulas Instead of Rollups

Rollups are great for pulling data from related databases, but they can’t do everything. Use a formula property when you need to:

• Calculate values within the same database (e.g., multiply hours by rate to get cost)
• Combine multiple properties with logic (e.g., “if status is Done and priority is High, show X”)
• Format or transform text (e.g., concatenate names, extract dates)

You can also combine rollups and formulas: roll up total hours from tasks, then use a formula in Projects to divide by team size or compare to a budget cap.

How to Keep Your Relations and Rollups Organized

As your workspace grows, it’s easy to lose track of which databases are related and why. Here’s how to stay organized:

Name relations and rollups clearly. Use descriptive names like “Related Tasks” or “Total Hours (Rollup)” so you remember what each property does.

Document your structure. Create a Notion wiki or knowledge base page that explains which databases are linked and what each rollup calculates. This is especially helpful for remote teams.

Limit the number of relations per database. More than three or four relations can make a database hard to navigate. If you need more, consider whether you’re tracking too much detail or could simplify your structure.

Use consistent property names across databases. If you call a date property “Deadline” in one database and “Due Date” in another, rollups and filters get confusing. Pick a naming convention and stick to it.

Can You Use Relations and Rollups in Notion Templates?

Yes—and they work beautifully in templates. When you duplicate a Notion page or template that contains databases with relations and rollups, all the connections and calculations come with it.

This is why many of the best Notion templates for project management rely heavily on relations and rollups. They let you see project health, task distribution, and progress metrics without any manual setup.

If you’re customizing a Notion template, check which relations and rollups are already configured. You can rename them, add new calculations, or link additional databases without breaking the original structure.

When choosing between free and paid Notion templates, paid options often include more sophisticated relation and rollup setups that save hours of configuration time.

Next Steps: Build Your Own Project Tracking System

Now that you understand how relations and rollups work, start small. Create a Tasks database and a Projects database, link them with a relation, and add one rollup to count tasks per project.

Once that’s working, add a second rollup for time estimates or budget, then experiment with filters and views. You’ll quickly see how much time you save compared to manual tracking.

If you want more project tracking ideas, explore the Notion templates category for ready-made setups you can adapt to your workflow.

Frequently asked questions

Can I create a relation between a database and itself in Notion?

Yes, you can create a self-referencing relation. This is useful for linking parent and child tasks, or creating hierarchies like 'Reports to' in a team database. When setting up the relation, choose the same database you're working in.

Do rollups update automatically when I change data in related entries?

Yes, rollups update in real time. If you edit a task's time estimate or mark it complete, any rollup that references that property will recalculate immediately across all related projects.

Can I use rollups with linked databases in Notion?

Yes, rollups work with linked databases (synced blocks). However, if the original database is in another workspace and you don't have edit access, the rollup may not update until the source is changed by someone with permission.

How many relations can I add to a single Notion database?

There's no hard limit, but Notion performance can slow down if you add too many relations or very large rollups. For most project tracking use cases, three to five relations per database is enough to stay organized without complexity.

Can I filter a Notion view by a rollup value?

Yes, you can filter, sort, and group by rollup properties just like any other property. For example, you can filter projects to show only those with more than 10 tasks, or sort by total hours in descending order.

Do I need a paid Notion plan to use relations and rollups?

No, relations and rollups are available on all Notion plans, including the free Personal plan. Advanced features like timeline view and larger upload limits require paid plans, but the core relation and rollup functionality is free.