How to write meeting minutes in English so action items do not get dropped

The call with colleagues in Leeds is wrapping up when the project manager adds one last thing: “Olena, could you send round the minutes?” You nod and open your notes. All you have is half-sentences, two arrows and the word budget with a question mark. An hour later you send a long email retelling the whole conversation.
On the next call something awkward comes to light. Nobody wrote to the supplier, because everyone was waiting for someone else. Your email said “we discussed the supplier issue”. It did not say who should write or by when. Everyone read the email, and nobody picked it up.
How are minutes different from a recap in chat?
Minutes are the record of a meeting: they capture decisions and tasks so that people can refer back to them later. A recap, a short summary in chat, only reminds people what they have just agreed. Minutes follow a template and are kept. A recap is buried by the next message in the channel.
A recap is fine after a short working call with three people. A few lines are enough:
Minutes are needed when a decision affects money, deadlines or other teams. People also ask for them when part of the team missed the call. If you are told “send the minutes”, they expect a structured email or a document. Three lines in chat will not do.
In English the record is called minutes, not protocol
Ukrainians often write “please find the protocol attached”, because the Ukrainian word for minutes is протокол. To an English-speaking colleague, protocol means a procedure or rules of conduct. They will look in the email for instructions, not for the outcome of the meeting.
The right word here is minutes, and in this sense it is used only in the plural. So we write “the minutes are attached”, not “is attached”. Keeping this record during a meeting is called “to take the minutes”. In document titles and in search you will also see the longer form minutes of meeting, but in an email minutes is enough.
What goes into the minutes
Readers look in the minutes for their own name and their own deadline. That is why the sections of the document follow the same template every time:
- Heading names the meeting and the date.
- Attendees lists everyone who was present.
- Apologies names those who said in advance they could not come.
- Decisions holds the decisions taken, one per line.
- Action items shows the task, the owner and the deadline.
- Next meeting gives the date and time of the next meeting.
The heading Apologies surprises people at first: it is not a list of apologies but of those who let you know they would be absent. It is the British shorthand for apologies for absence. The names, dates and sums in this article’s examples are invented.
“It was agreed that” keeps “who said what” out of the minutes
Minutes record the outcome, not how the conversation went. Colleagues do not care who objected or how many minutes the argument lasted. They need to know where things ended up. That is exactly why the passive voice fits here.
The three verbs carry different weight, so do not mix them up. Write agreed when the participants came to agreement. Decided suits a decision taken by, say, the project manager. Noted records a fact that needs no action yet. After “it was agreed that”, “would” sounds natural, although “will” also turns up in emails.
If no decision was reached, record that too, on a separate line:
An action item without a name and a date never gets done
Every task has four parts, and their order is fixed. First the name, then the verb, then the object and, at the end, the deadline. Compare two versions of the same assignment.
The first line commits nobody to anything. The second can be checked on Friday evening. The pattern “name + to + verb” is standard in minutes, so will is unnecessary here.
Choose verbs that leave a visible result: send, prepare, confirm, share, finalise. Discuss, look into and think about promise no result. If you write “discuss”, Andrii will not send anything.
The deadline is introduced by the preposition by, meaning “no later than”. Until means the action goes on right up to the named day. “Send it until Friday” sounds like “keep sending it non-stop until Friday”.
If there are many tasks, make a three-column table: Action, Owner, Deadline. No deadline was set on the call? Put TBC (to be confirmed) in the column and ask the owner in the same email.
What should the email after the call look like?
Short. The subject line gives the name of the meeting and the date. Then comes one sentence of thanks, the decisions as a list and the action items with names and deadlines. At the end, ask people to correct anything inaccurate. Send it the same day, while everyone still remembers the conversation.
Hi all,
Thanks for joining today’s call. Please find the minutes below.
Decisions
1. It was agreed that the launch would be moved to 2 June.
2. It was decided to keep the current supplier until the end of the quarter.
Action items
1. Andrii to send the revised contract to the supplier by Friday 21 March.
2. Iryna to confirm the venue by 18 March.
Please let me know by tomorrow if anything needs correcting.
Kind regards,
Olena thanks, decisions, tasks and a request for corrections, nothing more
The last line of the email matters more than it seems. It gives everyone a chance to object straight away rather than later. If nobody objects, you are left with a paper trail of what was agreed.
What to check before you press Send
Reread the email through the eyes of someone who was not on the call. Will they understand what was decided and what they themselves have to do? Then run through these four questions:
- Is there a name next to every task?
- Does every task have a date with the preposition by?
- Does each name come with a verb that produces a result?
- Does it say minutes rather than protocol, with the verb in the plural?
Business English lessons will help you write emails like this with confidence, without hunting for every word.
After that call, one line would have done the job: “Andrii to email the supplier by Friday.” Then the next call would have started with the supplier’s reply.