Review: Clauses That Identify the Right Thing

By the end of this lesson, you will be able to...

• Map a relative clause to the noun, person, component, place, time, or reason it describes.

• Repair a short technical update using who, which, that, where, when, and why.

• Decide whether a clause selects a subset or adds information about an already known object.

Idea in one sentence: Before editing the words, identify the target, the information boundary, and the evidence relation that the clause is supposed to express.

Core Insight

Consider a session-cleanup migration that fails in one region while the team is writing a status update. This one incident will test every clause decision before the next cluster introduces modifiers.

What You Can Now See

The first four lessons built one connected habit:

1. A clause can select the component that owns a responsibility.
2. Who, which, and that depend on the head noun and the role inside the clause.
3. No commas usually means the clause selects the noun; commas mark extra information about a noun already identified.
4. Where, when, and why attach place, time, and reason context, but they do not prove causality by themselves.

The review task is not to repeat these definitions. It is to use them together while reading an incident note.

The Synthesis Situation: A Session Cleanup Incident

At 14:00, a team deploys a session-cleanup migration. The system has two cleanup workers, a session table, a gateway, and three regions. During the deploy:

• one worker fails while running the old image;
• the table that stores active sessions grows quickly;
• latency rises in eu-west;
• retries increase after the migration, but the cause is still under investigation;
• Priya approved the migration and is now on call.

The facts are manageable. The first draft is not:

The worker that failed was running the old image. The engineer which approved the migration is on call. The table, that stores sessions, grew during the deploy. The region when traffic spiked had higher latency. The reason where retries increased is unclear.

Every sentence contains a real idea, but the clauses do not all perform the right job. A reader has to repair the people, the information boundary, and the context relation while also investigating the incident.

The trade-off in this review is compression versus inspection. Relative clauses let the writer connect facts without repeating every noun, but a compressed sentence can hide the target or make a hypothesis sound proven. The best revision is the shortest one that leaves the incident map recoverable.

The Four-Pass Review Method

Use four passes. Do not start by choosing a connector.

Pass 1: Mark the head noun

Underline the noun that the clause describes. Ask whether it is a person, a component, a group, a place, a time, or a reason.

The worker [that failed] was running the old image.
The engineer [which approved the migration] is on call.
The table [, that stores sessions,] grew during the deploy.
The region [when traffic spiked] had higher latency.
The reason [where retries increased] is unclear.

The first sentence has a worker. The second has an engineer. The third has a table. The fourth has a region. The fifth has a reason. Once the head nouns are visible, several repairs become predictable.

Pass 2: Ask what role and form the clause needs

For a person, who keeps the human referent clear. For a non-human component or artifact, which or that can work in a defining clause. Then ask whether the head noun acts or receives the action inside the clause.

The engineer who approved the migration is on call.

The engineer approved the migration, so the engineer is the subject.

The migration that the engineer approved starts at 14:00.

The engineer approved the migration, so the migration is the object.

The sentence does not become correct merely because it contains a relative word. The relative word and the words around it must preserve the intended roles.

Pass 3: Test the information boundary

Remove the clause and see whether the head noun still identifies the same target.

The worker that failed was running the old image.
The worker was running the old image.

There are two workers. The clause selects one, so it is defining and has no commas.

Now use a known name:

The session table, which stores active sessions, grew during the deploy.

The session table is already the target. The clause adds a useful fact, so commas mark it as extra information.

Do not use commas because the sentence feels long. Use them because the reader no longer needs the clause to identify the noun.

Pass 4: Check the context and evidence relation

Ask whether the clause expresses place, time, or reason:

The region where traffic spiked had higher latency.
The window when retries increased lasted eight minutes.
We are investigating why retries increased.

Where locates. When gives a time boundary. Why names the explanation under investigation. None of these forms proves that the location or time caused the symptom.

Repair the Incident Note

Now repair each sentence from the draft.

1. Keep the defining worker clause

The worker that failed was running the old image.

This sentence already works. There are two workers, so that failed selects the one under discussion. The clause is defining.

2. Make the person visible

Draft:

The engineer which approved the migration is on call.

Repair:

The engineer who approved the migration is on call.

