What Part 2 actually is
You get a visual source (timetable, brochure table, map/zone chart, facility schedule, or a simple flowchart) plus a short email/message that you must complete with drop-down blanks. Almost every question is Specific Information: match the scenario’s constraints to the exact cell/row/segment of the diagram, then use those facts to choose the correct answer or finish the reply naturally. There are 8 items, and a strong pacing target is ~9 minutes.
The 5-Step Routine (fast, repeatable, safe)
- Title first (2–3s): What is this thing? “Community Pool—Lap Lanes & Lessons”, “Airport Express—Fares & Zones”, “Community Garden—Plot Rules”. The title tells you the scope.
- Legend & Notes (10–15s): Read legends, units, symbols, and especially footnotes. Words like only, except, not valid, reduced service, closed, subject to change flip answers.
- Structure map (5–8s): How is info organized? Rows vs columns, time on one axis, zones/lines, process arrows. Know where a fact would live before you start hunting.
- Constraint string (5–10s): From the stem, write a compact line:
≥3 lanes, after 7 pm, weekdays. For fares: Zone 2→3, adult, off-peak. For rules: plot size ≤ 2m, compost allowed?.
- Triangulate & verify (15–25s): Go straight to the candidate cell/row/segment. Check every constraint, then ±1 cell/line for hidden exceptions. If one constraint fails → reject.
Result: You answer factual items fast and leave time to complete the reply drop-downs carefully.
Constraint Language Decoder (the difference between right and wrong)
- only = no other cases allowed.
- except = everything but that case.
- at least = ≥ (3 means 3 or more). at most = ≤.
- no later than 5 pm = ≤ 5:00. not until 5 pm = ≥ 5:00, nothing before.
- between A and B (check inclusivity): if the table shows “9–12”, assume inclusive unless a note says otherwise.
- per day / per week = billing period matters; don’t multiply wrongly.
- units = km vs m, kg vs g, $ vs ¢, 12-hour vs 24-hour time; confirm before you compute.
Write the critical word next to your constraint string to keep it visible while you read.
Completing the reply (drop-downs) based on the diagram
The reply is where accuracy meets tone. A safe structure is acknowledge → confirm → next step:
- Acknowledge: “Thanks for sending the pool schedule.”
- Confirm facts: “We’ll meet after 7 pm on Tuesday when ≥3 lanes are open.”
- Next step: “I’ll bring the wristbands.”
Drop-down tests (run all four):
- Meaning: Insert an option and re-read the full sentence. It must respect every constraint you verified.
- Tone: Polite/neutral language unless the source uses formal register; avoid slang or pushiness.
- Strength: Don’t upgrade may to will, should to must, or free to discounted.
- Grammar fit: Subject/verb agreement, tense, and prepositions (on Friday, at 6 pm, in Zone 3) must remain correct.
High-Frequency Trap Catalog (know them by name)
- Footnote ambush: A tiny note nullifies the cell you matched (“lessons use 1 lane 12–2” → your “2 lanes” window becomes “1 lane”).
- Near-match number: $13 vs $31, 12:30 vs 12:03.
- Direction flip: Eastbound table chosen for a westbound trip.
- Border case: A station on a zone edge charged as the higher zone per rules.
- Bundle illusion: Premium plan includes locker/towel; paying separately with Basic costs more than Premium.
- Per-night vs total: An option multiplies when the table already shows a total price.
- Weekday/Weekend swap: Saturday rules applied to Friday evening (Friday is weekday).
- “From” pricing: Minimum rate quoted as final price.
When one constraint fails, discard the option immediately. Don’t negotiate with it.
Decision Tests for Every Option (kill-switches)
- Anchor test: Can I point to the exact cell/row/symbol that supports it?
- All-constraints test: Do all parts of my constraint string hold simultaneously?
- Units/time test: Are the units and time windows exactly right (am/pm, ≤/≥, per-day vs total)?
- Footnote test: Is there any note that overrides this case?
- Reply consistency test: If used in the reply, does the sentence still match tone, strength, and facts?
One failed test → eliminate.
Mini-samples (short, text-based, realistic)
Sample 1 — Pool lanes timetable
Diagram snippet (text form):
Mon–Fri: 6–9 am: 3 lanes | 12–2 pm: 2 lanes (note: lessons use 1 lane) | 7–9 pm: 4 lanes
Question: You need ≥3 lanes after 7 pm on a weekday. Which time works?
Correct logic: Weekday evening band is 7–9 pm: 4 lanes → satisfies ≥3 and after 7 pm.
Wrong options look like: 12:30 pm (2 lanes → footnote reduces public lanes), Saturday 7 pm (weekend), 6:30 pm (not after 7).
Sample 2 — Transit zones & fares
Diagram snippet (text form):
Zones: 1 (Downtown) | 2 | 3 (Airport). Express not valid with Local Day Pass. Off-peak after 7 pm.
Question: Travel 2→3 at 6:45 pm with a Local Day Pass. What’s true?
Correct logic: 6:45 pm = peak; Local Day Pass not valid on Express → must use local service; fare follows peak rate table for 2→3.
Wrong options: Off-peak pricing; Express allowed with Local Day Pass; 1-zone fare.
Sample 3 — Membership brochure
Diagram snippet (text form):
Basic $38/mo (no locker). Plus $49/mo (locker). Premium $59/mo (locker + towel + 2 guest passes). $25 join fee (one-time).
Question: Member wants a locker and guest passes. Cheapest monthly choice?
Correct logic: Locker + guest passes only bundled in Premium; adding guest passes to Plus monthly would cost more overall.
Wrong options: Plus (no guest passes); Basic with paid locker (no official add-on shown).
What carries forward
This routine—Title → Legend/Notes → Structure → Constraint string → Triangulate & verify—is the same logic you’ll use for Part 6 (Information) when mapping paragraph topics, and for Part 7 (Viewpoints) when checking claims against stance. The difference in Part 2 is that footnotes and units decide everything. Respect them, and your accuracy jumps immediately.
