TOEIC Link Quality Assurance and Defect Tracking Vocabulary: The Inspect-to-Sign-Off Cluster Behind Part 4 and Part 7

A batch comes off the line, an inspector samples it, a unit fails inspection, the defect is logged and assigned a severity, the team investigates the root cause, a corrective action is taken, and the batch is either reworked or released. TOEIC Link keeps returning to the quality-assurance situation because it is procedural, document-heavy, and full of fixed language, without ever asking the test-taker to understand the underlying engineering. A Part 4 quality briefing, a Part 7 inspection report with its follow-up defect log, a Part 3 call between a QA lead and a supplier: all run on the same compact quality vocabulary.

This article is the focused QA and defect-tracking cluster, organized by the quality workflow — inspect, detect and log the defect, classify severity, investigate the cause, and take corrective action before sign-off — because that is the sequence ETS uses to build items. Learn the workflow, and you know where the answer sits before you finish reading the question.

Why quality-assurance vocabulary keeps returning

Three structural forces keep this cluster on the test.

Reason 1 — inspection is a fixed workflow. Sampled, inspected, passed or failed, logged, investigated, corrected, released — every status triggers the next step, and the sequence rarely varies. That built-in order gives ETS a clean anchor for sequence questions ("What must happen before the batch is released?") without any technical knowledge.

Reason 2 — the reports are structured. An inspection report records what was sampled, what the defect is, what severity it carries, and what the disposition is, while a corrective-action note states what was done and whether the fix was verified. That structure is exactly what Part 7 questions feed on, the same way a supply chain disruption and procurement escalation memo supplies structured escalation data for reading items.

Reason 3 — the collocations are fixed. You do not do a defect; a defect is logged or flagged, a unit fails inspection, a cause is investigated, and a corrective action is taken or implemented. TOEIC Link tests the pairing, not the bare noun — the collocation is the unit of memory.

The cluster, organized by the quality workflow

Memorize each group as a unit tied to one stage of the workflow.

Stage 1 — inspecting the batch

sample — to select a portion of a batch for checking. "The inspector sampled ten units from the shipment."
inspect — to examine against a standard. "Every batch is inspected before it ships."
specification (spec) — the documented requirement a unit must meet.
tolerance — the allowed range of variation. "The part was within tolerance."
acceptance criteria — the conditions a unit must satisfy to pass.

Stage 2 — detecting and logging the defect

defect — a flaw that violates the specification.
flag / log — to record a defect in the tracking system. "Two units were flagged for cracks."
fail inspection — to not meet the standard. "The batch failed inspection."
nonconformity — a formal term for a unit that departs from the spec.
reject — to refuse a unit that fails. "The lot was rejected."

Stage 3 — classifying severity

severity — how serious a defect is (critical, major, minor).
critical defect — a flaw that makes the unit unsafe or unusable.
priority — the order in which defects are addressed.
escalate — to raise a serious defect to a higher level. "Critical defects are escalated to the quality manager."

Stage 4 — investigating the cause

root cause — the underlying reason for the defect. "The investigation traced the root cause to a worn tool."
investigate — to determine why the defect occurred.
traceability — the ability to track a unit back through the process.
recurrence — the defect happening again. "The fix should prevent recurrence."

Stage 5 — taking corrective action and signing off

corrective action — the step taken to fix the cause. "A corrective action was implemented."
rework — to fix a defective unit rather than scrap it.
scrap — to discard a unit that cannot be reworked.
verify — to confirm the fix worked. "The corrective action was verified."
sign off / release — to approve the batch for shipment. "QA signed off on the batch."

How ETS builds items from this cluster

A Part 4 quality briefing announces that a batch failed inspection and asks what the listener should do next — the answer sits at the corrective-action stage. A Part 7 inspection report pairs the defect log with a follow-up email, and the question asks whether the batch was released or reworked — the disposition line holds the answer. Because the workflow is fixed, the correct option is almost always the next stage in the sequence, not a paraphrase of the defect itself.

For adjacent document types that recycle the same corrective-action language, work through the ISO 9001 internal audit nonconformity report decoding guide, which drills the same "finding → corrective action → verification" chain in a formal audit format.

Drill this cluster the way it is tested

Do not memorize the twenty-odd words as a flat list. Memorize them as five stages, each with its fixed collocation, and rehearse the sequence out loud: sample, inspect, fail, log, classify, investigate, correct, verify, sign off. When a Part 4 briefing or a Part 7 report drops you into the middle of that chain, you will know which stage comes next — and on TOEIC Link, the next stage is usually the answer.