5 exercises — practise converting verbs to nouns (implement→implementation, deploy→deployment, refactor→refactoring) to raise the register of sprint reports, postmortems, proposals, and architecture documents.
0 / 20 completed
1 / 20
A developer wants to make a technical report more formal. The draft reads: "We implemented the new caching layer last sprint." Which sentence uses nominalisation correctly to raise the register?
"The implementation of the new caching layer was completed last sprint." is the best nominalization. Nominalisation converts a verb (implement) into a noun (implementation), which becomes the grammatical subject or object. This increases information density and formality — essential in sprint reports, technical proposals, and architecture documents. The pattern is: verb → noun + "of" + object: implement → implementation of, deploy → deployment of, configure → configuration of. Option A ("the implementing of") uses a gerund, not a true nominalisation, and sounds unnatural in formal IT writing. Option C keeps the agent "we" with the nominalisation, which reduces the register gain.
2 / 20
A tech lead writes in a postmortem: "The service failed because we deployed too quickly." Which version correctly nominalises the verb deploy in a formal root-cause analysis?
"The service failure was due to a rapid deployment." nominalises both the cause (deploy → deployment) and the effect (fail → failure). This double nominalisation is characteristic of formal postmortems and incident reports. The structure "X was due to Y" with nominalised nouns is highly formal: "The outage was due to a misconfiguration of the load balancer", "The data loss was due to an incomplete rollback." Option A uses a gerund (deploying), which is informal. Option C uses the infinitive deploy rapidly — grammatically incorrect after "due to". Option D mixes informal gerund with the correct phrase structure.
3 / 20
An architecture document reads: "We need to authenticate users before they can access the dashboard." Which formal rewrite best nominalises this sentence?
"User authentication is required prior to dashboard access." demonstrates two nominalisations: authenticate → authentication and access (verb) → access (noun). The result is a compact, authoritative noun phrase typical of technical requirements documents and system design specs. Note the compound noun pattern: user authentication (noun + noun) rather than "authentication of users" — the compound form is more common in IT English. Similarly, dashboard access rather than "access to the dashboard". Option B ("the authenticating of") is a gerund phrase, not a true nominalisation. Option D drops the article before a singular countable noun ("authentication of user") — a grammatical error.
4 / 20
A software engineer writes a ticket title: "Refactor the payment module". The project manager wants a more formal noun-phrase title for the epic. Which option is correct?
"Payment module refactoring" is the most natural and concise nominalised epic title in IT English. In technical project management, epic and story titles use compound noun + nominalisation patterns: "Database migration", "API endpoint redesign", "Authentication flow refactoring". Note: refactoring (from the verb refactor) functions as a gerund-noun here — established as a standard IT term. Option A ("refactoring of the payment module") is grammatical but verbose for a title. Option C uses the non-standard "refactorisation" — the correct British nominalisation is refactoring in IT contexts. Option D is a full sentence, not a title.
5 / 20
A developer needs to make this sentence more formal for a technical proposal: "We will monitor performance and then optimise the queries if they run slowly." Which rewrite uses nominalisation most effectively?
"Performance monitoring will be conducted, with query optimisation to follow if degradation is detected." achieves the highest register through three nominalisations: monitor → monitoring, optimise → optimisation, and degrade → degradation. It also removes the first-person agent (we), which is typical of formal proposals and technical white papers. The structure uses passive voice with nominalisation — a combination that is the hallmark of advanced IT English in formal writing contexts. Option A is valid but uses the verbose "carry out" and "do" constructions. Option C repeats "the … of …" twice — technically correct but awkward. Option D retains the informal first person and uses gerunds rather than true nominalisations.
6 / 20
Senior is reviewing a pull request for the new API endpoint. The description reads: 'We processed the data and then returned it to the client.' Which revision best demonstrates nominalisation to improve clarity and professionalism in this code review context?
Nominalisation transforms verbs into nouns, creating more formal and precise statements. In this case, 'processing' becomes a noun phrase, clearly defining the action performed on the data. Option A is the most effective because it uses a nominalised verb phrase, avoiding the less direct phrasing of the original sentence which can sound somewhat conversational within a code review.
7 / 20
Product Manager is drafting an update for the daily standup. They state: 'The team implemented a new feature.' Which of the following options best demonstrates nominalisation to elevate the language and provide a more formal report on the progress?
Nominalisation involves converting verbs into nouns. 'Implementation' here acts as a noun phrase, providing a more formal and structured description of what the team achieved. Option 2 specifically uses 'implementation' correctly to elevate the language—the original sentence is acceptable in a casual setting but less suitable for a standup update or formal report. The other options are grammatically incorrect.
8 / 20
DevOps Engineer is writing the description for an automated deployment pipeline. The initial draft says: 'The system will scale automatically.' Which of the following options correctly uses nominalisation to enhance precision and formality in this technical document?
Nominalisation transforms verbs into nouns, creating a more precise technical description. 'Automatic scaling' is a standard noun phrase in DevOps, clearly defining the system's behavior. Option 2 correctly nominalises the verb 'scale', providing a formal and technically accurate description suitable for documenting an automated deployment pipeline.
9 / 20
QA Analyst is writing a bug report. The original text says: 'The application crashed when the user clicked the button.' Which revision best employs nominalisation to provide a more professional and detailed description of the issue?
Nominalisation transforms verbs into nouns, resulting in a more formal and precise description of the bug. 'A crash' is a standard technical term, while 'activating' provides a more specific noun phrase for describing the user action that triggered the error. Option 1 avoids conversational phrasing and clearly defines the event.
10 / 20
Architect is creating documentation for a new microservice. The draft reads: 'We will monitor the service's performance.' Which of the following options best employs nominalisation to create a more professional and formal description for this architectural document?
Nominalisation converts a verb phrase into a noun phrase for increased formality. 'Performance monitoring' is a standard term in IT architecture and clearly describes the action being taken. Option 2 provides the most formal and technically appropriate phrasing within this context – it's crucial to use established terminology when documenting architectural decisions.
11 / 20
Senior is reviewing a pull request for the new API endpoint. The description reads: 'We processed the data and then returned it to the client.' Which revision best demonstrates nominalisation to improve clarity and professionalism in this code review context?
Nominalisation transforms verbs into nouns, creating more formal and precise statements. In this case, 'processing' becomes a noun phrase, clearly defining the action performed on the data. Option A is the most effective because it uses a nominalised verb phrase, avoiding the less direct phrasing of the original sentence which can sound somewhat conversational within a code review.
12 / 20
Product Manager is drafting an update for the daily standup. They state: 'The team implemented a new feature.' Which of the following options best demonstrates nominalisation to elevate the language and provide a more formal report on the progress?
Nominalisation involves converting verbs into nouns. 'Implementation' here acts as a noun phrase, providing a more formal and structured description of what the team achieved. Option 2 specifically uses 'implementation' correctly to elevate the language—the original sentence is acceptable in a casual setting but less suitable for a standup update or formal report. The other options are grammatically incorrect.
13 / 20
DevOps Engineer is writing the description for an automated deployment pipeline. The initial draft says: 'The system will scale automatically.' Which of the following options correctly uses nominalisation to enhance precision and formality in this technical document?
Nominalisation transforms verbs into nouns, creating a more precise technical description. 'Automatic scaling' is a standard noun phrase in DevOps, clearly defining the system's behavior. Option 2 correctly nominalises the verb 'scale', providing a formal and technically accurate description suitable for documenting an automated deployment pipeline.
14 / 20
QA Analyst is writing a bug report. The original text says: 'The application crashed when the user clicked the button.' Which revision best employs nominalisation to provide a more professional and detailed description of the issue?
Nominalisation transforms verbs into nouns, resulting in a more formal and precise description of the bug. 'A crash' is a standard technical term, while 'activating' provides a more specific noun phrase for describing the user action that triggered the error. Option 1 avoids conversational phrasing and clearly defines the event.
15 / 20
Architect is creating documentation for a new microservice. The draft reads: 'We will monitor the service's performance.' Which of the following options best employs nominalisation to create a more professional and formal description for this architectural document?
Nominalisation converts a verb phrase into a noun phrase for increased formality. 'Performance monitoring' is a standard term in IT architecture and clearly describes the action being taken. Option 2 provides the most formal and technically appropriate phrasing within this context – it's crucial to use established terminology when documenting architectural decisions.
16 / 20
Senior is reviewing a pull request for the new API endpoint. The description reads: 'We processed the data and then returned it to the client.' Which revision best demonstrates nominalisation to improve clarity and professionalism in this code review context?
Nominalisation transforms verbs into nouns, creating more formal and precise statements. In this case, 'processing' becomes a noun phrase, clearly defining the action performed on the data. Option A is the most effective because it uses a nominalised verb phrase, avoiding the less direct phrasing of the original sentence which can sound somewhat conversational within a code review.
17 / 20
Product Manager is drafting an update for the daily standup. They state: 'The team implemented a new feature.' Which of the following options best demonstrates nominalisation to elevate the language and provide a more formal report on the progress?
Nominalisation involves converting verbs into nouns. 'Implementation' here acts as a noun phrase, providing a more formal and structured description of what the team achieved. Option 2 specifically uses 'implementation' correctly to elevate the language—the original sentence is acceptable in a casual setting but less suitable for a standup update or formal report. The other options are grammatically incorrect.
18 / 20
DevOps Engineer is writing the description for an automated deployment pipeline. The initial draft says: 'The system will scale automatically.' Which of the following options correctly uses nominalisation to enhance precision and formality in this technical document?
Nominalisation transforms verbs into nouns, creating a more precise technical description. 'Automatic scaling' is a standard noun phrase in DevOps, clearly defining the system's behavior. Option 2 correctly nominalises the verb 'scale', providing a formal and technically accurate description suitable for documenting an automated deployment pipeline.
19 / 20
QA Analyst is writing a bug report. The original text says: 'The application crashed when the user clicked the button.' Which revision best employs nominalisation to provide a more professional and detailed description of the issue?
Nominalisation transforms verbs into nouns, resulting in a more formal and precise description of the bug. 'A crash' is a standard technical term, while 'activating' provides a more specific noun phrase for describing the user action that triggered the error. Option 1 avoids conversational phrasing and clearly defines the event.
20 / 20
Architect is creating documentation for a new microservice. The draft reads: 'We will monitor the service's performance.' Which of the following options best employs nominalisation to create a more professional and formal description for this architectural document?
Nominalisation converts a verb phrase into a noun phrase for increased formality. 'Performance monitoring' is a standard term in IT architecture and clearly describes the action being taken. Option 2 provides the most formal and technically appropriate phrasing within this context – it's crucial to use established terminology when documenting architectural decisions.
What will I practise in "Nominalisation in IT English"?
Practise converting verbs to nouns (implement→implementation, deploy→deployment) in formal IT writing. 5 advanced exercises on nominalisation.
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.