Notion Relations & Rollups Explained Simply
Relations and rollups are what make Notion truly powerful. Let's demystify them.
What Are Relations?
Relations connect databases together, just like you'd link tables in a real database.
Example: Clients ↔ Projects
Clients Database ← Relation → Projects Database
This lets you:
- See all projects for a client
- See which client a project belongs to
- Automatically sync information
Creating a Relation
- In your Clients database, add a new property
- Choose "Relation"
- Select the Projects database
- Name it "Projects"
Now when you open a client, you can add projects to them!
What Are Rollups?
Rollups pull data FROM related databases. They're like "show me info from the other side."
Example: Count Active Projects
In your Clients database:
- Add property → Rollup
- Relation: Projects
- Property: Status
- Calculate: Count where Status = Active
Now each client shows their active project count!
Common Rollup Patterns
Total Tasks
- Relation: Projects
- Property: Tasks
- Calculate: Count all
Last Update Date
- Relation: Projects
- Property: Last Edited
- Calculate: Latest date
Revenue Tracking
- Relation: Projects
- Property: Value
- Calculate: Sum
Real-World Use Case
Agency Dashboard
Clients Database:
- Active Projects (Rollup: Count)
- Total Revenue (Rollup: Sum of project values)
- Last Activity (Rollup: Latest project update)
Projects Database:
- Client (Relation)
- Tasks (Relation to Tasks DB)
- Completion % (Rollup: Tasks with status Done)
Tasks Database:
- Project (Relation)
- Client (Rollup from Project)
With this setup, you have full visibility across clients, projects, and tasks!
Pro Tips
💡 Chain relations: Client → Project → Task → Subtask 💡 Use rollups for KPIs: Count active items, sum values, track dates 💡 Filter rollups: Only count tasks where Status = "Done" 💡 Sort by rollups: Find clients with most/least projects
Common Mistakes
❌ Creating too many relations (keep it simple) ❌ Not naming relations clearly ❌ Forgetting to add the reverse relation ❌ Using rollups when a simple property would work
Ready to automate these workflows? Check out our Automations guide!