How to summarise a meeting decision for someone who missed it
Your teammate missed a 40-minute meeting and has fifteen seconds to catch up. They do not need the discussion; they need the outcome. A good summary puts the decision first, the reason second and the actions third, and fits in 70–110 words.
The task
The briefYour team met for 40 minutes and decided to delay the app release by two weeks because the payment flow fails on older Android devices. QA will re-test on 6 March, and marketing has been told to hold the launch emails. Write ONE paragraph a teammate who missed the meeting can read in fifteen seconds.
Points to coverLead with the decision itself
Give the reason in one clause
Name who does what next
Include the date that matters
Length
70–110 words
Suggested time
12 minutes
Level
Easy
Planning tip: Decision first, reason second, actions third. A summary that narrates the meeting in order is a transcript, not a summary.
What a strong answer does
The first sentence is the decision, stated as a decision: what was agreed, not what was discussed.
The reason fits in a clause. One ‘because…’ is enough for someone who was not in the room.
Next steps name who does what and when. A team plus a date is an action; ‘testing will happen’ is not.
The one date that matters is impossible to miss.
It does not retell the meeting in order. Who spoke first, the options rejected and the long debate are history, not summary.
The reader can act without replying: if they own an action, they know it.
How to structure it
- 1
The decision
15–25 wordsOne sentence: what was decided, with the key change in numbers.
- 2
The reason
10–20 wordsOne clause or a short sentence explaining why.
- 3
Who does what
25–40 wordsEach action with its owner and, where there is one, its date.
- 4
What it means for the reader (optional)
10–20 wordsIf the reader has a task, or should stop doing something, say so. Otherwise, say where the full notes are.
Useful phrases
Frames, not finished sentences: put your own details where the [brackets] are, and use only the ones that fit what you are saying.
Stating the decision
- We agreed to [decision].
- The team decided to move [deliverable] to [new date].
Giving the reason
- This is because [reason].
- The reason is [reason], which [consequence].
Naming actions
- [Team or person] will [action] on [date].
- [Team or person] has already [action].
- Until then, [what is on hold] is on hold.
For the reader
- For you, this means [impact].
- Nothing changes on your side until [date].
- The full notes are in [place] if you need the detail.
Common mistakes, and how to fix them
Narrating the meeting: ‘First we discussed the issue, then Ravi suggested…’.
It makes the reader wait for the outcome. It is a transcript, not a summary.
Fix: Start with the decision, and leave out the order of the discussion.
Passive actions with no owner: ‘Testing will be done and the emails will be held.’
The reader cannot tell who is responsible, which is exactly what they needed to know.
Fix: Name the owner of every action: a person or a team.
A long explanation of the reason.
Three sentences on the technical problem turn a 15-second read into a minute and bury the actions.
Fix: One clause, with a link to the details if anyone needs them.
Burying the key date in the middle of a long sentence.
It is the thing people will plan around, and in a long sentence it gets missed.
Fix: Give the date its own short clause.
Ambiguous date formats: ‘4/5’.
That is 4 May in most of the world and April 5 in the United States. In an international team it is a real error.
Fix: Write the month as a word: ‘4 May’ or ‘May 4’, with the weekday if it helps.
Regional words such as ‘prepone’.
‘Prepone’, meaning to bring forward, is standard in Indian English but unknown to most international readers.
Fix: Use ‘bring forward’ and ‘push back’ or ‘delay’, which are understood everywhere.
Before you submit: a self-check
Is the decision the first thing the reader sees?
Is the reason a single clause?
Does every action have a named owner?
Is the key date written unambiguously?
Could the reader act without replying to you?
Is it 70–110 words?
Questions people ask
What should a meeting summary include?
The decision or decisions, the reason in brief, the actions with owners and dates, and anything the reader personally needs to do. Leave out the order of discussion and the options that were rejected, unless they change what someone should do.
How long should a meeting summary be?
For someone catching up on one decision, 70–110 words: a paragraph they can read in fifteen seconds. Meetings with several decisions may need a short list, but each item should still lead with its outcome.
Which tenses should a meeting summary use?
The past for the decision (‘we agreed’), the future for actions (‘the team will…’), and the present for current states (‘the launch is on hold’). That mix is natural and clear.
Paragraph or bullet points?
Bullets are common at work when there are several actions. This task asks for one paragraph, which trains the harder skill of ordering information so it reads clearly without any formatting.
Summarise a meeting decision for someone who missed it
70–110 words · 12 minutes · Easy. Free to start; you need a TalkDrill account to submit, not to read this guide.
Scored by AI on TalkDrill on
- Task response25%
- Organisation20%
- Grammar20%
- Vocabulary15%
- Mechanics (spelling and punctuation)10%
- Tone10%
