Meetings

Meeting Notes

Capture agenda, decisions, and action items in a consistent structure. Your active meeting note saves automatically in this browser.

Details

Saved locally

Agenda

Decisions

Action Items (Markdown Table)

Capabilities

Notes That Turn Into Action

The meeting notes tool is organized around outcomes, not transcription. These features help capture agendas, decisions, and follow-up work in one structured note.

Meeting Title and Date

Name the meeting and set the date at the top of every note. These fields appear in the exported Markdown as the document header, so anyone reading the file immediately knows which meeting the notes belong to without opening a file browser or checking the filename.

Attendees Field

Record names or roles of everyone present. Attendees are included in the Markdown export, which matters when notes are shared or archived — knowing who was in the room is often as important as knowing what was discussed, especially for decisions and accountability.

Agenda Blocks

Write the agenda before the meeting as a bullet list of topics. Having the agenda captured alongside the notes keeps the full meeting context in one place rather than distributed across a calendar invite, a chat message, and a separate document.

Explicit Decisions

Place decisions in their own section so readers can distinguish an agreement from the discussion around it. Confirm the exported record with attendees when accuracy matters.

Action Items Table

Capture action items in a three-column format: Owner, Action, and Due date. The Markdown table format renders cleanly in GitHub, Notion, Confluence, and any Markdown-compatible wiki, making it easy to paste action items directly into the project management tool your team already uses.

Export as Markdown

Copy the notes to your clipboard as Markdown or download a .md file. The exported Markdown includes all sections — title, date, attendees, agenda, decisions, and action items — formatted as a proper document ready to paste into a wiki, email, or team channel.

Why It Matters

How Structure Helps Meeting Follow-Through

A single stream of bullets makes decisions and next steps hard to find. Separate sections let readers scan for the outcome they need without treating every discussion point as an agreement.

Record action items with an owner and due date when those details are known. The structure makes missing ownership visible, but the notes still need to be reviewed and shared with the people responsible.

Using the same section order across recurring meetings also makes older notes easier to compare. Export each record to the team system that owns long-term access, permissions, and follow-up.

Use Cases

Meeting Types That Benefit From Structured Notes

Use these examples to decide when a structured meeting note is more useful than a blank page.

Daily Standups

Even brief standups benefit from a record. A date-stamped note with blockers and assigned items creates an audit trail that helps with sprint retrospectives and async catch-ups for teammates who couldn't attend.

One-on-One Meetings

1:1s between managers and reports often involve commitments, feedback, and development goals. Consistent notes let both participants track what was discussed, what was agreed, and whether previous action items were completed before the next meeting.

Sprint Planning and Reviews

Planning sessions produce decisions about scope, priorities, and ownership. Review sessions produce decisions about what shipped and what didn't. Both are worth capturing formally so the team has a record to reference mid-sprint and during retrospectives.

Client and Stakeholder Calls

External meetings require shareable, professional notes. The Markdown export produces a document that can be emailed to clients as a follow-up, providing a shared reference for what was discussed, what was agreed, and who owns the next steps.

Retrospectives

Retrospective notes capture what worked, what didn't, and what the team commits to trying differently. Storing these consistently makes it easy to review patterns across sprints and avoid repeating the same issues cycle after cycle.

Strategy and Planning Sessions

Longer planning sessions generate many decisions and commitments across multiple topics. The structured format ensures that every decision is captured in one place rather than scattered across discussion notes, making the output actionable rather than archival.

How It Works

The Before, During, and After Structure

A useful meeting note has a lifecycle. These steps explain how preparation, live capture, and follow-up work together.

01

Prepare the meeting before it starts

The meeting notes tool is designed around a three-phase workflow. Before the meeting: fill in the title, date, and attendees, then write the agenda. This takes two to three minutes and ensures the meeting starts with a shared reference for what's being covered. Having the agenda already written when the meeting begins also makes it easier to keep discussions on topic and signals to attendees that the meeting has clear goals.

02

Capture decisions and owners live

During the meeting: fill in the Decisions and Action Items sections in real time. The Decisions section should be reserved for actual commitments — "we will do X", "we will not do Y" — rather than options discussed or hypotheticals considered. The Action Items table works best when every action has a specific owner and a date; vague actions with no owner tend not to happen. Write action items in the moment rather than at the end of the meeting, when recall is already degrading.

03

Review and share the record

After the meeting, review names, decisions, owners, and dates before exporting. Share the Markdown through the team system you already use so attendees can correct anything captured inaccurately.

Workflow

Capture During the Call, Share Right After

A practical meeting-notes workflow begins before the call. Fill in the title, date, attendees, and agenda in advance so the record is ready when discussion starts.

Keep the decisions section visible as the meeting progresses and add to it immediately when a decision is made — not at the end of the meeting when you try to summarize. The same applies to action items: write them down the moment they are assigned. Late-meeting summary capture misses context and misattributes ownership. Real-time capture is more accurate and takes less time overall because you are not reconstructing what you remember rather than what was actually said.

For recurring meetings on the same topic, use the previous meeting's action items as the opening agenda item. This closes the loop on commitments from the previous session before new ones are added, which is the most direct way to build a culture of follow-through. Export each set of notes immediately after the meeting and file or share them consistently, so the format becomes a reliable expectation for everyone who attends.

Macros

Recurring Meeting Templates as Macros

If you run the same meeting every week — a team sync, a client status call, a sprint planning session — the agenda structure is usually the same with only the specific content changing. A macro template lets you define the recurring agenda headings, the attendees field phrasing, and the action item format once, then fill in the specific details for each instance. This reduces meeting prep to filling placeholders rather than rebuilding the structure each time.

Macros are particularly useful for meetings that follow a rigid format, like retrospectives with fixed sections (What went well / What could improve / Action items) or client status calls with a standard agenda (Progress since last call / Blockers / Next steps). Storing these formats as macros with placeholder fields for dates and specific content means every meeting of that type starts from an identical structure, which maintains consistency across the team regardless of who is taking notes.

Open Macros
Next Tools

Keep Working With the Right Tool

Jump to the next focused tool when the job moves from writing to planning, cleanup, tracking, or export.

To-Do ListMove action items into a task tracker. JournalReflect on meetings and decisions by date. Text MacrosReuse meeting agendas and follow-up templates.
FAQ

Meeting Notes FAQ

These answers cover exports, action items, recurring meetings, local storage, and how meeting notes differ from the general notepad.

Yes. All fields — title, date, attendees, agenda, decisions, and action items — save automatically in this browser. Export finished notes as Markdown for a portable backup.
Yes. Export downloads a .md Markdown file that includes all sections formatted as a proper document. You can also use Copy Markdown to send the content directly to your clipboard for pasting into Slack, Notion, or any other tool that renders Markdown.
Yes. Copy the action items section and paste the individual tasks into the to-do list tool, where you can assign due dates and priorities. The action items table format also renders in any Markdown environment, so you can paste it directly into a project issue or wiki page that your team uses for task tracking.
The meeting notes tool is designed around one active meeting note at a time. It saves in this browser. For a long-term meeting archive, export finished notes as Markdown and store them in your team wiki, project folder, or document system.
Yes. The action items section uses standard Markdown table syntax with pipe characters and header separators, which renders as a formatted table in GitHub, Notion, Confluence, GitLab, Obsidian, and most other Markdown-compatible tools. Plain text environments display it as a readable columnar text layout.

Build a Daily Writing Habit Too

Use the journal for daily entries, streak tracking, and a calendar view of your writing history.

Open Journal