All levels
Writing
#status-update
#async
#blockers
Weekly Status Updates
5 exercises — Done/In Progress/Blockers format, action verb tense, blocker communication, and how to report missed deadlines professionally.
0 / 25 completed
1 / 25
Your manager asks for a weekly status update. Which structure is most professional and easy to scan?
The Done / In Progress / Blockers format (sometimes "This week / Next week / Blockers") is the industry standard for async status updates. It is scannable, predictable, and actionable — a manager can immediately identify risks (the Blockers section) without reading the whole update. Ticket references should supplement, not replace, written summaries. Hour breakdowns are for billing reports, not team communication.
2 / 25
Complete this "Done" section item: "_____ the authentication middleware to support OAuth 2.0 PKCE flow — _____ and _____ in staging."
Use past simple action verbs for the "Done" section — concise, no subject pronoun. This is a conventional register in professional status updates: "Shipped", "Fixed", "Reviewed", "Deployed", "Merged". Present perfect ("Have updated") is grammatically possible but less common in this bullet-style format. Infinitives ("Update", "Test") are used in to-do or roadmap items, not completed work.
3 / 25
You are blocked on a task. Which blocker statement is most useful for your manager?
A useful blocker statement answers three questions: (1) What exactly is blocked? (the DB schema migration) (2) Who can unblock it? (@platform-team) (3) What is the timeline impact? (ETA: Monday). Including a ticket reference helps managers track it. Options A and B give no context. Option D contains blame framing — status updates should be neutral and factual.
4 / 25
Complete the "In Progress" item: "Migrating user-service to Kubernetes — target _____ end of sprint. Currently _____ on namespace configuration; ETA _____ Thursday."
"To be completed by" (infinitive passive) is natural for target dates in status updates: "Target to be completed by Friday". "Working on" is the standard gerund phrase for in-progress work. "ETA to complete" or "ETA: Thursday" both work — the infinitive form emphasises the completion event. "Completion by" (Option A) is common in formal project management writing but slightly stiff; all options are grammatically possible except Option C ("blocking" makes the writer the source of the block, not the subject of work).
5 / 25
You need to inform your manager that a deadline will be missed. Which message is most professional?
A professional missed-deadline notification must include: (1) what is delayed (checkout feature), (2) why (rate limit — discovered when), (3) new ETA (Monday EOD), and (4) mitigation in progress (caching layer). Option A is too informal (emojis, "lol"). Option B apologises but provides no context or recovery plan — an apology without a plan is not useful. Option D over-apologises and hedges ("may not be") when you already know it will miss the deadline — this lacks clarity.
6 / 25
During a code review of the new payment processing module, Sarah flags a potential security vulnerability. David responds with: 'Sounds good, just let me know if you find anything.' This response is:
<strong>Ineffective</strong>. It lacks specifics about the identified issue and doesn't demonstrate a proactive approach to resolving it. It also doesn't acknowledge Sarah's contribution, potentially leading to miscommunication and delayed remediation.The key here isn't just acknowledging the feedback, but demonstrating understanding and next steps. David's response fails to address the core issue (the vulnerability) or offer specific assistance, which is a critical component of effective communication during a code review.
7 / 25
During a sprint retrospective, the team discusses recurring issues with API documentation. Liam suggests adding a daily update to the project's Slack channel summarizing key documentation changes. Which of the following best reflects Liam's intention and potential impact?
Liam's suggestion focuses on proactive communication and transparency – key aspects of agile development. Slack updates are ideal for quickly disseminating information to a broad audience (stakeholders). The other options represent more rigid or potentially disruptive approaches (formal audits, dedicated reporting channels, mandatory reviews) that wouldn't necessarily align with the benefits of frequent documentation updates.
8 / 25
During a code review of the new user profile API, Maria points out that the field validation is insufficient, allowing users to upload oversized images. John responds with: 'Thanks for flagging that, Maria. I'll add some size limits.' This response demonstrates:
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
The correct answer (C) highlights John's inappropriate response. While acknowledging Maria's feedback is important, a good developer would elaborate on the specific validation changes needed and their impact – demonstrating an understanding beyond a simple 'thanks.' Options A and B are too vague, and D misses the core problem of insufficient field validation.
9 / 25
During a code review of the new user onboarding flow, Alex highlights a potential performance bottleneck caused by inefficient database queries. Ben responds with: 'That's interesting. We should probably look into it later.'
Which of the following best describes Ben's response and its likely impact on the review process?
Ben's response lacks urgency and doesn't propose any concrete steps. This can lead to the issue being sidelined and potentially impacting user experience. A strong response would acknowledge the potential bottleneck and initiate a plan for investigation – highlighting the importance of addressing performance issues during code reviews. The correct answer reflects this realistic scenario.
10 / 25
You're reviewing a pull request for a new feature: adding two-factor authentication (2FA) to the user login process. During the review, Emily points out that the current implementation doesn't handle rate limiting for failed login attempts, potentially opening a door for brute-force attacks. Mark responds with: 'Yeah, I was going to get to that later.'
Which of the following best describes Mark's response and its likely impact on the review process?
Mark's response fails to acknowledge the significant security implication – rate limiting is a fundamental component of 2FA. This inaction could leave the system vulnerable and delays crucial security improvements. A proactive developer would have identified this risk and proposed a solution during the review, demonstrating due diligence and protecting user accounts.
11 / 25
During a code review of the new payment processing module, Sarah flags a potential security vulnerability. David responds with: 'Sounds good, just let me know if you find anything.' This response is:
<strong>Ineffective</strong>. It lacks specifics about the identified issue and doesn't demonstrate a proactive approach to resolving it. It also doesn't acknowledge Sarah's contribution, potentially leading to miscommunication and delayed remediation.The key here isn't just acknowledging the feedback, but demonstrating understanding and next steps. David's response fails to address the core issue (the vulnerability) or offer specific assistance, which is a critical component of effective communication during a code review.
12 / 25
During a sprint retrospective, the team discusses recurring issues with API documentation. Liam suggests adding a daily update to the project's Slack channel summarizing key documentation changes. Which of the following best reflects Liam's intention and potential impact?
Liam's suggestion focuses on proactive communication and transparency – key aspects of agile development. Slack updates are ideal for quickly disseminating information to a broad audience (stakeholders). The other options represent more rigid or potentially disruptive approaches (formal audits, dedicated reporting channels, mandatory reviews) that wouldn't necessarily align with the benefits of frequent documentation updates.
13 / 25
During a code review of the new user profile API, Maria points out that the field validation is insufficient, allowing users to upload oversized images. John responds with: 'Thanks for flagging that, Maria. I'll add some size limits.' This response demonstrates:
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
The correct answer (C) highlights John's inappropriate response. While acknowledging Maria's feedback is important, a good developer would elaborate on the specific validation changes needed and their impact – demonstrating an understanding beyond a simple 'thanks.' Options A and B are too vague, and D misses the core problem of insufficient field validation.
14 / 25
During a code review of the new user onboarding flow, Alex highlights a potential performance bottleneck caused by inefficient database queries. Ben responds with: 'That's interesting. We should probably look into it later.'
Which of the following best describes Ben's response and its likely impact on the review process?
Ben's response lacks urgency and doesn't propose any concrete steps. This can lead to the issue being sidelined and potentially impacting user experience. A strong response would acknowledge the potential bottleneck and initiate a plan for investigation – highlighting the importance of addressing performance issues during code reviews. The correct answer reflects this realistic scenario.
15 / 25
You're reviewing a pull request for a new feature: adding two-factor authentication (2FA) to the user login process. During the review, Emily points out that the current implementation doesn't handle rate limiting for failed login attempts, potentially opening a door for brute-force attacks. Mark responds with: 'Yeah, I was going to get to that later.'
Which of the following best describes Mark's response and its likely impact on the review process?
Mark's response fails to acknowledge the significant security implication – rate limiting is a fundamental component of 2FA. This inaction could leave the system vulnerable and delays crucial security improvements. A proactive developer would have identified this risk and proposed a solution during the review, demonstrating due diligence and protecting user accounts.
16 / 25
During a code review of the new payment processing module, Sarah flags a potential security vulnerability. David responds with: 'Sounds good, just let me know if you find anything.' This response is:
<strong>Ineffective</strong>. It lacks specifics about the identified issue and doesn't demonstrate a proactive approach to resolving it. It also doesn't acknowledge Sarah's contribution, potentially leading to miscommunication and delayed remediation.The key here isn't just acknowledging the feedback, but demonstrating understanding and next steps. David's response fails to address the core issue (the vulnerability) or offer specific assistance, which is a critical component of effective communication during a code review.
17 / 25
During a sprint retrospective, the team discusses recurring issues with API documentation. Liam suggests adding a daily update to the project's Slack channel summarizing key documentation changes. Which of the following best reflects Liam's intention and potential impact?
Liam's suggestion focuses on proactive communication and transparency – key aspects of agile development. Slack updates are ideal for quickly disseminating information to a broad audience (stakeholders). The other options represent more rigid or potentially disruptive approaches (formal audits, dedicated reporting channels, mandatory reviews) that wouldn't necessarily align with the benefits of frequent documentation updates.
18 / 25
During a code review of the new user profile API, Maria points out that the field validation is insufficient, allowing users to upload oversized images. John responds with: 'Thanks for flagging that, Maria. I'll add some size limits.' This response demonstrates:
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
The correct answer (C) highlights John's inappropriate response. While acknowledging Maria's feedback is important, a good developer would elaborate on the specific validation changes needed and their impact – demonstrating an understanding beyond a simple 'thanks.' Options A and B are too vague, and D misses the core problem of insufficient field validation.
19 / 25
During a code review of the new user onboarding flow, Alex highlights a potential performance bottleneck caused by inefficient database queries. Ben responds with: 'That's interesting. We should probably look into it later.'
Which of the following best describes Ben's response and its likely impact on the review process?
Ben's response lacks urgency and doesn't propose any concrete steps. This can lead to the issue being sidelined and potentially impacting user experience. A strong response would acknowledge the potential bottleneck and initiate a plan for investigation – highlighting the importance of addressing performance issues during code reviews. The correct answer reflects this realistic scenario.
20 / 25
You're reviewing a pull request for a new feature: adding two-factor authentication (2FA) to the user login process. During the review, Emily points out that the current implementation doesn't handle rate limiting for failed login attempts, potentially opening a door for brute-force attacks. Mark responds with: 'Yeah, I was going to get to that later.'
Which of the following best describes Mark's response and its likely impact on the review process?
Mark's response fails to acknowledge the significant security implication – rate limiting is a fundamental component of 2FA. This inaction could leave the system vulnerable and delays crucial security improvements. A proactive developer would have identified this risk and proposed a solution during the review, demonstrating due diligence and protecting user accounts.
21 / 25
During a code review of the new payment processing module, Sarah flags a potential security vulnerability. David responds with: 'Sounds good, just let me know if you find anything.' This response is:
<strong>Ineffective</strong>. It lacks specifics about the identified issue and doesn't demonstrate a proactive approach to resolving it. It also doesn't acknowledge Sarah's contribution, potentially leading to miscommunication and delayed remediation.The key here isn't just acknowledging the feedback, but demonstrating understanding and next steps. David's response fails to address the core issue (the vulnerability) or offer specific assistance, which is a critical component of effective communication during a code review.
22 / 25
During a sprint retrospective, the team discusses recurring issues with API documentation. Liam suggests adding a daily update to the project's Slack channel summarizing key documentation changes. Which of the following best reflects Liam's intention and potential impact?
Liam's suggestion focuses on proactive communication and transparency – key aspects of agile development. Slack updates are ideal for quickly disseminating information to a broad audience (stakeholders). The other options represent more rigid or potentially disruptive approaches (formal audits, dedicated reporting channels, mandatory reviews) that wouldn't necessarily align with the benefits of frequent documentation updates.
23 / 25
During a code review of the new user profile API, Maria points out that the field validation is insufficient, allowing users to upload oversized images. John responds with: 'Thanks for flagging that, Maria. I'll add some size limits.' This response demonstrates:
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
A proactive understanding of the issue and immediate action taken.
<B a basic acknowledgement without detailing the next steps or impact.
<C a dismissive tone, potentially minimizing Maria's valuable feedback.
<D an overly technical response that doesn't address the user experience concern.
The correct answer (C) highlights John's inappropriate response. While acknowledging Maria's feedback is important, a good developer would elaborate on the specific validation changes needed and their impact – demonstrating an understanding beyond a simple 'thanks.' Options A and B are too vague, and D misses the core problem of insufficient field validation.
24 / 25
During a code review of the new user onboarding flow, Alex highlights a potential performance bottleneck caused by inefficient database queries. Ben responds with: 'That's interesting. We should probably look into it later.'
Which of the following best describes Ben's response and its likely impact on the review process?
Ben's response lacks urgency and doesn't propose any concrete steps. This can lead to the issue being sidelined and potentially impacting user experience. A strong response would acknowledge the potential bottleneck and initiate a plan for investigation – highlighting the importance of addressing performance issues during code reviews. The correct answer reflects this realistic scenario.
25 / 25
You're reviewing a pull request for a new feature: adding two-factor authentication (2FA) to the user login process. During the review, Emily points out that the current implementation doesn't handle rate limiting for failed login attempts, potentially opening a door for brute-force attacks. Mark responds with: 'Yeah, I was going to get to that later.'
Which of the following best describes Mark's response and its likely impact on the review process?
Mark's response fails to acknowledge the significant security implication – rate limiting is a fundamental component of 2FA. This inaction could leave the system vulnerable and delays crucial security improvements. A proactive developer would have identified this risk and proposed a solution during the review, demonstrating due diligence and protecting user accounts.
Frequently Asked Questions
What does the "Weekly Status Updates — Writing Exercise" exercise cover?
Practice writing clear, scannable weekly status updates for engineering teams. Done / In Progress / Blockers format, missed deadlines, and communication norms.
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 "Weekly Status Updates — Writing Exercise"?
This exercise has 25 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.