Defining vs Extra Information

LESSON

Technical English: Clauses, Modifiers, and Comparison

003 20 min beginner

Defining vs Extra Information

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

  • Decide whether a relative clause identifies one item or adds a comment about an item already identified.

  • Use commas to show that difference in a technical sentence.

  • Predict how removing a clause changes the scope of an incident or design claim.

Idea in one sentence: No commas means “which one?”; commas mean “here is another fact about the one we already know.”

Core Insight

An incident commander is reviewing a failed deployment. The platform has three workers:

The first note says:

The worker that failed was running the old image.

The clause that failed answers a selection question. The platform has several workers. Which worker was running the old image? The one that failed.

Later, the incident commander has already named worker-b in the report:

Worker B, which was running the old image, failed during the deploy.

Now which was running the old image is an additional fact about the already identified Worker B. The commas tell the reader that the main noun is not waiting for the clause to find its identity.

The words inside the clause are similar. The punctuation changes the information structure and therefore changes the claim.

This is not a style decoration. In a status update, the difference can decide whether the team rolls back one worker or every worker in a group.

The trade-off is visible: a defining clause keeps selection compact but delays the main verb, while an extra-information clause keeps the target clear but interrupts the main line with commas.

The Small Situation: A Rollback Decision

At 10:15, the deployment controller reports a failure. The team knows the following facts:

The first draft of the update is short:

The worker that failed was running the old image.

This is useful because the worker could refer to A, B, or C. The defining clause reduces the set. It selects B without requiring the writer to repeat Worker B in the first sentence.

The team then adds a second line:

Worker B, which was running the old image, failed during the deploy.

The noun is already unique: Worker B. The clause supplies context for the failure. If the reader removes the middle words, the core sentence still identifies the same worker:

Worker B failed during the deploy.

That removal test is the first practical tool in this lesson.

The Naive Idea: Commas Are Just Breathing Marks

A writer may add commas when a sentence feels long:

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

The result looks like a compromise between the two patterns, but standard written English does not use commas this way with a defining that clause. The punctuation signals an extra clause, while that is normally used for essential defining information.

Another tempting edit is to remove commas because the sentence is technical:

Worker B which was running the old image failed during the deploy.

Now the reader may treat which was running the old image as the information needed to identify which Worker B the writer means. But Worker B was already a unique name. The sentence has hidden an aside inside the noun phrase and made the reading less predictable.

The punctuation should follow the information job, not the writer's breathing pattern.

A Plain-to-Precise Bridge

In plain English, ask whether the reader needs the clause to find the noun.

In the deployment:

The technical names are:

The terms are less important than the reader's task. In a defining clause, the reader is still solving which one? In an extra-information clause, that question is already solved.

The Removal Test

Take the clause out of the sentence. Then ask two questions:

  1. Does the main noun still identify the same object or group?
  2. Does removing the clause change which members the sentence includes?

If the answer is no, the clause is probably defining.

The workers that failed were rolled back.

Remove the clause:

The workers were rolled back.

The first sentence rolls back only the failed workers. The second can mean all workers. The clause changes the selected set, so it is defining and has no commas.

If the head noun remains uniquely identified and the main claim keeps the same target, the clause can be extra information:

The payment service, which records the final charge state, emits PaymentCaptured.

Remove the clause:

The payment service emits PaymentCaptured.

The service is still one named component. The clause tells us an additional fact about it. Commas make that side information visible.

The test is not a license to delete every clause while editing. It is a way to discover what job the clause is doing before choosing punctuation.

Worked Comparison: Same Words, Different Claim

Consider a queue with four workers. Two failed during a migration; two remained healthy.

Defining: select a subset

The workers that failed were rolled back.

Trace the sentence:

Step Reader state Effect of the clause
1 Four workers are candidates. The workers names the group broadly.
2 that failed is read. The group is filtered to the two failed workers.
3 were rolled back is read. The action applies to the filtered subset.

The output is a partial rollback. Healthy workers are outside the selected set.

Non-defining: comment on the whole group

The workers, which failed during the migration, were rolled back.

Trace the sentence:

Step Reader state Effect of the clause
1 The workers is treated as an already known group. The target is the whole group.
2 which failed during the migration is read between commas. The clause adds a report about the group.
3 were rolled back is read. The action applies to all workers in the named group.

The output is a full rollback. If only two workers failed, this version overstates the incident or describes a different event.

The words workers, failed, and rolled back are nearly the same in both versions. The boundary is carried by selection versus comment, and the punctuation tells the reader which reading to use.

Choosing the Right Head Noun First

The same distinction works with singular nouns, names, and groups.

Several components share a role

The service that owns the payment state should emit PaymentCaptured.

There may be several services in the payment flow. The clause selects the owner. It is defining.

One component is already named

The payment service, which owns the payment state, should emit PaymentCaptured.

The name the payment service is already the selected component in this local context. The clause adds the ownership fact. It is non-defining.

A person is already named

Priya, who approved the migration, is on call.

Priya identifies one person. The comma clause supplies context.

If the team has several engineers and the name is not available, use a defining clause:

