---
title: "Meeting notes template – Display.dev"
description: "A repeatable meeting-notes format in plain Markdown – TL;DR, agenda, notes, decisions, and action items with owners. Publish it to a URL in one click, no account."
---

# Meeting notes template

A repeatable meeting-notes format in plain Markdown – TL;DR, agenda, notes, decisions, and action items with owners. Publish it to a URL in one click, no account.

- Format: Markdown
- Detail page: https://display.dev/templates/meeting-notes
- Raw template file: https://display.dev/template-sources/meeting-notes.md
- One-click anonymous publish (no account): POST the file to https://api.display.dev/v1/public/artifacts as multipart/form-data (`file` field)

## Agent prompt

Turn this meeting into notes on display.dev. Fetch the structure from https://display.dev/template-sources/meeting-notes.md and keep its sections: TL;DR, agenda, notes per topic, decisions, action items with owner and due date. Fill it from the transcript or discussion – every action item needs a named owner and a date, and the TL;DR states outcomes, not topics.

Publish it with the display.dev MCP publish tool if connected. Otherwise POST the file to https://api.display.dev/v1/public/artifacts as multipart/form-data (`file` field, optional `name`) – no account needed. You'll get back `previewUrl` (the link to share) and `claimUrl` (one-shot link to take ownership). Reply with both.

## What this template is for

Notes that people who skipped the meeting actually read. The TL;DR states
outcomes in three sentences; decisions and action items are separated so
neither hides in the prose; every action has an owner and a date.

Use the same format every week and a list of these reads as one series –
anyone can open last month's notes and reconstruct what happened.

## How teams use it

- **From transcript to notes in one step.** Paste the transcript to your
  agent with this structure; review the decisions section before sharing
  – that's where transcription nuance matters.
- **One URL per meeting, gated to the org.** Notes with candid discussion
  belong behind your company's Google or Microsoft sign-in, not in a doc
  anyone with a link can open.
- **Follow-ups in the comments.** "Done", corrections, and follow-up
  questions land as inline comments on the published page instead of a
  new thread.

## Template source

````markdown
# Growth weekly – 21 July 2026

**Attendees:** Sara (chair), Tom, Yuki, Deniz · **Duration:** 25 min ·
**Recording:** internal only

> **TL;DR:** Referral experiment extends two weeks with a bigger sample.
> Pricing-page rewrite ships Thursday. Yuki owns the churn-interview
> synthesis, due next Monday.

## Agenda

1. Referral experiment readout
2. Pricing-page rewrite status
3. Churn interviews – next steps

## Notes

**Referral experiment.** Two weeks in: 4.1% of invited users sent at
least one referral (target was 5%). Confidence interval still too wide to
call it – sample is 1,100 users. Tom proposes extending two weeks to
reach ~2,500. No objections.

**Pricing-page rewrite.** Copy approved Friday. Deniz lands the new
comparison table Wednesday; ship Thursday morning so there's a full day
of traffic before the weekend.

**Churn interviews.** Nine of ten interviews done. Recurring theme:
people churn at the seat-count review, not at renewal. Yuki synthesizes
into three findings with quotes.

## Decisions

- Extend the referral experiment to 4 August (sample ~2,500).
- Pricing page ships Thursday 24 July, morning.

## Action items

| Action | Owner | Due |
|---|---|---|
| Extend experiment config + new stop date | Tom | 22 Jul |
| Ship pricing-page rewrite | Deniz | 24 Jul |
| Churn-interview synthesis (3 findings, with quotes) | Yuki | 28 Jul |
| Book next readout with the wider team | Sara | 25 Jul |
````