Use cases · Nº 24 · 3 min read

Use Case: Meeting Recording In, Action List Out

The value of a meeting is what happens after it. How to turn recordings into decisions, owners, deadlines, and sent follow ups.

Meetings do not fail in the room. They fail in the forty eight hours afterwards, when the decisions everyone nodded at dissolve because nobody wrote them down, or the one person taking notes missed the bit that mattered to them. The fix used to be discipline. Now it is a recording and two minutes of AI.

First, the consent bit

Get consent before recording. Recording laws in Australia differ by state, and the details are beyond a blog article, but you do not need a law degree to adopt the policy that is both safest and best for relationships everywhere: tell people, every time. "I'm going to record this so I can be present instead of scribbling, and I'll send you the summary after." In several years of asking, I can count the objections on one hand, and the promised summary is usually received as a gift. When someone does object, do not record, take notes, the relationship outranks the workflow.

The bar is higher than a summary

Transcription is solved, plenty of tools do it, and a summary is table stakes. The valuable extraction is sharper than a summary. What I actually ask for, from any transcript:

  1. Decisions made, stated plainly, with who made them. Not topics discussed, decisions
  2. Actions, each with an owner and a date, and flag any action that left the room with neither, because those are the ones already failing
  3. Open questions, the things raised and parked, which are next meeting's agenda writing itself
  4. Risks and wobbles, anything that sounded like hesitation, concern, or a commitment made too quickly
  5. The follow up email, drafted, thanking, confirming the decisions and actions, in my tone, ready to send within the hour, because a follow up sent while the meeting is warm has ten times the force of Friday's

Paste a transcript into Claude with that list and you will never accept a plain summary again. Better, put those five points into a Meetings Project as standing instructions, drop transcripts in as they happen, and the format becomes automatic.

Client meetings, the quiet superpower

For sales and client conversations the same transcript carries extra freight. What did they say they cared about, in their own words? What objections surfaced? What did we promise? Proposals written from the transcript quote the client's own priorities back to them, which is why this article and the quoting article are best friends. And before the next meeting with the same client, thirty seconds of "brief me from our last conversation" makes you the best prepared person in the room, which clients read, accurately, as care.

Internal meetings, the accountability loop

Internally, the compounding move is the loop: this week's action list becomes the top of next week's agenda, automatically. Done, not done, blocked. Teams that run this loop have a different texture within a month, not because anyone got more disciplined, but because forgetting stopped being possible. The meeting notes stopped being a record and became a machine.

The deeper win across all of it is attention. The person scribbling notes is only half in the room. Recording plus extraction means everyone gets to actually listen, and the listening is where the judgement, the relationship, and the catch of the stray remark all live. The machine takes the stenography. The humans keep the conversation, which is the whole thesis of this series in one meeting room.

Image coming soon

From raw transcript to decisions, owners, and a drafted follow up

Next: the use case that feels most like magic the first time, pointing a camera at paper and getting data back.