5 min read · updated 13 Aug 2026

Meeting note templates for Obsidian.

Six templates for the meetings people actually sit in, sharing one small set of frontmatter fields so a folder of notes can be queried and not only read. Free, and yours to change.

1-on-1.md

VaultTemplates

---
title: ""
type: 1-on-1
date: 2026-01-01T10:00
attendees: []
tags: [meeting, 1-on-1]
summary: ""
---

# 1:1 with

## Summary

One or two sentences you would still understand in three months.

## Since last time

- Carried over from the previous 1:1:

## Their agenda

-

## My agenda

-

## Action items

- [ ] You:
- [ ] Name:

Six templates and a README, as plain files.

Download the templates

A 6 KB zip. No email, no account, no tracking pixel in a note.

Seven files, and that is the whole box.

Six templates and a README that explains the fields. No installer, no vault plugin, no folder structure you have to adopt. Unzip it somewhere in your vault and the files are notes.

One header on all six.

Headings you can write yourself. The frontmatter is the part worth copying from someone else, because it only starts paying once every note agrees on it.

A folder that answers questions.

Four spellings agreed on is the difference between reading notes one at a time and asking a year of them something. The README ships three queries to start from.

Every action item carries its owner.

A name inside the line survives being copied into a different note. A name in the heading above it does not, and that is the one convention the templates insist on.

What each of the six is for.

One to one

A recurring conversation, so the first section is what was carried over from the last one. Their agenda and yours stay separate, and feedback gets a place in both directions.

Team standup

Short enough that it still gets written on day forty. One line per person, blockers pulled out where somebody can act on them, and a parked list so the standup does not grow.

Client call

Scope and money get their own heading rather than sitting inside a paragraph, because that is the part you reread before the next invoice. Extra fields for client and project.

Interview

Quotes close to verbatim first, signals second, verdict last, in that order on purpose. Swap two fields and it works for user research instead of hiring.

Decision meeting

The question, the options with their costs, what was chosen and why. Doing nothing is printed as an option because it is a real one. A status field marks the ones still open.

Retro

Opens by checking whether the last retro's changes actually happened, which is the difference between a retro and a venting session. Caps the new changes at three.

Four fields, spelled the same everywhere.

title. The meeting headline, quoted. What you would say the meeting was, not what the calendar called it.
type. One of six values: one to one, standup, client call, interview, decision, retro. This is the field that lets you pull one kind of meeting out of a year of them.
date. ISO, like 2026-01-01T10:00. The time is optional and the format is not, because a date written three ways is three fields.
attendees. A YAML list of names. Later this is how you find every meeting a person was in, which is a question you will have long before you expect it.

Individual templates add a couple of their own: client and project, role and stage, decision and status, period. Add whatever else you want. As long as the four above stay spelled the same, a Dataview table over the folder keeps working.

Getting them into a vault.

Unzip into your vault. A folder called Templates is the usual place. The files are plain Markdown, so they are already readable notes before you configure anything.
Point Obsidian at the folder. Settings, then Files and links, then Template folder location. That is the core Templates plugin, which ships with Obsidian and is switched on by default.
Insert one from the command palette. Type template, pick the meeting kind, fill in the title and the date. Everything after that is just writing.

What it does not need.

No Dataview. The queries in the README are worth having and they are optional. Without the plugin those code fences sit in a note as plain text and break nothing.
No Templater. Each file carries a comment with the Templater and the core Templates version of the date line, so you can pick one and delete the comment. Typing the date by hand also works and never breaks after an update.
No account and no sync. Six files on your disk. Copy them into a second vault, mail them to a colleague, put them in a repo.
No attribution. Change the headings, drop three of the templates, ship the rest inside your own pack. That is what they are for.

Where Aside sits in this.

The section layout is not invented for the download. It mirrors the structure Aside writes: a summary, the key points, the decisions, action items as checkboxes with an owner in the line, the open questions. Aside is a Mac meeting copilot that records the call, transcribes it, and leaves that note as a Markdown file in a folder you already own, which is an argument with its own page.

It is not out yet. There is a list on this site for the release, and these templates are useful whether or not you ever join it. If you are typing your notes by hand today, a shared set of fields is most of the benefit anyway.

Last updated 13 August 2026.