TOEIC Link Landscape Irrigation System Audit and Controller Inspection Vocabulary: The Services Cluster for Part 3, Part 4, and Part 7

In TOEIC Link, a landscape irrigation audit is never just someone turning on the sprinklers — it is a scheduled audit, a zone-by-zone test, a distribution-uniformity check, a controller reprogramming, and a water-use report, and ETS can test every stage. A property manager and an irrigation technician discuss why the audit found low uniformity in the front zones and whether the cause is a broken head or a scheduling error in the controller (Part 3). A recorded notice tells building tenants that irrigation will run manually during the daytime audit and will return to the overnight schedule that evening (Part 4). An audit report sits beside a water bill and a repair estimate, and a question asks which zone was overwatering, why the controller schedule was revised, or how much water the recommended fixes are expected to save (Part 7 triple passage). Because an irrigation audit always moves through the same arc — schedule the audit, test each zone, measure uniformity, reprogram the controller, report the savings — ETS can set what the field test found against what the controller was set to do and leave exactly one answer standing. Miss a term like distribution uniformity, zone, run time, or controller schedule and a linked pair can slip in one move.

This article organizes the cluster by the audit sequence — the audit, the zone test, the uniformity check, the controller, and the water-use report — because that sequence is exactly how ETS threads the pieces together. Because an irrigation system must not contaminate the potable supply, pair this first with the backflow preventer testing and certification cluster — the same "protect the drinking water at the connection point" logic ETS uses to test a backflow device is the logic that governs where an irrigation system taps the main. And because irrigation and outdoor lighting share the same landscape zones and low-voltage wiring, contrast this with the outdoor landscape lighting installation cluster whenever the passage turns from watering the zone to lighting it.

Why landscape-irrigation and controller vocabulary is overweighted

Reason 1 — an audit report plus a water bill is a ready-made linked set. The report records what each zone is doing; the bill records what all that watering cost. The two cross-reference each other exactly, forcing a single conclusion — precisely what a linked set needs. ETS asks which zone drove the high bill, and only one reading survives.

Reason 2 — an audit passes through defined stages. Because every audit follows the same steps — schedule, zone test, uniformity check, controller reprogramming, report — ETS can ask "What must the technician do before revising the schedule?" or "Why was the run time reduced?" with exactly one correct answer. The reader has to match the stage against the rule.

Reason 3 — the terms are fixed trade conventions. Distribution uniformity, run time, zone, controller schedule, and precipitation rate mean the same thing across every irrigation contractor. 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 audit sequence

Stage 1 — the scheduled audit

Verbs and collocations: schedule the irrigation audit, walk the site, inventory the zones, review the water history, note the coverage.

Nouns: irrigation audit, site walk, zone inventory, coverage, water history.

The trap ETS sets here is audit against repair call. An audit is a planned assessment of the whole system; a repair call is a response to a specific failure, and a Part 3 conversation may hinge on which one is being described — "this isn't a broken-pipe callout, we're doing the full efficiency audit." Match the purpose to the visit and the scope question answers itself.

Stage 2 — the zone-by-zone test

Verbs and collocations: test each zone, activate the zone, check the heads, spot the broken head, note the overspray.

Nouns: zone, sprinkler head, rotor, spray head, broken head, overspray.

This is where ETS tests working versus failed. A zone test either confirms the heads deliver even coverage or it flags a fault; a Part 4 announcement may report that "zone four showed two broken heads and significant overspray onto the walkway." The question then asks which zone needs repair — and the head condition is the pivot.

Stage 3 — the distribution-uniformity check

Verbs and collocations: measure distribution uniformity, place catch cups, calculate the precipitation rate, identify dry spots, flag low uniformity.

Nouns: distribution uniformity, catch cup, precipitation rate, dry spot, uniformity score.

ETS distinguishes a hardware problem (a broken head lowers uniformity) from a scheduling problem (uniformity is fine but the run time is wrong). A triple passage sets the uniformity score against the controller schedule and asks whether the fix is a repair or a reprogramming. Only a low uniformity score points to hardware.

Stage 4 — the controller programming

Verbs and collocations: reprogram the controller, set the run time, adjust the schedule, install a rain sensor, group the zones.

Nouns: controller, run time, watering schedule, rain sensor, seasonal adjustment.

The controller is where the schedule lives; the run time is how long each zone waters. ETS loves the conditional here: "If the rain sensor is installed, the controller will suspend the cycle after measurable rainfall." The question asks what change reduces waste without harming the landscape — and the seasonal adjustment or rain sensor is the answer.

Stage 5 — the water-use report

Verbs and collocations: issue the water-use report, project the savings, recommend the upgrades, prioritize the repairs, document the baseline.

Nouns: water-use report, baseline, projected savings, upgrade, payback period.

The water-use report ties the audit together — it states the baseline usage, the recommended fixes, and the projected savings. Part 7 sets the report's projected savings against the estimate's cost and asks which upgrade has the shortest payback period. The savings figure drives that answer.

The paraphrase traps ETS relies on

• audit ↔ repair call — planned assessment versus specific failure response. Scope questions hinge on which visit is described.
• broken head ↔ scheduling error — a hardware fault versus a controller setting. Only low uniformity points to hardware.
• run time ↔ precipitation rate — how long it waters versus how fast water is applied. Overwatering questions read both together.
• baseline ↔ projected savings — current usage versus expected reduction. Payback questions compare the two against cost.

How to drill this cluster

Do not memorize the words as a flat list. Rebuild the audit sequence from memory — audit, zone test, uniformity check, controller, water-use report — and at each stage say the collocation aloud and the one trap ETS sets there. Then run the two linked clusters back to back: the backflow preventer testing cluster trains the water-protection language at the point where the system connects to the main, and the outdoor landscape lighting cluster trains the low-voltage language that shares the same landscape zones. When you can predict, before reading the question, that a fix will hinge on whether the fault is a broken head or a schedule error, the cluster has moved from vocabulary you recognize to vocabulary you can use under time pressure — which is the only kind that scores.