meeting follow up action items template

A meeting is not finished until the owners are visible.

Meeting follow-up should convert conversation into decisions, assigned actions, and unresolved questions. A recap that only says thanks is not enough.

Use the template See related tools
Search intent Teams and client-service operators who need a repeatable recap after calls and working sessions.

This page is a practical guide, not a guarantee of leads, revenue, compliance, payment collection, or platform approval.

Meeting recap structure

A safe starting template.

Adapt this to the buyer's business, tools, consent rules, contracts, and platform policies before using it with real customers.

01
Context: meeting name, date, attendees, and purpose.Review manually before external use.
Step
02
Decisions: what was agreed and what changed.Review manually before external use.
Step
03
Action items: owner, task, due date, and dependency.Review manually before external use.
Step
04
Open questions: what still needs an answer before work continues.Review manually before external use.
Step

Checklist

What to verify before using the workflow.

Send the recap while the meeting is still fresh.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Separate decisions from discussion notes.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Assign one owner per action.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Call out blockers clearly.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Link files, examples, and references used in the meeting.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Avoid these mistakes

The page should reduce risk, not just increase clicks.

Writing a transcript instead of a follow-up.

Fix this before treating the workflow as production-ready.

Listing tasks with no owner.

Fix this before treating the workflow as production-ready.

Leaving due dates implied.

Fix this before treating the workflow as production-ready.

Failing to capture changed scope.

Fix this before treating the workflow as production-ready.