Notion at Work: Meeting Management

Meeting management in Notion works best when every meeting lives in one “master” database, while the rest of the workspace shows tailored, filtered “gateways” into that master record. That structure lets teams keep agendas, notes, resources, and follow-up deliverables attached to each meeting—without duplicating data or losing context across clients and internal teams.

The session lays out a practical blueprint using a fictitious Loggerhead Labs workspace. A home page calendar view is built as a linked database that points to the master meetings database, then refined views appear inside each client (or “area”) page. Clicking any meeting from these gateways opens a single meeting page containing everything needed before, during, and after the meeting: meeting purpose and outcomes, pre-meeting resources, an agenda, live notes, and post-meeting action items assigned to specific people with deadlines. Past and upcoming meetings also stay navigable through the calendar and list views.

To build the system, the first step is creating the master meetings database with a small set of widely useful properties. The title becomes a “label” so each meeting can be uniquely identified. A “format” select field captures whether the meeting is in person, video conference, or a call. A “when” date property schedules the meeting, and a “location” text property stores the room, address, or link. A relation property (named “areas” in the demo) connects each meeting to the relevant client/area database, enabling filtered views later.

Populating the database includes handling recurring meetings. Since Notion doesn’t provide the same kind of recurrence automation as Google Calendar, the recommended workaround is to generate enough instances in advance (e.g., for a quarter or a year) using Google Sheets, then copy/paste into Notion. The “label” can be composed from a description plus the meeting date to keep each entry unique and easy to recognize.

The next step is creating a meeting template so new meetings inherit a consistent structure. The template includes sections for purpose/outcomes, resources, an agenda sub-table (with topic, duration, and leader), a notes area, and a deliverables/action-items sub-table (with deliverable name, responsible person, and deadline). Once the template exists, creating a new meeting becomes a one-click process that automatically generates the same framework.

Finally, the session shows how to create the gateways. A linked database view in calendar format becomes the default home-page interface. A list view can also be added for readability. Then, inside each client/area page, another linked database view is created with a filter based on the relation property so only meetings for that client appear. Sharing is handled by linking to full views or specific meeting pages, with attention to permissions for guests and outsiders.

In the Q&A, the discussion highlights that Notion’s Google Calendar integration isn’t available yet, but an upcoming API is expected to enable it. It also clarifies that updating a template won’t retroactively change existing meeting instances, while a newer template feature involving linked databases and related-property filtering can help automate how new items appear in those linked contexts.