5 exercises — practise impersonal passive reporting patterns in postmortems and status updates.
0 / 8 completed
1 / 8
Which sentence correctly uses the impersonal passive "it is reported that" pattern in an incident summary?
"It is reported that..." is correct: this impersonal passive pattern uses dummy subject "it" + passive reporting verb + "that"-clause to attribute a claim without naming the source, a common hedge in incident summaries when the reporting source is a monitoring system or unconfirmed source. Option B scrambles the auxiliary and participle order ("it reported is"), which is ungrammatical. Option C incorrectly forms this as a question via inversion, which does not fit a declarative statement. Option D misplaces "that" after "reported the outage" instead of before the clause it introduces, breaking the clause boundary.
2 / 8
Which sentence correctly uses the "subject + is reported to + infinitive" raised-passive pattern as an alternative to "it is reported that"?
"The root cause is reported to have been a memory leak" is correct: this is the "subject-raising" passive alternative to "it is reported that the root cause was...", where the logical subject of the "that"-clause ("the root cause") is promoted to the main clause subject, followed by "to have been" (a perfect infinitive expressing that the reported event happened before now). Option B incorrectly mixes "reported that" with an infinitive-style raised subject, which is not a valid combination — "reported that" requires a full finite clause, not "have been". Option C inverts the word order ungrammatically. Option D places "reported" between the subject and "is", disrupting the required auxiliary-participle sequence.
3 / 8
Which sentence correctly uses "it is believed that" to hedge an unconfirmed technical claim in a postmortem?
"It is believed that..." is correct: this passive hedging construction distances the writer from full certainty about the claim, appropriate for a postmortem where root cause is still "pending further investigation". Option B uses "believes" without the passive auxiliary "is" and without a valid subject for the active verb (dummy "it" cannot actively "believe" something) — this misuses "it" as if it were an animate subject. Option C misplaces "that" after "the race condition" rather than immediately after "believed", breaking the clause. Option D incorrectly uses the progressive "-ing" form ("is believing"), which does not fit this fixed reporting-passive pattern; belief verbs like "believe" are not normally used in the progressive.
4 / 8
Choose the sentence with the correct tense sequencing in a raised passive describing a past technical event reported now.
"Is understood to have affected" is correct: the perfect infinitive "to have affected" signals that the affecting happened before the present reporting moment (all pre-2.0 versions were already released and already affected), matching how the claim is currently understood. Option A uses the plain infinitive "to affect", which would suggest an ongoing or future-oriented state rather than a completed past situation now being reported on — a subtly different, less accurate meaning for versions already released. Option C incorrectly uses a gerund "to affecting", which is not a valid infinitive form. Option D scrambles the word order, placing "understood" between the subject and "is".
5 / 8
A status update says: "_____ that the fix will be backported to the LTS branch next week." Choose the correct impersonal passive opening.
"It is expected that..." is correct: the passive reporting pattern with dummy subject "it" is the standard impersonal way to convey a plan or forecast without naming who specifically expects it (the team, management, etc.), fitting the hedged, professional tone of a status update. "It expects" (option B) incorrectly treats "it" as an active, animate subject capable of expecting something, which is not idiomatic here. "It is expecting" (option C) uses the progressive form, which does not fit this fixed stative-passive reporting pattern. "Expected it is" (option D) scrambles the word order into a non-standard, ungrammatical sequence.
6 / 8
During a daily stand-up meeting, David says: 'The performance degradation on the search index was reported to our team yesterday.' What's the most accurate way to complete this sentence for clarity?
Again, using 'the search index degradation has been reported' correctly employs the raised-passive structure. This maintains a neutral tone and avoids assigning ownership of the observation to David. Option A is too verbose; option C misrepresents the timing of the reporting; and option D incorrectly attributes the statement.
7 / 8
John wrote in a PR description: 'The database migration was completed successfully. It is reported that the data synchronization process took 3 hours.' Which sentence best completes this statement to provide crucial context?
The raised passive construction focuses on reporting an event. Option A provides a more precise description of the measurement than simply stating 'it took 3 hours.' Options B and C are grammatically awkward. Option D is overly verbose and lacks clarity regarding the migration itself.
8 / 8
During a standup meeting, Emily says: 'The database query performance degradation was reported to have increased by 30%.' What is the best way to complete this sentence for clarity and precision?
Using 'reported to increase' is the most natural and accurate way to convey a measured technical observation. The other options either use incorrect prepositional phrases or unnecessarily repeat the reporting action, making the sentence less clear and more verbose.
What will I practise in "Reporting Verb Passives in Technical English — IT Grammar Exercise"?
Practise impersonal passive reporting patterns like it is reported/believed/understood that, and the raised-subject alternative, for hedged attribution in
How many exercises are in this module?
This module has 8 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.