Meeting Memory Checklist
Use this one-page checklist to make sure every important meeting produces usable memory instead of clutter.
Choose your next step before the meeting disappears
If this checklist exposed a real follow-through leak, do not stop at diagnosis. Pick the shortest honest next step now: pressure-test your workflow with proof, start with the $19 paid entry, or compare the broader Starter Pack shelf first.
Not ready to buy yet? The founding-list option is still right below, but warm checklist readers no longer have to scroll past a waitlist ask before they can choose proof-first or paid.
Want the paid brief when it opens?
If the meeting-follow-through problem is real for you but you are not ready to buy a workflow kit yet, join the Meeting Memory founding list here before you lose the thread.
Prefer the full pitch first? Open the Meeting Memory prelaunch brief →
Most meetings already get captured. The real failure happens after the call, when decisions stay fuzzy, action items lose owners, and the follow-up never gets sent.
This checklist is the minimum operating layer that stops that decay. Bookmark it, hand it to a team lead, or use it as the review standard after every important call.
Before the meeting
- Clear purpose stated in the invite
- Right people invited: decision-makers + implementers
- Pre-read or context shared if needed
- Recording or transcription enabled if your stack supports it
During the meeting
- Decisions stated explicitly, not just discussed
- Action items captured with owners
- Deadlines mentioned out loud
- Open questions noted
Immediately after the meeting
- Summary written in 2–3 sentences
- Decisions extracted and listed separately
- Every action item has exactly one owner
- Every action item has a visible deadline
- Follow-up message drafted before context leaks
Before leaving the workflow
- Follow-up message sent, not just drafted
- Note saved to a canonical location with a clear title
- Title format is consistent: [Date] [Type] [Client/Topic]
- Tags added for later searchability
Within 24 hours
- Action items appear in the task manager, not just the meeting note
- Decisions added to the client or project record if relevant
- Stakeholders notified of outcomes they need to know
Weekly review
- Scan the last week of meeting notes for dropped tasks
- Update client or project records with new preferences and context
- Archive notes that no longer need active attention
The minimum working version
- Summary — what happened in 2–3 sentences
- Decisions — what was agreed
- Action items — who owns what, with deadlines
- Follow-up sent — before you move on
- Note stored — with a clear searchable title
Quick diagnostic
- Can you find the decision record without searching email?
- Does a new team member know who owns each action item?
- Will the deadline appear in someone's task system?
- Did the follow-up get sent before you moved to the next task?
- Could you find this note three months from now?
If any answer is no, the meeting produced clutter instead of memory.
Tool stack
| Layer | Purpose | Options |
|---|---|---|
| Capture | AI note taking | Fathom, Fireflies, tl;dv, Granola |
| Action | Task management | Linear, Todoist, Notion, ClickUp |
| Memory | Knowledge storage | Notion, Obsidian, Slite, Reflect |
The tools matter less than the workflow. A consistent process with average tools beats an inconsistent process with perfect tools.
Still comparing meeting tools before you lock the workflow?
If this checklist exposed a follow-through leak but you still need to choose or replace the capture layer, jump into the live Stream 03 comparison pages instead of restarting the research loop on generic vendor homepages.
These five links create distinct Stream 03 meeting-memory-checklist feeder surfaces so Henry can measure whether workflow-problem readers actually enter the warm SEO comparison lanes.
Choose proof or paid
Ready to buy? Start with the $19 founder prompt pack. Still skeptical? Run the meeting-notes Prompt Evaluator demo first and inspect the workflow pressure-tested before you pay.
These two links now use separate Stream 10 proof-vs-paid tags so checklist visitors can be compared cleanly by direct-buy vs proof-first behavior.
Run the extractor on a matching sample
Do not drop into a blank app if the workflow problem is already obvious. Open the closest sample and inspect whether the extractor produces a usable recap, action list, and follow-up structure before you decide what to buy next.
These three links create distinct Stream 07 meeting-memory-checklist demo surfaces so Henry can compare which checklist readers actually choose a proof-first extractor path.
Want the full working version?
Want the trust-first comparison page first? Review the Starter Pack shelf. If one workflow leak is clearly hurting most, go straight to the paid Meeting Memory System or start smaller with the $19 founder prompt pack. Still deciding between the app, the low-ticket entry, and the proof-first path? Open the extractor homepage and choose from all 4 routes in one place.
Join the Meeting Memory founding list
Get the launch announcement, first issue preview, and founding-member access for the paid Meeting Memory brief.