← All Notion guides · Choose the feature · Try a short exercise
Relations and Rollups are often taught together in Notion, which makes them sound interchangeable. They are not. A Relation creates the connection. A Rollup uses that connection to show or calculate information.
Relation: “Which client does this project belong to?”
Rollup: “What is the total value of this client’s projects?”
Relation = connection
A Relation property connects a database record to one or more records in another database. If a project belongs to Sarah Chen, the Project record can relate directly to Sarah’s Client record.
PROJECT
Website redesign → Client: Sarah Chen
That relationship can also be shown in the other direction, so Sarah’s Client record can show the projects related to her.
Rollup = information through the connection
Once the relation exists, a Rollup can use it to retrieve or calculate a property from the related records.
CLIENT
Sarah Chen
Related projects: Website redesign, Brand refresh
Total project value: $5,500
In this fictional example, Website redesign has a numeric Project Value of $3,000 and Brand refresh has $2,500. A rollup in Clients uses Projects → Project Value → Sum to calculate $5,500. The reciprocal Projects relation must exist in Clients; typing the client name into a text property does not create it. See Notion’s official Relations and Rollups documentation.
Sarah Chen ↔ Website redesign
Sarah Chen ↔ Brand refresh
Website redesign: $3,000
Brand refresh: $2,500
Project Value: Number
Relation: Projects
Property: Project Value
Calculate: Sum → $5,500
Illustrative diagram using the fictional records in this guide; not a Notion screenshot.
Which feature do you need?
| If you want to… | Use |
|---|---|
| Connect a task to its project | Relation |
| Connect an invoice to its client | Relation |
| Count a client’s related projects | Rollup |
| Sum invoice amounts for a client | Rollup |
| Show the due date from a related record | Rollup |
| Display an existing database on another page | Linked view, not a Rollup |
If your goal is to show the same Projects data on a dashboard, you may need a linked view instead. Compare Linked Database vs Relation in Notion to choose between displaying records and connecting them.
Try it: choose the property
Three everyday requests. Pick the feature you would use, then open each answer.
“This invoice belongs to Sarah. I want to open her client record.”
Relation. Connect the invoice record to Sarah’s record in Clients. This identifies who the invoice belongs to.
“Sarah has two related projects worth $3,000 and $2,500. Show their total.”
Rollup: $5,500. In Clients, choose the Projects relation, the numeric Project Value property, and Sum. The relation must exist before the rollup can use it.
“Put my active projects on a Today page.”
Linked view. Display the existing Projects data source on Today and filter its Status property to Active. You are choosing which records to see, rather than creating a new connection.
If you can name the job first, you do not need to memorise every Notion property.
Already using a rollup, but the result looks wrong? Follow the rollup troubleshooting guide for empty results, missing Sum options and incorrect totals.
A correct calculation can still use the wrong records
In the practice example, Sarah has Website redesign ($3,000) and Brand refresh ($2,500). Keep these checks separate: which pages are connected, which values those pages contain, and which calculation uses them.
| Connected records | Numeric values | Expected Sum |
|---|---|---|
| Both projects | 3000 and 2500 | $5,500 |
| Website redesign only | 3000 | $3,000 — the missing relation excludes Brand refresh |
| Both projects | 3200 and 2500 | $5,700 — the connection stays the same; a source value changed |
Common mistake: changing the calculation to compensate for a missing related page. If Brand refresh is absent from Sarah’s Projects relation, fix that connection first. A different calculation will not decide which client the project belongs to.
Another mistake: treating an empty Project Value as confirmed zero. Review missing amounts separately before trusting the total. These fictional values test the setup; they are not pricing recommendations.
Build the relation with the Clients–Projects walkthrough. If the connected pages and source values are correct but the result differs, use the rollup troubleshooting checks. To display the records on a dashboard, choose a linked database view.
Frequently asked questions
Can I create a rollup without a relation?
A rollup uses a relation to find the records whose property it will display or calculate. Set up and populate that relation first.
Does a relation automatically connect all matching client names?
No. Select the intended client page in the relation. Matching text names in separate databases are not enough to connect their records.
Does a rollup always produce a number?
No. Its result depends on the selected property and calculation. This example selects a numeric Project Value property and Sum to produce a total.
Should I use a rollup to show my Projects database on another page?
Use a linked view to display the existing records elsewhere. A rollup retrieves or calculates a property through a relation; it is not a replacement for a database view.
Why can a correctly configured rollup still show an incomplete total?
Sum only includes numeric values from the records connected through its selected relation. Check that every intended project is related to the client and that its Project Value is filled in. A correct calculation cannot supply missing source information.
Once your records are connected, use AND/OR filters to show the appropriate work or add a Kanban view to organise projects by progress.
A practical rule before adding either
Do not start by asking which Notion property looks clever. Ask what the workspace needs to know.
Need to know something about what is connected? Rollup.
Need to see the same records in another context? Linked view.
Example: a freelance client system
A Client can relate to Projects. Projects can relate to Invoices. Time entries can relate to Projects. Those relationships create the structure. Rollups can then surface totals and useful context without maintaining duplicate values.
This is how a workspace starts behaving like a system rather than a collection of tables.
Do not connect everything
More relations do not automatically create a better system. Every connection should earn its place by answering a question, powering a useful view, reducing duplicate entry or making a decision easier.
If the relation never changes what you see or what you do, it may just be architecture for architecture’s sake.