Turning meeting notes into update slides

Meeting notes are written fast. They capture who said what, half-finished thoughts, action items and the occasional “follow up on this??”. They’re useful to the people who were there and close to unreadable for everyone else.

But often the people who weren’t in the room are exactly the ones who need the update: a manager, another team, a client, or the wider company at a weekly all-hands. A few clear slides can carry the important parts of a meeting to them in a couple of minutes.

Here’s a routine for getting from raw notes to update slides without spending an afternoon on it.

Step 1: Tidy the notes while they’re fresh

Do this within a day of the meeting, while you still remember what the shorthand means.

Read through once and tag each line as one of four things:

• D for a decision
• P for progress or a status update
• B for a blocker, risk or issue
• A for an action, with an owner and a date if you have them

Anything that doesn’t fit, such as discussion that went nowhere or side conversations, can be left out of the update. It’s still in the notes if anyone needs it.

This one pass does most of the work. You’ve turned a timeline of a conversation into categories of outcome.

Step 2: Decide who the update is for

The same meeting can produce different updates.

Audience	What they want	How much detail
Your manager	Decisions, blockers, anything needing them	Brief
Another team	What affects them and when	Only the relevant parts
A client	Progress, next steps, anything needing their input	Polished, no internal debate
The whole company	Headline progress	Very brief

Pick one audience per update. If you need two, make two short versions.

Step 3: Use a fixed structure

A consistent structure makes updates fast to write and easy to read, especially if you send them every week. Four to six slides usually covers it. If the update is for a daily or weekly team check-in, a team stand-up template follows a similar shape.

Slide 1: Summary

One headline sentence and three short lines. For example:

“Mobile checkout is on track for the 15 March release.”

• Payment provider integration complete
• Design review moved to next week
• Need a decision on guest checkout by Friday

(An illustrative example.) If someone only sees this slide, they should have what they need.

Slide 2: Decisions made

List each decision from your D tags in plain words. Include the reason if it’s likely to be questioned. Decisions are the most useful part of most meetings and the most likely to get lost, so give them their own slide.

Slide 3: Progress

What moved forward since the last update, from your P tags. Keep it to the meaningful items. A simple three-column table works well: workstream, status, note.

Slide 4: Blockers and risks

Your B tags, each with what’s needed to clear it and who can help. If you need something from the audience, say so clearly here.

Slide 5: Next steps

Your A tags as a short table: action, owner, due date. This slide is the one people come back to, so keep owners and dates accurate.

Step 4: Rewrite for someone who wasn’t there

Notes are full of context the audience doesn’t have. As you move each item onto a slide, rewrite it.

Expand shorthand. “PP int done, waiting on QA” becomes “Payment provider integration finished; testing starts Monday.”

Remove names where they don’t help. “Rahul said maybe we should consider…” becomes the idea itself, or the decision if one was made. Keep names for action owners.

Drop the debate, keep the outcome. If the meeting spent twenty minutes on a choice, the update needs the choice and one line of reasoning.

Say what you need. Vague items like “discuss timeline” become specific asks: “Need agreement on moving launch by one week.”

Step 5: Keep it short

An update deck is a quick read, not a presentation in its own right. A few guidelines:

• One idea per slide where possible, with a headline that says it.
• Short lines, not paragraphs. If you need to explain more, add a speaker note or link to the full notes. Tidy, tagged notes are plain text, which is the easiest input if you’d like to turn plain text into slides and then edit the draft.
• No decoration for its own sake. A clean, consistent layout every week is easier to scan than a fresh design each time.

If the update starts life as a written page each week, a weekly update page that presents well shows how to set that page up.

Step 6: Link back to the notes

Add a link to the full meeting notes on the last slide, or in the message you send with the deck. Anyone who wants the detail can find it, and the slides don’t need to carry everything.

Make it a weekly habit

If you run the same meeting every week, set up a notes template that already uses the four headings: Decisions, Progress, Blockers, Actions. Take notes straight into those sections during the meeting. Afterwards, tidying takes minutes. If the meeting is a project’s first, from project plan to kickoff presentation covers that deck.

A quick checklist

• Are the notes tagged into decisions, progress, blockers and actions?
• Is the update aimed at one audience?
• Does the first slide work on its own?
• Has shorthand been rewritten for someone who wasn’t there?
• Does every action have an owner and a date?
• Is there a link to the full notes?

Five slides, ten minutes, and the people who missed the meeting know exactly where things stand.