How to Write a Meeting Follow-Up Memo

How to Write a Meeting Follow-Up Memo

The meeting ends. Chairs scrape back, laptops close, someone says "great, so we're agreed" — and within an hour the details have gone soft. Who was going to chase the supplier? Was the launch date moved, or just discussed? The follow-up memo exists to answer those questions before they become a second meeting.

Done well, it takes fifteen minutes to write and saves hours of confusion. Done badly, it adds to the pile of internal email nobody opens. The difference is not length or polish. It is whether the memo gives every reader a clear answer to one question: what happens next, and who is doing it?

A follow-up memo is not a set of minutes

Minutes record a discussion; a follow-up memo records an outcome. Minutes might note that three options were considered and that finance raised concerns about timing. A follow-up memo says: option two was chosen, finance will confirm the budget by 22 April, and no further work on options one and three is needed.

That distinction keeps the document short. Aim for a single page, and half a page is often enough. If formal minutes already exist, your memo sits alongside them as the action list, not as a second account of the same conversation.

Draft it while the meeting is still in the room

The best time to write is before people leave. Keep a running note during the meeting, then use the final five minutes to read the actions back: "So Priya is checking the contract, Tom is reworking the schedule, and I am booking the venue by Friday. Anything wrong with that?"

Correcting a name or a date in the room takes seconds. Chasing it by email the next morning takes days. Send the memo the same day if you can, and within twenty-four hours at the latest. If something is still unresolved, say so and give it a date: Decision on the second supplier deferred to the 16 April meeting is far more useful than silence.

Capture four things, and nothing else

Almost every useful follow-up memo contains the same four elements. Cover these and you have covered what matters.

  • Decisions. What was agreed, stated plainly. Include anything explicitly ruled out, because people often remember closed options as still open.
  • Actions. The tasks that follow. One action per line, written as a verb first: Draft the revised quote, not revised quote discussion.
  • Owners. One name per action. A team, a department or "we" is not an owner. If two people share a task, name the one who reports back.
  • Deadlines. A date, and a time if it matters. "End of next week" means different things to different people; "by 5pm on Friday 19 April" does not.

Anything else — background, thanks, long explanations — is optional. Leave it out unless a reader genuinely needs the context to act.

Structure that gets read

Use the standard memo header, then organise the body under short headings. A reader should be able to find their own name and deadline in under ten seconds.

Decisions first, actions second, next steps third. Put the actions in a list rather than a paragraph. If your organisation uses a task tracker, mirror the wording in the memo so the two match.

To: Project team

From: Rachel Nwosu

Date: 14 March

Subject: Follow-up — March project review

Decisions

The client launch moves to 9 May. The original April date is no longer viable. Training will run as two sessions rather than one.

Actions

  1. Send the revised schedule to the client — Daniel, by 12pm on 15 March.
  2. Confirm the training room booking — Meera, by 20 March.
  3. Update the risk log with the new launch date — Rachel, by 18 March.

Next steps

Progress will be reviewed at the team meeting on 27 March. Anything not completed by then should be flagged to Rachel beforehand.

Plain language, fewer mistakes

Write for the person who missed it

Short words and active sentences. Write "Meera will book the room", not "the room booking will be actioned". Name the person who does the thing rather than the thing that must be done.

Cut the phrases that pad internal writing: as discussed, going forward, please be advised, at your earliest convenience. They add length without adding information. Dates, names and verbs do the work. Spell out acronyms the first time, and give a one-line reason for any decision that might otherwise look odd. A decision people understand is a decision they follow.

Habits that weaken a memo

  • Vague owners. "Marketing to review" leaves everyone waiting for someone else to start.
  • Missing dates. An action without a deadline is a wish.
  • Burying the decision. If the key point sits in paragraph four, half the readers will miss it.
  • Length for its own sake. Two pages of narrative get skimmed; one page of specifics gets used.
  • Numbering nothing. Numbered actions make it easy to reply "action 3 done" or "action 5 needs more time".
  • Copying the world. Send it to the people who need to act or know, and state who else should be informed.

Before you hit send

Do a final pass with five quick questions. Is every decision stated in one clear sentence? Does every action have one named owner? Does every owner have a date? Could someone who was not in the meeting understand it? Is it shorter than it needs to be?

If the answer to any of those is no, fix it now rather than in a follow-up to the follow-up. A good memo ends the conversation about what was agreed and starts the work of doing it. Read it once as if you were the busiest person on the list — then send it.

Photo: StartupStockPhotos / Pixabay