Run AI meeting notes on one real meeting, check the summary, and compare the time with your usual write-up.
[[big 23 min | a client call, from its end to a checked summary sent. By hand: 40.]]
The other 20 went on checking it. Even Microsoft says to check AI output before you send it to anyone.
---
First, your baseline: how long notes take you now, from the end of the meeting to sending.
?> Which meeting will you use? An internal project meeting => Best for a first go. You'd write these notes anyway, so the comparison is fair. A client call => Only if your company's rules allow it and the client agrees. Cut anything said off the record before you send.
---
[[checklist Before you send the invite, how many are true? | Your company approves this tool for this meeting | The invite says you'll record | The tool handles the meeting's language (Meet's notes skip Chinese, Malay and Tamil) | No bot joins your other meetings by itself (Fireflies does, by default) | 0-2 => Not this meeting yet. Fix the gaps or pick another. | 3 => Close the last gap before the invite goes out. | 4 => Ready. Send the invite.]]
---
[[chat You: Quick note, I'm recording this for the notes. Okay with everyone? | Client: Not today, if that's alright. | You: Sure, I'll take them by hand.]]
Then use a different meeting for this.
---
[[order Put the follow-up in order | Take light notes on decisions and actions | Start the timer when the meeting ends | Run your summary prompt on the transcript | Check each decision, owner and date against its timestamp and your notes | Send it, then stop the timer]]
---
[[doc email | Client review | Agreed: two workshops next month | Venue shortlist: you, Friday (1) | First workshop: 6 March (2) | Agreed: 20 per session (3) | 1: The client took this one. | 2: They said "early next month". | 3: Only suggested. They wanted 15. | find 3]]
---
| Said | Should say | Type | |---|---|---| | First workshop: 6 March | Early next month | Invented deadline | | Agreed: 20 per session | 15 or 20, still open | Suggestion turned into decision | | Name split in two | One word | Transcription error |
Other types: wrong owner, dropped disagreement, something missing.
---
[[flow Timer on | Prompt 2, wait 1 | Check 12, fix 6, read 2 | Sent: 23 min]]
That's 17 minutes under the 40-minute baseline (40 - 23). If your first try is slower than your baseline, log it anyway.
---
?? Next day, a colleague replies: "I said end of month, not end of week." What goes on your list? Nothing, since the thread now has the right date Nothing, it came after you'd already sent + The fix, marked as found by someone else => Your check missed it, so it belongs on the list. Those are the ones to look for next time.
---
?# Your note with the summary Hi all, the decisions and actions from {the meeting} are below. Still open: {what wasn't decided}. If I've got an owner or a date wrong, reply by {day} and I'll fix it.
After your next recorded meeting, send the checked summary with the note above, then write the minutes it took beside your baseline.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).