Turn a recording into notes, decisions and owners

Meeting notes have a specific failure mode. Someone takes them, everyone agrees they were useful, and then nothing in the notes becomes work that anyone is responsible for. Three weeks later the same decision gets made again.

This playbook is about the second half of that problem. Getting a transcript is easy and not very valuable. Getting owned, dated tasks out of it is the part that changes anything.

Upload the recording

Open Meetings and add a recording. Audio or video both work, and most common formats are accepted up to 500MB.

It is transcribed and diarized, which means the speakers are separated from each other. Worth knowing: separating voices is not the same as identifying them, so you will get "Speaker 1" and "Speaker 2" rather than names until you assign them.

Name the speakers before you do anything else

Open the transcript and assign names to the speakers.

This takes about twenty seconds and it changes the quality of everything downstream. An action item that says "Speaker 2 will send the pricing" cannot become a task with an owner. One that says "Priya will send the pricing" can.

Ask for the summary

With the transcript in place, ask the employee to write it up.

Read the transcript of this meeting and write it up as:

1. What was decided, and by whom.
2. What was explicitly left open, and what has to happen before it
   can be decided.
3. Anything someone committed to doing, with who committed to it.

Do not include discussion that did not lead anywhere. If a decision
was implied but never actually stated, say that it was implied rather
than recording it as decided.

The last sentence is the one that matters. Meetings are full of things that felt agreed and were never said out loud. A summary that quietly promotes those to decisions is worse than no summary, because now there is a document people will point at.

Review the proposed action items

The employee proposes action items rather than creating them. They appear on the meeting page for you to accept, edit or reject.

Do not skip this. The proposals are usually good and occasionally confidently wrong, and the whole point of an approval step is that the cost of a bad task landing in someone's queue is higher than the cost of ten seconds of reading.

Accepting one turns it into a real task, with an owner and a due date, tracked alongside everything else.

Make it happen without you

Once the shape works, stop doing it by hand. A scheduled job can watch for new meetings and run this same treatment on each one, so the summary is waiting for you rather than being something you have to remember to request.

What good looks like

The test is not whether the summary reads well. It is whether, two weeks later, the things people committed to in that room are visible somewhere other than the transcript.

If your action items keep coming back vague, the honest diagnosis is usually that the meeting was vague. A transcript is a fairly unforgiving mirror.

Also covers

Turning every action item into a tracked task with a due date. Accepting a proposal above does exactly this: it becomes a real task, with an owner and a date, in the same list as everything else your team is doing.

The part worth being deliberate about is the date. Proposals carry a due hint taken from what was said in the room — "by Friday", "before the next review" — and those are often vaguer than a date field wants.

For each action item, set the due date from what was actually said. If the
transcript only implies a timeframe, set the date you think was meant and
note in the task that it was inferred.

If nothing was said about timing at all, leave the due date empty rather
than inventing one. An undated task is honest; a task due next Tuesday that
nobody agreed to is a small fiction that somebody will be measured against.

An undated task is easy to spot and chase. A confidently wrong date looks settled, and the person who owns it finds out they are late for a deadline they never accepted.