Meetings
Meeting follow-up people use
Most follow-up messages are too long because they try to prove the meeting happened. The useful version tells people what changed and what they own.
Published 2026-08-18 · Updated 2026-08-18 · 4 min readA meeting follow-up format for turning decisions, action items, owners, dates, and open questions into a usable message.
Write decisions first
Put decisions above discussion notes. If a decision is tentative, label it as open. Do not let a suggestion become a decision just because it sounds tidy.
A good assistant should flag unclear decisions rather than smooth them over.
Make ownership boringly clear
Every action needs one owner. Shared ownership usually means no ownership. Add a due date or the next review point.
When the owner is unclear, write 'owner needed' instead of guessing.
Keep the message short
People read follow-up when it is short enough to act on. Use sections for decisions, actions, open questions, and risks.
Use Bumblebee when follow-up should become tracked work instead of a message that disappears in a thread.
Preserve open questions and risk
A polished recap can accidentally erase uncertainty. Keep a separate section for questions that still need an answer, assumptions that need checking, and dependencies that could change the plan.
If the meeting did not establish an owner or deadline, say so. 'Owner needed' is operationally useful; a confident guess is not.
Bring actions back at the review point
Sending the recap is not the end of follow-up. Every material action needs a date or a moment when it returns to view. Otherwise the message becomes another archive of good intentions.
Bumblebee can help keep that continuity: prepare the message, register the commitment, and surface what remains open before the next meeting.