Practise the IT-English phrasing of meeting follow-up emails: recapping decisions, action items, owners and next steps.
0 / 22 completed
1 / 22
Which opening best 'recaps' a meeting concisely?
A brief recap framing plus a clear list is the standard, efficient follow-up structure.
2 / 22
A follow-up lists 'action items' with owners. Why include an owner per item?
Naming an owner per action item creates accountability and avoids tasks falling through the cracks.
3 / 22
Which phrase best states a 'next step' with a deadline?
A specific owner, task and date make the next step actionable and trackable.
4 / 22
Why confirm 'decisions made' in the follow-up?
Recording decisions prevents later disagreement about what the meeting concluded.
5 / 22
Which closing invites correction politely?
Inviting corrections keeps the record accurate and signals openness.
6 / 22
David from the code review mentioned a potential performance bottleneck in the new API endpoint. You've just sent a follow-up email summarizing the discussion and action items. Which of the following sentences best reflects your intention when stating that Sarah is responsible for investigating this further?
Consider: This isn't simply assigning blame, but clarifying ownership for resolution.
The correct answer clearly assigns responsibility to Sarah while acknowledging the original request. Options A and D are too verbose or imply a demand rather than a collaborative task assignment. Option B is technically accurate but lacks direct ownership; it simply restates David's request without specifying who should act upon it. Focusing on clear ownership, as demonstrated in option 2, is key to effective follow-up emails.
7 / 22
John from the sprint planning meeting highlighted a key challenge: integrating the new authentication service with our existing microservices. You've drafted a follow-up email summarizing the discussion and outlining next steps. Which sentence best communicates your intention when assigning Mike the task of creating a proof-of-concept integration?
Consider: This isn't just delegating a small task, but clearly defining responsibility for a critical technical exploration.
The correct answer (Excellent) demonstrates an understanding of clear communication in a technical context. Assigning responsibility with a specific task (creating a proof-of-concept) is crucial for effective project management and avoids ambiguity. The other options are either too vague, assign blame unnecessarily, or fail to provide the necessary level of detail for Mike to understand his role.
8 / 22
Alex from the Slack channel reported that the response time for the new user signup API was consistently slow during peak hours. You've drafted a follow-up email to the team summarizing the issue and assigning tasks. Which of the following sentences best clarifies Ben's role in addressing this concern?
The key here isn't just assigning ownership; it's about making sure Ben understands *what* is expected of him. Option A focuses on a lack of detail which is exactly what we need to avoid. Options B and C are too vague – 'responsible' doesn't convey action. Option D provides the necessary specificity, ensuring Ben knows how his work contributes to solving the problem. A good follow-up clarifies expectations, reducing ambiguity.
9 / 22
David from the code review mentioned a potential performance bottleneck in the new API endpoint. You've just sent a follow-up email summarizing the discussion and action items. Which of the following sentences best reflects your intention when stating that Sarah is responsible for investigating this further?
Consider: This isn't simply assigning blame, but clarifying ownership for resolution.
The correct answer clearly assigns responsibility to Sarah while acknowledging the original request. Options A and D are too verbose or imply a demand rather than a collaborative task assignment. Option B is technically accurate but lacks direct ownership; it simply restates David's request without specifying who should act upon it. Focusing on clear ownership, as demonstrated in option 2, is key to effective follow-up emails.
10 / 22
John from the sprint planning meeting highlighted a key challenge: integrating the new authentication service with our existing microservices. You've drafted a follow-up email summarizing the discussion and outlining next steps. Which sentence best communicates your intention when assigning Mike the task of creating a proof-of-concept integration?
Consider: This isn't just delegating a small task, but clearly defining responsibility for a critical technical exploration.
The correct answer (Excellent) demonstrates an understanding of clear communication in a technical context. Assigning responsibility with a specific task (creating a proof-of-concept) is crucial for effective project management and avoids ambiguity. The other options are either too vague, assign blame unnecessarily, or fail to provide the necessary level of detail for Mike to understand his role.
11 / 22
Alex from the Slack channel reported that the response time for the new user signup API was consistently slow during peak hours. You've drafted a follow-up email to the team summarizing the issue and assigning tasks. Which of the following sentences best clarifies Ben's role in addressing this concern?
The key here isn't just assigning ownership; it's about making sure Ben understands *what* is expected of him. Option A focuses on a lack of detail which is exactly what we need to avoid. Options B and C are too vague – 'responsible' doesn't convey action. Option D provides the necessary specificity, ensuring Ben knows how his work contributes to solving the problem. A good follow-up clarifies expectations, reducing ambiguity.
12 / 22
David from the code review mentioned a potential performance bottleneck in the new API endpoint. You've just sent a follow-up email summarizing the discussion and action items. Which of the following sentences best reflects your intention when stating that Sarah is responsible for investigating this further?
Consider: This isn't simply assigning blame, but clarifying ownership for resolution.
The correct answer clearly assigns responsibility to Sarah while acknowledging the original request. Options A and D are too verbose or imply a demand rather than a collaborative task assignment. Option B is technically accurate but lacks direct ownership; it simply restates David's request without specifying who should act upon it. Focusing on clear ownership, as demonstrated in option 2, is key to effective follow-up emails.
13 / 22
John from the sprint planning meeting highlighted a key challenge: integrating the new authentication service with our existing microservices. You've drafted a follow-up email summarizing the discussion and outlining next steps. Which sentence best communicates your intention when assigning Mike the task of creating a proof-of-concept integration?
Consider: This isn't just delegating a small task, but clearly defining responsibility for a critical technical exploration.
The correct answer (Excellent) demonstrates an understanding of clear communication in a technical context. Assigning responsibility with a specific task (creating a proof-of-concept) is crucial for effective project management and avoids ambiguity. The other options are either too vague, assign blame unnecessarily, or fail to provide the necessary level of detail for Mike to understand his role.
14 / 22
Alex from the Slack channel reported that the response time for the new user signup API was consistently slow during peak hours. You've drafted a follow-up email to the team summarizing the issue and assigning tasks. Which of the following sentences best clarifies Ben's role in addressing this concern?
The key here isn't just assigning ownership; it's about making sure Ben understands *what* is expected of him. Option A focuses on a lack of detail which is exactly what we need to avoid. Options B and C are too vague – 'responsible' doesn't convey action. Option D provides the necessary specificity, ensuring Ben knows how his work contributes to solving the problem. A good follow-up clarifies expectations, reducing ambiguity.
15 / 22
David from the code review mentioned a potential performance bottleneck in the new API endpoint. You've just sent a follow-up email summarizing the discussion and action items. Which of the following sentences best reflects your intention when stating that Sarah is responsible for investigating this further?
Consider: This isn't simply assigning blame, but clarifying ownership for resolution.
The correct answer clearly assigns responsibility to Sarah while acknowledging the original request. Options A and D are too verbose or imply a demand rather than a collaborative task assignment. Option B is technically accurate but lacks direct ownership; it simply restates David's request without specifying who should act upon it. Focusing on clear ownership, as demonstrated in option 2, is key to effective follow-up emails.
16 / 22
John from the sprint planning meeting highlighted a key challenge: integrating the new authentication service with our existing microservices. You've drafted a follow-up email summarizing the discussion and outlining next steps. Which sentence best communicates your intention when assigning Mike the task of creating a proof-of-concept integration?
Consider: This isn't just delegating a small task, but clearly defining responsibility for a critical technical exploration.
The correct answer (Excellent) demonstrates an understanding of clear communication in a technical context. Assigning responsibility with a specific task (creating a proof-of-concept) is crucial for effective project management and avoids ambiguity. The other options are either too vague, assign blame unnecessarily, or fail to provide the necessary level of detail for Mike to understand his role.
17 / 22
Alex from the Slack channel reported that the response time for the new user signup API was consistently slow during peak hours. You've drafted a follow-up email to the team summarizing the issue and assigning tasks. Which of the following sentences best clarifies Ben's role in addressing this concern?
The key here isn't just assigning ownership; it's about making sure Ben understands *what* is expected of him. Option A focuses on a lack of detail which is exactly what we need to avoid. Options B and C are too vague – 'responsible' doesn't convey action. Option D provides the necessary specificity, ensuring Ben knows how his work contributes to solving the problem. A good follow-up clarifies expectations, reducing ambiguity.
18 / 22
Maria sent a follow-up email after a code review, stating: 'Let's circle back on this next week.' What is the best way to complete this sentence to clearly define a timeframe and action?
The phrase 'circle back' is vague. Option 2 provides a specific action (scheduling a meeting) and timeframe ('next week'). Options A and D are too open-ended, while option B doesn't explicitly set a deadline.
19 / 22
During a sprint retrospective, Sarah mentioned that the team struggled to estimate story points accurately. In her follow-up email summarizing the discussion, why is it important to explicitly state 'We agreed to…'?
Confirming decisions is crucial for clarity and accountability. Explicitly stating what was agreed upon provides a documented record that everyone can refer back to. It prevents ambiguity and ensures alignment moving forward.
20 / 22
You've drafted an email to the team after a standup update where you highlighted a critical bug affecting user login. Which of the following closing sentences is most appropriate for politely requesting further action?
Option 2 uses polite language ('appreciate your prompt attention') and emphasizes the urgency without being demanding. The other options are too casual or lack a clear call to action. It's important to balance politeness with the need for action.
21 / 22
As a Senior Developer, you're reviewing a PR submitted by Ben. He included a comment: 'This change significantly improves the API response time.' You've sent a follow-up email summarizing the discussion and action items. Which of the following sentences best reflects this feedback in your summary?
Option 1 accurately captures Ben's positive feedback by stating that he 'highlighted a key improvement'. It avoids misinterpreting his comment and clearly conveys the intended outcome. Options A and D are too vague, while option B focuses on testing rather than the core improvement.
22 / 22
During a Slack discussion about a failing integration test, Emily reported: 'The new service returns a 500 error when attempting to update user profiles.' You've drafted a follow-up email to the team summarizing the issue and assigning tasks. Which of the following sentences is most suitable for concluding this email?
Option 2 is a pragmatic and proactive closing. It suggests ongoing monitoring without placing undue pressure or demanding immediate action beyond observation – a sensible approach to a potentially complex problem. Options A and D are too directive, while option B implies a lack of urgency.
What does the "Meeting Follow-up Emails" exercise cover?
Practise the IT-English phrasing of meeting follow-up emails: recapping decisions, action items, owners and next steps.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Meeting Follow-up Emails"?
This exercise has 22 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Email & Writing exercises?
Browse the full Email & Writing hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.