A useful follow-up answers three questions quickly: what changed, what needs to happen and who needs to respond. It should preserve the difference between an idea discussed in the meeting and a commitment someone actually accepted.
Lead with decisions and required responses.
Put the important changes first. If the reader needs to approve, correct or confirm something, say exactly what and by when. Keep background below the decisions rather than making every reader reconstruct the point.
Write actions as deliverables.
Use a verb and an inspectable result. “Look into the issue” is vague. “Share the three options and a recommendation” describes an output the next meeting can review.
| Field | Question to answer |
|---|---|
| Deliverable | What will exist when the action is complete? |
| Owner | Who accepted responsibility? |
| Date | When is the result needed? |
| Dependency | What must happen first? |
| Review | Where will progress or completion be checked? |
Keep uncertainty visible.
If someone was suggested as an owner but did not accept, write “owner to confirm” and name who will resolve it. If the date depends on another decision, record that condition.
Do not convert “we could” into “we will.” The action register should reflect the commitment, not strengthen it through editing.
Give the record somewhere to live.
Link the reviewed meeting record and the work system where ongoing tasks are maintained. Decide which place is authoritative for task status so two lists do not quietly diverge.
At the next meeting, read back changes to the old actions before adding new ones. Close completed items with evidence or a clear acknowledgement of the result.
MAKE IT YOURS
Your editable template.
Replace the bracketed prompts, remove what you do not need, and save a version for your team.
MEETING FOLLOW-UP Subject: [Meeting name]: decisions and next steps Hello [team], Here is the reviewed record from [meeting / date]. DECISIONS - [Decision and any condition] - [Decision and any condition] NEXT STEPS Action [A-001]: [Specific deliverable] Owner: [Confirmed name / owner to confirm] Due: [Date] Dependency: [If any] Review point: [Where / when] Action [A-002]: [Specific deliverable] Owner: [Confirmed name / owner to confirm] Due: [Date] Dependency: [If any] Review point: [Where / when] PLEASE CONFIRM [Specific correction, ownership or date needed] by [date]. OPEN QUESTIONS - [Question / person resolving it / date] RECORD AND WORK LOCATIONS Reviewed meeting record: [Link] Task-status source: [Link] Next meeting / checkpoint: [Date] Thank you, [Name] ACTION REGISTER FIELDS ID | Deliverable | Confirmed owner | Due | Dependency | Status | Evidence | Next review [Fill one row per action in your preferred document or work system] Prepared with the MeetriX resource library. Adapt to your organisation. https://meetrix2.lisan.com/resources/follow-ups/