The engineer who approved the migration is on call.

The head noun remains broad until the clause narrows it.

The information boundary is a property of the situation, not a permanent property of the noun. Engineer can be defining in one sentence and non-defining after a person's name in another.

Relative Words and Commas

The previous lesson focused on choosing who, which, or that from the head noun. This lesson adds a second decision: whether the information is essential or extra.

For defining clauses:

The reviewer who found the schema mismatch opened the incident.
The queue that the worker reads is full.
The service which stores the payment state emits the event.

For non-defining clauses:

The reviewer, who found the schema mismatch, opened the incident.
The queue, which the worker reads, is full.
The service, which stores the payment state, emits the event.

The last group is only appropriate when the head noun is already unique in context. In standard written English, do not use that in a non-defining clause:

The service, that stores the payment state, emits the event.

Use which for a non-human extra clause or who for a person:

The service, which stores the payment state, emits the event.
The reviewer, who found the mismatch, opened the incident.

Do not memorize this as a punctuation trick. First decide the information boundary; then the available relative forms follow from that decision.

What This Changes in Technical Communication

The distinction helps readers estimate the scope of a claim before they act on it.

An incident update with a defining clause can tell an operator which machines to drain:

Drain the nodes that failed their health checks.

An update with an extra clause can provide context about a known target:

Drain node B, which failed its health check at 10:15.

The first sentence describes a selection rule. The second describes one named node and adds evidence. Confusing them can produce either an incomplete mitigation or an unnecessarily broad one.

The same choice matters in design notes:

Use the queue that isolates retries.
Use the queue, which isolates retries, for the notification path.

The first sentence may choose one queue among alternatives. The second assumes the queue is already known and gives the reason it is useful. A reviewer can disagree with the reason without losing the identity of the queue.

Trade-offs and Limits

Defining clauses pack a selection rule into one sentence. They reduce repetition and make the target subset visible, but the main verb arrives later and the sentence can become dense.

Non-defining clauses preserve a known target and add evidence or context. They make the main noun easy to find, but the commas interrupt the main line and can make a side fact sound more certain than the evidence supports.

The punctuation does not validate the fact. The service, which owns the payment state, ... still requires architecture and code evidence. It also does not resolve an ambiguous name. If Worker B refers to different instances across two clusters, name the cluster or use a defining condition.

The boundary signal is a disagreement about scope. If one reader rolls back only two workers and another rolls back all four, revisit the clause and punctuation before discussing the deployment itself.

Common Confusions

Confusion: commas are optional when the sentence is understandable

Why it is tempting:

The words are often intelligible either way, especially when the reader already knows the system.

Better model:

Commas tell the reader whether the clause selects members or comments on an already selected noun. “Understandable” is not enough when the action has a different operational scope.

Confusion: extra information means unimportant information

Why it is tempting:

The clause is removable, so it can feel like decoration.

Better model:

Extra means the noun is already identified, not that the fact is unimportant. The old image may be the evidence that explains the failure; it is still extra information when Worker B is already named.

Confusion: every plural noun with a relative clause names a subset

Why it is tempting:

Plural groups often contain multiple members, and a that clause frequently filters them.

Better model:

Check the commas and the situation. The workers that failed selects a subset. The workers, which failed, reports a property of the whole group.

Check Your Understanding

Check: The fleet has healthy and failed nodes. Which sentence requests a rollback only for failed nodes?

A. Roll back the nodes, which failed their health checks.

B. Roll back the nodes that failed their health checks.

C. Roll back the nodes, that failed their health checks.

Think first, then reveal.

Answer: B. The defining clause filters the fleet to nodes that failed. A makes the whole already-known group sound as if it failed; C is not the standard punctuation pattern for this clause.

Check: Which sentence treats Payment service as already identified and adds an ownership fact?

A. The service that owns payment state emits the event.

B. The payment service, which owns payment state, emits the event.

Think first, then reveal.

Answer: B. The named service is already the target; the comma clause adds context. A starts with the broad class service and uses the clause to select one owner.

Check: Remove the clause from this sentence: The workers that failed were rolled back. What changes?

Think first, then reveal.

Answer: Without the clause, The workers were rolled back can include every worker. The clause is defining because it changes the selected set.

Practice: Edit an Incident Update

A queue has four workers. Only Worker B failed its health check. Worker B was running the old image. The incident note contains these two drafts:

The worker that failed was running the old image.
Worker B, which was running the old image, failed its health check.

Explain why both can be correct, then write a third sentence for this new context: the report has already named Worker B, and the reader needs to know that it failed during the migration.

One good answer is:

Worker B, which failed during the migration, was running the old image.

The first draft selects the worker from a group. The second and third drafts start with a unique name and add a fact between commas. If the team later discusses all four workers, restore the defining form:

The workers that failed during the migration were rolled back.

Before you publish an update, mark each relative clause as selects or comments. Then check whether the action applies to the selected subset or to the already named whole.

Daily Practice Lines

Resources

Key Takeaways

PREVIOUS Who, Which, and That in Engineering Sentences NEXT Where, When, and Why Clauses in Incidents