Narrative Tenses (Past Simple, Past Continuous, Past Perfect, Past Perfect Continuous) – English Grammar Exercises for B2

1  (b) was monitoring

• Why it is correct: Past Continuous. It sets the ongoing background action that was abruptly interrupted by the database going offline (Past Simple).
• Error Analysis: (a) monitored (Common Mistake – fails to show the action was in progress); (c) had monitored (Meaning Trap – implies the monitoring was completely finished before the crash); (d) was monitored (Structural Error – incorrect passive voice).

2  (a) shut

• Why it is correct: Past Simple. It represents a sudden, definitive event that moved the narrative timeline forward.
• Error Analysis: (b) was shutting (Meaning Trap – shutting down abruptly is an instantaneous failure, not a gradual background process here); (c) had shut (Common Mistake – incorrect sequence, it didn’t happen before the previous sentence’s timeline); (d) shuts (Structural Error).

3  (c) had risen

• Why it is correct: Past Perfect. The temperature had already reached a critical level before the engineer checked the room.
• Error Analysis: (a) rose (Common Mistake – implies the temperature started rising exactly when he checked); (b) was rising (Meaning Trap – implies it was currently going up, but “to a critical level” suggests it had already achieved that state); (d) has risen (Structural Error).

4  (d) had been draining

• Why it is correct: Past Perfect Continuous. It clearly describes a hidden, ongoing process that accumulated over time (“for over three hours”) right up until the past moment of the crash.
• Error Analysis: (a) was draining (Common Mistake – ignores the duration marker “for over three hours”); (b) drained (Meaning Trap – lacks the emphasis on continuous, simmering activity); (c) has been draining (Structural Error).

5  (b) disconnected

• Why it is correct: Past Simple. Used for immediate, consecutive actions in the past (identified -> disconnected).
• Error Analysis: (a) had disconnected (Meaning Trap – timeline error, he didn’t disconnect it before identifying the threat); (c) was disconnecting (Common Mistake); (d) disconnect (Structural Error).

6  (c) was attempting

• Why it is correct: Past Continuous with “While” indicates a background action in progress when another short, sudden action (the generator failed) occurred.
• Error Analysis: (a) attempted (Common Mistake); (b) had attempted (Meaning Trap); (d) have attempted (Structural Error).

7  (b) had forgotten

• Why it is correct: Past Perfect. The failure happened in the narrative present (the incident), but the reason for the failure (forgetting the battery) happened much earlier (“last month”).
• Error Analysis: (c) forgot (Common Mistake – fails to emphasize the chronological gap between the two past events); (a) was forgetting (Meaning Trap); (d) has forgotten (Structural Error).

8  (c) was struggling

• Why it is correct: Past Continuous. Describes the ongoing state of the system while the terminal was simultaneously being flooded with errors.
• Error Analysis: (a) struggled (Common Mistake); (b) had struggled (Meaning Trap); (d) struggles (Structural Error).

9  (c) had already applied

• Why it is correct: Past Perfect. “By the time” sets a hard deadline in the past. The action of applying the patch was fully completed before the CTO arrived.
• Error Analysis: (a) already applied (Common Mistake – missing the auxiliary verb required for the sequence); (b) was already applying (Meaning Trap – implies the action was incomplete, changing the meaning); (d) had already apply (Structural Error).

10  (a) had been running

• Why it is correct: Past Perfect Continuous. Identifies the root cause: an intense, continuous action taking place over a duration (“all night long”) prior to the system failure.
• Error Analysis: (b) were running (Common Mistake – misses the ‘past before the past’ relationship); (c) ran (Meaning Trap); (d) have been running (Structural Error).

11  (c) was compressing

• Why it is correct: Past Continuous. The corruption (Past Simple) happened at the exact moment the system was in the middle of compressing the files.
• Error Analysis: (a) compressed (Common Mistake); (b) had compressed (Meaning Trap – logically flawed, if it had already finished compressing, it wouldn’t have crashed “while” doing it); (d) compresses (Structural Error).

