Work & Productivity·March 24, 2026

Another Meeting to Recap the Last Meeting: The PM's Playbook

TL;DR

Six meetings today. Zero decisions. Notes nobody reads. Here's the project manager's playbook to ship summary, decisions, and action items while the meeting is still fresh.

A project manager's dual-monitor desk during a live meeting — left monitor shows a Zoom/Teams call grid with active speakers, right monitor shows a Gantt timeline and a sticky-note kanban with red 'blocked' tags, a third laptop running an active recording with audio waveform and a red REC indicator, a calendar showing back-to-back meetings, a coffee mug, and a notebook with handwritten action items

It's 4:47 PM. You just got out of the third hour-long meeting today. None of them produced a decision.

There was the standup that ran 22 minutes long because someone wanted to "loop back" on a thing from last sprint. The cross-functional sync where two teams had different definitions of "done" and you spent forty minutes on the same definition you spent forty minutes on last week. The status update where the engineering lead had to leave at minute 18 and now there are three follow-up meetings on the calendar to recap the part of the meeting they missed.

You have notes. They are in three different docs, two Slack DMs, and a Post-it on your laptop that says "FRIDAY — vendor question?? — Karen??"

You also have an inbox of seventeen people who weren't in the meetings and now want a recap. By tomorrow.

Every PM has this Wednesday. The job, in theory, is keeping the team moving toward outcomes. The job, in practice, is the meeting industrial complex — and writing the notes nobody will read for the meetings that nobody decides anything in.

Here is what actually works.

The move: stop taking notes during the meeting

The mistake every PM makes is splitting their attention between facilitating and note-taking. You can do one of those well. You cannot do both.

Stop taking notes. Record the meeting. Let the tool transcribe. Generate the summary, decisions, and action items. Send. Move on.

You facilitate the meeting. The tool documents the meeting. Those are different jobs and they should never have been the same job.

The playbook

Before the meeting: get consent in the invite

Add one line to the meeting invite or the first slide:

"This meeting will be recorded for note-taking purposes. Transcript and summary will be shared with attendees."

Do this every time. Make it your default. Get explicit verbal consent at the top of the call. Don't record meetings with HR-sensitive, privileged, or off-the-record content — that's a rule, not a guideline.

During the meeting: hit record. Facilitate.

Start the recording — Record audio uses your device's microphone and recordings cap at 50 MB (roughly 50 minutes), so it's for a meeting in the room; for a video call or a longer meeting, use your meeting tool's recorder and upload the audio file (MP3, M4A…) it saved (video isn't accepted). Run the meeting like a meeting — keep time, keep people on topic, ask clarifying questions, make sure decisions actually get made.

You are not writing things down. You are running the room. The tool is writing things down.

Right after: get the recap

