Meeting Action Items Template:
Free CSV & Worked Example

01 / START HERE

Copy the meeting action items template

Use one row per task. The copy button uses tabs between columns: paste into cell A1 of a blank spreadsheet. If your spreadsheet puts everything into one column, import the CSV and select a comma separator. Replace the placeholders after pasting.

The CSV contains the same headers and three placeholder rows. It has no formulas, macros or automatic reminders. Your working copy lives wherever you save it; this page does not save task updates.

02 / SIX USEFUL FIELDS

What belongs in an action item?

To move this tracker into actual sales records, use the CRM task handoff example. It separates the customer’s commitment from the internal person tracking it.

Begin the task with a verb and describe an observable result. “Send the revised homepage wireframe” gives the owner something specific to deliver. “Website” is too broad to check.

• ID: keep a stable reference, such as A1, when a task carries over to another meeting.
• Action: include the actual deliverable and any constraint that changes its meaning. Checking whether an integration works is different from installing it.
• Owner: name the person who accepted responsibility. If that was not agreed, write “owner to confirm” and resolve it with the participants.
• Due date: use the final agreed date. Include a time zone when a specific time matters. An absent deadline stays “date to confirm”.
• Status: use a small shared set, such as Not started, In progress, Blocked and Done. Use “status to confirm” when you have no update.
• Source / notes: record the meeting date, a permitted transcript reference, dependencies and changes to the agreement. Restrict sensitive source material to the intended audience.

Owner, deadline and status fields also appear in Smartsheet’s action-item templates and Miro’s meeting action items template. We include a source column because checking the original conversation helped us resolve contradictions in our own test.

03 / A WORKED EXAMPLE

Eight action items from one client meeting

Our fictional scenario has Emma working with client Liam on a booking website. The conversation is set on September 7, 2026; we ran the synthetic test on September 6. The dates below belong to that scenario. We reconstructed these rows from the script and answer key, rather than copying the AI task list unchanged.

Completion status is unknown for every row. The test records commitments, not subsequent work. The example CSV therefore uses “Status to confirm” throughout.

Keep decisions and open questions separate

The October 8 launch date is a confirmed project decision. Whether to include a Spanish version remains an open question with no agreed owner or deadline. Neither needs to become an invented task such as “Liam delivers Spanish copy by October 8”. Record the decision and question alongside the tracker, then add a task only when someone agrees to do the work.

04 / WHY WE CHECK THE SOURCE

A plausible task can still have the wrong owner

The first Fireflies action list put subscription-plan confirmation under Emma. Our script assigned it to Liam, due September 15. A neat table would not have fixed that error by itself: we needed to check who actually accepted the task.

The same source also changed the copy deadline from September 14 to September 16. Keep the final agreement in the Due date column and preserve the replaced date in notes if it helps explain the change. Do not leave both dates looking equally current.

These are specific findings from a small synthetic pilot. Our Fireflies AI review shows the original notes and action items, plus a separate second recording and the limits of that comparison. This guide does not add another product test.

05 / AFTER THE MEETING

Keep the action tracker useful next week

1. Confirm the initial rows. Ask participants to check their own actions, dates and dependencies. Resolve “owner to confirm” before treating a task as assigned.
2. Update the existing row. Carry A1 into the next meeting with the same ID. Add the update date and reason if the deadline changes; keep the original commitment visible in notes.
3. Describe the blocker. “Blocked: waiting for approved logo” is more useful than changing a missed deadline without explanation. Identify the next decision or dependency.
4. Close with evidence. Mark a task Done when its agreed deliverable has been confirmed. Add the completion date and a suitable link or note.

For the client-facing message, use our copyable meeting follow-up email. The email communicates the agreed next steps; the tracker keeps their later status in one place. Check the audience before including internal notes or links.