12  (c) brought

• Why it is correct: Past Simple. Concludes a sequence of consecutive completed actions: bypassed -> cleared -> brought.
• Error Analysis: (a) had brought (Meaning Trap); (b) was bringing (Common Mistake); (d) bring (Structural Error).

13  (c) had detected

• Why it is correct: Past Perfect. The software identified the anomaly “hours earlier,” a clear indication of a past event occurring before the main timeline of the crash.
• Error Analysis: (a) detected (Common Mistake); (b) was detecting (Meaning Trap); (d) has detected (Structural Error).

14  (b) had been sitting

• Why it is correct: Past Perfect Continuous. Emphasizes the continuous, uninterrupted state (“for six months”) before the sudden execution of the command in the past.
• Error Analysis: (a) was sitting (Common Mistake – fails to account for the duration leading up to a past event); (c) sat (Meaning Trap); (d) has been sitting (Structural Error).

15  (b) confirmed

• Why it is correct: Past Simple. The act of confirming happened sequentially later as part of the post-incident investigation.
• Error Analysis: (a) had confirmed (Meaning Trap – timeline error, they didn’t confirm it before the incident); (c) were confirming (Common Mistake); (d) confirm (Structural Error).

16  (c) was downloading

• Why it is correct: Past Continuous. The downloading was actively in progress and was abruptly stopped by the firewall activation (Past Simple).
• Error Analysis: (a) downloaded (Common Mistake); (b) had downloaded (Meaning Trap – if they had downloaded it completely, the firewall block would have been useless); (d) downloads (Structural Error).

17  (b) had been trying

• Why it is correct: Past Perfect Continuous. Represents a prolonged, repetitive effort (“for weeks”) that culminated in a past success (“finally succeeded”).
• Error Analysis: (a) were trying (Common Mistake); (c) tried (Meaning Trap); (d) have been trying (Structural Error).

18  (c) remained

• Why it is correct: Past Simple. A factual statement of the state of the data upon reviewing the aftermath.
• Error Analysis: (a) had remained (Meaning Trap – “remained” already implies a state of being left over, making Past Perfect redundant and awkward here); (b) was remaining (Common Mistake – stative concept); (d) remains (Structural Error – shifts to present tense in a past report).

19  (a) had implemented

• Why it is correct: Past Perfect. Standing in the past (informing the board), the engineer refers to an action completed even further back in the past (“last year”).
• Error Analysis: (b) implemented (Common Mistake – loses the depth of the timeline); (c) were implementing (Meaning Trap); (d) have implemented (Structural Error).

20  (c) had been working

• Why it is correct: Past Perfect Continuous. By a specific point in the past (“By 8:00 AM this morning”), the team’s continuous labor had accumulated to fourteen hours.
• Error Analysis: (a) was working (Common Mistake); (b) worked (Meaning Trap); (d) have been working (Structural Error).

In professional contexts such as Incident Reports or legal documentation, Narrative Tenses are essential for creating an objective, unambiguous timeline:

1. Past Simple (The Event Log): Used for single, completed actions. It is the core of the report, detailing exactly what failed and what actions were taken in chronological order (e.g., The system failed; I disconnected the server).
2. Past Continuous (The Environment): Used to document what the system or user was doing exactly at the moment of failure. It helps identify triggers (e.g., The crash happened while the system was compressing files).
3. Past Perfect (The Pre-existing Condition): Used to explain facts, configurations, or missed actions that were established before the incident occurred. It is vital for root cause analysis (e.g., The generator failed because they had forgotten to replace the battery).
4. Past Perfect Continuous (The Simmering Threat): The ultimate tool for diagnosing technical issues. It highlights prolonged, hidden activities that drained resources or compromised security over a specific duration before causing the ultimate failure (e.g., A script had been draining memory for three hours).