5 exercises — precise quantification in performance reports, incident metrics, and capacity planning.
Key patterns:
A threefold / twofold reduction/increase — multiplicative noun phrase
P99/P95 latency of [X ms] — standard percentile metric format
In the order of / approximately / roughly — hedged estimates
From X to Y, a reduction of Z% — before/after plus derived change
0 / 16 completed
1 / 16
A performance report needs to describe a dramatic improvement in build time. Which sentence quantifies the improvement most precisely and professionally?
"A threefold reduction" is precise quantification using a multiplicative noun phrase. It is more formal than "3x faster" and appropriate for written performance reports. Adding the before-and-after figures (from 18 minutes to just over 6 minutes) makes the metric independently verifiable. "Just over" is an honest hedging quantifier when the exact figure is 6.1 minutes. Option C is informal (or so). Option D is nonsensical (by about a lot). Related patterns: "a 40% reduction in", "a twofold increase", "reduced by a factor of three".
2 / 16
An incident metric report describes the tail latency. Which sentence is most precise for a p99 latency figure?
P99 latency (99th percentile) is the standard metric for describing tail latency in incident reports. A precise report names the metric (P99 latency), the peak value (1,240 ms), the time frame (during the incident window), and the baseline for comparison (180 ms). Option D uses north of — an informal approximation idiom that has a place in verbal communication but is too vague for a written report. Options A and C are uselessly vague. Related patterns: "P50/P95/P99 latency of", "error rate of approximately", "in the order of".
3 / 16
A capacity planning report estimates future traffic. Which sentence uses quantification language most appropriately for an estimate?
"In the order of [figure]" is a quantification hedge for estimates — it signals that the figure is an approximation of the correct magnitude rather than a precise measurement. Pairing it with an explicit basis (3× growth assumption over twelve months) makes the estimate auditable: if the assumption changes, the estimate changes proportionally. Option A is vague; option C is grammatically incoherent; option D is not a sentence. Related patterns: "approximately", "roughly", "up to", "at least".
4 / 16
A sprint review report needs to describe a partial improvement in error rate. Which sentence quantifies it most accurately?
Precision in sprint reviews requires before/after figures plus the derived percentage change. Reporting both the absolute values (2.3% to 0.4%) and the derived reduction (approximately 83%) allows stakeholders to verify the arithmetic and understand both the relative and absolute scale. Approximately hedges the derived percentage because 83.% is not a round number. Option C uses informal approximation (or something). Option D is too qualitative for a metrics report. Related patterns: "a 40% reduction in", "down from X to Y, a decrease of Z%".
5 / 16
A capacity planning document warns about approaching a system limit. Which sentence quantifies the risk most effectively?
"North of [threshold]" is an informal but widely used idiom in engineering communication meaning "above" — it is appropriate in sprint reviews and verbal updates but less so in formal reports. However, in this sentence it is balanced by precise figures: 87% (current), 80% (threshold), and approximately 2 GB per day (growth rate). The combination gives operations teams the three data points they need to plan a response. Option A and C lack the specific numbers required for action. Related patterns: "exceeding the target by", "within N% of the limit", "growing at a rate of".
6 / 16
Sarah from DevOps is reviewing a PR that adds logging to the authentication service. She needs to describe the impact of the new logging in her comment. Which sentence best quantifies the expected increase in log volume?
'Adding this logging will significantly improve debugging.'
A. 'We anticipate approximately 20% more logs generated per request.'
B. 'The logging will drastically reduce response times.'
C. 'This change will provide detailed audit trails.'
D. 'It's a simple addition, so the impact should be minimal.'
'We anticipate approximately 20% more logs generated per request.' offers a concrete and measurable quantification of the expected increase. Options B and C are qualitative descriptions of benefits, while option D is dismissive and lacks any numerical data. Quantifying impact with percentages is crucial for technical reporting to allow stakeholders to understand the scale of change.
7 / 16
Mark, a SRE, is drafting a Slack message regarding an API endpoint. The response time has degraded significantly during peak hours. Which sentence accurately describes the severity of the issue?
'The API is working fine.'
A. 'Average response times have increased by 50ms during periods of high traffic.'
B. 'Users are experiencing occasional slowdowns.'
C. 'We've identified a minor performance bottleneck.'
D. 'Everything is running smoothly and efficiently.'
'Average response times have increased by 50ms during periods of high traffic.' provides a precise quantification of the problem using measurable data (milliseconds) and context (peak hours). The other options are vague or dismissive, failing to communicate the seriousness of the issue. Accurate reporting needs specific metrics with context.
8 / 16
Sarah from DevOps is reviewing a PR that adds logging to the authentication service. She needs to describe the impact of the new logging in her comment. Which sentence best quantifies the expected increase in log volume?
'Adding this logging will significantly improve debugging.'
A. 'We anticipate approximately 20% more logs generated per request.'
B. 'The logging will drastically reduce response times.'
C. 'This change will provide detailed audit trails.'
D. 'It's a simple addition, so the impact should be minimal.'
'We anticipate approximately 20% more logs generated per request.' offers a concrete and measurable quantification of the expected increase. Options B and C are qualitative descriptions of benefits, while option D is dismissive and lacks any numerical data. Quantifying impact with percentages is crucial for technical reporting to allow stakeholders to understand the scale of change.
9 / 16
Mark, a SRE, is drafting a Slack message regarding an API endpoint. The response time has degraded significantly during peak hours. Which sentence accurately describes the severity of the issue?
'The API is working fine.'
A. 'Average response times have increased by 50ms during periods of high traffic.'
B. 'Users are experiencing occasional slowdowns.'
C. 'We've identified a minor performance bottleneck.'
D. 'Everything is running smoothly and efficiently.'
'Average response times have increased by 50ms during periods of high traffic.' provides a precise quantification of the problem using measurable data (milliseconds) and context (peak hours). The other options are vague or dismissive, failing to communicate the seriousness of the issue. Accurate reporting needs specific metrics with context.
10 / 16
Sarah from DevOps is reviewing a PR that adds logging to the authentication service. She needs to describe the impact of the new logging in her comment. Which sentence best quantifies the expected increase in log volume?
'Adding this logging will significantly improve debugging.'
A. 'We anticipate approximately 20% more logs generated per request.'
B. 'The logging will drastically reduce response times.'
C. 'This change will provide detailed audit trails.'
D. 'It's a simple addition, so the impact should be minimal.'
'We anticipate approximately 20% more logs generated per request.' offers a concrete and measurable quantification of the expected increase. Options B and C are qualitative descriptions of benefits, while option D is dismissive and lacks any numerical data. Quantifying impact with percentages is crucial for technical reporting to allow stakeholders to understand the scale of change.
11 / 16
Mark, a SRE, is drafting a Slack message regarding an API endpoint. The response time has degraded significantly during peak hours. Which sentence accurately describes the severity of the issue?
'The API is working fine.'
A. 'Average response times have increased by 50ms during periods of high traffic.'
B. 'Users are experiencing occasional slowdowns.'
C. 'We've identified a minor performance bottleneck.'
D. 'Everything is running smoothly and efficiently.'
'Average response times have increased by 50ms during periods of high traffic.' provides a precise quantification of the problem using measurable data (milliseconds) and context (peak hours). The other options are vague or dismissive, failing to communicate the seriousness of the issue. Accurate reporting needs specific metrics with context.
12 / 16
David from QA is reporting on a recent deployment of the new user onboarding flow. He needs to quantify the improvement in conversion rates for users completing the signup process. Which sentence best describes this improvement?
Option A provides a precise numerical quantification of the improvement – 'approximately 15%' is ideal for technical reporting. Options B and C are vague and subjective. Option D doesn't offer any specific data; it simply states the flow 'performed better'.
13 / 16
Ben from Development is writing a PR description for a new feature that reduces database query latency. He needs to quantify the expected performance gain. Which sentence best describes this?
Option 1 is too vague. Option 2 uses precise language – 'reduction in query execution time' – which is suitable for technical documentation and PR descriptions. Options 3 and 4 are subjective and don't provide a measurable metric.
14 / 16
Frank from Operations is creating a report on server CPU utilization. The average CPU usage has increased from 30% to 85% during peak hours. Which sentence best communicates this change?
Option 2 uses clear and direct language to describe the significant increase in CPU utilization (30% to 85%). It's crucial to accurately represent this data when communicating about system performance. Options 1, 3, and 4 are misleading or inaccurate.
15 / 16
Liam, a SRE, is drafting a Slack message regarding a database query performance issue. The average query latency has increased from 2ms to 15ms during peak load. Which sentence accurately describes the severity of this degradation?
'The database performance is experiencing some slowdowns.'
Option 1 provides the most impactful quantification. Stating the increase by a factor of 7.5 immediately highlights the severity. Options 2 and 3 are too vague about the magnitude of the change. Option 4 downplays the issue entirely – it's crucial to acknowledge performance degradation, especially when quantified.
16 / 16
Rajesh, a Technical Writer, is drafting an update for the system's monitoring dashboard. The number of failed requests to the payment processing service has increased from 1% to 5% during periods of high transaction volume. Which sentence best quantifies this change?
'The payment service is experiencing more errors.'
Option 0 provides a precise quantification of the problem – 'doubled' (5% compared to 1%). This immediately conveys the severity and urgency. The other options are too vague or dismissive of the issue. Quantifying increases in error rates is vital for understanding potential impact.
What will I practise in "Quantification Language in Technical Reporting — IT Grammar Exercise"?
Practice expressing precise quantities in performance reports, incident metrics, sprint reviews, and capacity planning documents.
How many exercises are in this module?
This module has 16 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.