Be in the meeting, not taking minutes.

What a good meeting note actually contains

Almost nobody rereads a full transcript, and almost everybody rereads a decision list. A meeting note earns its place when it answers three questions without being read end to end: what did we decide, who is doing what, and what is still open.

The transcript is the evidence layer underneath that — it matters when a decision is disputed a month later, and it is close to worthless as a daily artifact. Keeping both, a short structured summary on top and the full text underneath, is what makes the note survive a busy week.

• Decisions, with enough context to be understood out of the room
• Action items with an owner and, where it exists, a date
• Open questions, so the next meeting has a starting point
• The full transcript, kept but not read by default

Recording responsibly

Recording a conversation carries legal obligations that differ by country and by state, and social obligations that are the same everywhere. Say that you are recording, say what the recording is for, and stop if someone objects. A meeting where one participant is uncomfortable produces worse information than one with no recording at all, so consent is a quality question as much as a compliance one.

Why the summary should stay next to the source

Summaries in one tool and recordings in another is how organizations end up with decisions nobody can trace. When the write-up lives in the same note as the transcript that produced it, checking a claim is a scroll rather than a search across systems.

It also makes correction cheap. If the model misattributed a commitment, you fix it in the note that everyone reads, and the corrected version is the one that circulates.