How to record action items in meeting minutes (and get them done)

Use one row for one commitment

“Discuss the launch plan” is a topic. “Approve the launch email” is still hard to track because it says neither who will approve it nor when. An action item should tell the owner what finished work looks like and when the group expects it.

Put the owner first, then the deliverable and deadline. This is a fictional example:

Ananya Rao will send Finance the signed vendor quote as a PDF by
29 October 2026, 3:00 pm IST. Status: Open.
Source: launch review, 25 October 2026, agenda item 2.

A verb such as send or publish gives the team something to verify. “Look into the quote” leaves the result undefined. If the task is research, name the output: “Compare the two quotes in the procurement document and recommend one.”

Choose one owner, even when several people will help. A team name can tell readers where the work belongs, but it cannot answer who will report back. Add collaborators in a separate field if they matter.

Copy this meeting-minutes action tracker

Copy the block into Google Docs or Word as text, or recreate its columns as a table. Keep a shared spreadsheet if you need to sort by deadline. This is an original, fictional worked example of an action record, not a complete statutory minutes form. Replace the names and commitments before use.

EXAMPLE WORKING MoM: Weekly launch review
DATE AND TIME: 25 October 2026, 11:00 am IST
ATTENDEES: Ananya Rao, Ravi Menon, Meera Shah
NOTES BY / TRACKER KEPT BY: Ravi Menon
DECISION D-01: Use the revised launch date of 2 November 2026.
ACTION RECORD AS AT: 25 October 2026, 11:30 am IST

| ID | Owner | Action and checkable deliverable | Due date and time | Status | Update / source / evidence |
|---|---|---|---|---|---|
| LR-01 | Ananya Rao | Send Finance the signed vendor quote as a PDF | 29 Oct 2026, 3:00 pm IST | Open | Owner and date confirmed; agenda item 2 |
| LR-02 | Ravi Menon | Post the revised support roster in the launch document | 29 Oct 2026, 12:00 pm IST | In progress | Draft started; implements D-01 |
| LR-03 | Meera Shah | Review version 3 of the launch email; record approval or requested edits in the document | 30 Oct 2026, 12:00 pm IST | Blocked | Waiting for Ananya's signed quote in LR-01; agenda item 3 |
| LR-04 | Ananya Rao | Send the printer a request for a revised delivery quote | Not agreed | Open | Owner accepted; Ravi to ask Ananya for a date on 26 Oct |

STATUS KEY: Open = accepted, not started; In progress = work started; Blocked = a named dependency prevents progress; Done = deliverable checked; Dropped = the group explicitly cancelled it.
OVERDUE: Flag an unfinished item whose agreed due date has passed; keep its work status too.
NEXT REVIEW: 1 November 2026

Use this status key as a team convention. “Done” needs evidence, such as the sent email or a link to the finished document. A missing deadline is a gap to resolve; it does not by itself mean work is blocked. (A blocked item can also be overdue.) Keep a separate list of proposed tasks whose owners have not accepted them.

For online meetings, add a transcript reference when one exists. Microsoft documents transcript downloads for Teams organisers and co-organisers by default; access depends on IT policy. Google says Meet transcripts are saved in the organiser's Drive; availability depends on edition and settings. [11][12] Use a meeting date and agenda item if there is no recording. Check that intended readers can open any source link.

How to write an action someone can check

Before you add a row:

1. Confirm who accepted the work. Use a person's name. If nobody accepted it, mark it “Owner not agreed” in the proposed-task list and ask the meeting lead to resolve ownership.
2. Name what they will hand over or change. Use a file or another visible outcome. For a review task, allow for approval or requested changes; don't imply the reviewer has already approved it.
3. Record the agreed calendar date. Include a time and time zone when timing matters. “Next Friday” becomes ambiguous when the notes travel; a date invented by the note taker creates a different problem.
4. Agree how to check completion. “Ask the supplier for a quote” is done when the request is sent. “Obtain a quote” needs the supplier's reply. Choose the one the owner actually accepted.

Don't turn every idea into a task. “We could ask the supplier for a discount” is a suggestion. It becomes an action only after someone accepts it: “Ravi will ask the supplier for a revised quote by 29 October.” If a person says “I can look at that,” ask whether they are taking it on and when they can report back. That small read-back is cheaper than debating later whether the room made a promise.

