You walk out of a meeting knowing something important got agreed. Two days later, nobody can say what it was. One person "thought someone else was handling it." Another remembers the exact opposite of what happened.

That is the gap between a meeting that happened and a meeting that changed something. The summary is the only part of the meeting that survives the room. Here's how to write one people actually act on.

A summary is not minutes, and not a transcript

Three different documents, three different jobs:

Transcript — every word, in order. Useful as evidence, useless for scanning.
Minutes — a formal record of who was there, what was proposed, what was voted on. For boards and governance. Here's how to write meeting minutes.
Summary — the trailer. Decisions, action items, open questions. Readable in under two minutes.

A summary that reads "we discussed the timeline" is not a summary. It's a diary entry. The reader — especially someone who wasn't in the room — needs to know what changed, not what was talked about.

The three things a summary must capture

Everything else is context. These three are the work:

Decisions. Written as finished sentences. "Launch moves to March 3" is a decision. "Discussed the launch date" is not.
Action items. A verb, one owner, a real date. One person, not "the team."
Open questions. What was raised and not answered, and who is finding out.

If a point isn't a decision, an action, or something still open, it probably doesn't belong.

Why most summaries are wrong

The mistake is timing. Most people write the summary hours after the call, from memory, and memory is a bad recording device.

By hour two, "I'll follow up on the proposal" has become "we'll figure out the proposal." The owner blurs into the team. The deadline disappears. A decision that felt settled in the room gets rewritten as a discussion because you can no longer tell them apart.

The fix is to capture while the meeting is still happening — decisions and actions as they land, not everything that was said. If you have a transcript, summarize from the transcript, not from what you remember of it.

A method that works

Before: know the objective

One sentence on what this meeting is trying to decide. If you can't write it, the meeting shouldn't happen. That sentence becomes the first line of the summary.

During: capture the three, not the verbatim

Don't transcribe. Watch for the moments that count: someone commits to a date, someone says "we're going with X," someone raises a problem and no one answers it. Write those down as they happen, in shorthand.

The last five minutes

Before anyone leaves, read the decisions and actions back out loud. "So we're moving launch to March 3, and Sam is updating the project board by Friday." Half the summary is done before the call ends, and the gaps surface while the right people are still in the room.

After: write it the same day

The longer you wait, the more the detail fades and the more the summary becomes a reconstruction instead of a record.

The action-item formula

Vague action items are why nothing gets done. "Chase the supplier" is not an action item. This is:

Jamila to contact the supplier by Thursday to confirm the revised delivery date and post it in the project channel.

Four parts, every time:

Verb first. One observable result, not a topic.
One owner. A person, not a team. If two people "own" it, nobody does.
A real date. Not "end of week" — a specific day.
Enough context to start. What it connects to, or what it's blocking.

Split compound tasks. "Update the proposal and get legal approval and send it to the customer" is three handoffs pretending to be one.

Keep decisions, discussion, and actions apart

One of the most common summary mistakes is mixing the three layers, so a reader can't tell an idea from an authorization:

Discussion — the options, evidence, and objections that shaped the outcome.
Decision — what the group approved, or explicitly did not.
Action — a concrete step someone is taking, with an owner and a date.

Keep them in separate sections. If a decision reverses an earlier one, say which one: "Replaces the February 14 date agreed on September 28" saves a confused reply later.

A template you can use

Copy these fields into any doc and drop what doesn't apply. For a fuller version, grab the meeting minutes template.

Meeting: [name] Date: [date] Attendees: [names] Purpose: [one sentence — what this meeting was called to decide]

Decisions

[Decision, as a finished sentence, with who agreed]

Action items

[Action] — [Owner] — [Due]

Open questions

[Question] — [who is finding out] — [by when]

Next steps

[What happens before the next meeting, and when that meeting is]

When the summary has to be right

For an internal standup, "good enough" is fine. For a sales call, a client kickoff, an interview, or a QBR, "good enough" isn't — the summary becomes the record. If a customer later claims "I never said that," the summary is either your proof or your problem.

That's where writing from evidence pays off. A summary backed by the transcript — where every decision and action item links to the exact quote, speaker, and timestamp it came from — isn't a recollection. It's a record. When someone disputes what was agreed, you can click through to the moment it was said.

Meetbook does this automatically: it records the call, then the summary and action items it produces each carry the quote, speaker, and timestamp they came from. But the discipline is the same whether you use a tool or a notebook — write decisions as decisions, name one owner per action, and do it while the meeting is still in the room. For platform-specific steps, here's how to summarize a Zoom meeting.

The five-second version

Know the objective before the call.
Capture decisions and actions as they happen — not the verbatim.
Read them aloud in the last five minutes.
Write the summary the same day, from the transcript.
Name one owner and a real date on every action.

The summary is the only part of the meeting that survives. Make it the part that does the work.

How to Summarize a Meeting with Action Items