Engineer is a person, and who is the natural choice. The clause identifies the engineer; it does not add a comment about a person already named.

If the report has already introduced Priya, a different boundary is appropriate:

Priya, who approved the migration, is on call.

The name is unique, so the comma clause adds context.

3. Repair the table clause

Draft:

The table, that stores sessions, grew during the deploy.

The comma-plus-that combination is not the standard form for an extra non-human clause. Choose the information boundary first.

If several tables exist and the session table must be selected:

The table that stores active sessions grew during the deploy.

If the report has already named the session table:

The session table, which stores active sessions, grew during the deploy.

Both can be correct. The incident context decides whether the clause identifies or comments.

4. Repair the region clause

Draft:

The region when traffic spiked had higher latency.

Repair:

The region where traffic spiked had higher latency.

The clause describes an event inside a place, so where attaches to region. If the report has already named eu-west, write:

Eu-west, where traffic spiked, had higher latency.

The first version selects a region. The second adds context about a known region.

5. State the reason as an investigation

Draft:

The reason where retries increased is unclear.

Repair:

We are investigating why retries increased after the migration.

Why introduces the reason question. Where cannot attach to reason for this job. The revised sentence also keeps the evidence status honest: the team is investigating rather than claiming a root cause.

The Repaired Update

Put the sentences back together:

The worker that failed was running the old image. The engineer who approved the migration is on call. The session table, which stores active sessions, grew during the deploy. The region where traffic spiked had higher latency. We are investigating why retries increased after the migration.

The paragraph is still compact, but each reader question has an answer:

The paragraph does not pretend to know more than the evidence. It identifies the worker and region, reports the table behavior, and leaves the retry cause open.

Retrieval Checks

Use these quick decisions without looking back at the explanations.

Check: There are three queues, and only one receives messages from the failing worker. Which sentence selects it?

A. The queue, which receives messages from the worker, was full.

B. The queue that receives messages from the worker was full.

Think first, then reveal.

Answer: B. The clause answers “which queue?” and therefore defines the target. A would require the queue to be already identified.

Check: The report has already named us-east. Which sentence adds the traffic fact?

A. The region where traffic spiked had higher latency.

B. Us-east, where traffic spiked, had higher latency.

Think first, then reveal.

Answer: B. The proper name identifies the region; the comma clause adds context.

Check: Which sentence reports a reason under investigation rather than a proven cause?

A. We are investigating why retries increased after the migration.

B. The migration when retries increased caused every error.

Think first, then reveal.

Answer: A. Why introduces the open explanation. When only places events in time and cannot prove causality.

Transfer: Review a Deployment Note

A second team writes this note:

The gateway which rejected the request was restarted. The engineer, that changed the timeout, is on call. The cluster when latency rose is still serving traffic. We are checking the reason where the queue grew.

Repair it in four passes. A strong revision is:

The gateway that rejected the request was restarted. The engineer who changed the timeout is on call. The cluster where latency rose is still serving traffic. We are checking why the queue grew.

If the gateway and engineer have already been named, extra-information versions are also possible:

Gateway B, which rejected the request, was restarted. Priya, who changed the timeout, is on call.

A good answer should:

• identify the head noun in each sentence;
• use who for the individual engineer;
• use that or which consistently for the gateway, depending on the information boundary;
• use where for the cluster and why for the reason;
• avoid claiming that the restart or timeout caused the queue growth without evidence.

Daily Practice Lines

• The worker that failed was running the old image.
• The region where traffic spiked had higher latency.
• We are investigating why retries increased after the migration.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Relative clauses - Focus: retrieve defining, non-defining, and context-clause patterns while editing the incident note.
• [ARTICLE] Microsoft Writing Style Guide: Grammar - Focus: choose punctuation and sentence boundaries that keep technical scope visible.

Key Takeaways

• Map the head noun before choosing the relative word.
• Use defining clauses to select a component, person, place, or subset; use commas for extra information about a known target.
• Use where for place, when for time, and why for an explanation under discussion.
• Check whether the clause changes operational scope and whether the evidence supports the claim.
• Compact English is useful only when another engineer can recover the same incident map.