Meeting notes and action items template (free)
Last updated
This meeting notes and action items template puts the action register at the centre. Every action has a verb, one owner, a due date and a status, and the register carries forward from one meeting to the next, so the first item at every meeting is checking what was done. The notes themselves stay short.
Download it as a Word file, copy the plain-text version, or read the filled-in example of a weekly operations meeting with a running action log.
Word file (.docx), free and without signing up. Opens in Google Docs and Pages too.
What’s in the template
The minutes open with these details:
- Meeting
- Date
- Time
- Location (or video platform)
- Facilitator
- Notes taken by
- Present
- Apologies
- Previous meeting
Then the body follows the meeting in this order:
- 1. Review of open actions — Go through the register from last time. For each open action: done, in progress with a new date, or dropped with a reason.Actions closed: · Actions re-dated: · Actions dropped:
- 2. Agenda items — One block per item. Keep the notes to what was decided and what action came out of it.Item: · Notes: · Decision: · New actions (see register):
- 3. Decisions this meeting — Each decision on its own line, so they can be found without reading the notes.
- 4. New action items — Start each with a verb. One owner. A date, not "next week". Add to the register with the next number.Action: · Owner: · Due:
- 5. Parked items — Raised but not discussed. Say when they will be, or they are not parked, they are lost.
- 6. Next meeting — Date and time, and anything that must be ready beforehand.
- Action register — The running list, numbered across the year. Copy it into the next meeting's notes before the meeting.
At the end: action register and decisions, as tables you can keep across meetings.
The template
Download it as a Word file, or copy the text version into your own document.
Meeting Notes and Action Items Meeting: Date: Time: Location (or video platform): Facilitator: Notes taken by: Present: Apologies: Previous meeting: 1. Review of open actions [Go through the register from last time. For each open action: done, in progress with a new date, or dropped with a reason.] Actions closed: Actions re-dated: Actions dropped: 2. Agenda items [One block per item. Keep the notes to what was decided and what action came out of it.] Item: Notes: Decision: New actions (see register): 3. Decisions this meeting [Each decision on its own line, so they can be found without reading the notes.] 4. New action items [Start each with a verb. One owner. A date, not "next week". Add to the register with the next number.] Action: Owner: Due: 5. Parked items [Raised but not discussed. Say when they will be, or they are not parked, they are lost.] 6. Next meeting [Date and time, and anything that must be ready beforehand.] Action register [The running list, numbered across the year. Copy it into the next meeting's notes before the meeting.] Action register No. | Action | Owner | Raised | Due | Status Decisions No. | Decision | Date
What an action item needs
An action is a sentence someone can do. "Supplier contract" is a topic; "Send the revised supplier contract to legal" is an action. Each one needs the four fields below, and the register is only as useful as the weakest of them.
- Verb first: send, draft, book, decide, confirm. If you cannot find the verb, the action is not clear yet.
- One owner: a name, not a team. Two owners means nobody checks the date.
- A due date: a real date the owner agreed to in the meeting, not "ASAP" or "ongoing".
- A status: open, in progress, done, or dropped. Dropped is a legitimate status; silently deleting actions is not.
Running the register across meetings
Number actions across the year, not per meeting, so 2026-47 means something in March and in November. Open each meeting by walking the register: the owner says done, a new date, or drop. Re-dating is fine once; an action re-dated three times is either too big or nobody wants it, and the meeting should decide which.
Keep done actions in the register for one more meeting so people see them closed, then move them to an archive section or delete them. A register with 80 lines, 60 of them done, stops being read.
Keeping the notes short
The notes exist to explain the actions and decisions, not to replace being there. Two or three lines per agenda item is usually enough: what the question was, what was decided, and what action follows. If a topic needs more, it deserves its own document that the notes link to.
Common mistakes
- Actions buried in prose. If an action is only in the notes and not in the register, it will not be checked next week.
- Assigning actions to people who were not in the meeting without telling them. Add them, then tell them the same day.
- Mixing decisions and actions. A decision is done when it is made; an action is done when someone does it.
- Closing an action because the date passed. It is done when the work is done, or dropped with a reason.
- Starting a fresh register each meeting. The point is continuity.
Example: filled-in meeting notes with action items
What the template looks like once it’s been used. The organisation and people are made up.
Operations weekly, Northgate Logistics, week 42
Date: Wednesday 14 October 2026
Time: 9:00 am to 9:45 am
Location: Depot meeting room, Dev Patel by video
Facilitator: Dev Patel, Operations Manager
Notes taken by: Carla Mendes
Present: Dev Patel, Carla Mendes, Jonas Weber, Aisha Rahman, Ben Holloway
Apologies: None
Previous meeting: Wednesday 7 October 2026
1. Review of open actions
2026-38 (Jonas Weber, replace the dock 3 shutter motor): done, fitted on 9 October.
2026-39 (Aisha Rahman, agree new collection window with Pennant Foods): in progress; Pennant has proposed 6:00 to 8:00 am, Aisha confirming with the night shift. Re-dated to 21 October.
2026-40 (Ben Holloway, quote for a second forklift battery): done, quote circulated 12 October, discussed under item 2.
2026-36 (Dev Patel, review agency driver rates): re-dated for the second time to 28 October. Dev to bring a decision, not a further update.
2. Forklift battery quote
Ben Holloway presented two quotes: a replacement battery at 4,200 and a reconditioned unit at 2,600 with a 12-month warranty. The reconditioned unit would cover the afternoon shift during charging.
Decision: buy the reconditioned unit. Action 2026-41 raised.
3. Pennant Foods collection window
Covered under action 2026-39. If the night shift cannot cover 6:00 am, Aisha Rahman will propose 7:00 to 9:00 am instead. No decision needed this week.
4. November peak staffing
Carla Mendes reported that two of the four seasonal warehouse roles are filled. Jonas Weber asked for the remaining two to start by 9 November for training. Action 2026-42 raised.
5. Decisions this meeting
Buy the reconditioned forklift battery at 2,600 with 12-month warranty.
Seasonal starters must begin by 9 November.
6. Parked items
Vehicle tracking renewal (Ben Holloway): on the agenda for 21 October.
7. Next meeting
Wednesday 21 October 2026, 9:00 am. Dev Patel to have the agency rate decision ready for 28 October.
Action register
| No. | Decision | Outcome |
|---|---|---|
| 1 | Buy the reconditioned forklift battery, 2,600, 12-month warranty | 14 October 2026 |
| 2 | Seasonal starters to begin by 9 November 2026 | 14 October 2026 |
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | Order reconditioned forklift battery and confirm delivery date | Ben Holloway | 17 October 2026 |
| 2 | Fill remaining two seasonal warehouse roles with a start date no later than 9 November | Carla Mendes | 30 October 2026 |
| 3 | Confirm Pennant Foods collection window with the night shift | Aisha Rahman | 21 October 2026 |
| 4 | Bring a decision on agency driver rates | Dev Patel | 28 October 2026 |
Tips for meeting notes with action items
- Paste last week's register into the notes before the meeting starts, so reviewing it is the first thing on screen.
- Read each new action back to its owner before moving on: "Ben, order the battery and confirm delivery by Friday the 17th?" Get a yes.
- Keep the register in the notes document itself, not a separate tool, unless everyone in the meeting already uses that tool daily.
- Flag any action re-dated twice. Either break it up or drop it in the meeting.
- Send the notes with the register at the top. Owners should see their names without scrolling.
Related templates
- Meeting summary template — The short recap you send after a meeting: decisions, actions and open questions, written to be read in two minutes.
- Staff meeting minutes template — The regular all-staff meeting of an office, clinic or branch: updates, policy changes, schedules and recognition.
- Project meeting minutes template — The weekly status record: where each workstream stands, which milestones moved, what changed on the risk log and what was decided.
- Level 10 meeting template — The 90-minute EOS weekly leadership meeting, with its fixed agenda, to-do list and issues list laid out in order.
- All meeting minutes templates
Or let the notes write themselves
A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.
Questions
What is the difference between meeting notes and action items?
Notes record what was discussed and decided; action items record what someone has agreed to do afterwards, with an owner and a date. Notes are read once. Action items are checked at every following meeting until they are done, which is why they belong in a separate register rather than in the body of the notes.
How do you write an action item?
Start with a verb, name one owner, and give a date the owner agreed to. "Draft the Q4 staffing plan, Carla, 30 October" is complete. Add a number so it can be referred to later and a status so it can be closed. Keep the wording short enough to read in a table.
How do you track action items across meetings?
Keep one numbered register that is copied into each meeting's notes. Open every meeting by reviewing it: each owner says done, gives a new date, or asks to drop the action. Leave completed actions visible for one more meeting, then archive them. Numbering across the year, rather than per meeting, makes old actions easy to cite.
Who should take notes and track action items?
One named person per meeting, ideally not the facilitator, who has enough to do. In many teams the role rotates. Whoever takes the notes also owns the register between meetings: chasing dates is not their job, but making sure the register is current before the next meeting is.
Can AI meeting notes capture action items?
AI note tools generally pick out candidate actions from a conversation, and that list is a useful check against what you wrote down. They are less reliable at owners and dates, which are often implied rather than said, so confirm those in the meeting. If you record a meeting to do this, let attendees know.