I started tracking whether people actually read meeting summaries. Sent them out for about three months to groups of 5 to 12 people. The response rate was low enough to be embarrassing. Two replies, out of what I’d estimate was somewhere north of 200 summaries sent.
What I’d been writing looked like notes. What people needed was a decision record. Those are not the same thing.
What the difference actually is
A notes document captures what happened. It might run three pages, list every topic discussed, and include full paragraphs under each agenda item. It’s accurate and it’s useless.
A summary answers three questions: what was decided, who does what by when, and what does the reader need to do (if anything). Everything else is archive material. If your summary requires more than 90 seconds to read, it’s too long.
The five-bullet limit I mentioned is a heuristic, not a rule. Some meetings genuinely produce more outputs. But if you find yourself writing a sixth bullet, ask whether that point actually needs to be in the summary or whether it belongs in a linked doc that only some readers need.
Four templates by meeting type
These aren’t interchangeable. A weekly team sync and a board update are trying to do different things for different audiences.
Weekly team sync.
Date: [date] Attendees: [names] Decisions made: - [decision 1] - [decision 2] Action items: - [Name]: [task] by [date] - [Name]: [task] by [date] Blocked: [what's stuck and who's unblocking it] Next sync: [date/time]
The “Blocked” line is the one most people skip. It’s also the one that actually gets things done. If something is stuck, say so explicitly. Don’t bury it in the decision list.
Client meeting.
Date: [date] Meeting: [client name] / [your company] Participants: [names and roles] What we aligned on: - [point 1] - [point 2] Open items: - [item]: [owner] by [date] Next steps for client: - [ask 1] - [ask 2] Next scheduled touchpoint: [date]
The separate section for “next steps for client” matters. It makes clear what you’re asking them to do, which is often the whole reason you had the meeting. Folding their action items in with yours creates confusion about who owns what.
Project kickoff.
Project: [name] Date: [date] Core team: [names] Agreed scope: - [what's in] - [what's explicitly out] Milestones and owners: - [milestone 1]: [owner], target [date] - [milestone 2]: [owner], target [date] Decision log: - [key decision made in kickoff] Outstanding questions (to be resolved by [date]): - [question 1] - [question 2]
The “what’s explicitly out” line is one I’ve come to think is the most important part of any kickoff document. Scope creep usually starts with things nobody said were out of scope. Naming them kills ambiguity early.
Board or exec update.
Date: [date] Attendees: [names and titles] Decisions requiring board/exec action: - [decision, vote outcome if applicable] Key information shared: - [topic]: [one-line summary] Follow-up commitments: - [person]: [commitment] by [date] Next meeting: [date]
Board summaries get shared more widely than the people in the room expect. Write this one as if the CEO will forward it to someone who wasn’t there. Because they probably will.
The five-minute rule
Write the summary within five minutes of the meeting ending. Not tomorrow morning. Not “later today.” Five minutes.
Here’s why it actually matters: your memory of what was decided decays faster than your memory of what was discussed. Ten minutes after a meeting, you can still tell someone roughly what was covered. But you’re already fuzzy on whether [name] committed to the Tuesday deadline or just said “probably Tuesday.” Write it while the room is still in your head.
According to research on memory and forgetting from the American Psychological Association, recall accuracy for contextual details drops significantly within the first 20 minutes after an event. The transcript is your backup, not your primary source. Your primary source is the read of the room.
Common mistakes
Summarizing the discussion instead of the outputs. Nobody who wasn’t in the meeting needs to know that “there was a long discussion about the design timeline.” They need to know the decision: 6-8 weeks, design team owns it.
Sending the transcript instead of the summary. Transcripts have their place in a linked appendix for anyone who wants the full record. They should never be the top-line deliverable.
No explicit owner on action items. “We’ll follow up on the vendor contract” is a commitment to nothing. “Sara will send the revised contract to legal by Thursday EOD” is a commitment.
What happens when you automate this
Tools like Craqly can generate a first draft of this structure during the meeting itself, surfacing decisions and action items in real time rather than leaving you to reconstruct them afterward. The output still needs a human edit (the AI doesn’t know which “follow up” was a serious commitment and which was a polite deflection), but it cuts the post-meeting writing time significantly. I’ve found the generated draft is usually 70% right on action items and closer to 85% right on decisions. Good enough to edit from, not good enough to send as-is.
The templates above work with or without AI assistance. The format is the same either way. What changes is how much time you spend filling it in.
If you’re sending summaries that nobody reads, my honest guess is it’s not a technology problem. It’s a length problem.