Amplenote Explained 17: How to take meeting notes (and introducing networked thought & atomic notes)
Based on Amplenote's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Capture meeting notes directly in Amplenote Daily Jots to avoid creating a new note for every meeting.
Briefing
Meeting notes stop being a tagging chore when they’re written where the day already lives: in Amplenote’s Daily Jots, with inline links that point to small, self-contained “atomic notes.” Instead of creating one new note per meeting (which quickly multiplies into separate files for every person, meeting type, and topic), the workflow ties each meeting to the date automatically and uses links to organize the information after the fact.
The first approach—one note per meeting—works but scales poorly. A meeting with Bill creates a “work meeting with Bill” note; a friendly meeting with Bill creates a “personal meeting with Bill today” note; a meeting with Sarah adds yet another note, likely requiring tags for Sarah, for personal vs. work, and for other themes like “shared rituals.” The result is a growing pile of notes that still need manual organization.
The improved system shifts the capture step into the Daily Jot. Because Daily Jots are created automatically, meeting notes can be typed directly into the day’s entry. The key move is to link key words inside the jot—such as the person’s name—to dedicated notes. When Sarah’s page is opened, backlinks show every meeting note that referenced Sarah, effectively turning the day’s text into an index.
From there, the workflow becomes even more powerful by linking multiple concepts from the same line. Linking “work meeting” alongside the person creates a natural-language structure like “A work meeting with Bill.” With two inline tags on the same line, Amplenote can automatically organize meeting notes along both dimensions. Visiting Bill’s note reveals a backlinks list of all meetings ever had with him, and filters can narrow that list—for example, excluding references marked as “work meeting” to show only personal meetings.
This approach relies on atomic notes: small notes designed to encapsulate a single idea, object, or person and serve a single purpose. A “Bill” note holds notes about Bill. A “personal meeting” note groups friendly meetings. A “shared rituals” note captures that theme. A “Simplify onboarding” note exists to hold tasks and meeting-relevant notes for that specific project. Atomic notes can be empty placeholders when the goal is simply to link and organize, or they can contain ongoing content—like a running to-do list inside the Bill note.
The net effect is a meeting-note system that stays lightweight during capture and stays navigable afterward. By combining Daily Jots (for time-based capture) with atomic notes and inline links (for semantic organization), meeting notes can be organized without leaving the day’s workspace—while still supporting filtered views by person, meeting type, and topic.
Cornell Notes
Meeting notes become manageable when they’re captured inside Amplenote’s Daily Jots and organized through inline links to atomic notes. Instead of creating a separate note for every meeting (which forces extra tagging and creates lots of scattered notes), the workflow types meeting details directly in the day’s jot and links key words like a person’s name. Linking multiple concepts on the same line—such as “work meeting” plus the person—lets backlinks and filters automatically produce views like “all meetings with Bill” or “only personal meetings with Bill.” Atomic notes are the backbone: each one holds one purpose (e.g., Bill, shared rituals, Simplify onboarding) and can be empty or contain ongoing content like to-dos.
Why does the “one note per meeting” approach become messy as meetings multiply?
How does capturing meeting notes in a Daily Jot reduce friction?
What does linking key words inside a Daily Jot accomplish for later navigation?
How do two inline links on the same line enable more precise filtering?
What are atomic notes, and why are they central to this workflow?
Review Questions
- How would you structure a meeting line in a Daily Jot to support both “by person” and “by meeting type” retrieval?
- Give two examples of atomic notes from the transcript and state what single purpose each one serves.
- What’s the difference between using atomic notes as empty link targets versus storing ongoing content inside them?
Key Points
- 1
Capture meeting notes directly in Amplenote Daily Jots to avoid creating a new note for every meeting.
- 2
Turn key words (like a person’s name) into inline links so backlinks automatically build an index on the linked note.
- 3
Use multiple inline links on the same line (e.g., person + “work meeting”) to enable automatic organization across dimensions.
- 4
Build a library of atomic notes that each encapsulate one purpose, such as Bill, shared rituals, or Simplify onboarding.
- 5
Keep atomic notes empty when they function as link targets, or add content when ongoing tracking (like to-dos) is needed.
- 6
Use backlinks and filters on atomic notes to answer questions like “all meetings with Bill” or “only personal meetings with Bill.”