printable · A4 portrait · v0.1.0
Meeting Notes
Structured one-page meeting minutes: header with date/time/location/chair, attendees, a topics table with discussion and explicit outcomes, action items with owners and due dates, and next meeting. Turns raw notes into a record people can act on.
Paste the prompt into Claude (or any agent that can fetch URLs) with your content — you get back a finished, self-contained HTML file.
Live preview — the example content ships with the template and is replaced by your content.
What an agent may change — and what content you should have ready. Everything outside these slots is fixed by design.
Slots
| Slot | Type | Req. | Example |
|---|---|---|---|
doc-title |
text | yes | Meeting Notes — Q4 Roadmap Review — 14 Aug 2026 |
meeting-title |
text | yes | Q4 Roadmap Review |
meeting-date |
date | yes | 14 Aug 2026 |
meeting-time |
text | yes | 10:00 – 11:15 |
meeting-location |
text | yes | Boardroom + Teams |
meeting-chair |
text | yes | Sanne (chair) · Bram (notes) |
attendees |
text | yes | Sanne de Wit, Bram Verlaan, Jorik Smit · Apologies: Lisa Chen |
next-meeting-info |
text | no | Thu 28 Aug, 10:00, boardroom — Q4 kickoff. |
footer-note |
text | no | Notes circulated to attendees + leadership |
Repeat: topic (1–10×)
One row per agenda topic, in the order discussed.
| Slot | Type | Req. | Example |
|---|---|---|---|
topic-name |
text | yes | Q4 priorities |
topic-notes |
text | yes | Three candidate themes reviewed against capacity… |
topic-outcome |
text | yes | Decided: residency #1, onboarding #2; billing v2 moves to Q1. |
Repeat: action (1–12×)
One row per action item.
| Slot | Type | Req. | Example |
|---|---|---|---|
action-desc |
text | yes | Draft EU data-residency plan and share with legal |
action-owner |
text | yes | Jorik |
action-due |
text | yes | 21 Aug |
Optional blocks
next-meeting— Next-meeting box at the bottom. Remove if no follow-up is planned.
The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).
Condense, don't transcribe (remove the data-example rows — they are preview content only). topic-notes is the essence of the discussion in 1–3 sentences; topic-outcome must start with exactly one of 'Decided:', 'Action:', 'Parked:' or 'No decision —' so outcomes are scannable. Every action needs one named owner (a person, not a team) and a due date — if the user's notes lack an owner or date, ask or mark it '[owner?]' rather than inventing one. Keep attendee names exactly as given, apologies after a '·'. Preserve the meeting's language; keep section labels unless asked. One page unless the meeting had more than ~8 topics. Do not editorialize or add opinions that weren't in the notes.
Published versions are immutable: /t/meeting-notes@{version}/ never changes once live. /t/meeting-notes/ always points at the latest.