5 exercises — distinguish formal stakeholder communication from informal team chat and master the vocabulary of each register.
0 / 20 completed
1 / 20
A message is being sent to the CTO and external stakeholders about a service outage. Which message is most appropriate?
Stakeholder communication requires formal register: complete sentences, precise timestamps, professional vocabulary ("service disruption", "remediation", "postmortem"), and commitment to follow-up. Option A uses informal vocabulary ("prod", "probs", emoji) inappropriate for a CTO/external audience. Option C uses abbreviations and sentence fragments unsuitable for formal communication. Option D is brief and direct but lacks the precision and professionalism expected in executive communication.
2 / 20
A developer is messaging their team on Slack to ask for help with a deployment blocker. Which message matches the informal Slack register?
Slack messages to teammates use informal register: lowercase, no full stop, contractions, direct language, quick question. Option B is natural Slack communication. Option A is absurdly over-formal for a team chat. Option C is telegraphic (appropriate for a ticket summary but cold for a Slack request). Option D is formal and complete — suitable for an email but stilted for Slack.
3 / 20
Which version of this finding is most appropriate for a formal incident report?
Formal technical writing uses nominalisation: "investigation revealed" (not "we found out"), "misconfiguration" (not "wrong config"), "service degradation" (not "things broke"), "primary contributing factor" (precise causal language). This register is required in postmortems, SLA breach reports, and audit-facing documents. Options A and D use informal phrasal verbs and vague vocabulary. Option C is too terse for a formal report.
4 / 20
A formal change management document needs to record who approved a deployment. Which sentence is most appropriate for formal documentation?
Formal documentation often uses passive voice with a named agent ("was approved by the infrastructure team lead") — this is more precise about role than personal name ("Jake"), which may not be meaningful to all readers. Passive voice in formal documents depersonalises actions appropriately. Option A is correct but uses a first name (informal/potentially ambiguous in large organisations). Option C is vague. Option D is informal and lacks precision.
5 / 20
Which sentence contains a register mismatch inappropriate for a client-facing SLA report?
"Basically", "ran out of servers", and "we've sorted it" are informal phrases entirely inappropriate for a formal SLA report sent to clients. "Sorted it" is a phrasal verb typical of casual speech. "Ran out of servers" lacks the technical precision expected in formal incident documentation. Options A, B, and D use appropriate formal vocabulary and structure for client-facing SLA communications.
6 / 20
Alex from the Infrastructure team sent this message to the development team regarding a failing automated test:
'This thing is broken. Seriously, fix it ASAP!'
Which of the following best describes the register used in Alex's message?
Alex's message uses casual language ('thing', 'fix ASAP') and a somewhat demanding tone. This aligns with an informal register common in internal Slack conversations when immediate action is needed. Formal communication would prioritize clear technical descriptions and a respectful request for assistance. The use of exclamation marks also contributes to the informal style.
7 / 20
You're writing a pull request description for a minor bug fix related to user authentication. Which of the following options best demonstrates formal register? Consider the purpose of this document – to clearly communicate changes to reviewers and maintain an accurate record.
Option A: 'Fixed a small issue with logins. No big deal.'
Option B: 'Implemented a correction to address a vulnerability in the user authentication process, improving security compliance.'
Option C: 'Quick fix for login problems. Let me know if you need more details.'
Option D: 'Resolved an error that prevented some users from logging in – it's now working!'
Option B uses precise terminology (vulnerability, authentication process, security compliance) and a formal tone suitable for a PR description. It clearly states the purpose of the change and its impact. The other options are too informal – using phrases like 'no big deal' or overly casual language is inappropriate for documenting technical changes in a professional setting.
8 / 20
During a standup meeting, Sarah reports the following:
'I'm stuck on this API endpoint. It's giving me some weird errors and I can't figure out why.'
Which of the following best describes the register used in Sarah's statement?
Sarah's statement is typical of informal communication during a standup. It's concise, focuses on the immediate issue, and doesn't delve into excessive detail. The register is relaxed and geared towards quick updates within a team setting. A formal update would require more context and a structured explanation.
9 / 20
You are drafting an email to a client outlining the root cause of a recent service degradation. Which sentence demonstrates the most appropriate level of formality?
Option A: 'The system had a hiccup and briefly went down.'
Option B: 'Following a thorough investigation, we identified a configuration error within the load balancer that resulted in intermittent connectivity issues.'
Option C: 'We're looking into it. It should be fixed soon!'
Option D: 'There was an issue with the server. We're working on it.'
Option B utilizes precise technical language (configuration error, load balancer, connectivity issues) and a professional tone suitable for communicating with clients about complex technical problems. It avoids overly simplistic explanations or vague statements. The other options are too informal and lack the detail needed to reassure a client.
10 / 20
David, a senior engineer, is reviewing Emily's code. Emily's comment in the commit message reads: 'Fixed the bug'.
Which of the following statements best describes why this comment is an example of an inappropriate register?
A) It lacks technical detail and doesn't explain what the bug was or how it was fixed.
B) It uses overly complex jargon that would confuse other developers.
C) It's too verbose and provides unnecessary information about the code change.
D) It's perfectly acceptable, as brevity is valued in commit messages.
Option A accurately identifies the problem: the comment lacks crucial technical details. A formal register requires sufficient context to allow reviewers to understand the change fully. While brevity is desirable, it shouldn't come at the expense of clarity and explanation—a good commit message should provide enough information for another developer to quickly grasp the purpose of the modification.
11 / 20
Alex from the Infrastructure team sent this message to the development team regarding a failing automated test:
'This thing is broken. Seriously, fix it ASAP!'
Which of the following best describes the register used in Alex's message?
Alex's message uses casual language ('thing', 'fix ASAP') and a somewhat demanding tone. This aligns with an informal register common in internal Slack conversations when immediate action is needed. Formal communication would prioritize clear technical descriptions and a respectful request for assistance. The use of exclamation marks also contributes to the informal style.
12 / 20
You're writing a pull request description for a minor bug fix related to user authentication. Which of the following options best demonstrates formal register? Consider the purpose of this document – to clearly communicate changes to reviewers and maintain an accurate record.
Option A: 'Fixed a small issue with logins. No big deal.'
Option B: 'Implemented a correction to address a vulnerability in the user authentication process, improving security compliance.'
Option C: 'Quick fix for login problems. Let me know if you need more details.'
Option D: 'Resolved an error that prevented some users from logging in – it's now working!'
Option B uses precise terminology (vulnerability, authentication process, security compliance) and a formal tone suitable for a PR description. It clearly states the purpose of the change and its impact. The other options are too informal – using phrases like 'no big deal' or overly casual language is inappropriate for documenting technical changes in a professional setting.
13 / 20
During a standup meeting, Sarah reports the following:
'I'm stuck on this API endpoint. It's giving me some weird errors and I can't figure out why.'
Which of the following best describes the register used in Sarah's statement?
Sarah's statement is typical of informal communication during a standup. It's concise, focuses on the immediate issue, and doesn't delve into excessive detail. The register is relaxed and geared towards quick updates within a team setting. A formal update would require more context and a structured explanation.
14 / 20
You are drafting an email to a client outlining the root cause of a recent service degradation. Which sentence demonstrates the most appropriate level of formality?
Option A: 'The system had a hiccup and briefly went down.'
Option B: 'Following a thorough investigation, we identified a configuration error within the load balancer that resulted in intermittent connectivity issues.'
Option C: 'We're looking into it. It should be fixed soon!'
Option D: 'There was an issue with the server. We're working on it.'
Option B utilizes precise technical language (configuration error, load balancer, connectivity issues) and a professional tone suitable for communicating with clients about complex technical problems. It avoids overly simplistic explanations or vague statements. The other options are too informal and lack the detail needed to reassure a client.
15 / 20
David, a senior engineer, is reviewing Emily's code. Emily's comment in the commit message reads: 'Fixed the bug'.
Which of the following statements best describes why this comment is an example of an inappropriate register?
A) It lacks technical detail and doesn't explain what the bug was or how it was fixed.
B) It uses overly complex jargon that would confuse other developers.
C) It's too verbose and provides unnecessary information about the code change.
D) It's perfectly acceptable, as brevity is valued in commit messages.
Option A accurately identifies the problem: the comment lacks crucial technical details. A formal register requires sufficient context to allow reviewers to understand the change fully. While brevity is desirable, it shouldn't come at the expense of clarity and explanation—a good commit message should provide enough information for another developer to quickly grasp the purpose of the modification.
16 / 20
Alex from the Infrastructure team sent this message to the development team regarding a failing automated test:
'This thing is broken. Seriously, fix it ASAP!'
Which of the following best describes the register used in Alex's message?
Alex's message uses casual language ('thing', 'fix ASAP') and a somewhat demanding tone. This aligns with an informal register common in internal Slack conversations when immediate action is needed. Formal communication would prioritize clear technical descriptions and a respectful request for assistance. The use of exclamation marks also contributes to the informal style.
17 / 20
You're writing a pull request description for a minor bug fix related to user authentication. Which of the following options best demonstrates formal register? Consider the purpose of this document – to clearly communicate changes to reviewers and maintain an accurate record.
Option A: 'Fixed a small issue with logins. No big deal.'
Option B: 'Implemented a correction to address a vulnerability in the user authentication process, improving security compliance.'
Option C: 'Quick fix for login problems. Let me know if you need more details.'
Option D: 'Resolved an error that prevented some users from logging in – it's now working!'
Option B uses precise terminology (vulnerability, authentication process, security compliance) and a formal tone suitable for a PR description. It clearly states the purpose of the change and its impact. The other options are too informal – using phrases like 'no big deal' or overly casual language is inappropriate for documenting technical changes in a professional setting.
18 / 20
During a standup meeting, Sarah reports the following:
'I'm stuck on this API endpoint. It's giving me some weird errors and I can't figure out why.'
Which of the following best describes the register used in Sarah's statement?
Sarah's statement is typical of informal communication during a standup. It's concise, focuses on the immediate issue, and doesn't delve into excessive detail. The register is relaxed and geared towards quick updates within a team setting. A formal update would require more context and a structured explanation.
19 / 20
You are drafting an email to a client outlining the root cause of a recent service degradation. Which sentence demonstrates the most appropriate level of formality?
Option A: 'The system had a hiccup and briefly went down.'
Option B: 'Following a thorough investigation, we identified a configuration error within the load balancer that resulted in intermittent connectivity issues.'
Option C: 'We're looking into it. It should be fixed soon!'
Option D: 'There was an issue with the server. We're working on it.'
Option B utilizes precise technical language (configuration error, load balancer, connectivity issues) and a professional tone suitable for communicating with clients about complex technical problems. It avoids overly simplistic explanations or vague statements. The other options are too informal and lack the detail needed to reassure a client.
20 / 20
David, a senior engineer, is reviewing Emily's code. Emily's comment in the commit message reads: 'Fixed the bug'.
Which of the following statements best describes why this comment is an example of an inappropriate register?
A) It lacks technical detail and doesn't explain what the bug was or how it was fixed.
B) It uses overly complex jargon that would confuse other developers.
C) It's too verbose and provides unnecessary information about the code change.
D) It's perfectly acceptable, as brevity is valued in commit messages.
Option A accurately identifies the problem: the comment lacks crucial technical details. A formal register requires sufficient context to allow reviewers to understand the change fully. While brevity is desirable, it shouldn't come at the expense of clarity and explanation—a good commit message should provide enough information for another developer to quickly grasp the purpose of the modification.
What will I practise in "Formal vs Informal Register in IT English — Grammar Exercise"?
Practise formal and informal register in IT writing: stakeholder emails vs Slack messages, nominalisation, passive voice, professional vocabulary.
How many exercises are in this module?
This module has 20 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.