Pulling out action items, owners and due dates

An action item needs three things: what's to be done, who's doing it, and by when. AI summaries often catch the first and slip on the other two. Your job is to check all three.

What you need

• The transcript, not only the summary.
• The attendee list with the full names people use at work.
• A place where tasks live after the meeting, such as a shared task list, a spreadsheet or your project tool.
• An agreed rule for dates, such as "write the day and date, never just 'Friday'".
• Ten minutes within a day of the meeting, while people still remember it.

Why tasks go wrong

Three things go wrong most often.

The owner is wrong. Tools that label speakers rely on diarisation. One reference says diarisation can be combined with speaker recognition systems to provide the speaker’s true identity¹. How a given tool assigns names varies. If the labels swap, a task lands on the wrong person. The summary then reads smoothly, and nobody spots the problem.

The task was never agreed. Someone says "we should update the website." The summary writes "Sam to update the website." Nobody asked Sam. One reference notes that chatbot-style tools can produce believable but false content². An owner nobody agreed to would be one such error.

The date is vague. "Next week" or "end of the month" means different things on different days. A transcript doesn't carry the meeting date inside each sentence.

How to pull them out

• Ask the tool for actions only, as a list with "task, owner, due date" columns. Don't ask for a story.
• Mark anything the tool couldn't fill in. A blank is better than a guess.
• Open the transcript and search for each task by a keyword.
• Read the sentences around it. Did someone clearly take it on, or did they just mention it?
• Write the date in full, based on the meeting date.
• Send the list to the owners and ask each to reply yes or no.

A format that holds up

A small table works better than prose:

The last column isn't decoration. It lets a reader jump back to the original words if there's an argument later. The second row shows an honest blank, which is more useful than a tidy guess.

This table is an example layout, with made-up names and dates.

Tell people what's being tracked

People expect the notes to match what happened. If the tool assigns tasks on its own, say so. Then attendees can correct it on the spot, rather than finding a task with their name on it in a surprise email a day later.

Decisions and actions are different

A decision is something the group settled. An action is something one person now has to do. They often come together, but not always. The minutes reference says the main job of minutes is to record the decisions made, so all official decisions must be included³. Tasks that follow from them belong beside them.

Even a short note shows the style. The same source gives the example of a routine motion noted simply as "moved by Ann and passed"³. That's about the right level of detail for a decision line. The action then gets its own row.

Say it in the room

You can help the tool. At the end of a meeting, read the actions back out loud. For example, "To confirm, Priya sends the quote by Friday. Nobody has the venue yet." Now the transcript holds a clean statement. The room also gets a chance to say "that's not right."

To shape the whole record, read about writing the minutes. Cleaner names and dates start with the pre-meeting setup.