Run meetings from connected notes

Use a Meeting Object as the durable home for one conversation. The meeting date places it on Calendar, the body holds the agenda and notes, and linked Tasks keep follow-up work visible after everyone leaves the room.

What you will build

This workflow uses:

• the shipped Meeting Object Type preset;
• a reusable meeting template;
• Calendar for date-based access;
• Task context for follow-up work;
• links, tags, and backlinks for connected context.

1. Add the Meeting Object Type

1. Open New → Add object type.
2. Choose the Meeting preset.
3. Review the schema and create the Type.

The preset includes:

• title;
• description;
• attendees;
• type, with 1:1, Standup, Review, Planning, and Workshop options;
• date as Date & time;
• reviewed as a checkbox;
• tags and a Notes body.

Because Meeting has a Date & time property, it can appear on Calendar. Open Object type settings → Calendar Settings if you want a Meeting quick-create button on each day or want to hide Meetings from the day sidebar.

Learn more about creating and editing Object Types and Calendar settings.

2. Create a meeting template

Create one Meeting Object with a body like this:

## Outcome

What should be true when this meeting ends?

## Agenda

- Topic

## Notes

## Decisions

## Follow-ups

Open the Object’s ⋯ menu, choose Save as template, and name it. If most Meetings use this structure, open Object type settings → Templates and mark it as the default.

Templates supply starting content; they do not lock the body or rewrite existing Meetings. See Templates.

3. Prepare before the meeting

Create the Meeting from its template, then:

1. Give it a specific title, such as “Project Atlas weekly review”.
2. Set the date and time.
3. Choose the meeting type.
4. Add attendees.
5. Write the intended outcome and agenda.
6. Link relevant Objects from the body with [[wikilinks]].

Use links for Projects, People, previous Meetings, or source material that already exists in the Workspace. A linked Object gains a backlink to the Meeting, so the connection remains discoverable from either side.

See Links and transclusion and Relations and backlinks.

4. Find the Meeting from Calendar

Open Calendar and select the meeting day. The Meeting appears under On this day and in the day sidebar unless its Type is hidden there.

You can also use:

• the command palette to search its title;
• the Meeting Type page to browse every Meeting;
• tags such as #planning or #one-on-one for cross-Type grouping.

If the time changes, drag the Meeting to another Calendar day or update its Date & time property. See Search and the command palette.

5. Take notes without losing the agenda

During the meeting, write below the prepared headings. Useful editor patterns include:

• todo blocks for lightweight, in-note actions;
• [[Object]] links for named context;
• ![[Object]] when the source content should be visible inline;
• ((block references)) for a precise passage;
• comments when a block needs an asynchronous discussion.

Use Focus mode when you want the body without surrounding navigation, and Find when a long transcript or notes page becomes difficult to scan. See Blocks and formatting and Find, outline, and focus.

6. Turn follow-ups into Tasks

For each action that needs tracking:

1. Create a Task from Tasks → New.
2. Write an outcome-focused title.
3. Set a date, deadline, status, and priority as needed.
4. Set Context to the Meeting Object.

Context is an Object relation. It keeps the Task connected to the Meeting and makes it available in the Task dashboard’s Context tab.

If the meeting is represented by the built-in Event Type, Lar also ships a Meeting follow-up Workflow recipe. Add it from Workflows, review it, and run it manually from the Event’s menu. It creates a “Follow up” Task and links the Event as context. The recipe is scoped to Events; it does not automatically apply to a custom Meeting Type.

See Tasks and Workflows.

7. Close and review

Before leaving the Meeting Object:

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

The reviewed checkbox is deliberately simple: it records that you processed the notes. If you need a richer lifecycle, add Select options to the Type or create a Saved Query for Meetings where reviewed is unchecked.

Optional refinements

• Create Collections for recurring series, such as “Design reviews” or “Team 1:1s”.
• Add a relation to a custom Project Type if every Meeting should link to a Project in a typed property.
• Turn on Related Content below Meeting bodies to surface Objects with shared tags, backlinks, or semantic similarity.
• Export one Meeting as a shareable document, or use Share for encrypted collaboration.

See Collections, Graph and related content, and Sharing.