Keep decisions separate from the work they cause. “The team chose 2 November” is a decision; “Ravi will update the roster” is its action. Link them, as D-01 and LR-02 do above. An owner's acceptance of a task also does not establish that a formal resolution passed; record that through your organisation's required procedure.

How to track actions between meetings

Keep the meeting record and the current work state distinguishable. For an informal team, a dated action snapshot and a separate live table can be enough. A spreadsheet or project tool helps when several meetings feed the same queue. Pick one tracker, name its keeper, and give each action a stable ID. Copying the same task into successive lists without an ID makes it hard to tell whether it is new or still unfinished.

Use a small routine:

1. Share the agreed action list after the meeting. Ask owners to flag errors promptly. Follow your organisation's process for approving formal minutes; task confirmation is a separate check.
2. Ask owners to update progress between meetings, with a dated note and evidence when they finish. Let the tracker keeper handle missing updates. If a dependency threatens the deadline, raise it with the person who can unblock it before the due date.
3. Before the next meeting, filter for unfinished items. Flag overdue rows using their agreed dates. Keep “Not agreed” deadlines visible too; they need a decision rather than a guessed date.
4. Review exceptions at the meeting. Agree whether to keep the plan, reassign the work, change its scope or cancel it. Record any new deadline and who agreed to it. Read new actions back before people leave.

An action tracker is like a parcel register: the same parcel keeps its tracking number when delivery is delayed. Giving an overdue task a new row and a fresh date each week can make a growing backlog look like new work. Keep the ID and show what changed.

For example, this fictional update carries LR-01 forward:

LR-01 | Ananya Rao | Send Finance the signed vendor quote as a PDF
Original due: 29 Oct 2026, 3:00 pm IST
Status at 1 Nov review: Blocked; original deadline missed
Reason: Supplier has not returned the signed quote.
Revised due: 3 Nov 2026, 3:00 pm IST; agreed by Ananya and meeting lead Ravi on 1 Nov.
Next step: Ananya to chase the supplier on 2 Nov by 10:00 am IST.
Dependency: LR-03 review deadline also needs to be reconsidered.

Keep that update in the live tracker and reference LR-01 in the next meeting's record. Don't silently rewrite the earlier meeting's account of what was agreed. Under Robert's Rules, corrections to already approved minutes follow a formal amendment process; FAQ 16 explains it. [7]

What AI note takers can extract

AI note takers' docs describe ways to extract candidate tasks. This table reports what each maker says; we haven't tested extraction accuracy yet.

“Maybe I can send that over” leaves acceptance unresolved. An extracted deadline might belong to a different task; a speaker label might be wrong. The cited docs establish no shared accuracy rate. Fathom lists Auto-Generate Action Items under Premium features, for Premium and Team plans only. [5] Granola's MCP gives free (Basic) accounts personal and public notes from the last 30 days. [6] Check your own plan and settings before you adopt a workflow. (A documented control is evidence of what the maker promises, not proof that a particular extraction is right.)

Check each candidate against the surrounding conversation, including later changes or cancellations. Ask the named person to resolve missing ownership or timing; leave unknown fields as “Not agreed”. Have a person confirm the final row before sending it into a task system or to a client. A source link helps you audit an extraction; it does not create agreement.

What meeting rules apply?

The format here is a recommendation for tracking work. Under Robert's Rules, minutes record the actions taken at a meeting, and a summary of debate is improper; that rule is explained in official FAQ 15. The site's own caution says applicable law, bylaws and special rules can override its default rules. Don't apply that rule to every kind of minutes. [7]

For an Indian company meeting, ask the company secretary to check the applicable Companies Act provisions and secretarial standards. For an RWA meeting or housing society AGM, identify the law under which the body is registered and check the relevant state rules and registered bylaws with its secretary. Use the governing sources to establish quorum, required content, approval, signing and retention; this action tracker does not establish any of them. This is general information, not legal advice.

About this page

Candor is being built as personal voice intelligence for everyone. You can join the Candor waitlist at candor.inc. Candor's own documentation is at candor.inc/docs.

Candor's docs on this page's topic: What the summary includes.

Candor's dictation and meeting notes are free. [9]

Last checked: 4 November 2026. Report an error to support@candor.inc.