# Meeting Notes and Action Items: Write Them So They Get Done

> How to turn meeting notes into action items with one owner, one date and a clear finish, plus examples, a simple log and how to keep client details safe.

Louvain, 2026-11-16. Source: https://louvain.ai/blog/meeting-notes-action-items

# Meeting Notes and Action Items: Write Them So They Get Done

![Geometric cards linked to a marked action](https://media.babylovegrowth.ai/blog-images/organization-67554/1794812008552_Geometric-cards-linked-to-a-marked-action.jpeg)

Good meeting notes record what was decided and who now owes what, by when. Everything else is supporting detail. The notes fail when actions sit in a document nobody reopens, or when they carry no owner and no date. The fix has two parts: a clear way of writing each action, and one place where commitments stay linked to their source and visible to the right people. This guide gives you both.

## TL;DR

- Keep three things apart in your notes: what was discussed, what was decided and what someone has agreed to do.
- Write every action with one named owner, a verb, a real date and a way to tell it is finished.
- Read each action back before the meeting ends, so the owner confirms it in the room.
- Send the actions the same day and open the next meeting with them.
- Keep client details out of general logs. Use a system where each person sees only what they are allowed to see.

## Table of Contents

- [Notes, decisions and actions are three different things](#notes-decisions-and-actions-are-three-different-things)
- [What meeting notes should capture](#what-meeting-notes-should-capture)
- [How to write one action item](#how-to-write-one-action-item)
- [Examples for different kinds of meeting](#examples-for-different-kinds-of-meeting)
- [A simple action log](#a-simple-action-log)
- [Why actions still go missing](#why-actions-still-go-missing)
- [Handling confidential details in notes and logs](#handling-confidential-details-in-notes-and-logs)
- [Where Louvain fits](#where-louvain-fits)
- [A checklist before you send the notes](#a-checklist-before-you-send-the-notes)
- [FAQ](#faq)
- [Sources](#sources)

## Notes, decisions and actions are three different things

Most messy notes mix three kinds of statement into one list. Separating them is the single biggest improvement you can make.

A discussion records what the group considered. A decision records what the people with authority agreed. An action is work that a named person has accepted in order to carry the decision forward. One UK consultancy's guide to action logs makes the same split, and adds that an item is only an action once [the person and the expected outcome are confirmed](https://www.kayco.net/info/action-log).

A short test helps. Take a line from your notes and ask what it is:

- "Sales were up on last quarter." That is information.
- "Consider a later launch date." That is an idea.
- "Launch on Monday." That is a decision.
- "Maya to update the schedule." That is an action.

This labelling approach comes from a UK guide to [writing minutes that clarify decisions and actions](https://collegeofmediaandpublishing.co.uk/how-to-write-meeting-minutes-that-clarify-decisions-and-actions/). It matters because a list that mixes all four makes it hard to know what anyone is actually expected to do.

A common trap is turning a suggestion into a commitment. "Perhaps we should change the form" is not "Redesign the form by Friday". If nobody agreed to the work, write it as an open question or as a proposed action awaiting an owner. Do not assign it by guesswork.

## What meeting notes should capture

You do not need a transcript. The UK Civil Service's own guidance says many meetings need no full notes, but action points should always be recorded and shared. For a recurring team meeting, a compact record is enough.

The NHS Humber guide to action and decision notes is a good model for small firms too. It says notes should state whether an action is required or a decision was taken. They should also show the lead's initials or job title, a target completion date and progress comments. The same guide says notes should be produced [within one week of the meeting](https://brand.humber.nhs.uk/wp-content/uploads/2023/09/Action-and-Decision-Notes-Guide.pdf). For most firms, within one working day is a better habit, because owners forget details fast.

The charity governance body Good Governance lists the core elements of minutes as [actions agreed, who will do each one and the deadline](https://www.good-governance.org.uk/assets/uploads/publication-documents/Covid100-revisited-minute-taking.pdf). Context for each action is useful extra information, not the main content.

In practice, a good record has four blocks:

1. **Decisions** made, each in one sentence.
2. **Actions**, each with an owner and a date.
3. **Open questions or blockers**, each with the person who will resolve it.
4. **Next check**: when and where these actions will be reviewed.

The same guidance on quality minutes says to summarise key points rather than transcribe. It also says to check that someone who was not in the room would understand the result. That second check is useful for partners who read the notes a week later with no memory of the call.

## How to write one action item

A usable action item has four parts:

- **Owner:** one named person.
- **Verb:** a concrete action such as send, draft, approve or book.
- **Date:** a real calendar date, not "soon" or "next week".
- **Done when:** the result that shows it is finished.

Put together, the pattern reads: "[Owner] will [verb] [specific thing] by [date], done when [result]."

Compare two versions of the same item.

Weak: "Look into the engagement letter."

Strong: "Priya will send the revised engagement letter to the client by Thursday 20 November. Done when the client has replied with a signed copy or comments."

The weak version has no owner, no end and no way to tell progress. The strong one can be checked by anyone.

### One owner, not a group

A task owned by everyone is owned by no one. If two people share the work, name one as the owner and the other as support. The owner is the person who answers when someone asks where it stands.

### Read it back in the room

Owners and dates are the details people forget or remember differently. So before the meeting closes, say each action aloud: "So Ari owns the security review, done by 7 November, and he posts the findings in the channel. Right?" This catches missing owners and unrealistic dates while everyone is still present.

If an owner is blank or a date is a guess, write "owner to be confirmed" or "date unknown". An honest blank is better than an invented commitment. It tells everyone the meeting has not finished assigning the work.

### Keep the row short

An action list should let an owner find their next step without reading an account of the whole conversation. Link to the source notes or the decision instead of copying paragraphs into the action row. Long rows bury the task and make progress updates hard to scan.

## Examples for different kinds of meeting

The pattern stays the same across meeting types. What changes is the kind of action you expect. These are illustrative examples, not real client records.

| Meeting | Weak action | Strong action |
|---|---|---|
| Client project review | Follow up on scope | Tom will email the client the scope change summary by Friday 21 November. Done when the client confirms in writing. |
| Partner meeting | Sort out the hiring plan | Helen will present two role descriptions for the audit senior post by 28 November. Done when partners approve one. |
| Sales pipeline call | Chase the proposal | Sam will call the prospect's finance lead on Monday to agree a decision date. Done when the date is recorded against the deal. |
| Property management review | Fix the boiler issue | Aisha will get two contractor quotes for the boiler at the Leeds block by Wednesday. Done when both are filed and sent to the managing agent. |
| Founder weekly | Improve onboarding | Jo will cut the signup form to five fields by Thursday. Done when the change is live. |

Notice what each strong action avoids. None says "look into", "explore" or "keep an eye on". Those phrases describe thinking, not work. If the honest next step is thinking, name the output: a one-page options note, a call with a named person, a quote.

## A simple action log

You do not need a complicated template. A four-column table is enough for most small teams: action, owner, due date and status. A UK writer on meeting minutes makes the same recommendation, and also suggests making "actions from last time" the [first item on every recurring agenda](https://www.itmanagement101.co.uk/a-template-for-meeting-minutes-agenda-for-recurring-meetings/). That habit turns the log from a record into a routine: mark what is done, then chase what is not.

Firms that want more detail can add fields. A UK action-log guide suggests context, expected outcome, evidence of completion and dependencies. It also says to mark items as "proposed" or "awaiting an owner" rather than assigning them by inference. The same guide is in the [action log template from Kay & Co.](https://www.kayco.net/info/action-log).

A workable weekly rhythm:

1. During the meeting, mark items with a letter: D for decision, A for action, Q for question, B for blocker.
2. Within the hour, turn the marks into plain sentences.
3. Read the actions back to the owners.
4. Send the record the same day.
5. Open the next meeting with the old actions, and carry over anything unfinished with a new date.

## Why actions still go missing

Teams that write good notes still lose actions. The cause is usually not the writing. It is where the notes live.

A note in a document does nothing on its own. Nobody is nudged to open it. It holds no place in anyone's priorities. When an item slips, no one is told. So the commitment lives in a file while the real work happens in email, chat and calendars.

Three patterns repeat in firms of 10 to 200 people:

- **The action sits in the notes, the reply sits in email.** Nobody can see that the client has already answered.
- **The owner changes in chat.** "I'll pass this to Dan" never reaches the log.
- **The date moves on a call.** The log still shows the old one.

The result is the status meeting: an hour of people reading out what they think they owe. Our guide on [seeing where every project stands without a status meeting](https://louvain.ai/blog/project-status-without-status-meetings) covers that side in more depth.

The practical answer is to keep commitments connected to the places where work happens: email, documents, meetings, chats and calendar. When a commitment is linked to its source, you can check it in seconds instead of asking around.

## Handling confidential details in notes and logs

For consultancies, law firms, accountancies and property managers, meeting notes often contain client names, fees, disputes or personal data. That raises two questions: who should see each note, and what happens when an AI tool reads it.

Start with proportion. One action-log guide advises recording only what is needed for coordination, using the organisation's approved location and access arrangements, and avoiding confidential meeting content or unnecessary personal information in a general log. Sensitive actions should go through a restricted reference instead, as the [action log guidance explains](https://www.kayco.net/info/action-log).

That works, but it relies on people remembering the rule every time. Two habits make it easier:

- Write the action without the sensitive detail, and point to the restricted source. "Priya to send revised engagement letter, see client file" tells the team enough.
- Check who can open the folder or channel where notes are kept. Wide access is the most common leak in small firms.

Firms that run on Microsoft Teams will find a practical overview in this [Teams governance guide for UK SMEs](https://abersecure.co.uk/blog/teams-governance), which covers who can see what in shared spaces.

The question gets sharper when you connect Claude or ChatGPT to company knowledge. An assistant that can read every note can repeat any of it to anyone who asks. The safe set-up is one where access is decided fact by fact, so each person and each AI agent sees only what they are allowed to see. That is the design principle behind Louvain, covered on our [security and data handling page](https://louvain.ai/security).

## Where Louvain fits

Louvain is permissioned company memory for growing teams. It connects your email, documents, meetings, chats and calendar, and turns them into checked facts, each cited to its source. Permissions are enforced on every individual fact. A partner, a junior and an AI agent each see only what they are cleared to see.

For meeting actions, that means you can track commitments and see what is owed. You can ask who agreed to what with a client and get an answer traced back to its source. Each morning you get a daily brief rather than a round of status calls. You can see how this works on the [Louvain meetings page](https://louvain.ai/meetings).

![Where Louvain fits](https://media.babylovegrowth.ai/blog-images/organization-67554/1794812057787_Where-Louvain-fits.jpeg)

Louvain also works inside Claude, ChatGPT and other AI tools as a connector. Your team can ask those tools about clients, deals and decisions, and they only get what each person may see.

The Team plan costs £20 per person per month and the Business plan costs £40 per person per month. Enterprise is priced on request. See the [Louvain pricing page](https://louvain.ai/pricing) for what each plan includes.

![Louvain](https://media.babylovegrowth.ai/blog-images/organization-67554/1794490655900_louvain.jpg)

Louvain is used by consultancies, accountancies, property managers, startups and commercial teams in the UK and Europe. If you want the version for your sector, start with the pages for [professional services](https://louvain.ai/solutions/professional-services), [accounting](https://louvain.ai/solutions/accounting), [startups](https://louvain.ai/solutions/startups) or [commercial teams](https://louvain.ai/solutions/commercial-teams).

## A checklist before you send the notes

Run this list over every set of notes before they leave your hands:

- Is each line labelled as information, idea, decision or action?
- Does every action have one owner and one real date?
- Does every action say what "done" looks like?
- Were the actions read back in the meeting?
- Are unknowns marked as unknown, not guessed?
- Is client-sensitive detail left out of the general log?
- Does the next agenda start with these actions?

If you can answer yes to all seven, your notes will survive the week.

## FAQ

### What is the difference between meeting notes and action items?

Meeting notes record what was discussed and decided. Action items are the specific tasks that follow, each with an owner and a date. Keep them in separate sections so that nobody has to read the whole discussion to find their next step.

### How soon should I send meeting notes and actions?

Send actions the same day if you can. The NHS Humber guidance sets a maximum of one week for action and decision notes, but a shorter gap works better because owners and dates are still fresh. Ask owners to confirm or update their items before the next meeting.

### Who should own an action item?

One named person, never a team or "everyone". If several people are involved, pick the one who will answer when someone asks where it stands. If nobody has accepted the work, mark it as awaiting an owner instead of assigning it.

### Do I need full minutes for every meeting?

No. For routine meetings, a short record of decisions, actions, open questions and the next check is enough. Fuller minutes are worth keeping where a serious concern is raised, as the NHS Humber guide notes for matters such as staff welfare or patient safety.

### Can I let an AI tool read my meeting notes?

Yes, if access is controlled. The tool should only see what the person asking is allowed to see, and answers should point back to their source. Check this before you roll an assistant out to a team that handles confidential client data.

## Sources

- [Action log: a practical template for meeting follow-up](https://www.kayco.net/info/action-log)
- [How to Write Meeting Minutes That Clarify Decisions and Actions](https://collegeofmediaandpublishing.co.uk/how-to-write-meeting-minutes-that-clarify-decisions-and-actions/)
- [A Guide to Producing Action/Decision Notes](https://brand.humber.nhs.uk/wp-content/uploads/2023/09/Action-and-Decision-Notes-Guide.pdf)
- [Covid100 revisited: minute taking, Good Governance](https://www.good-governance.org.uk/assets/uploads/publication-documents/Covid100-revisited-minute-taking.pdf)
- [Meeting Minutes Template with Action Items](https://www.itmanagement101.co.uk/a-template-for-meeting-minutes-agenda-for-recurring-meetings/)
- [Teams Governance for UK SMEs: A Practical Guide](https://abersecure.co.uk/blog/teams-governance)

## Recommended

- [How to See Where Every Project Stands Without a Status Meeting](https://louvain.ai/blog/project-status-without-status-meetings)
- [Meetings](https://louvain.ai/meetings)