Add the recording to your Sources in CorpGPT (if you recorded in the app, it's already there). Open the Make pane ("Make from these sources") and ask Chat beside it. Run, in order:

  • Summary (Make) — a clean TL;DR. What we discussed, where we landed, what's next.
  • Decisions log (ask Chat) — the decisions it finds, with the rationale, cited so you can check them against the transcript.
  • Action items (Make) — each action, with owners where the discussion named them, the deadline (if mentioned), and supporting context.
  • Open questions (ask Chat) — things that came up but didn't get resolved. Then make a Meeting Agenda and the next meeting's agenda writes itself.

Four artifacts. Each one is grounded in the actual transcript — Make results list the recording they were built from, and an answer Chat draws from the transcript names it as the source, so you can verify it.

Send

Open the email or the Slack thread. Paste the summary. Add the decision log and action items. Hit send.

The recap goes out while the meeting is still fresh. The old workflow ate the rest of your day and the recap landed Thursday morning, by which point three people had already asked "what was decided?" in Slack.

For the people who weren't there: the executive brief

Open the Make pane again. Generate an Executive brief — short, written for someone who reads it between meetings. That goes to your VP, the cross-functional partner who couldn't make it, and your own manager.

You look like you ran a tight meeting because you did, and now you also look like you communicated it cleanly because you did.

Beyond the one meeting: the project library

Build a per-project collection

Every meeting transcript, every status update, every decision memo, every stakeholder doc — drop into a collection per project in My Documents. "Q2 Platform Migration — meetings & decisions."

Six weeks in, when somebody asks "wait, what did we decide about the third-party integration?", you don't go hunting through Slack. You ask Chat: "The decision about the third-party integration vendor — what was decided, and what was the rationale?". Cited answer, with the meeting it came from.

Generate the status report on demand

End of the week. Status report due. Tick the project's collection in the Sources pane. Ask for:

  • A weekly status update (ask Chat to draft it) — accomplishments, in-progress, blockers, next week's plan, key decisions.
  • A Risk check (Make) — the new risks it finds in this week's meetings.
  • An Executive brief (Make) — the one-pager your sponsor will actually read.

Review it. Send it.

Pre-meeting prep, also automated

Before each recurring meeting, ask Chat, with the project's collection ticked: "What did we decide last meeting? What action items were due this week? What's still open from two weeks ago that we never closed?"

You walk into the standup with the agenda already in your head.

The features doing the work

Record audio — record a meeting in the room with your device's microphone (Sources pane → Add → Record audio, with consent); recordings cap at 50 MB (roughly 50 minutes). For longer meetings or calls, upload the audio file (MP3, M4A…) your meeting tool saved (up to 50 MB; video isn't accepted). Transcribed, with who spoke shown in its Transcript tab, and searchable with Chat. The transcript is the source of truth for everything else.

The Make pane — Summary, Action items, Executive brief, Meeting Agenda, Risk check. Built from the actual transcript; results land in Things I've made.

Chat across everything — ask any question across the project's library, or describe any prior meeting, doc, or decision and Chat searches for the passages that best match and names the document they're in. It drafts the decisions log and the status update, too.

My Courses — when you take over a project mid-flight, pick the prior meeting transcripts and decision memos and CorpGPT plans a short course from them (eight steps per module, from a summary to a quiz), so you walk into your first standup actually knowing where things stand.

Why this actually works

Three forces are doing the real work.

First, transcripts make decisions traceable. The biggest source of meeting friction isn't the meeting — it's the disagreement two weeks later about what was decided. With a transcript and a cited decisions log, that disagreement gets much shorter. The decision is right there, with the rationale, and you can open the transcript and read it back if anyone wants to relitigate.

Second, summarization scales attention. You can run six meetings, get six clean recaps, and send six action-items emails before 5 PM. You couldn't do that by hand. Nobody can. The tool turns "I was in too many meetings to write good notes" into a non-issue.

Third, your project memory compounds instead of evaporating. Every Slack channel goes stale. Every Notion page gets stale. The transcripts and decision logs in your collections never do — describe what you need and Chat searches for it and names the document it's in. Your project's institutional knowledge finally lives somewhere it can be found.

What this can't do

Be honest about this.

CorpGPT does not run your meeting. It does not facilitate, push back on bad ideas, manage the loud person, or notice that the engineering lead is uncharacteristically quiet. It does not own the project. It does not make the strategic call when the room is split.

It also does not auto-join calls. You start the recording. You get consent. You decide which meetings get recorded and which ones don't. The HR conversation, the privileged legal review, the sensitive 1:1 — those are not for the tool, period.

What it does is take the grunt work out of the note-taking-and-recap workflow. The typing, the formatting, the first draft. The judgment calls — facilitation, prioritization, escalation, the actual project management — that's still you.

The bottom line

Six meetings. Zero decisions. A backlog of recap emails. A team that's tired of meetings about the meetings.

Now: you facilitate, the tool documents, and the team gets the summary while the meeting is still fresh. You spend your hours on actual project work, not note-taking.

Notes while the meeting is fresh. Not days later. Finally look like a pro — because you finally are one, instead of a stenographer with a calendar.

Open CorpGPT. Hit record on the next meeting.


Keep reading

Ready to try it yourself?

Upload any document and see it in action. Free to start, no credit card.

Start My Free Workspace