An engineer needs to report the same incident in two places: a Slack channel and an executive postmortem report. Which pair correctly matches register to context?
Register means choosing language appropriate to the audience, channel, and purpose. Slack uses informal but clear language: contractions, abbreviations, a timeframe, and a commitment to update. The executive report uses formal register: full noun phrases (degradation event), precise timestamps (UTC), and a quantified impact (40% error rate). Option A reverses the registers. Option C puts over-formal language in Slack, which wastes readers' time and misreads the channel. Related patterns: shifting between docs ↔ PR comments ↔ Slack ↔ email.
2 / 28
A developer is writing a PR description and then a verbal standup update about the same change. Which pair is most register-appropriate?
A PR description is written documentation — it should be concise, precise, and use technical vocabulary (exponential backoff with jitter). A standup is verbal and conversational — the same technical content is delivered in natural spoken English with a brief explanation of why ("it was using linear backoff"). Neither register is dumbed down — both contain the key technical information, but the delivery adapts to the channel. Options A, C, and D all show register mismatches. Related patterns: written doc ↔ verbal update, formal commit message ↔ Slack mention.
3 / 28
An engineer receives a Slack message: "heads up — auth is flaky on staging, seeing 401s on the /token endpoint." Which reply is most register-appropriate for Slack?
Slack communication in an engineering team uses informal but informative register: a brief acknowledgement (Cheers — on it), a concrete action statement (will check the token endpoint config and rotation schedule), and a time commitment (back to you in 30). Option A is over-formal for Slack and wastes reading time. Option C is sarcastic and unprofessional. Option D provides no information about what will happen. Related patterns: informal acknowledgement + action + timeframe = effective Slack reply.
4 / 28
A technical lead is writing an Architecture Decision Record (ADR) about switching from REST to GraphQL. Which sentence is most appropriate for the formal ADR register?
ADRs require formal, precise, attributable language: a named evaluation process (after evaluating), specific technical reasoning (over-fetching overhead), a clear decision statement (the team has decided to adopt), a defined scope (client-facing API layer), and a reference to supporting documentation. This register ensures the ADR is useful months or years later. Options A, C, and D are informal and lack the traceability an ADR requires. Related patterns: "following a review of... the decision has been made to...", "as per the evaluation criteria defined in..."
5 / 28
A code review comment flags a potential performance issue. Which comment demonstrates the best register for a constructive PR review?
Code review comments should use professional collegial register: name the problem precisely (N+1 query behaviour), suggest a concrete solution (join or eager loading), use a modal for appropriate softness (may introduce), and offer collaboration (happy to discuss). Option A is blunt and provides no actionable guidance. Option C is informal and unprofessional. Option D is aggressive and inappropriate. The register in option B is constructive: it respects the author while being technically specific. Related patterns: "consider refactoring... this may affect... one option would be to..."
6 / 28
Sarah, the DevOps engineer, needs to quickly report a database outage to her team on Slack. Which of the following messages best reflects an appropriate level of formality for this situation?
Option B uses precise language and avoids overly casual phrasing like 'totally down,' suitable for a rapid team update. It clearly states the problem's impact and indicates action being taken. Options A is too informal, C is vague, and D is unnecessarily formal for this immediate notification.
7 / 28
Lena, a junior developer, receives an email from the API team detailing a recent performance degradation. The email states: 'The service is currently experiencing high latency and occasional timeouts.' Which of the following responses should she send in reply?
Option B maintains a professional tone while clearly articulating the issue and indicating an ongoing investigation. It avoids overly casual language like 'Sounds bad!' or simplistic statements, demonstrating appropriate communication for a technical update. Options A is too informal, C lacks detail, and D is overly demanding.
8 / 28
David, an architect, is writing a section of a System Design Document outlining the decision to migrate from SOAP to gRPC. Which sentence best reflects the formal register required for this document?
Option B utilizes formal language, explaining the rationale behind the decision (improved performance and reduced overhead) in a structured manner. It avoids subjective opinions ('faster and cooler') and focuses on objective technical benefits. Options A is too informal, C is directive, and D lacks context.
9 / 28
During a daily standup meeting, Ben reports a bug he found while testing a new feature. Which of the following statements is the most appropriate way for him to communicate this information?
Option B provides a clear and concise description of the issue without excessive detail or emotive language. It focuses on the observable behavior and avoids blaming or demanding immediate action. Options A is too informal, C is overly reliant on asking for help, and D is overly specific.
10 / 28
Sarah, the DevOps engineer, needs to quickly report a database outage to her team on Slack. Which of the following messages best reflects an appropriate level of formality for this situation?
Option B uses precise language and avoids overly casual phrasing like 'totally down,' suitable for a rapid team update. It clearly states the problem's impact and indicates action being taken. Options A is too informal, C is vague, and D is unnecessarily formal for this immediate notification.
11 / 28
Lena, a junior developer, receives an email from the API team detailing a recent performance degradation. The email states: 'The service is currently experiencing high latency and occasional timeouts.' Which of the following responses should she send in reply?
Option B maintains a professional tone while clearly articulating the issue and indicating an ongoing investigation. It avoids overly casual language like 'Sounds bad!' or simplistic statements, demonstrating appropriate communication for a technical update. Options A is too informal, C lacks detail, and D is overly demanding.
12 / 28
David, an architect, is writing a section of a System Design Document outlining the decision to migrate from SOAP to gRPC. Which sentence best reflects the formal register required for this document?
Option B utilizes formal language, explaining the rationale behind the decision (improved performance and reduced overhead) in a structured manner. It avoids subjective opinions ('faster and cooler') and focuses on objective technical benefits. Options A is too informal, C is directive, and D lacks context.
13 / 28
During a daily standup meeting, Ben reports a bug he found while testing a new feature. Which of the following statements is the most appropriate way for him to communicate this information?
Option B provides a clear and concise description of the issue without excessive detail or emotive language. It focuses on the observable behavior and avoids blaming or demanding immediate action. Options A is too informal, C is overly reliant on asking for help, and D is overly specific.
14 / 28
Sarah, the DevOps engineer, needs to quickly report a database outage to her team on Slack. Which of the following messages best reflects an appropriate level of formality for this situation?
Option B uses precise language and avoids overly casual phrasing like 'totally down,' suitable for a rapid team update. It clearly states the problem's impact and indicates action being taken. Options A is too informal, C is vague, and D is unnecessarily formal for this immediate notification.
15 / 28
Lena, a junior developer, receives an email from the API team detailing a recent performance degradation. The email states: 'The service is currently experiencing high latency and occasional timeouts.' Which of the following responses should she send in reply?
Option B maintains a professional tone while clearly articulating the issue and indicating an ongoing investigation. It avoids overly casual language like 'Sounds bad!' or simplistic statements, demonstrating appropriate communication for a technical update. Options A is too informal, C lacks detail, and D is overly demanding.
16 / 28
David, an architect, is writing a section of a System Design Document outlining the decision to migrate from SOAP to gRPC. Which sentence best reflects the formal register required for this document?
Option B utilizes formal language, explaining the rationale behind the decision (improved performance and reduced overhead) in a structured manner. It avoids subjective opinions ('faster and cooler') and focuses on objective technical benefits. Options A is too informal, C is directive, and D lacks context.
17 / 28
During a daily standup meeting, Ben reports a bug he found while testing a new feature. Which of the following statements is the most appropriate way for him to communicate this information?
Option B provides a clear and concise description of the issue without excessive detail or emotive language. It focuses on the observable behavior and avoids blaming or demanding immediate action. Options A is too informal, C is overly reliant on asking for help, and D is overly specific.
18 / 28
Mark is reviewing a PR that uses the curl command to debug an API endpoint. The comment reads: 'This isn't working – the response is just returning gibberish!' Which of the following options best captures Mark's feedback in a more appropriate register for a code review?
Insufficient – Mark's original statement is too informal for a code review. The correct response provides precise, technical feedback about the data mismatch, using standard terminology and requesting specific action. Option B is overly emotive and unprofessional; options C and D lack clarity.
19 / 28
Elena, a senior backend engineer, needs to briefly update the team on a performance issue with their new caching layer. Which of the following statements is most suitable for a Slack message?
Insufficient - Elena's initial statement is too formal and technical for a quick update on Slack. Option B offers a concise and professional description of the issue without jargon. Options A and D are overly detailed; option C is far too informal.
20 / 28
A developer is writing a PR description for a change that improves API response times. Which sentence best conveys the technical impact of the modification?
Insufficient – The other options are too vague or informal. Option 2 clearly states the technical impact (reduced latency and improved performance) using precise terminology. It's a professional way to describe the change without relying on subjective claims like 'faster now.'
21 / 28
Alex, a QA engineer, is writing a comment on a code review for a newly submitted pull request. The PR introduces a change to the authentication flow using JWTs. Which of the following statements would be most appropriate and professional in this context?
The implementation seems straightforward and aligns with our existing security best practices.
The original prompt asks for a formal and constructive comment. Option B directly suggests improvements with specific details (logging) which is typical of a code review. Options A and C are too informal/demanding; option D focuses on monitoring rather than the technical implementation itself. The phrase 'looks good' is also appropriate in this scenario.
22 / 28
During a standup meeting, Liam reports a problem he encountered while deploying a new microservice. He says: 'The thing just failed!' Which of the following options best represents a more polished and informative way for Liam to communicate this issue?
The deployment process experienced an unexpected error during the final stage.
Liam's initial statement is too casual and lacks technical detail. Option B offers a concise and professional description of the issue, acknowledging the need for investigation without resorting to overly informal language. Options A and D are too abrupt; option C provides a slightly more detailed, but still acceptable, alternative.
23 / 28
You're crafting an API response to a user's request for their order history. The response includes a list of orders and their associated details. Which sentence is the most suitable way to phrase this in a technical document?
The API returns a JSON array containing all completed orders with relevant information such as ID, date, total amount, and status.
Option B is too informal. Option A is also not suitable for a technical document. Option C accurately describes the API response in formal language, specifying the format (JSON array) and the data included (ID, date, total amount, status). Option D is overly simplistic.
24 / 28
Mark is writing a Slack message to his team about an intermittent issue with a new feature. Which of the following options best conveys the severity and nature of the problem?
We're seeing occasional performance degradation with the new feature, primarily during peak usage times. Further investigation is required to determine the root cause.
Mark's initial statement is too vague and potentially alarming. Option C provides a precise description of the problem (intermittent performance degradation, peak usage), highlighting its impact (response times) and indicating the need for further investigation – all in appropriate formal language for Slack. Options A and D are overly dramatic; option B is still too informal.
25 / 28
Maria, a data engineer, needs to update her team on a recent issue with their data pipeline. She sends a Slack message saying: 'The ETL job failed! Seriously messed up.' Which of the following phrases is most appropriate for Maria's communication in this context?
Insufficient – Maria's initial message is too informal and doesn't convey the seriousness of the issue. Option A provides a professional and detailed description of the failure, outlining the consequences (data inconsistencies) and suggesting next steps. Options B and C are overly casual, while option D lacks specific information.
26 / 28
David, an architect, is documenting a proposed upgrade to their monitoring system. He writes: 'We're switching to Prometheus for better metrics collection.' Which of the following sentences best reflects the appropriate formality and precision required in this document?
Insufficient – David's original statement is too informal and lacks technical precision. Option A uses formal language, clearly stating the purpose of the migration (metrics collection) and specifying Prometheus as a time-series database. Options B and C are colloquial, while option D is incomplete.
27 / 28
Kevin, a DevOps engineer, is reporting a problem during a daily standup meeting: 'The server keeps crashing.' Which of the following responses is most suitable for Kevin's update?
Insufficient – Kevin's initial statement is vague and doesn't offer any actionable information. Option A prompts for specific details (error message) which are crucial for troubleshooting. Options B and C are too informal, while option D lacks a commitment to investigation.
28 / 28
During a standup meeting, Mark reports an issue with a deployed application: 'The app is timing out.' Which of the following responses is most suitable for Mark's update, demonstrating technical awareness and professionalism?
Option 2 provides context and suggests a possible cause (bottlenecks) while also stating that investigation is underway. It's more informative than simply saying 'it's not working.' Options 1 and 3 are too informal, and option 4 lacks detail.
What will I practise in "Register Shifting: Formal to Informal in IT English — Grammar Exercise"?
Practice choosing appropriate register across IT documentation, Slack, standups, PR comments, and executive reports. 5 exercises, Intermediate level.
How many exercises are in this module?
This module has 28 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
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.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.