Subject
- Follow-up: [meeting]: decisions and next actions
Resources
Turn a meeting into the next clear move.
A concise meeting follow-up template for decisions, actions, owners, dates, risks, and open questions.
01
Make decisions easy to find.
02
Give every action one accountable owner.
03
Keep ambiguity visible instead of inventing tidy answers.
Use it now
Copy this meeting follow-up
Replace the prompts, delete empty sections, and keep the final message focused on action rather than proof that the meeting happened.
Opening
- Thanks, everyone. Here is the short version of what changed and what happens next.
Decisions
- [Decision]: [why it matters / constraint]
- [Open decision]: needs [missing input] by [date]
Actions
- [Owner]: [outcome], due [date or review point]
- [Owner needed]: [outcome], assign by [date]
Risks and open questions
- [Risk or dependency]: [person who can resolve it]
- [Question]: [needed before which decision]
Close
- Reply with corrections to ownership, dates, or decisions. We will review open items on [date].
Copy, print, or paste this structure into the tool where your work already lives.
Where it helps
Use the template when the work needs structure.
Project review
Capture scope changes, dependencies, owner commitments, and the next decision point.
One-on-one
Record agreed support, manager actions, employee actions, and what returns next time.
Customer meeting
Separate customer needs, commitments made, unanswered questions, and follow-up dates.
How it works
Make the handoff explicit.
Good delegated work has a clear input, a useful artifact, and a moment where a person can review what happens next.
Write decisions first
If a call is tentative, mark it open rather than making it sound final.
Name one owner
Add a date or review point and state what done looks like.
Keep the recap short
Move discussion detail to notes; send only what people need to act.
Useful outputs
Work you can inspect, share, and act on.
The output is something you can review, not a vague promise that AI saved time.
01Decision list
02Action register
03Owner and date table
04Open questions
05Risks and dependencies
06Short send-ready recap
Meeting follow-up template / review point
Active workflowHuman decision
01PreparedDecision listReady
02CheckedMake decisions easy to find.Visible
03BoundaryConsequential actionWith you
The boundary
Assistance does not remove accountability.
The template should preserve uncertainty. Do not infer a decision, owner, or deadline that the meeting did not establish.
Read about security and trustFrequently asked questions
The practical questions, answered.
01When should meeting follow-up be sent?
Send it while the context is fresh, ideally the same day, after the meeting owner has checked decisions, ownership, and dates.
02How long should it be?
Usually short enough to scan in under two minutes. Link to full notes rather than putting the transcript into the follow-up.
03What if an owner is unclear?
Write 'owner needed' and make assigning one the next action. Do not hide ambiguity with shared ownership.
Get access
Give Bumblebee one real job to handle.
Start with an output you can recognize, review, and improve.