TOEIC Link — Lost Luggage and Baggage Claim Vocabulary Cluster

A mishandled bag is a small logistics failure written up as correspondence, which makes it a natural TOEIC Link setting. A baggage irregularity report, a tracing update, or a claim response rarely tests whether you know a bag went missing; it tests whether you can read three things at once — where the bag currently is in the system, what stage the claim has reached, and who is responsible for the next action. Those three facts decide what the passage's questions are really asking, and a reader who fixes them first has the situation anchored before the options appear.

This guide walks the baggage journey from check-in to delivery as a connected sequence, isolates the tracing and compensation vocabulary the test leans on, and closes with a drill protocol. It builds on general travel terminology and pairs with the corporate travel and business trip vocabulary cluster, since both track an itinerary with responsibilities that shift as it progresses, and with the orientation in what TOEIC Link measures.

The bag as a tracked-journey sequence

The organizing fact is that a checked bag is not simply present or lost — it moves through a tracked chain of custody, so a claim exists to locate the bag within that chain. A passage reasons about whether the reader can place the bag at the right stage, so tracking the sequence reads the situation the way the airline logged it.

A bag's journey begins when the passenger checks in a bag and receives a baggage claim tag (the bar-coded stub matching the bag to the passenger). The bag is loaded, may be transferred between connecting flights, and should arrive on the baggage carousel at the destination. When it does not, the passenger files a property irregularity report (PIR) at the baggage service desk, which opens a tracing process. The bag is then classified as delayed (located, en route), lost (not located after a set period, usually 21 days), or damaged. A passage may hinge on the delayed-versus-lost distinction: a bag that has not arrived is usually delayed, not lost, and the test likes a passenger who declares a bag lost when the report only says it is still being traced.

The distinction between delayed and lost organizes much of the vocabulary. A delayed bag is expected to be delivered once located; a lost bag triggers a compensation claim. A passage may present a passenger demanding reimbursement for a bag the notice describes as located and out for delivery, and expect the reader to see that tracing has succeeded — the same "in progress versus concluded" gap the test uses across its service passages.

The tracing and status vocabulary — where the number begins

The heart of a lost-luggage passage is the small set of terms describing how the airline locates the bag, and the test concentrates its inference questions there. The central idea is the file reference.

When a report is filed, the passenger receives a file reference number (or PIR number) used to track the status of the trace. A passage may turn on a passenger who cannot get an update because they quote the flight number instead of the file reference, and expect the reader to see which identifier the system actually uses. Status vocabulary is precise: a bag may be traced (located in the system), on hand at a station, forwarded to the destination, or out for delivery. A passage stating a bag was "found at the connecting airport and is being sent on" is testing a forwarded status, not a resolved delivery — the bag is located but not yet returned.

Delivery vocabulary sits alongside. Once located, a bag is delivered to the address on the report, and the passenger may be asked to confirm receipt. A passage may present a passenger whose bag was marked delivered but who never received it, expecting the reader to connect the gap to an address on the report that needs updating. The reader who tracks whether the status is "located," "in transit," or "delivered" avoids reading an en-route bag as a returned one.

The claim and compensation vocabulary — where the harder passages live

When the passage turns from where the bag is to what the passenger is owed, the vocabulary shifts to the claim structure, and this is where the harder passages live. The central term is the claim.

A claim for a delayed or lost bag is governed by rules that cap and condition the payout. Interim costs for essentials while a bag is delayed are reimbursable expenses, usually requiring receipts and subject to a daily limit; a passage may hinge on a passenger who assumes any purchase is covered and expect the reader to locate the receipt-and-limit condition. For a lost bag, compensation is capped by a liability limit (a maximum the carrier will pay), and excluded items — cash, electronics, valuables — are often not covered. A passage stating a passenger "expected full value for a laptop in a checked bag" is often testing an exclusion clause, not a processing error. This gap between "what I lost" and "what is covered" mirrors the distinction the test probes in the invoice and payment terms vocabulary cluster: the stated total is bounded by terms the reader must find.

Documentation vocabulary is precise. A claim typically requires the claim tag, the file reference, the boarding pass, and an itemized list of contents with proof of value. A passage may turn on a claim rejected for missing documentation rather than for an invalid loss, and expect the reader to see that the loss was accepted but the paperwork was incomplete. The test likes the moment where a valid claim stalls on a procedural gap — the same "substance versus form" logic it uses in approval passages elsewhere.

Deadline, responsibility, and escalation vocabulary

Around the claim sit the terms that govern timing and who acts next, and passages test the sequence. A claim must be filed within a time limit (often 21 days for a delayed bag from the delivery date, or 7 for damage), and a bag not located within the tracing window is declared lost, at which point the claim moves to settlement. A passage may present a passenger who waits for the bag past the deadline and expect the reader to see that the filing clock, not the passenger's patience, governs eligibility. Responsibility can shift between carriers on a connecting itinerary: the last carrier usually handles the claim regardless of which airline mishandled the bag, and a passage stating the passenger "was told to contact a different airline" is often testing this handoff, not an evasion.

Escalation vocabulary closes the cluster. If a claim is denied or a settlement disputed, a passenger may appeal or refer the matter to the regulator, and a passage may describe a passenger unsure why the airline still handles a claim after denying it — expecting the reader to infer an open appeal. The difference between a closed claim and one under review is the same "concluded versus in progress" distinction that runs through every baggage passage on the test.

Drill protocol — reading baggage notices under time pressure

Practice this cluster with a fixed routine so the tracing logic becomes reflex rather than recall.

First, on any baggage notice, answer three questions before reading the options: where the bag currently is (traced, forwarded, out for delivery, or declared lost), what stage the claim has reached (filed, under review, settled, or denied), and who acts next (the passenger, the last carrier, or an appeal body). Those three facts predict most questions more reliably than rereading the report.

Second, separate delayed from lost. A bag can be missing because it is still being traced, because it was located and is in transit, or because the tracing window closed and it is declared lost — three different states the test deliberately blurs. When a passage says a bag has not arrived, look for which of the three the notice actually describes before choosing.

Third, flag every limit and deadline. The hardest baggage passages live in the gap between what a passenger claims and what the liability limit, exclusions, or filing window allow, and the reader who tracks those conditions reads a partial settlement as a term, not a mistake. Pair this cluster with the corporate travel and business trip vocabulary cluster so the itinerary logic and the claim logic reinforce a single "where is it, and who owes what" reading.

Read this way, a lost-luggage notice stops being a wall of apology and becomes three questions — located where, claim at what stage, next action by whom — which is exactly the structure TOEIC Link builds its questions around.