Writing Concise Meeting Recaps

After most meetings, someone writes a recap: a short email or Slack message that captures what was decided and what happens next. A good recap saves everyone time, prevents forgotten tasks, and keeps the team aligned. A bad recap buries the decisions under a wall of text that nobody reads. This lesson teaches the structure, tense, and phrasing of a recap that actually gets used.

Lead with the decision

The biggest mistake is starting with background. Readers want the outcome first. Open with the single most important decision in one sentence.

• Weak: Today we had a meeting to discuss the launch and various topics came up.
• Strong: We decided to delay the launch to March 14 to fix the payment bugs.

The second version delivers the headline in one line. Everything after it is detail.

The three-part structure

A clean recap has three sections:

1. Decisions : what the group agreed on.
2. Action items : what happens next, with owners and dates.
3. Open questions : anything unresolved.

Example:

Decisions

• Launch delayed to March 14.
• We will fix the payment bugs before any new features.

Action items

• Fix the Stripe webhook bug : @Maria : by Friday
• Write a regression test for refunds : @Dev : by Monday
• Notify the 12 affected customers : @Sales : today

Open questions

• Do we offer a credit to affected customers? (discuss Thursday)

Writing action items

An action item needs three parts: a verb, an owner, and a due date. Without all three, the item is easy to drop.

• Weak: Look into the bug.
• Strong: Investigate the root cause of the webhook bug : @Priya : by Wednesday.

Start each item with a strong verb: fix, write, send, review, schedule, investigate, draft. The owner is the one person accountable, usually tagged with @name in Slack or listed by name in email.

Tense for outcomes

Use the present perfect for decisions that stand now:

• We have decided to delay the launch. (The decision is final and current.)

Use the past simple for finished actions at the meeting:

• Sam presented the Q3 numbers. (A completed action in the meeting.)

Use will for future actions:

• Maria will fix the bug by Friday.

Avoid the present continuous for decisions: We are deciding suggests the decision is not yet final.

Length and format

A recap should be scannable in under 30 seconds. Use short lines, bullet points, and bold labels. If your recap is longer than ten lines, you are probably writing too much background. Cut anything that is not a decision, an action, or an open question.

A useful test: if a teammate who missed the meeting can act on this email without asking a question, it is a good recap.

Common mistakes

1. No owner on action items. Look into the bug with no name means nobody does it.
2. No due date. By Friday creates urgency; without it, the task drifts.
3. Too much process, not enough outcome. Readers care about decisions, not a minute-by-minute of the discussion.

Practice

Turn these rough notes into a clean action item:

talked about the bug, someone should fix it, also need a test

A strong version:

• Fix the webhook bug : @Maria : by Friday
• Add a regression test : @Dev : by Monday

You can now write recaps that keep teams aligned. In the final lesson of this course, you will learn the norms of Slack and async communication, where the rules are different from email.