Short answer first: good meeting notes contain four things. Decisions, tasks with a named owner, a date for each task, and the questions you did not settle. Write them so that someone who was not there can follow what was decided, keep the detail proportionate to the meeting and circulate them promptly after any required checks. The template below has the four headings and a filled-in example. A task is only written properly when it names a person and a date, so "Sarah calls the supplier by Wednesday" counts and "contact supplier" does not.
When a meeting ends without clear actions, the discussion can be hard to use afterwards. A 2017 Harvard Business Review article put executives at nearly 23 hours a week in meetings. In Microsoft's Work Trend Index from 2023, 55 per cent of 31,000 full-time employed or self-employed workers said the next steps at the end of a meeting are unclear. A clear record can help make the next action visible; the time needed depends on the meeting.
Why do most meeting notes fail?
They fail in one of two directions. Some are far too long: someone writes down nearly everything that is said, and the result is three pages that nobody opens. Others are far too thin: three loose words that made sense in the room and mean nothing a week later.
Both miss the purpose. Notes are not there to reproduce the conversation. They are there to hold what the meeting produced, so that it still exists when people have gone back to their desks. When they do not, the same question comes back. Atlassian's State of Teams 2024 found that in organisations with poor meeting cultures, people spend 50 per cent more time in unnecessary meetings than on their high-priority work.
What do good meeting notes contain?
For a routine working meeting, begin with four things to capture.
- Decisions. What was decided, in one sentence each. Not what was discussed.
- Tasks. What has to be done, and who owns it. A task without an owner belongs to nobody.
- Dates. When each task is due. "Soon" is not a date.
- Open questions. What was not settled, and what comes back next time.
People who write minutes as part of their job say the same. Universities run on committees, and their guides are blunt. Loughborough tells its secretaries that minutes are not a verbatim record, and to concentrate on conclusions, decisions, actions and who is responsible for carrying them out. Robert's Rules, a widely used manual of meeting procedure, describes minutes under its rules as a record of actions rather than discussion. Other bodies may require reasons or a summary of issues, so follow the applicable procedure.
The University of Bath adds the test that settles most doubts: write so that someone who was not at the meeting can follow the decisions that were made. Read your notes as the colleague who was ill that day. If that person would have to ask what a line means, the line is not finished.
What does a template for meeting notes look like?
Copy this into whatever you write in. It works for a team meeting, a project group and a meeting with a client.
Meeting: [topic]
Date: [date]
Attendees: [names]
DECISIONS
- [what was decided]
TASKS
- [task], owner: [name], due: [date]
- [task], owner: [name], due: [date]
OPEN QUESTIONS
- [what still has to be settled]
NEXT MEETING: [date, or "not planned"]
The template filled in
This fictional example shows the template after a product-planning meeting.
Meeting: Scope of the spring release
Date: 12 March
Attendees: Sarah, Tom, Priya, Dan
DECISIONS
- Export ships in the spring release. Sharing moves to summer.
- The beta group stays at 50 users until the export errors are fixed.
TASKS
- Draft the release notes for export, owner: Priya, due: 19 March
- Fix the CSV encoding error, owner: Tom, due: 17 March
- Email the beta group about the delay to sharing, owner: Sarah, due: 13 March
OPEN QUESTIONS
- Should export cost anything on the free plan? Dan brings numbers next time.
NEXT MEETING: 26 March
The example records a decision, a responsible person and a date for each action. It is a model to adapt, not a record of a real product meeting.
How do you write a task that gets done?
Most of the value of the notes sits in the task lines, and most weak notes are weak there. Manchester's governance handbook asks for minutes that are action focused and indicate responsibility for actions, key deliverables and timescales. It wants actions to be specific, and to carry a target date, which will normally be the date of the next meeting.
In practice a task needs a verb, a name and a date. The table shows stronger notes after the owner, date and decision have been confirmed. Do not invent those details from an ambiguous remark.
| Initial remark | Incomplete note | After confirmation |
|---|---|---|
| "We should contact the supplier" | Contact supplier | Sarah calls the supplier about the late delivery, by Wednesday |
| "Let's look at the budget again" | Budget to be revisited | Tom sends a revised budget with two options, by Friday |
| "Someone has to tell the client" | Inform client | Priya emails the client today that the launch moves to May |
| "I think we agreed on the logo" | Logo? | Decision: logo B. Dan sends the files to the printer by Monday |
If you cannot write the strong version, the meeting has not decided yet. That is worth finding out while people are still in the room, so keep one question ready: "who does that, and by when?"
Keep a running list of tasks
Tasks are forgotten between meetings, not during them. Manchester's handbook recommends that actions go into the minutes and also into a separate log of matters arising, which follows the committee from one meeting to the next. For a team that is one shared list with four columns: the task, the owner, the date and the status.
Open each meeting by going through the list. A task that remains open across meetings needs a status check, and saying so aloud is better than carrying it into a fourth.
How do you take notes while you take part?
Writing and listening compete for the same attention, as they do in a long lecture. A few habits keep the writing small.
Before the meeting
- Put the four headings in the document before anyone arrives.
- Copy the open questions from last time to the top of the page. Agree where they belong on the agenda.
During the meeting
- Capture decisions and tasks, plus reasons, qualifications or dissent where the meeting requires them.
- Write a decision in the words that were used when it was made. The meaning shifts when you rephrase it later.
- Say each task aloud before the meeting ends, with the name and the date.
- If an item remains unresolved, record the question and agree who will take it forward.
After the meeting
- Read the notes through once as the colleague who was not there.
- Circulate promptly to authorised recipients, following any approval or confidentiality rules.
- Put the tasks where the team looks every day, and not only in the notes.
Mistakes that make notes useless
- Writing everything down. You end up with a transcript and not notes, and nobody reads it.
- Tasks without an owner. "We should" is a wish. A name makes it a task.
- Waiting to write them up. What was agreed fades faster than you expect.
- Omitting required reasoning or dissent. A formal record may need more than the outcome; follow the body's rules.
- Keeping the notes in a private file. Notes that only the writer can find have not been sent.
How long should notes be, and when should they go out?
Short, and soon. Let the necessary decisions, actions and context determine the length. Manchester's handbook describes good minutes as a balance between being concise and being precise, and it warns against anything like a word-for-word record.
The timing matters as much as the length. Manchester asks that minutes are drafted as soon as possible following the meeting, and Loughborough that they are circulated as soon as possible. For a routine team, the same day is a useful target where feasible. It is not a substitute for required review or approval.
If the full notes need longer, consider sharing confirmed urgent actions separately with the appropriate people.
What is the difference between meeting notes and formal minutes?
Notes are a working record for the people who were there. Minutes are the official record of a body that takes formal decisions, such as a board, a committee or a general meeting. Their required content and approval procedures can differ.
| Meeting notes | Formal minutes | |
|---|---|---|
| Written for | The team | The body, and anyone who needs the record later |
| Content | Decisions, tasks, dates, open questions | Decisions, recommendations, attendance and any reasoning or dissent required by the body |
| Names | On every task | Roles more often than names |
| Approval | Whatever the team agrees | Follow the body's rules; Manchester normally uses chair sign-off and committee approval |
On names, Loughborough's guidance is that comments should generally not be assigned to individuals unless they were made in the context of their role. Bath's guide allows names where they are necessary: where an action is needed, or where a strong or dissenting view has to be recorded. On approval, Manchester describes the chair signing off the draft before the committee approves it at its following meeting. Formal minutes also carry more of the reasoning: Manchester asks that they document the reasons for a decision, and Bath notes that minutes can be used in external audits and legal proceedings.
How should you adapt the template?
The headings are a starting point. Add or change them for the purpose of the meeting.
- A weekly team meeting is mostly tasks. Start from last week's list, mark what is done, and add what is new.
- A meeting with a client is mostly decisions. Write down what was agreed on scope, price and dates, and send the notes to the client too, so that both sides hold the same record.
- A one-to-one gives few decisions and many open questions. Note what each of you will do before you meet again.
- A project group at university needs the dates most of all. Nobody is anybody's manager, so a named owner for each part of the report and a date for each draft do the work a manager would have done.
- A workshop produces material more than decisions. Where permitted, preserve the relevant board material and record what the group chose to take further.
The test stays the same in all five. A person who was not there reads the notes and knows what happens next.
Should you record the meeting as well?
It can help, and it changes the job. With a recording you no longer have to catch every detail while it is said. You take part, write down decisions and names, and let the recording hold the rest.
A recording is worth most where details matter and come fast: a technical review, a supervision meeting about a thesis, an interview with a customer. It is worth least in a short stand-up, where the four headings take two minutes to fill in by hand.
Everyone in the meeting has to know that it is being recorded, before it starts. A recording also does not replace the four parts. A transcript of 40 minutes is the opposite of half a page, so someone still has to decide what goes under each heading. How AI takes meeting minutes covers the rules on recording and what to check in an AI draft, and the best meeting notes apps compares the tools.
Where Notibo fits
Notibo records microphone audio in a browser on a computer or phone and returns a transcript and structured notes: a summary, the main points and action items. On a phone, keep the page open and the screen unlocked. For a video meeting on a computer, it can take the sound of a browser tab in Chrome or Edge, and no bot joins the call. You can also upload a recording you already have, as the transcription page shows.
Use the template with it. The notes Notibo writes are a draft, and you hold them against the four headings: move each decision under decisions, put a name and a date on each task, and add the questions that were left open. The transcript is split by speaker only where Notibo can tell the voices apart, so names are yours to add. The text can be corrected in the app and exported as PDF or Word.
Notibo transcribes 78 languages. The audio is deleted when the transcript and notes are saved. Files are stored in the EU, in Frankfurt, and transcription and the AI notes run on processors in the United States under Standard Contractual Clauses.
Pro is free for 14 days with 240 minutes of recording and no card. The trial starts with your first recording or an explicit trial-start action and ends by itself, and afterwards the account keeps the free plan with 30 minutes a month. Pro is 9.99 euro a month or 88.99 euro a year, with 1,200 minutes a month.