Run meetings from connected notes

Walk into the “Project Atlas weekly review” with the agenda, last week’s notes, and the open follow-ups one click away. Walk out with every decision recorded and every action tracked as a Task that points back to the meeting it came from.

In short

Add the Meeting preset, save a meeting template, and prepare each meeting with an agenda and links. Take notes in the body, then turn decisions into Tasks whose Context is the Meeting.

What you will build

By the end you will have:

• a Meeting Object Type, created from the shipped preset;
• a reusable meeting template that every new Meeting starts from;
• Meetings that appear on your Calendar by date;
• follow-up Tasks linked to their Meeting through the Task Context relation;
• a query that lists every planning meeting in a month.

1. Add the Meeting Object Type

1. In the sidebar, choose + next to Object types to open the Add new object type gallery.
2. Under Templates, choose Meeting.
3. Review the schema, then choose Create object type →.

The preset gives each Meeting:

Property	Kind	Use it for
title	Text	“Project Atlas weekly review”
description	Text	One-line purpose
attendees	Text	Who was there
type	Select: 1:1, Standup, Review, Planning, Workshop	The kind of meeting
date	Date & time	When it happens; puts it on Calendar
reviewed	Checkbox	Whether you have processed the notes

It also has tags and a Notes body.

Because Meeting has a Date & time property, it appears on Calendar. To get a one-click “Create Meeting for this day” button on each day, open the Type’s Object type settings → Calendar and turn on Create object from calendar.

See Create and edit an Object Type and Calendar and events.

2. Save a meeting template

1. Create a Meeting and give its body this structure:

   ## Outcome
   
   What should be true when this meeting ends?
   
   ## Agenda
   
   - Topic
   
   ## Notes
   
   ## Decisions
   
   ## Follow-ups

2. Open the Object’s ⋯ menu and choose Save as template, then name it.

3. To start every new Meeting this way, open Object type settings → Templates and mark the template as the default.

A template only supplies starting content. It never locks the body or rewrites existing Meetings. See Templates.

3. Prepare before the meeting

Create the Meeting, then:

1. Give it a specific title, such as “Project Atlas weekly review”.
2. Set date to the meeting’s date and time.
3. Choose its type, such as Review.
4. Fill in attendees.
5. Write the intended outcome and the agenda.
6. Link related Objects from the body with [[wikilinks]]: the Project, the people involved, last week’s Meeting, the spec under discussion.

Every Object you link gains a backlink to the Meeting. Open the Project Atlas page later and this Meeting is listed there, without any extra filing.

See Links and transclusion and Relations and backlinks.

4. Find the Meeting again

Open Calendar and go to the meeting day. The Meeting is listed under On this day.

Other ways to reach it:

• search its title in the command palette;
• open the Meeting Type in the sidebar to browse every Meeting;
• tag Meetings, such as #planning or #one-on-one, to group them with other Types.

If the meeting moves, drag it to another day on Calendar or change its date property. See Search and the command palette.

5. Take notes without losing the agenda

During the meeting, write under the prepared headings. These editor features help:

• todo blocks for small in-note actions;
• [[Object]] links for named context;
• ![[Object]] to show another Object’s content inline;
• ((block references)) to point at one precise passage;
• comments on a block that needs discussion after the meeting.

For a long page, use Focus mode to hide the surrounding navigation and Find to jump through the text. See Blocks and formatting and Find, outline, and focus.

6. Turn follow-ups into Tasks

For each action that needs tracking:

1. Open Tasks and choose ＋ New.
2. Write an outcome-focused title, such as “Send Sam the revised Atlas timeline”.
3. Set Date, Set deadline, Set status, and Set priority as needed.
4. Under Set context, choose the Meeting.

Context is a relation, so the Task stays connected to the Meeting and is grouped under it in the Task dashboard’s Context tab.

Meeting follow-up workflow

Lar also ships a Create a meeting follow-up Workflow. It works on the built-in Event Type, not on a custom Meeting Type. Add it from Workflows › Templates and turn it on, then run it from an Event’s ⋯ menu: it creates a “Follow up” Task with the Event as its context.

See Tasks and Workflows.

7. Close and review

Before you leave the Meeting:

1. Summarize the decisions.
2. Confirm every tracked follow-up has a Task.
3. Add any final links or tags.
4. Check reviewed.

The reviewed checkbox simply records that you processed the notes. For a list of Meetings still waiting for review, build a Saved View on the Meeting Type with a filter on reviewed; checkbox filters need the filter builder rather than a TQL query.

Try it: list a month of planning meetings

Type this TQL query into the search field in the app header:

type:Meeting prop.type:planning prop.date:>=2026-10-01 prop.date:<2026-11-01

It returns every Planning meeting in October 2026. Select options are matched by their stored value, which for the preset is the lowercase label (1-1, standup, review, planning, workshop). Choose ★ save beside the field to keep the query.

Optional refinements

• Create a Collection for a recurring series, such as “Design reviews” or “Team 1:1s”.
• Add a relation from Meeting to a Project Type if every Meeting should belong to a Project as a typed property.
• Turn on Show Related Content below the body in Object type settings → Layout to surface Objects that share tags or links with each Meeting.
• Export a Meeting as a document, or use Share for end-to-end encrypted collaboration.

Next: Build a daily review. Related: Collections, Graph and related content, and Sharing.