TOEIC Link Quality Control and Defect Inspection Vocabulary: The Cluster for Part 3, Part 4, and Part 7

In TOEIC Link's business world, someone is always checking whether a product meets standard. A quality-control inspector calls the production floor because a batch failed inspection and shipment has to be held (Part 3). A recorded briefing tells staff that a defect was found in a recent lot and the affected units are being pulled for rework (Part 4). An inspection report sits beside a corrective-action memo that assigns a deadline to fix the process (Part 7 double passage). Because a quality problem follows a fixed arc — inspect, find the defect, take corrective action, verify — ETS can link two documents with exactly one defensible answer. Miss a term like defect, inspection, or rework and you can lose a linked pair at once.

This article organizes the cluster by the inspection-to-corrective-action timeline — the inspection, the defect, the corrective action, and the verification — because that sequence is precisely how ETS threads the pieces together. If your general business base is thin, build it first with the TOEIC Link vocabulary essentials guide; this cluster layers on top. A failed inspection often ends in a customer complaint about the faulty product, so pair this with the customer complaint and service recovery cluster if the resolution side is where you slip.

Why quality-control vocabulary is overweighted

Reason 1 — an inspection produces naturally linked documents. An inspection report plus a corrective-action memo is a ready-made double passage. The problem recorded in one and the fix assigned in the other cross-reference each other — exactly what a linked set needs to force a single conclusion.

Reason 2 — a defect creates responsibility-and-deadline questions. Because a defect must be fixed by someone by a date, ETS can ask "Who is responsible for the correction?" or "By when must the process be fixed?" with one correct answer. The reader has to combine the finding from one document with the assignment in the other.

Reason 3 — the terms are fixed quality conventions. Defect, inspection, and rework mean the same thing at every plant. That rigidity makes the cluster perfectly testable — and perfectly learnable. The collocation is the unit of memory.

The cluster, organized by the quality timeline

Stage 1 — the inspection

Verbs and collocations: inspect a batch, conduct a quality check, test a sample, meet the standard, comply with specifications.

Nouns: inspection, quality control, standard, specification, sample, batch, lot.

Watch inspection / quality check / audit — a stem may name one while the passage uses another. All three point to the moment the product is examined. Standard / specification / requirement cluster tightly, and a Part 7 question often turns on whether a single item met the spec.

Stage 2 — the defect

Verbs and collocations: find a defect, fail inspection, fall below standard, detect a flaw, reject a unit.

Nouns: defect, flaw, fault, defective unit, reject, nonconformity, failure rate.

Defective / faulty / flawed are interchangeable here, and a stem naming a bad unit maps to whichever passage carries the finding. Failed inspection / did not pass / below standard often anchor a "why was the shipment held?" question, and the answer is the specific defect that was found.

Stage 3 — the corrective action

Verbs and collocations: rework the units, correct the process, recall the batch, discard the rejects, retrain the operators.

Nouns: corrective action, rework, recall, root cause, deadline, responsible party.

Rework / repair / fix are close synonyms, and a stem naming the corrective action maps to whichever passage assigns it. Root cause — the underlying reason for the defect — often sets up a "what caused the problem?" question, and the answer is stated once, in only one of the two documents.

Stage 4 — the verification

Verbs and collocations: reinspect the batch, verify the fix, confirm compliance, approve for shipment, clear the hold.

Nouns: reinspection, verification, approval, sign-off, clearance, release.

Reinspect / recheck / verify all describe confirming the fix, and a stem asking what happens before shipment resumes maps to whichever passage announces the clearance. A Part 4 update that says the batch was "approved for release" is the classic close of this arc.

The paraphrase traps that decide linked questions

ETS rarely repeats a word across two documents. The mismatch is the test.

• A report says units are "nonconforming"; the question asks about the "defective products." Same fact, different words.
• A memo says a batch "did not pass inspection"; the stem calls it a "quality-control failure." You match the paraphrase, not the vocabulary.
• A note says the line will be "reworked"; the question asks how the company will "correct the problem." The collocation is the bridge.

When a defect reaches the customer as a faulty delivery, the follow-up language overlaps with the customer complaint and service recovery cluster — study the two together if the "what will the company do for the customer?" question is where you lose points.

How to drill this cluster

1. Learn the arc, not the list. Memorize the four stages in order — inspection, defect, corrective action, verification — so that when a passage names one stage, you already expect the next.
2. Pair each term with its paraphrase. For every word, write the "different words, same fact" version ETS is likely to use in the stem. Defective → does not meet the standard. Rework → fix the units.
3. Practice the two-document jump. Take an inspection report and a corrective-action memo, and force yourself to answer "who fixes it by when?" by combining the finding from one and the assignment from the other. That jump is the entire skill.
4. Time the Part 4 briefing. Recorded quality updates come fast. Train to catch the defect, the affected batch, and the deadline in a single pass — those three are almost always the three questions.

Master the inspection-to-corrective-action arc and its paraphrase pairs, and the quality-control cluster stops being a source of lost linked pairs and becomes a set of predictable, high-value points.