TOEIC Link Uniform Rental and Linen Service Vocabulary: The Route-and-Exchange Cluster for Part 3, Part 4, and Part 7

In TOEIC Link, a uniform-rental or linen contract is never just "the company that brings clean shirts" — it is a route delivery, a soiled-for-clean exchange, a garment count, an inventory adjustment, an invoice, and a service agreement, and ETS can test every stage. A restaurant manager and a route driver discuss why this week's delivery came up two aprons short and whether the shortage is on the count sheet or in the wash (Part 3). A recorded message tells staff that the linen service will shift its Tuesday pickup to Wednesday for the holiday week and to leave soiled items in the labeled bin (Part 4). A delivery ticket sits beside a monthly invoice and a service agreement, and a question asks which item was back-ordered, why the account was charged a replacement fee, or when the contract renews (Part 7 triple passage). Because a rental service always moves through the same weekly loop — deliver clean, collect soiled, reconcile the count, invoice, renew — ETS can set what the delivery ticket shows against what the invoice charges and leave exactly one answer standing. Miss a term like exchange, short, replacement charge, or service agreement and a linked pair can slip in one move.

This article organizes the cluster by the weekly service cycle — the route delivery, the soiled-for-clean exchange, the count reconciliation, the invoice, and the agreement renewal — because that cycle is exactly how ETS threads the pieces together. Because a rented uniform program lives next to the sourcing and standard rules of the workplace, pair this first with the corporate uniform and workwear procurement cluster — the same "who wears what, and to what standard" logic that governs procurement governs which garments a route service is contracted to supply. And because a linen route is a recurring billed delivery, contrast this with the invoice and payment terms cluster whenever the passage turns from the garment count to the invoice line.

Why uniform-rental and linen vocabulary is overweighted

Reason 1 — a delivery ticket plus an invoice is a ready-made linked set. The ticket says what was delivered and collected this week; the invoice says what the account was charged. The two cross-reference each other exactly, forcing a single conclusion — precisely what a linked set needs. ETS asks why a replacement fee appears or which item was shorted, and only one reading survives.

Reason 2 — a rental service runs on a fixed weekly loop. Because every cycle follows the same order — deliver clean garments, collect soiled ones, reconcile the count, adjust inventory, invoice — ETS can ask "What should the manager check before approving the invoice?" or "Why was the delivery short this week?" with exactly one correct answer. The reader has to match the stage against the count.

Reason 3 — the terms are fixed trade conventions. Exchange, soiled, short, replacement charge, and service agreement mean the same thing across every uniform and linen provider. That rigidity makes the cluster perfectly testable — and perfectly learnable. The collocation, not the isolated word, is the unit of memory.

The cluster, organized by the weekly service cycle

Stage 1 — the route delivery and clean stock

Verbs and collocations: deliver the order, drop off clean garments, restock the account, scan the delivery, sign the ticket.

Nouns: route driver, delivery ticket, delivery schedule, clean stock, par level.

The recurring trap: a Part 4 notice announces a schedule change — the usual Tuesday delivery moves to Wednesday. A question asks what staff should do in the meantime, and the answer is to leave soiled items in the labeled bin, not to skip the pickup. Schedule change ≠ cancellation.

Stage 2 — the soiled-for-clean exchange

Verbs and collocations: exchange the soiled items, collect the used garments, pick up the dirty linens, swap one-for-one, bag the returns.

Nouns: soiled linen, used garments, exchange bin, one-for-one exchange, laundry bag.

This is the heart of the cluster. A rental service runs on a one-for-one exchange: the driver leaves as many clean garments as the account returns soiled. In Part 3, a manager who "forgot to put out last week's soiled aprons" is told this week's clean count will be short — the exchange can't put out more than it took back. ETS loves this because the cause (missing returns) and the effect (short delivery) sit one step apart.

Stage 3 — the count and inventory reconciliation

Verbs and collocations: reconcile the count, verify the quantity, flag the discrepancy, adjust the inventory, note the shortage.

Nouns: count sheet, garment count, discrepancy, shortage, overage.

A discrepancy is the linked-set engine. The delivery ticket says twenty shirts; the manager counts eighteen. The question asks what accounts for the difference, and the answer lives in the other document — two shirts were tagged for repair, or two were never returned. The reader matches the shortage on the count sheet to the note on the invoice.

Stage 4 — the invoice and replacement charge

Verbs and collocations: issue the invoice, itemize the charges, apply a replacement charge, dispute a line item, approve for payment.

Nouns: monthly invoice, line item, replacement charge, damage fee, lost-garment fee.

A replacement charge is the most tested billing term here. When a garment is lost, damaged beyond repair, or never returned, the service bills a replacement fee — and the manager who sees it on the invoice has to trace it back to the delivery record. Part 7 sets the invoice line against the delivery ticket and asks which garment triggered the fee. Only one item on the ticket is marked missing.

Stage 5 — the service agreement and renewal

Verbs and collocations: renew the agreement, review the terms, adjust the service level, add an item to the contract, give notice.

Nouns: service agreement, contract term, renewal date, service level, notice period.

The service agreement closes the loop. A Part 7 passage pairs the contract with a request to add a new garment type or change a delivery frequency, and asks whether the change is allowed before the renewal date or requires written notice. The answer is in the terms, not the delivery ticket.

Size changes and new hires — the sub-cluster that pays off

One recurring mini-scenario deserves its own note: the size change. When a new employee joins or an existing one needs a different fit, the account submits a size change and the service adds or swaps garments on the next route. Watch for size change, new-hire setup, add a wearer, and garment swap. ETS uses this to test a small inference: a delivery that suddenly includes an extra set of shirts usually means a new wearer was added, not that the service made an error. The clean read is "an employee was added to the account," and a distractor will call it a mistaken over-delivery.

Paraphrase traps ETS reuses

• "The delivery was short" → "fewer garments arrived than expected." The paraphrase drops the trade word short and states the count plainly. Recognize that short, shorted, and came up short all describe a delivery below the expected count.
• "A replacement charge was applied" → "the account was billed for a missing item." ETS swaps the invoice term for the plain cause. The link is garment-not-returned → fee-charged.
• "Leave soiled items in the labeled bin" → "place used garments where the driver can collect them." The Part 4 instruction gets reworded; the action is unchanged.
• "The agreement renews automatically" → "the service continues unless the account gives notice." The renewal clause becomes a plain if-then, and the tested detail is the notice period.

How to drill this cluster

Read each term inside its stage, not alone. Exchange means little in isolation; a one-for-one exchange of soiled for clean carries the whole logic of why a delivery can come up short. When you meet a delivery ticket in Part 7, ask the three questions ETS asks: what was delivered, what was collected, and what does the invoice charge for. The answer to the third almost always sits in the gap between the first two. For the wider "billed service" pattern that a linen route shares with every account, review the invoice and payment terms cluster; for the sourcing-and-standard side of what employees actually wear, review the corporate uniform and workwear procurement cluster. Learn the collocation, follow the weekly loop, and the shorted delivery and the mystery invoice line stop being traps and start being the single defensible answer.