David Neira is an official Notion Ambassador and the founder of NotioStore, where he builds custom Notion operating systems for architecture, construction, and interior design firms. He run 40 Notion Setup Sessions per week and writes here about making Notion hold up under real client work.
You’ve got your tasks in one database and your projects in another, and you want each project to show how many of its tasks are done. You know it’s possible. But you’re staring at two options that sound almost the same, relation and rollup, unsure which one you actually need. You add one, it doesn’t do what you hoped; you add the other, and it demands something you haven’t set up yet; twenty minutes later you’ve got a tangle and no progress. Two features, endlessly confused, standing between you and a connected system.
Relations and rollups are the two features that turn separate Notion databases into one connected system, and they’re the two people mix up most. Here’s the distinction that ends the confusion: a relation connects records, and a rollup summarizes what’s connected. Once you understand Notion relations vs rollups, which one does what, and the single rule that ties them together, this stops being a guessing game and becomes obvious. They’re not competing options; they’re two halves of one idea.
The confusion is understandable, because both features live in the same place, deal with connections between databases, and get introduced together, so they blur into one vaguely intimidating concept called “the database-linking stuff.” People reach for one when they need the other, or assume they’re two names for the same thing, and then nothing behaves as expected.
The cost of that confusion is real. Some people give up and keep their databases as separate, disconnected lists, which throws away the entire point of a connected workspace. Others resort to counting and copying numbers by hand between databases, tedious, error-prone work that the right setup would do automatically. And plenty conclude that Notion databases are simply too complicated and retreat to a simpler tool, when they were two clearly-understood features away from exactly what they wanted. Clearing up this one distinction is often the difference between a pile of lists and a system that actually connects.
A relation links records across two databases. That’s its whole job: connection. When you add a relation between Tasks and Projects, each task can point to the project it belongs to, and, because relations are two-way, each project automatically knows which tasks are its own. You’ve built a bridge between the two databases.
Think of a relation as the wiring between databases. On its own, it doesn’t calculate anything or summarize anything, it simply establishes that these records and those records are connected. That connection is the foundation everything else builds on, but by itself, a relation just links; it doesn’t count, total, or summarize. For that, you need the second feature.
A rollup reaches through a relation and pulls information back from the connected records, then summarizes it. Once your Tasks relate to your Projects, a rollup on the Projects database can show the number of tasks each project has, the percentage complete, the total hours, or the latest due date, all calculated automatically from the related tasks.
So where a relation connects, a rollup summarizes. It’s the feature that turns a bunch of linked records into a useful number or summary sitting right on the parent record. A rollup is how a project shows its own progress without you counting anything, how a client shows their total invoiced value, how anything shows a summary of the things connected to it.
A rollup reaches through a relation and pulls information back from the connected records, then summarizes it. Once your Tasks relate to your Projects, a rollup on the Projects database can show the number of tasks each project has, the percentage complete, the total hours, or the latest due date, all calculated automatically from the related tasks.
So where a relation connects, a rollup summarizes. It’s the feature that turns a bunch of linked records into a useful number or summary sitting right on the parent record. A rollup is how a project shows its own progress without you counting anything, how a client shows their total invoiced value, how anything shows a summary of the things connected to it.
Here’s the rule that makes the whole thing click, and that most people miss: a rollup needs a relation to exist first. A rollup doesn’t create a connection; it reads through one that’s already there. So the order is always the same, build the relation to connect the records, then add the rollup to summarize across that connection. Try to add a rollup with no relation in place, and Notion has nothing for it to read through, which is exactly the “it’s asking for something I don’t have” wall people hit.
That gives you a simple decision rule. Use a relation when you want to connect records, this task belongs to that project, this invoice belongs to that client. Use a rollup when you want to see a summary of what’s connected, how many tasks, the total invoiced, whether everything’s done. In practice they almost always come as a pair: relate first, then roll up.
Here’s it working. An interior design studio wanted each project to show its total budget, added up from all the individual cost line items, but kept fumbling the two features, adding a rollup that wouldn’t work, then a relation that didn’t summarize. Once they saw the order, they related their Costs database to their Projects so each cost belonged to a project, then added a rollup on Projects that summed the related costs. Suddenly every project displayed its running total automatically, no adding up by hand, and the same pattern let them roll up task progress and hours too. The features had confused them for weeks; the order made them obvious in minutes.
Rollups are powerful but bounded. A rollup can only summarize what’s reachable through a relation, and only in the ways it offers, count, sum, percent complete, earliest or latest, show the original values, and a handful more. It can’t perform arbitrary logic or combine values in complicated ways. When you need calculation beyond what a rollup provides, a formula is the tool, and rollups and formulas often work together, with a formula operating on what a rollup pulls in.
A couple of practical notes. Rollups occasionally take a moment to recalculate, and chaining rollups of rollups can get fragile, so keep them as simple as the job allows. And resist the urge to pile relations and rollups onto every database, a table drowning in them gets heavy and hard to read, so use them where they earn their place. Understanding these two features also isn’t the whole of good database design; you still need sensible structure underneath them. But relations and rollups are the pair that connects a workspace, and knowing which is which is a genuine turning point.
Don’t just read about the difference, build it, because doing it once in the right order makes it stick for good. Take two databases you already have that ought to be connected, tasks and projects, or costs and projects, and first add a relation linking them.
Then, with that relation in place, add a rollup on the parent that counts or sums something from the connected records. Doing it in that sequence, relation first, rollup second, cements both the distinction and the dependency permanently: the relation is the pipe, the rollup is what you pull through it. After that, you’ll always know which one you need.
If you’d rather have your databases connected and summarizing correctly from the start, relations and rollups set up properly across a workspace that actually works together, book a discovery call and we’ll build it with you.
A pile of tasks isn’t task management. Real task management is knowing, at any moment, what to do next, and that takes more than a list. This is a step-by-step tutorial for using Notion for task management.
Entrepreneurs can replace expensive tools with Notion by consolidating the overlapping ones, notes, docs, projects, wiki, simple CRM, into a single subscription, while keeping only the specialized tools that genuinely earn their price.
New to Notion? Discover the most common beginner mistakes and how to avoid them so you can build a smarter, simpler, and stress-free Notion system.
Built for the businesses that build everything else.
No product pitches. No padding. One weekly read for serious operators.