Note-Taking Systems That Work

What you'll learn: a compact shorthand system for capturing names, numbers, times, and reasons in real time, without writing full sentences.

Why full sentences will sink you

The single most common note-taking mistake in CELPIP Listening is trying to write down what you hear the way you'd write a sentence. By the time you've written "the meeting was moved to," the speaker has already said three more clauses you needed. Because the audio plays once and keeps moving regardless of your writing speed, your notes need to be built for speed and recall cues, not readability by anyone else.

The core shorthand toolkit

Build a small, consistent set of symbols and abbreviations you use every time, so you're never inventing shorthand mid-recording:

• Arrows for change: → for "becomes/changes to" (e.g., mtg 3pm → 4pm).
• Up/down arrows for increase/decrease: ↑ cost, ↓ staff.
• Question mark for uncertainty or a stated problem: ? parking when a problem is raised but not yet resolved.
• Plus/minus for opinion: + for something a speaker likes or supports, − for something they dislike or oppose.
• "b/c" for because, capturing the reason a speaker gives for an opinion or decision — this single abbreviation matters more than almost any other, because Viewpoints and Discussion questions are built around reasons, not just conclusions.
• First-letter names: track speakers as M and J rather than writing full names, and keep a consistent column or line per speaker in Discussion and Conversation parts.
• Numbers as digits, always: 3 not "three," $40 not "forty dollars" — digits are faster to write and faster to scan afterward.

A two-column layout for multi-speaker parts

For Problem Solving, Daily Life Conversation, and Discussion (any part with two or more speakers), split your note space into columns, one per speaker, rather than one linear stream. This makes it far faster to answer "who said X" questions, because you're not hunting through a mixed timeline — you just scan one column.

Worked example

Audio (paraphrased): "So the community centre pool is closing for renovations starting June 1st, and it won't reopen until September. Mira thinks that's way too long, especially since the kids' swim lessons run all summer, but Dev says the upgrade includes a new accessible ramp, so he thinks it's worth the wait."

Shorthand notes:

pool: closed Jun1 → reopen Sep
Mira: − too long, b/c kids lessons all summer
Dev: + worth wait, b/c new accessible ramp

That's roughly 20 words of shorthand capturing every fact a question could target: the closure dates, both opinions, and both reasons — written in the time it takes to say two sentences aloud.

Note-taking checklist

• I have a fixed abbreviation for "because," change, increase/decrease, and opinion, and I use them automatically.
• I write numbers, times, and names as short fragments, never full words when a symbol works.
• I use a column or clear speaker tag whenever more than one person is speaking.
• I never stop writing to "catch up" mentally — if I miss a word, I leave a gap and keep moving.

Common mistakes

• Writing full sentences and falling permanently behind the audio after the first missed clause.
• Inventing new shorthand symbols mid-test instead of drilling a fixed set beforehand.
• Taking detailed notes on the first speaker and none on the second, then guessing on their questions.
• Not writing down reasons (b/c clauses), which are exactly what Viewpoints and Discussion questions test.

Recap

A reliable shorthand system — consistent symbols for change, opinion, and reason, digits for numbers, and columns for multiple speakers — is what turns a one-pass recording from a memory gamble into a controlled note-capture exercise. Drill the toolkit above until it's automatic before test day, so your attention during the real test goes to listening, not to inventing abbreviations on the fly.