Part 5 — Listening for Viewpoints

What you'll learn: how to separate a speaker's overall opinion from each individual reason they give for it, since Viewpoints questions test both separately.

What this part tests

Listening for Viewpoints is usually a single speaker delivering an opinion on a topic — often something with two reasonable sides (remote work, a local development project, a change in school policy) — along with several supporting reasons. Unlike Discussion, there's no second voice to push back, which means the entire structure of the monologue is: stated opinion, followed by a sequence of reasons, sometimes followed by an acknowledged counterpoint the speaker still disagrees with.

Questions on this part test at two levels: the speaker's overall position (do they support or oppose X), and the individual reasons given (which of the following is NOT a reason the speaker mentions, or which reason did the speaker give for point Y specifically). Getting the overall stance right but mixing up which reason belongs to which point is one of the most common ways test-takers lose points here.

Number your reasons as you hear them

Because Viewpoints monologues typically string together two, three, or four distinct reasons in support of one conclusion, number them as you write (r1, r2, r3) rather than writing them as an undifferentiated block. This makes "which reason" questions much faster to answer, since you can match a question's specific detail back to a numbered line instead of re-reading a paragraph of notes.

Worked example

Audio (paraphrased):

"I think the city was right to add the new bike lane on Fourth Street, even though it's caused some complaints. For one thing, cyclist injuries on that street have already dropped since it opened. It's also encouraged more people to bike to work instead of drive, which helps with the traffic congestion downtown. Now, some business owners say it's reduced parking and hurt foot traffic — and I get that concern — but the data so far doesn't actually show a drop in nearby sales."

Shorthand notes:

opinion: + bike lane (Fourth St)
r1: ↓ cyclist injuries
r2: ↑ biking to work, ↓ traffic
counter: biz owners say ↓ parking/foot traffic
speaker: still + , sales data unchanged

Sample question: "According to the speaker, what happened to sales near the bike lane?" The correct answer is that sales have not dropped, despite the business owners' concern — a detail easy to miss if a listener stops updating notes once the counterpoint is raised, assuming the speaker has conceded the point.

Viewpoints checklist

• I capture the overall stance (for/against) in the first line of my notes.
• I number each supporting reason separately as it's given.
• I note any counterpoint the speaker acknowledges, and separately note whether they still hold their original opinion afterward.
• I don't stop taking notes once a counterpoint appears — the speaker's response to it is often what's tested.

Common mistakes

• Recording the overall opinion correctly but attaching the wrong reason to the wrong point.
• Assuming a speaker changes their mind when they acknowledge a counterpoint, when they usually go on to reaffirm their original stance.
• Losing count of how many distinct reasons were given, which matters for "how many reasons does the speaker mention" questions.
• Treating the counterpoint itself as the speaker's own opinion.

Recap

Viewpoints monologues follow a stance-then-reasons structure, often closing with an acknowledged-but-rejected counterpoint. Numbering each reason as you hear it, and continuing to take notes through the counterpoint to catch the speaker's response, is what protects the detail-level questions this part is built around.