How to Summarise a Meeting in English (With Examples)

Meetings end. The coffee goes cold. Everyone leaves. And then someone has to write up what actually happened. If that someone is you, and English is not your first language, this post is for you.

Summarising a meeting in English is a core professional skill. Done well, it keeps your team aligned, shows you understood the discussion, and protects everyone if there is confusion later. Done badly, it creates more questions than the meeting answered. Let’s fix that.

What a Good Meeting Summary Actually Does

A meeting summary is not a transcript. You are not recording every word. You are capturing three things:

1. What was discussed (the key topics)
2. What was decided (the outcomes)
3. What happens next (action points, owners, deadlines)

That structure gives your summary a clear shape. Every sentence you write should belong to one of those three buckets.

The Language You Need

Meeting summaries follow predictable patterns. Once you have the right phrases, it gets much easier. Here are the key ones, organised by purpose.

To introduce the summary:

• Following today’s meeting, I’d like to summarise the key points.
• Please find below a brief summary of our discussion.
• This email confirms the outcomes of our meeting on [date].

To report what was discussed:

• We discussed the current timeline for the project.
• The team reviewed the latest sales figures.
• There was some debate around the proposed budget.

To report decisions:

• It was agreed that the deadline would be moved to 15 March.
• The team decided to proceed with Option B.
• We reached a consensus on the new pricing structure.

To assign action points:

• [Name] will send the revised proposal by Friday.
• The marketing team is responsible for preparing the presentation.
• All team members should review the document before the next meeting.

To close:

• Please let me know if I have missed anything or if you have any corrections.
• Our next meeting is scheduled for [date].

Notice the tense choices. When reporting decisions, passive constructions like it was agreed and it was decided sound formal and neutral. That is often exactly what you want in a professional context. For action points, use the future with will or a present simple structure with clear ownership.

A Worked Example

Let’s say your team had a meeting about a delayed product launch. Here is a weak summary followed by a strong one.

Weak:

We talked about the launch. It is delayed. Someone will fix it. We’ll meet again soon.

This tells the reader almost nothing useful. No specifics, no ownership, no deadline.

Strong:

Following today’s meeting, I’d like to summarise the key points discussed.

We reviewed the current status of the Q3 product launch. It was agreed that the launch date would be pushed back to 20 October due to delays in the supply chain.

Action points: Sara will contact the supplier by Wednesday to confirm the revised delivery schedule. James is responsible for updating the marketing materials to reflect the new date. All team members should flag any further concerns to Sara before Friday.

Our next meeting is scheduled for 12 October at 10:00. Please let me know if I have missed anything.

Same meeting. Completely different level of clarity. The second version is something colleagues can act on.

This kind of structured professional writing is exactly what we practise in daily coaching sessions. If you want regular, focused practice on real business writing tasks, click here to find out more.

Practice Exercise

Try these exercises. Fill in the blank with the most appropriate word or phrase from the options given.

1. _______ today’s meeting, please find below a summary of the key points.
a) Despite   b) Following   c) During   d) Between

2. It _______ that the new supplier would be contacted by the end of the week.
a) decided   b) was deciding   c) was agreed   d) has agreed

3. Ana _______ the updated report to the team before Thursday.
a) will send   b) was sending   c) sends   d) had sent

4. Rewrite this sentence in a more formal, professional style:
“John has to call the client and tell them the price went up.”

5. Put these three sentences in the correct order for a meeting summary:
a) Action points: Tom will revise the budget proposal by Friday.
b) Following today’s meeting, I’d like to summarise the key outcomes.
c) It was decided that the current budget is insufficient for Phase 2.

These are the kinds of tasks we work through together in coaching sessions, where you get real feedback on your answers rather than just checking a list. For more details on daily coaching, click here.

Vocabulary to Know

• to summarise /ˈsʌm.ə.raɪz/ – Level: B1 – to give a short account of the main points of something – Example: Could you summarise what was discussed in the first half of the meeting?
• action point /ˈæk.ʃən pɔɪnt/ – Level: B2 – a specific task assigned to a person following a meeting, with a clear deadline – Example: The main action point from the meeting was for James to contact the client by Thursday.
• to reach a consensus /tuː riːtʃ ə kənˈsen.səs/ – Level: B2 – to arrive at a general agreement among a group – Example: After an hour of discussion, the board finally reached a consensus on the new policy.
• to proceed with /tə prəˈsiːd wɪð/ – Level: B2 – to continue or move forward with a plan or course of action – Example: The team decided to proceed with the original proposal.
• outstanding /ˌaʊtˈstæn.dɪŋ/ – Level: B2 – (in a business context) not yet completed or resolved – Example: There are still two outstanding items from last week’s meeting.
• to defer /tə dɪˈfɜː/ – Level: C1 – to postpone something to a later time or meeting – Example: The budget discussion was deferred until the CFO could attend.
• minutes /ˈmɪn.ɪts/ – Level: B1 – the official written record of what was said and decided in a meeting – Example: Could you take the minutes for today’s meeting?
• to table something /tə ˈteɪ.bəl ˈsʌm.θɪŋ/ – Level: C1 – (British English) to bring a topic forward for discussion; (American English) to postpone it. Context matters enormously here. – Example: The chair decided to table the staffing issue until more data was available.
• in light of /ɪn laɪt ɒv/ – Level: C1 – considering the information or circumstances just mentioned – Example: In light of the new figures, the team agreed to revise the forecast.
• point of order /pɔɪnt əv ˈɔː.də/ – Level: C2 – a formal objection raised during a meeting that the rules of procedure are not being followed – Example: The delegate raised a point of order before the vote could take place.

FAQ

How long should a meeting summary be?
As short as it can be while still being complete. A one-hour meeting can usually be summarised in 150 to 300 words. If your summary is longer than the meeting felt, you are probably including too much. Focus on decisions and action points, not the debate that led to them.

Should I send the summary by email or write it in a shared document?
This depends on your company’s culture. Email is common for external meetings or smaller teams. Shared documents (Notion, Google Docs, Confluence) work better when multiple people need to update action points over time. When in doubt, do both: send a brief email and link to the document.

What is the difference between meeting minutes and a meeting summary?
Meeting minutes are a formal, official record, often used in legal, board, or governance contexts. They follow a set format and are sometimes signed off. A meeting summary is less formal and more practical. It is focused on communication rather than record-keeping. Most day-to-day professional meetings need a summary, not full minutes.

If writing clear, professional English at work is something you want to get consistently better at, daily coaching sessions are built around exactly that kind of real-world practice. Find out more here.