Connecting your projects to tasks & meeting notes

TL;DR

Create a “Projects” database page per initiative and store high-level properties like timeline, team, and priority.

Briefing Cornell Notes

Briefing

Notion’s database relations let teams bundle a project’s big-picture details with the tasks and meeting notes that support it—so nobody has to hunt across pages to understand what’s happening. The setup starts with a “Projects” database that stores high-level initiatives (like timeline, product manager, engineer team, and priority) and gives each project its own dedicated page for mixed content such as code snippets, videos, PDFs, and Figma files.

From there, two supporting databases provide the operational and documentation layers: a “Tasks” database where each entry is a specific engineer action (often viewed in board form by status), and a “Meeting Notes” database that holds the notes tied to work. Notion’s strength is that the same underlying data can be displayed in multiple database views—table, board, timeline, calendar, list, or gallery—so teams can look at tasks in the format that matches how they plan and track work.

The core workflow is creating relation properties inside the “Projects” database. First, a new property is added (for example, “Tasks”), and the property type is set to Relation. The relation configuration prompts the user to choose which database to connect; selecting the “Tasks” database and creating the relation links each project to one or more task pages. The same steps are repeated to add a second relation property (for example, “Meeting Notes”) that connects the “Projects” database to the “Meeting Notes” database.

After the relations exist, linking becomes a matter of selecting relevant entries from dropdown lists. When a team member clicks the empty relation field next to a project, Notion surfaces all tasks (or notes) from the connected database. Choosing the items via the blue plus buttons attaches them to that project, and the selected pages then appear as the project’s associated work. This creates a fast path to context: opening a task or meeting note from within a project eliminates the need to search separately.

Relations also mirror automatically in both directions. Adding a relation property in one database causes the same relation to appear in the related database as well—so tasks can show which project they belong to, and meeting notes can show their associated project. The result is a “fully connected” projects view where cross-functional teams can jump into any project and immediately see the relevant tasks and meeting notes together, improving collaboration and reducing missed context. Because relations are bidirectional, adding a task or note can also include selecting its project from the related database, keeping the system consistent as work evolves.

Cornell Notes

The key idea is to connect Notion databases so each project page automatically links to the tasks and meeting notes that belong to it. A “Projects” database holds high-level initiative details, while separate “Tasks” and “Meeting Notes” databases store the execution and documentation. By adding Relation properties in the Projects database (one pointing to Tasks, another pointing to Meeting Notes), each project can be associated with multiple task pages and multiple note pages. Notion mirrors these relations in the connected databases, so tasks and meeting notes also show their related project. This bundling gives teammates instant context and reduces time spent searching across pages.

How do relation properties change what a project page contains in Notion?

A project page in the “Projects” database gains new fields when a Relation property is added. For example, adding a “Tasks” relation property lets a project link to one or more entries from the “Tasks” database. Adding a “Meeting Notes” relation property does the same for the “Meeting Notes” database. Once linked, opening a related task or note is just a click away from the project page, eliminating separate searching.

What’s the practical difference between the Projects database and the Tasks database?

The “Projects” database stores broader, high-level initiative information—such as timeline, product manager, engineer team, and priority—and each project has its own page for mixed content (code snippets, videos, PDFs, Figma files). The “Tasks” database stores specific engineer actions, with each task as its own page. Tasks are often organized in a board view grouped by status rather than plotted on a timeline like projects.

How does Notion let teams view the same database data in different ways?

Notion databases support multiple views of the same underlying entries. The transcript notes options like table, board, timeline, calendar, list, and gallery. That means teams can track tasks by status in a board view while still switching to other formats when planning or reviewing work.

What does “bidirectional” relations mean for connected databases?

When a relation property is added to one database, the same relation property is automatically mirrored in the related database. So if “Projects” links to “Tasks,” then “Tasks” will also show a relation back to the relevant project. The same applies between “Projects” and “Meeting Notes,” enabling consistent navigation from either side.

How do teams actually select which tasks and notes belong to a project?

After creating the relation properties, the user clicks the empty area next to the relation field on a project entry. Notion displays entries from the connected database, and the user selects the relevant ones using the blue plus buttons. After selection, the project entry shows the linked task and note pages as its associated work.

Why does linking meeting notes to projects improve collaboration?

Meeting notes become part of the project’s context bundle. Instead of searching for notes elsewhere, teammates can open the project and immediately access the associated meeting notes and tasks. This reduces friction for cross-functional teams and helps ensure everyone works from the same project context.

Review Questions

When creating a relation property in the Projects database, what property type must be selected and what database must be chosen?
How does a bidirectional relation affect what appears in the Tasks or Meeting Notes database after linking from Projects?
What are at least three different database view types mentioned, and how might each be useful for tasks or projects?

Key Points

1
Create a “Projects” database page per initiative and store high-level properties like timeline, team, and priority.
2
Add a Relation property in the Projects database that points to the “Tasks” database to link relevant task pages to each project.
3
Add a second Relation property in the Projects database that points to the “Meeting Notes” database to attach meeting documentation to each project.
4
Select related entries using the dropdown and blue plus buttons so tasks and notes appear directly on the project page.
5
Expect relations to mirror automatically in connected databases, enabling navigation from tasks or notes back to the project.
6
Use different database views (table, board, timeline, calendar, list, gallery) to match how teams plan, track, and review work.

Highlights

Linking a project to tasks and meeting notes turns scattered information into a single context hub.

Relation properties are mirrored automatically, so tasks and meeting notes also show their associated project.

Notion databases can be viewed in multiple formats—table, board, timeline, calendar, list, and gallery—without changing the underlying data.

Once relations are set, teammates can open a task or note directly from the project page instead of searching elsewhere.