CELPIP blog
CELPIP Listening Part 1: Track the Decision, Not the Story
Quick answer
Short answer: CELPIP Listening Part 1 is a problem-solving dialogue, and in practice sets every one is a decision arc: a problem appears, two or three fixes get proposed, objections kill most, and one survives — sometimes patched together from the wreckage. The questions ask which option won, which lost, and why each loser died. Follow it like a story and you drown in detail; keep a live ledger of each option’s status and the answers sit in your notes. The audio plays once, so the ledger is built live.
The ledger: option, objection, status
Listen to a handful of Part 1 dialogues and the same shape keeps surfacing. Someone has a problem — a delivery, a booking, a broken thing. A fix is proposed; an objection lands. A second fix comes up, maybe a third; objections kill some, modifications rescue others, and by the final line one plan is standing. The questions are built on that shape, not the surface chatter: what did they decide, what did they reject, and what killed each loser.
The ledger is three columns kept live while the audio plays. Option: two words for each proposal, the moment it’s raised. Objection: the reason someone pushed back — a few words, because the why-questions come straight from this column. Status: alive, dead, or revived, updated whenever the conversation touches it. You aren’t recording what was said — you’re recording what each exchange did to each option’s state. That’s the whole trick: the story is long, but the state is small. The Part 1 guide breaks down the question formats this ledger feeds.
A delivery problem, ledgered live
Two colleagues — Priya and Marco — a client event on Saturday, banners stuck at a supplier: ten lines of dialogue, with what a strong candidate’s ledger does beside each.
| What you hear | What the ledger does |
|---|---|
| Marco: 'The Kelowna supplier just called - the banners won't ship until Thursday, and the client's event is Saturday morning.' | Problem at top: banners Thu / need Sat |
| Priya: 'Could we pay for overnight courier once they ship?' | COURIER — alive |
| Marco: 'I checked - Friday delivery in theory, but they won't guarantee weekend handling past the depot.' | COURIER → dead: no wknd guarantee |
| Priya: 'Then we drive up Thursday night and collect them ourselves.' | DRIVE — alive |
| Marco: 'It's five hours each way, and the van's at the trade show until Friday.' | DRIVE → dead: no van |
| Priya: 'I'll take my own car. The banners roll up - they'd fit.' | DRIVE → revived: her car |
| Marco: 'The banners would. But the display stands ship in the same crate, and those won't fit in a hatchback.' | DRIVE = banners only · stands still open |
| Priya: 'What about the print shop on Granville? They quoted us on stands last year.' | SHOP — alive (stands) |
| Marco: 'Call them. If they can print the stands by Friday, you drive up for the banners and we're covered.' | Decision: SHOP stands + DRIVE banners |
| Priya: 'Booking it now. And I'll keep the courier order in as a backup - worst case we return duplicates.' | COURIER → revived: backup only |
Notice what the ledger is not: a transcript. When the questions arrive — why did they rule out the courier? what will Priya carry in her car? what did they finally agree to do? — each one reads off a single row.
The trap: alive at minute one, dead by minute two
The most reliable wrong answer in Part 1 practice sets is the early favourite: the first proposal, which got the most airtime and your freshest attention. By the end of the audio it’s dead — but the option list resurrects it, and recognition does the rest. A story listener remembers the courier discussion better than the print-shop line that won. A ledger listener glances at the status column — dead, no weekend guarantee — and moves on.
The mirror-image trap is the revival. An option gets shot down, you mentally file it as gone, and two exchanges later a modification brings it back — the van is unavailable, but her own car is not. Stop tracking at the first death and you will confidently eliminate the correct answer. States move in both directions; only the final state answers the what-did-they-decide question, and the only defence is touching the row every time the conversation does.
Make the ledger automatic
The ledger has to run underneath comprehension, and that takes reps against timed dialogues — the listening practice page has full Part 1 sets to build it on. Start on paper with all three columns; within a few sets the notation collapses on its own, and ‘courier x wknd’ becomes a complete row written in three seconds. Then audit: after each dialogue, every question should map to a ledger row. A question your ledger can’t answer names the exact state change your ear let through untracked.
FAQ
Questions people ask
How many options does a CELPIP Listening Part 1 dialogue usually raise?
Two to four in most practice sets. The ledger doesn't care - each proposal gets a row when it appears, and rows stay short: two words for the option, a few for the objection.
What if I can't write fast enough to keep the ledger?
Shrink the notation, not the tracking. A word, an arrow, and a cross or check is enough - 'courier x wknd' records an option, its death, and the reason in three seconds.
Do the questions really ask why an option was rejected?
Constantly - across practice sets, rejected options and their reasons are among the most common Part 1 targets. The winner alone answers one question; the objection column answers the rest.