Post-Meeting Rescue

You just left a call with vague "I'll send that over" commitments. Let's capture them before they disappear.

When to Use

• Just ended a meeting (especially with clients, stakeholders, or cross-functional teams)
• Multiple people said "I'll follow up on that"
• No one took notes (or the notes are useless)
• You have a bad feeling that action items are going to slip

Trigger: "Just got out of [meeting]" or "What did we even decide in that meeting?"

The Problem

Meetings end. Everyone scatters. Vague commitments float in the air:

• "I'll send that over"
• "Let's circle back on that"
• "Someone should look into X"
• "We'll figure it out offline"

2 weeks later: "Wait, who was supposed to do that?"

The Protocol (3 minutes)

Step 1: Dump What You Remember (60 seconds)

Immediately after the meeting, before the memory fades.

Prompt:

"What do you remember from that meeting? Don't organize it yet—just dump everything: decisions, questions, things someone said they'd do, things that seemed important."

Let them brain-dump. Don't interrupt.

Step 2: Extract Commitments (60 seconds)

From the dump, pull out anything that sounds like a commitment:

Pattern matching:

• "I'll..." → Commitment
• "We should..." → Vague (clarify WHO)
• "Someone needs to..." → Orphaned (assign or flag)
• "Let's..." → Probably nothing will happen
• "Can you..." → Commitment (if they said yes)

Format each commitment:

For orphaned items:

"This one doesn't have an owner or deadline. Do you want to claim it, or flag it in your follow-up?"

Step 3: Generate the Follow-Up (60 seconds)

Draft a message they can send immediately:

Template:

Subject: Action Items from [Meeting Name] - [Date]

Hi all,

Quick recap of what we agreed to:

**Decisions Made:**
- [Decision 1]
- [Decision 2]

**Action Items:**
- [ ] @Sarah: Send updated deck (by Friday EOD)
- [ ] @Me: Review proposal (by Monday)
- [ ] [Open]: Look into API issue — needs owner

**Next Steps:**
- Next sync: [Date/time if set]
- [Any other context]

Let me know if I missed anything!

[Name]

Why this works:

1. Creates a record — Now it's written down
2. Assigns accountability — Names attached to items
3. Surfaces orphans — "Needs owner" forces a response
4. Sets the norm — You become the person who makes meetings useful

Step 4: Send Prompt

"This email is ready. Send it within 30 minutes while the meeting is fresh in everyone's minds. The longer you wait, the more people will have a different memory of what was agreed."

If they hesitate:

"The worst case is someone corrects you. The likely case is everyone's relieved someone captured this."

Quick Capture Mode (If They're Rushing)

If they only have 30 seconds:

"Give me the ONE thing that will fall through the cracks if you don't write it down right now."

Get that one thing. Write it down. They can do the full capture later.

The Meeting Debrief (Optional, for Important Meetings)

For high-stakes meetings (client, executive, negotiation), add:

What went well?

• [1-2 things]

What was surprising?

• [Anything unexpected]

What's the real takeaway?

• [The thing that actually matters, not the official summary]

What should we do differently next time?

• [For the next meeting with this group]

If No Action Items

Sometimes meetings are just discussions. That's fine.

"Sounds like this was more of a discussion than a decision meeting. If that's right, no action items needed. But if there WAS something that needs to happen, say it now before it disappears."

Output

User should get:

1. A clean list of commitments (WHO / WHAT / BY WHEN)
2. A draft follow-up email ready to send
3. Any orphaned items flagged
4. Confidence to send within 30 minutes

This skill is about capture, not note-taking. For better meeting notes during the meeting, that's a different workflow.