Turn Raw Meeting Notes Into Action Items

Most meetings end with everyone vaguely agreeing that things need to happen and nobody entirely sure who is doing which thing by when. The notes are usually a mix of fragments, timestamps, half-sentences, and asides that made sense in the room but read like noise an hour later.

Cowork can take that pile and produce something usable: a decisions summary, a clean action list, owners, dates. The processing takes about thirty seconds. The part that takes time is making sure you have captured the right owners and dates, because that still requires a human who was in the room.

Getting the Input Ready

The input file can be almost anything:

• Your own typed notes, even if they are fragmentary
• A Zoom or Teams transcript export (the auto-generated ones with speaker labels)
• A Google Doc export saved as .docx or .txt
• A voice-memo transcription

Drop the file in your Cowork folder. One file per meeting works cleanest. If you have notes from multiple meetings and want to process them together, that works too, but the output will be one combined document, which can get cluttered.

One thing worth doing before you run the prompt: scan the notes quickly for any shorthand or internal abbreviations. If your notes say “ping JS about Q3 deck,” Cowork will probably figure out that JS is a person but may not know their full name. You can either expand the abbreviation before running, or let Cowork flag it as TBD and fill it in yourself.

The Prompt

With the notes file in the folder:

Read the meeting notes or transcript file in this folder. Write a clean summary of what was decided (not everything that was said, just the decisions and key context). Then extract every action item mentioned. For each action item, identify: the task, the person responsible (if named), and the due date (if mentioned). If a due date or owner is not mentioned, mark it as TBD. Format the output as a Markdown file called meeting-summary.md with two sections: Decisions and Action Items. Under Action Items, use a table with columns: Task, Owner, Due Date, Notes.

The key instruction is “decisions, not everything that was said.” Without that, Cowork will try to summarize every topic discussed, and the summary becomes nearly as long as the original notes.

What the Output Looks Like

The meeting-summary.md file will have two sections.

The Decisions section is a short bulleted list of things the group actually resolved. Not “we discussed the timeline,” but “the timeline is Q3 launch with a soft deadline of August 15.” If nothing was decided on a topic, it does not appear here.

The Action Items section is a table. A typical row looks like:

Task	Owner	Due Date	Notes
Draft the onboarding email sequence	Sarah	June 27	Needs legal review before send
Pull Q2 retention numbers from the dashboard	TBD	TBD	Mentioned in passing, unclear if assigned

The Notes column is where Cowork puts context from the transcript that did not fit cleanly into the other columns. Pay attention to rows where both Owner and Due Date are TBD. Those are the action items most likely to fall through the cracks.

The Fiddly Part: Verifying Ownership

This is the step you cannot skip. Cowork reads what is in the notes, not what was actually agreed in the room. If someone’s name is mentioned near a task but they were not actually assigned to it, Cowork may still mark them as the owner. If a commitment was made verbally and nobody typed it down, it will not appear in the output at all.

Read through the Action Items table before you share it. For any row where you are not sure about ownership, go back to the original transcript and check. This takes maybe five minutes for a standard one-hour meeting and is the most valuable five minutes of the whole workflow.

Pushing Actions Into a Task Doc

If your team tracks work in a shared task document (a simple .md file, a to-do list, anything text-based that lives in the same folder), you can extend the prompt:

Add this line to the end: “Also append each action item to the file called open-tasks.md in this folder, preserving any tasks already in that file.”

Cowork will read the existing task list, add the new items, and save the file. This is the simplest possible version of automatic task tracking, and it works well if your team is already disciplined about keeping that one file current.

For more structured task systems (Notion, Linear, Asana), you need the relevant connector. With the connector active, you can swap the last instruction to “create a task in Linear for each action item with the owner as the assignee and the due date as the deadline.” The connector handles the API call; you just review the created tasks and adjust anything that looks off.

When the Notes Are Really Messy

Some meetings produce notes that are essentially incomprehensible to anyone who was not there. Stream-of-consciousness notes, notes full of inside references, notes taken on a phone with autocorrect running wild. Cowork handles these better than you might expect because it is reading for meaning, not format. But the less structure the input has, the more TBDs you will see in the output.

For very messy notes, run the prompt once, look at the TBDs, then send a follow-up prompt: “For the TBD items in the Action Items table, look for any context in the notes that hints at an owner or a timeline, and update the table if you find anything.” This second pass usually resolves a few of the ambiguous rows.