Announcements and instructions create a distinctive listening problem: understanding is valuable only if the listener can convert it into the correct state or action. A speaker may mention an original time, revise it, add an exception, attach a condition, distinguish what is optional from what is required, and then finish with the one instruction that determines what the listener must actually do.
This guide is SETC-SEC-LISTEN-110, the practical-action audio-architecture spoke inside the Secondary English Listening Examination Performance lane. It owns the integrated exam-performance problem created by announcements, notices, schedules, instructions, procedures, warnings, bookings, service information and other audio where dates, conditions, sequence and final states matter.
It does not duplicate the general listening foundation, the deep note-taking owner, or SETC’s specialist Listening Test Distractors | Track Corrections, Alternatives and Final Meaning Without Chasing Keywords. Those pages own broader mechanisms. This article coordinates them around action-bearing practical audio in which a small relational word—unless, except, after, before, only, instead, optional, required—can reverse the correct answer.
Maren turns instructions into architecture: prerequisite, step, condition, exception, action. Iona keeps each value attached to its role and status. Leonie protects the moving stream when numbers, names and changes arrive close together.
IDENTIFY THE ACTION JOB → LABEL TIMES/VALUES → TRACK STATUS → ATTACH CONDITIONS → MARK EXCEPTIONS → PRESERVE SEQUENCE → UPDATE CHANGES → FIND THE FINAL ACTION → ANSWER → RESET
Part I | Why practical audio is deceptively difficult
1. Practical language feels easy because the vocabulary is familiar
Words such as time, room, bring, pay, book, arrive and collect are common. That familiarity can hide the real challenge: relationship control. The learner must know which time is original, which is final, who the instruction applies to, whether an item is optional, and what must happen before another action becomes possible. Practical listening often tests logic embedded in everyday language.
2. Several true values can appear
An announcement can mention normal opening time, temporary opening time and last entry. All are true. Only one answers a specific question. Values must be bound to roles rather than stored as isolated numbers.
3. Original information can become obsolete
“The session was due to begin at two, but it will now start at two thirty.” The first time is not false; it is historical. The listener must update status. This is why final-state control is central to announcements.
4. Conditions make statements non-universal
“Members enter free if they book online.” Free entry is not a universal property of membership. The condition belongs to the proposition. Losing it produces an over-broad answer.
5. Exceptions reverse patterns
“All groups meet at nine except Group C, which arrives at ten.” The broad rule is easier to remember, but the exception is often the tested detail because it discriminates among similar options.
6. Optional and required information can sound equally important
Speakers may discuss an optional resource at length and mention a required document briefly. Duration does not determine status. Listen for required, must, need to, optional, recommended and can.
7. Sequence creates dependency
“Submit the form before booking an appointment.” Both actions are required, but order matters. A list without relation is incomplete.
8. Warnings add negative instructions
“Do not enter until the light turns green.” The learner must preserve prohibition and condition. Content-word notes such as “enter / light green” can accidentally remove the negative relationship.
9. Practical audio is often dense with numbers
Dates, times, prices, room numbers, reference codes and quantities may appear in one minute. Each value needs a label. Unlabelled numbers are fragile memories.
10. The listener may need to act on corrected spelling or names
Proper names and letter sequences can be high precision tasks. But exact spelling should only consume attention when the assessment requires it. Otherwise, role tracking can be enough.
Part II | Build an action-state model
11. Start with “what must the listener know or do?”
Before the audio, translate the task into an action job: final time, required item, sequence, exception, route, deadline, price, condition or warning. Practical listening improves when the listener is not treating every detail as equally actionable.
12. Separate actor from action
Instructions may apply to students, visitors, members, staff or one subgroup. “Who must do this?” is part of the proposition. Group labels deserve attention when rules differ by category.
13. Separate normal state from temporary state
An announcement can describe the usual rule and a one-day change. Mark NORMAL versus TODAY/THIS WEEK. Temporal scope prevents obsolete default information from winning.
14. Separate initial plan from current plan
Use OLD → NEW or cross-out notation where writing is useful. The current plan should become visually dominant.
15. Separate recommendation from requirement
“You may want to bring…” is not the same as “You must bring…”. Modality controls obligation.
16. Separate permission from obligation
“You can submit online” describes an option; “you have to submit online” describes a requirement. Exact relational language matters more than the shared verb.
17. Separate deadline from event time
Applications may close Friday while the event occurs Tuesday. Label times by role immediately.
18. Separate arrival time from start time
“Arrive by 8:45 for a 9:00 start.” Both times can be answer options. A role label prevents confusion.
19. Separate price from deposit
A booking can require a small deposit and a larger full fee. “$20” is meaningless without status.
20. Separate list price from discounted price
Attach the condition: standard 30; student 20 with ID. A value should carry its eligibility rule.
Part III | Times, dates and deadlines
21. Time values need event labels
Use “open 9”, “arrive 8:45”, “tour 9:30”. This adds little writing and greatly reduces binding errors.
22. Corrected time
“Three—sorry, three thirty.” Mark the first time obsolete. Do not leave both equal.
23. Approximate time
“Around three” should not become “exactly three”. Preserve approximation if answer choices distinguish it.
24. Earliest and latest times
“No earlier than…” and “by…” set boundaries. A single number without the inequality relation loses meaning.
25. Duration versus clock time
“The tour starts at two and lasts ninety minutes.” Ninety is duration, not start time.
26. Time zone or regional reference
Where a task legitimately includes time-zone conversion, preserve the source time and conversion rule. Do not calculate while critical audio continues if the format allows later work.
27. Relative time
“The following morning”, “two days earlier” and “next Friday” require relation. Store the relation before performing calendar arithmetic.
28. Repeating schedules
“Every weekday except Wednesday” combines pattern and exception. Notes should show both.
29. Deadline versus extension
An original deadline can be extended for a subgroup or all participants. Track who benefits from the change.
30. Booking window
Opening date, closing date and event date can all appear. Role binding is essential.
Part IV | Numbers, quantities and units
31. Number recognition is only the first step
A correctly heard number can still become a wrong answer if unit, group or status is lost. The useful memory is a labelled value.
32. Similar-sounding numbers
Thirteen/thirty and fifteen/fifty can be trained directly, but context and unit should be restored quickly. Pure digit drills are not the final task.
33. Prices
Attach currency, category and condition. “25 student if booked early” is more robust than “25”.
34. Percentages
Know what the percentage refers to and whether it represents increase, decrease or share.
35. Room numbers
Room 204 can compete with a date or time. Label role.
36. Reference numbers
If exact sequence is assessed, chunk digits. If it merely identifies an item printed elsewhere, do not over-invest attention.
37. Quantities with minimums
“At least three” means three or more. Preserve the boundary.
38. Quantities with maximums
“No more than ten” is not “about ten”. Scope words matter.
39. Ranges
“Between four and six” describes interval. Avoid selecting one endpoint unless the question asks.
40. Changed quantities
An order can be revised from twenty to fifteen units. Final-state tracking applies to quantities as well as times.
Part V | Conditions
41. If
The action applies only when a condition is satisfied. Attach condition to action in notes.
42. Unless
Unless introduces an exception to the expected action. Rewrite mentally if needed: action happens except when condition C occurs.
43. Provided that
This marks a condition for permission or result. Preserve it.
44. Only if
The condition is necessary. Do not generalise beyond it.
45. As long as
Permission or validity continues while a condition holds.
46. Before
One action is prerequisite. Sequence matters.
47. After
One action cannot occur until another is complete.
48. Until
Marks an endpoint or condition duration. “Wait until green” is not “wait while green”.
49. When
Can express time or condition. Use context.
50. Otherwise
Introduces consequence if the condition is not met. This can be answer-bearing.
Part VI | Exceptions and subgroup rules
51. General rule plus one exception
Write the general rule compactly and box the exception. Exceptions are cognitively expensive because they compete with an established pattern.
52. Several exceptions
Use subgroup labels rather than prose. Keep each exception attached to the correct category.
53. One subgroup with stricter rule
A rule may be optional for most and required for one group. Status differs by actor.
54. One subgroup with later time
Do not let the majority schedule overwrite the exception.
55. Age-based or category-based conditions
Where relevant, preserve the category without making assumptions beyond the audio.
56. Member versus non-member
Fees or access can differ. Labels are essential.
57. Online versus in-person booking
Different processes may have different deadlines or prices. Keep branches separate.
58. Weekday versus weekend
A common practical distinction. Do not merge schedules.
59. Regular versus special event rule
Temporary exceptions should not overwrite the long-term rule if the question asks normal practice.
60. Exception scope
An exception may apply only to time, not to price or location. Update the correct field only.
Part VII | Required, optional, recommended and prohibited
61. Required
Must, need to, required and have to indicate obligation. If the question asks what to bring, required items outrank recommendations.
62. Optional
May, can, if you wish and optional indicate choice. Do not convert them into requirements.
63. Recommended
Should, advisable and recommended are stronger than optional suggestion but weaker than obligation. Degree matters.
64. Prohibited
Must not, cannot, prohibited and do not indicate negative action. Preserve negation visibly.
65. No longer required
A previous requirement can be cancelled. Final status matters.
66. Newly required
A change can add an obligation. Mark the update.
67. Required for one stage only
An item may be needed at registration but not during the event. Attach time or stage.
68. Recommended because of a condition
“Bring a jacket if you plan to stay for the evening session.” Recommendation plus condition.
69. Prohibited unless authorised
Restriction can have exception. Preserve both.
70. Status-word priority
In practical audio, small modality words often carry more answer value than the main noun.
Part VIII | Sequence and procedure
71. Number the major steps
When order matters, use 1–2–3. Avoid prose.
72. Prerequisite
“Register before paying” creates dependency, not just sequence.
73. Parallel action
“While the device is charging, complete the form.” Two processes overlap. A simple linear list can misrepresent this.
74. Conditional branch
“If the screen shows red, restart; otherwise continue.” The procedure forks. Notes may need a branch diagram.
75. Repeated cycle
Some instructions loop until a condition is met. Preserve the stop condition.
76. Optional step
Do not insert an optional recommendation into the mandatory sequence.
77. Safety step
Warnings can precede action. Preserve prohibition or check as part of process.
78. Final verification
“Check the confirmation email before leaving” is a required final stage, not decorative advice if stated as obligation.
79. Corrected sequence
A speaker may change order after clarifying. Update step numbers.
80. Sequence versus chronology
Instructions describe what should happen; narratives describe what did happen. Keep procedural and historical order distinct.
Part IX | Changes and corrections
81. Correction words are high-value signals
Actually, sorry, rather, instead, correction and now often change status. Listen beyond the first plausible value.
82. Self-repair without a signal word
A speaker can restart and replace a phrase. Proposition completion matters more than cue vocabulary.
83. Partial correction
Only one field changes. Do not discard stable values.
84. Full plan revision
Time, venue and procedure can all change. Rebuild the state compactly.
85. Temporary change
“This week only” matters. Do not generalise.
86. Permanent change
“From next month onward” marks new default.
87. Delayed change
The new rule may begin later. Current and future state differ.
88. Conditional change
A revision may apply only if weather, capacity or another condition occurs.
89. Change reason
Questions may ask why the schedule changed, not what the new schedule is. Track trigger.
90. Change confirmation
A later statement may confirm that a proposed change became final. Proposal and confirmation differ.
Part X | Warnings and safety-style instructions
91. Warning architecture
Condition → risk → required/prohibited action. Preserve all three when relevant.
92. Negative instruction
“Do not…” must remain negative in notes. Content-only shorthand can reverse it.
93. Threshold warning
“If temperature exceeds X…” attaches a numeric boundary to action.
94. Exception to warning
A restriction may not apply to authorised users or certain times. Keep scope.
95. Sequence after warning
Warning may interrupt procedure and then process resumes. Do not treat it as another step unless it is one.
96. Recommended precaution
Distinguish advice from mandatory safety rule.
97. Emergency versus routine instruction
Same object, different condition. Identify trigger.
98. Risk versus consequence
“The floor may be slippery, so use the other entrance.” The risk is not the action.
99. Warning purpose
Questions can ask why an instruction is given. Track cause or risk.
100. Calm precision
Practical warning audio can feel urgent, but the examination still rewards exact relations, not emotional reaction.
Part XI | Announcements
101. Announcement opening
Usually establishes audience, event and purpose. Use it to create the action frame.
102. Schedule announcement
Track normal, changed and final times with labels.
103. Venue announcement
Original location, closed area and new meeting point can coexist.
104. Event cancellation
Distinguish cancelled, postponed, moved online or rescheduled. These states are not equivalent.
105. Delay announcement
Expected time and revised time both matter. Add reason only if question demands it.
106. Access announcement
Who may enter, when and through which route? Conditions matter.
107. Registration announcement
Deadline, eligibility, required documents and method are common fields.
108. Fee announcement
Standard fee, discount, deposit and refund conditions need labels.
109. Transport announcement
Departure point, time, alternative route and disruption can interact.
110. Public-service announcement
Action, audience and effective date are often central. Keep message purpose above examples.
111. Reminder announcement
May repeat old information and add one change. Identify what is genuinely new.
112. Multi-part announcement
Use section labels when several events or groups are covered.
Part XII | Instructions
113. Registration instructions
Sequence, documents, deadline and confirmation.
114. Booking instructions
Choice, availability, deposit and final confirmation.
115. Equipment instructions
Safety, sequence and conditional branches.
116. Digital process instructions
Login, verification, upload, submission and confirmation can be separate stages.
117. Application instructions
Eligibility, form, evidence, deadline and outcome notification.
118. Travel instructions
Route, transfer, departure and arrival conditions.
119. Event instructions
Arrival, identification, seating, materials and exit.
120. Classroom or training instructions
Task order, permitted materials, submission and checking.
121. Laboratory-style instructions
Sequence and safety may be tightly linked. Preserve prerequisites.
122. Survey or interview instructions
Who participates, how responses are recorded and what must be completed.
123. Route instructions
Spatial sequence and landmarks bridge toward the visual-listening owner.
124. Multi-stage procedural explanation
Longer instructions need sectioning: prepare, execute, verify, finish.
Part XIII | Names, spelling and codes
125. Proper-name function
If the name identifies a person only, exact spelling may be unnecessary. If the answer requires spelling, precision becomes central.
126. Spelled names
Chunk letters and use familiar letter-name distinctions.
127. Repeated spelling correction
A speaker can correct one letter. Update only that field.
128. Alphanumeric codes
Separate letters and digits in chunks.
129. Phone numbers
Group digits; preserve country or area code only if required.
130. Email-style information
Symbols, spelling and domain can demand exact capture. Practice according to the target exam.
131. Street or place names
Use printed options where provided; do not recreate spelling if unnecessary.
132. Reference labels
A code may only need matching to a printed field. Task determines precision.
133. Name versus role
When multiple people are involved, role can sometimes be more useful for memory than unfamiliar name.
134. Exactness budget
Spend attention on exact form only where marks require it.
Part XIV | Forms and completion tasks
135. The form is already a map
Use field labels to predict answer type. Do not duplicate printed structure in notes.
136. Name field
Expect spelling or selection depending on format.
137. Date field
Know whether start, booking or birth/event date is required.
138. Time field
Attach action role.
139. Price field
Check condition and currency.
140. Address field
Exactness can be high; preview printed context carefully.
141. Category field
A word or short phrase must fit the field semantics.
142. Quantity field
Unit may be printed or may need capture.
143. Reason field
Requires semantic compression, not raw noun copying.
144. Status field
Confirmed, pending, cancelled, optional or required may be the key.
145. Multiple similar fields
Keep row/column alignment. Correct information in wrong field is still a performance error.
146. Completion review
Read the completed form structurally. Does every answer fit its field and the audio?
Part XV | Distractor families in practical audio
147. Original-time distractor
True before update, wrong now.
148. Standard-price distractor
Wrong for a discounted category.
149. Deposit/full-price distractor
Correct amount, wrong role.
150. Recommended/required distractor
Same item, different obligation.
151. Optional/prohibited distractor
Modality reversed.
152. General-rule/exception distractor
Majority rule wrongly applied to subgroup.
153. Deadline/event-date distractor
Correct date, wrong action.
154. Cause/consequence distractor
Reason for delay confused with result.
155. Mentioned-alternative distractor
Option considered but not chosen.
156. Near-number distractor
Nearby value from same announcement.
157. Unit distractor
Right number, wrong unit.
158. Scope distractor
Rule for one group generalised to all.
159. Sequence distractor
Correct steps, wrong order.
160. Negation distractor
Prohibited action becomes required or allowed.
Part XVI | Diagnostic tests
161. Number-only test
Can the learner distinguish common number contrasts without language complexity?
162. Number-plus-role test
Can values remain bound to time, price and room?
163. Final-state test
Can the learner update after one and then two corrections?
164. Condition test
Does the answer preserve if/unless/only?
165. Exception test
Can subgroup rules survive a dominant general pattern?
166. Modality test
Can the learner distinguish required, recommended, optional and prohibited?
167. Sequence test
Are steps stored in dependency order?
168. Warning test
Can risk, trigger and action remain distinct?
169. Form-binding test
Does correct information go to correct field?
170. Spelling-precision test
When exact form is required, can the learner hold and record it?
171. Note-cost test
Do heavy notes cause later instruction loss?
172. Recovery test
Does one missed number cause the next instruction to disappear?
173. Rate test
Does faster natural pace expose number or note bottlenecks?
174. Speaker test
Does practical comprehension transfer across voices?
175. Topic test
Does the action-state model survive unfamiliar service contexts?
176. Answer-transfer test
Can correct understanding become a concise, valid response?
Part XVII | Practice progression
177. Stage 1: one value, one action
Short announcements with clear role labels.
178. Stage 2: two values, one distractor
Train role binding.
179. Stage 3: one correction
Original and final state.
180. Stage 4: condition
Attach if/unless to action.
181. Stage 5: exception
General rule plus subgroup.
182. Stage 6: requirement hierarchy
Required, recommended and optional items.
183. Stage 7: sequence
Three-step procedure.
184. Stage 8: warning
Trigger, risk and prohibited action.
185. Stage 9: several numbers
Dates, times and prices in one clip.
186. Stage 10: two revisions
Track final state through multiple changes.
187. Stage 11: longer announcement
Several groups or sections.
188. Stage 12: unfamiliar speaker
Test transfer.
189. Stage 13: unfamiliar context
Use new practical domain.
190. Stage 14: mixed question families
Detail, condition, sequence and inference together.
191. Stage 15: target timing
Match official playback rules.
192. Stage 16: unseen integrated section
Verify robust practical listening.
Part XVIII | Drills
193. Label-every-number drill
No naked numbers allowed. Every value gets unit or role.
194. Correction-chain drill
Old → revised → final.
195. Condition-attachment drill
Write action and condition on one line.
196. Exception-box drill
General rule plus boxed subgroup.
197. Modality ladder drill
Order must, should, may and must not by force.
198. Sequence-card drill
Reorder steps from audio after first hearing.
199. Branch-procedure drill
If A → X; otherwise → Y.
200. Required-versus-recommended drill
Same items, different status words.
201. Deadline-role drill
Application close, payment due, event date, arrival time.
202. Price-role drill
Deposit, full fee, discount and refund.
203. Warning-negation drill
Preserve do not, unless, until.
204. Partial-update drill
Only one field changes.
205. Sparse-note announcement drill
Allow only final states and exceptions.
206. No-note short instruction drill
Test whether writing is necessary.
207. Delayed-action drill
Ask what to do after several later details.
208. Form-completion drill
Map values to printed fields.
209. Spelling drill
Use only where exact spelling matters.
210. Recovery-after-number drill
Insert one hard number before an easy instruction and score containment.
Part XIX | Resident casebook
211. Maren: prose notes for instructions
Maren writes full sentences and misses the revised venue. A compact action map—time, place, must-bring—works better.
212. Iona: correct number, wrong role
She hears 25 perfectly but assigns it to price instead of participant limit. Her rule becomes value plus role.
213. Leonie: correction cascade
She misses the word “instead”, doubts the first value and stops listening. Recovery training keeps the uncertainty local until later context resolves it.
214. Maren: optional detail dominates
An optional book is discussed at length, while the required ID is mentioned briefly. She learns to track status words rather than duration.
215. Iona: outside knowledge overrides announcement
A transport delay sounds likely to be weather-related, but the speaker says staffing. Evidence wins.
216. Leonie: unfamiliar code fixation
She tries to perfect a reference number not needed for her question and loses the next instruction. Precision follows task scope.
217. Maren: sequence without dependency
She records steps but misses that verification must happen before payment. Arrows restore prerequisite logic.
218. Iona: exception over-generalised
She hears the special Saturday rule and applies it to weekdays. Scope labels fix it.
219. Leonie: number cluster
Date, price and room arrive together. A three-column label system keeps values bound without transcription.
220. Maren: final action over-written
She understands the whole procedure but the question asks what participants must do first. Minimum sufficient output matters.
221. Iona: recommendation becomes rule
“You should arrive early” is treated as mandatory. Modality ladder restores degree.
222. Leonie: late announcement fatigue
Near the end of the listening paper she stops marking corrections. Final-third practice preserves the update routine.
Part XX | Transfer across practical audio
223. Schedule to price
Same final-state mechanism, different value type.
224. Price to location
Correction tracking should survive surface change.
225. Announcement to instruction
Move from final-state listening to action sequence.
226. Instruction to warning
Negation and condition become more important.
227. Familiar service to unfamiliar service
Use action architecture when world knowledge is thinner.
228. Clear speaker to new speaker
Numbers and status words must remain accessible.
229. Moderate to faster natural pace
Reduce notes and preserve labelled values.
230. Short to multi-part announcement
Add section labels and subgroup separation.
231. Paper form to digital form
Field binding survives interface change.
232. Direct answer to paraphrased question
Meaning must survive wording changes.
233. One correction to multiple revisions
Track until state stabilises.
234. One subgroup to several subgroups
Increase rule-binding load gradually.
Part XXI | Stress tests
235. Number-density stress
Several values in short succession.
236. Correction-density stress
Multiple updates across fields.
237. Exception stress
Dominant rule plus subtle subgroup.
238. Modality stress
Must, should, may, cannot in one announcement.
239. Sequence stress
Several stages with prerequisite and branch.
240. Warning stress
Negative instruction plus exception.
241. Spelling stress
Only where format requires exact capture.
242. Unfamiliar-context stress
New practical domain with accessible language.
243. Speaker-variation stress
New clear voices.
244. Rate stress
Natural pace increase.
245. Note-limit stress
Restrict external memory.
246. No-note stress
Short task tests internal state model.
247. Recovery stress
One missed value before easy action.
248. Late-paper stress
Practical audio after sustained listening.
249. Form-layout stress
Unfamiliar but clear field arrangement.
250. Unseen full practical section
Integrate under target rules.
Part XXII | Measurement
251. Value-binding accuracy
Are numbers attached to correct roles?
252. Final-state accuracy
Are corrections and current values preserved?
253. Condition accuracy
Are if/unless clauses retained?
254. Exception accuracy
Are subgroup rules kept separate?
255. Modality accuracy
Required, recommended, optional and prohibited remain distinct.
256. Sequence accuracy
Are steps and prerequisites correctly ordered?
257. Warning accuracy
Are trigger, risk and action distinguished?
258. Form-binding accuracy
Does information enter the correct field?
259. Note efficiency
Do labels preserve values without causing lag?
260. Recovery cost
Does one missed detail damage later instructions?
261. Transfer penalty
Do new voices or contexts create manageable cost?
262. Late-section decay
Do final-state and exception rules survive fatigue?
Part XXIII | Teacher protocol
263. Ask for role, not just number
“What was 25?” reveals whether the value is bound.
264. Compare normal and temporary state
Use minimal pairs.
265. Teach status vocabulary explicitly
Optional, required, postponed, cancelled, confirmed and pending are high-value words.
266. Model branch diagrams
Use them only when instructions genuinely branch.
267. Fade written labels
External structure should become lighter as skill stabilises.
268. Design fair corrections
Earlier values should be plausible, final change clearly supported.
269. Use authentic practical relationships
Do not create arbitrary number traps without communicative logic.
270. Preserve unseen announcements
First-contact value binding matters.
271. Route note mechanics outward
Use the note-taking owner for detailed shorthand problems.
272. Route distractor mechanics outward
Use the specialist distractor owner for general correction/alternative mechanics.
273. End with new practical contexts
Transfer should be tested beyond familiar schedules and prices.
274. Monitor late-paper status errors
These often reveal procedural fatigue.
Part XXIV | Self-study protocol
275. Preview fields
Know which values or actions matter.
276. Attempt audio-first
Do not begin with transcript.
277. Label values minimally
Number plus role.
278. Mark updates
Old state visibly obsolete.
279. Check conditions
Ask whether the action was universal.
280. Check exceptions
Identify subgroup rules.
281. Use replay diagnostically
Where practice permits, target the unresolved field.
282. Use transcript after reconstruction
Find exact missed relation.
283. Write one repair rule
Example: “No naked numbers; label every value.”
284. Test new audio
Transfer immediately.
285. Return after delay
Use another practical task later.
286. Integrate under official rules
Remove practice-only control before readiness decisions.
Part XXV | Parent-supported practical listening
287. Give one short announcement
Include a time, change and final action.
288. Ask “what changed?”
Build final-state listening.
289. Ask “what must you do?”
Build action extraction.
290. Ask “who is the exception?”
Build scope awareness.
291. Ask “what is optional?”
Build modality precision.
292. Keep it brief
Practical listening practice should not turn every household instruction into a test.
Part XXVI | Exam-day operating model
293. Before audio
Identify value/action categories and answer count.
294. When a number appears
Bind it immediately to role or unit.
295. When a correction appears
Update the right field and mark old state obsolete.
296. When a condition appears
Attach it to the action on the same mental line.
297. When an exception appears
Separate subgroup from general rule.
298. When modality appears
Preserve required, recommended, optional or prohibited.
299. When sequence appears
Number steps and prerequisites.
300. When one value is missed
Mark uncertainty and protect the next action.
301. When notes become dense
Return to labelled states rather than prose.
302. When two answers seem plausible
Compare role, status, condition and time.
303. Before moving on
Complete the required answer, not a summary of the whole announcement.
304. At final review
Check field alignment, units, scope and updated values.
Part XXVII | Technical appendix: action-state template
WHO → MUST/MAY/MUST NOT → ACTION → WHEN → WHERE → CONDITION → EXCEPTION → FINAL STATE. Not every task uses every field. The template exists to make practical information relational rather than a bag of details.
Part XXVIII | Technical appendix: status dictionary
Original: earlier plan. Current: active state. Proposed: possible but not final. Confirmed: committed. Cancelled: no longer occurring. Postponed: delayed. Optional: permitted but not required. Required: obligatory. Recommended: advised. Prohibited: not allowed. Conditional: depends on another state.
Part XXIX | Technical appendix: practical-audio error ledger
Useful categories include number recognition, number-role binding, final-state update, condition loss, exception loss, modality confusion, sequence error, prerequisite error, warning negation, spelling precision, form alignment, note lag, recovery cascade and answer-scope transfer. Record only patterns that affect the next training decision.
Part XXX | Final checklist
- I label numbers by role or unit.
- I distinguish normal, original and current states.
- I track changes until the final plan stabilises.
- I keep conditions attached to actions.
- I mark exceptions visibly.
- I distinguish required, recommended, optional and prohibited.
- I preserve step order and prerequisites.
- I keep warnings negative where they are negative.
- I use the printed form or table as structure when provided.
- I do not over-spend attention on names or codes unless exactness is required.
- I recover after a missed number or detail.
- I answer the requested action or state, not every fact I heard.
Closing synthesis | Practical listening is state control
Announcements and instructions reward the listener who knows that everyday language carries hidden state. A time can be normal, original, revised or final. An item can be required, recommended or optional. A rule can apply to everyone except one group. An action can be permitted only after another action. A warning can reverse an apparently obvious instruction. The vocabulary may be simple; the logic is not.
Maren turns that logic into an action map. Iona keeps every value attached to source, role, condition and status. Leonie keeps the live stream available when numbers and corrections arrive close together. Their shared standard is operational accuracy: after the recording ends, the learner should know not merely what words were said, but what is true now, who it applies to and what must happen next.
Previous: SETC-SEC-LISTEN-100 | Talks and Monologues · Hub: Secondary English Listening Examination Performance · Next: SETC-SEC-LISTEN-120 | Listening Comprehension with Visuals
Advanced Practical-Listening Casebook | When Small Words Change the Action
The main article builds the action-state model. This casebook pushes it into dense realistic situations where several individually true details compete. Each case asks the learner to preserve role, status, condition, exception and final action while resisting the urge to treat practical audio as a bag of easy nouns and numbers. The most important information is often carried by small relational language: only, except, until, instead, no longer, after, unless, required, optional.
Case 1 | Normal opening time versus temporary opening time
A centre normally opens at nine, but on one particular day will open at ten because of maintenance. The question asks when visitors can enter that day. Both times are true statements; only the temporary state answers the job. The repair rule is temporal status: NORMAL 9 / TODAY 10. A listener who stores only numbers must guess later.
Case 2 | Start time versus arrival time
An event begins at ten, but participants are asked to arrive at nine thirty for registration. A question asks when participants should arrive. The value “10” is more semantically prominent because it is the event time, yet the operational answer is 9:30. Role labels—ARRIVE, START—prevent this common binding error.
Case 3 | Arrival time changes, start time does not
The speaker corrects the arrival instruction from 9:30 to 9:15 while keeping a 10:00 start. Learners who treat the whole schedule as changed may alter both times. Practical updates are field-specific. Update only the value the speaker revises.
Case 4 | Deposit versus total fee
A booking requires a 20-unit deposit against a total fee of 80. A question asks what must be paid when booking. The answer is the deposit, not the larger and more memorable total. Amount plus payment stage forms one proposition.
Case 5 | Full fee versus early-booking fee
The standard fee is 80, but bookings before a stated deadline cost 65. A learner who hears “80” first can commit too early. The discounted price is conditional on time. Store 80 STANDARD; 65 IF BEFORE DEADLINE.
Case 6 | Discount exists but does not apply to this person
The announcement mentions a student discount, but the question concerns an adult visitor. The discounted amount is true but irrelevant. Practical audio frequently contains subgroup values that must remain attached to eligibility.
Case 7 | Optional resource discussed at length
The speaker spends several sentences praising a guidebook and one short sentence saying identification is required. Duration can mislead. If the task asks what participants must bring, status vocabulary outranks discussion length. Notes can mark ID MUST / guide optional.
Case 8 | Recommended item versus compulsory item
Participants should bring a water bottle but must bring their entry pass. “Should” and “must” share positive direction but differ in obligation. A distractor can exploit that similarity. Modality is part of meaning.
Case 9 | Something is no longer required
An old instruction says printed confirmation is needed. The speaker announces that digital confirmation is now sufficient and paper is no longer required. Learners familiar with the old rule may retain it. Final-state status beats prior knowledge and earlier mention.
Case 10 | Something becomes newly required
A document that was previously optional becomes mandatory from a future date. The learner must preserve effective date as well as status. “Required” without “from next month” can be too broad.
Case 11 | Deadline versus last possible action
Applications close on Friday, but payment can be completed until Monday for applications submitted before the deadline. The two deadlines govern different actions. Write action first, date second rather than storing two calendar values.
Case 12 | Event postponed, not cancelled
The speaker says an event will not happen Saturday and gives a new date. “Cancelled” is a tempting but inaccurate status. Practical state vocabulary matters because postponed preserves the event while changing time.
Case 13 | Event cancelled, replacement offered
The original event is cancelled and a different event is offered. Do not treat the replacement as a rescheduled original if the speaker distinguishes them. Status and identity both change.
Case 14 | Venue changed, route instructions partly unchanged
The destination moves from Hall A to Hall B, but the first half of the route is identical. A learner who discards all route information creates unnecessary memory work. Update only what changes.
Case 15 | Main entrance closed, side entrance open
The map or announcement may mention the main entrance first. The current action is use side entrance. “Main” does not mean current. Final accessibility status controls.
Case 16 | Everyone except one group
All participants arrive at nine except advanced group members, who arrive at ten. A general rule dominates most of the audio, yet one subgroup question requires the exception. Box exceptions because they are easy to overwrite with the majority pattern.
Case 17 | One group has extra requirement
Everyone completes the online form; international participants additionally upload one document. The exception adds, rather than replaces, the general rule. Notes should show BASE RULE + subgroup addition.
Case 18 | One group is exempt
Most participants pay a fee; volunteers do not. Exemption removes a requirement. The same “exception” concept can add or subtract an action, so direction matters.
Case 19 | Weekday rule with weekend exception
Entry is free on weekdays, while weekends require payment. Familiar repeated schedule patterns can produce automatic generalisation. Day category stays attached to rule.
Case 20 | Weekend rule with one special Saturday
The usual weekend fee is waived for a special event on one Saturday. The hierarchy now has three layers: weekday, normal weekend, special Saturday. Do not flatten them.
Case 21 | If condition changes action
“If you arrive after six, use the side door.” The side door is not the universal route. Condition and action form one unit. A question about five o’clock should not select it.
Case 22 | Unless condition reverses default
“Use the main hall unless your confirmation says Room 3.” Learners often find unless harder under speed because it defines an exception through negation. Rewrite mentally as main hall for everyone except Room-3 confirmation holders.
Case 23 | Only if sets a necessary condition
“You can receive the reduced fee only if you register online.” Online registration is necessary for discount. Do not infer that everyone who registers online is automatically eligible if another condition exists elsewhere.
Case 24 | Two conditions must both hold
Discount applies to students who book before Friday. Student status alone is insufficient; deadline alone is insufficient. Store conditions as a conjunction: student + early booking → discount.
Case 25 | Either condition can qualify
An action is permitted for members or invited guests. The logic differs from requiring both. Practical listening can test and/or relationships even with simple vocabulary.
Case 26 | Sequence with a hidden prerequisite
The speaker says to choose a time slot, but earlier notes that account verification must be complete first. A learner remembering actions without dependency may reverse them. Procedure notes should distinguish steps from prerequisites.
Case 27 | Sequence with parallel work
While a file uploads, the learner is instructed to complete another field. This is not step 2 after step 1; the tasks overlap. A simple flow diagram can represent parallel actions more accurately.
Case 28 | Sequence with a branch
If confirmation appears, continue to payment; if not, return to the previous screen. The procedure is conditional. Linear numbered notes can mislead unless branch logic is shown.
Case 29 | Sequence with an optional shortcut
A faster route exists for users with a saved profile, while everyone else follows the full process. Optional shortcut should not replace the default procedure.
Case 30 | Final verification is easy to miss
After several action steps, the speaker says to check the confirmation email. Learners often mentally finish when payment is complete. The final check is still a required stage if the speaker says so. Procedural listening continues until the action chain closes.
Case 31 | Warning interrupts the procedure
The speaker gives step two, inserts a warning, then resumes with step three. A learner can accidentally number the warning as another step. Function matters: warning qualifies the process rather than advancing it.
Case 32 | Warning applies only under a threshold
Do not use the equipment if a reading exceeds a value. The number is a condition boundary, not a target. Number plus comparison operator matters.
Case 33 | Negative instruction loses the negative
Notes contain “enter red light” after audio says “do not enter while the red light is on.” Content words survived; meaning reversed. Negation needs visible notation such as NO or ✗.
Case 34 | “Until” reversed
“Wait until the light turns green” means action starts after the state changes. A learner who treats until as “while” performs the opposite action. Temporal connectors deserve direct training.
Case 35 | Exact spelling matters in one field only
The form asks for a surname and two other conceptual answers. The learner should invest orthographic precision in the name without trying to transcribe surrounding explanation. Exactness is task-weighted.
Case 36 | One letter is corrected
The speaker spells a name, then says “that final letter is N, not M.” Update the one position instead of rewriting the full name while audio continues.
Case 37 | Reference number contains grouped digits
Chunking 382-417 is easier than six independent digits. Grouping should follow the spoken or printed structure where possible.
Case 38 | Number correction after a pause
The speaker gives a code, continues, then returns to correct it. Final-state tracking must remain available even after attention has moved. A light note makes the field editable.
Case 39 | The announcement gives background before action
Several sentences explain why a service is changing before the speaker states what users must do. A learner who writes all background can miss the action. The question job should bias attention toward the operational section.
Case 40 | The announcement gives action before explanation
The speaker states the new route first and then explains why. If the question asks reason, the learner must keep listening after already knowing what to do. Practical audio can separate action and cause across sections.
Case 41 | Same value, different role
The number 12 appears as both a room number and a participant count in different parts of the recording. Role labels prevent false matching.
Case 42 | Same date, different year
An announcement compares this year’s deadline with last year’s. The day and month match but the historical reference differs. Time frame belongs to the value.
Case 43 | Approximate versus exact arrival
“Aim to arrive around nine” differs from “registration closes at exactly nine.” One is recommendation, one boundary. An option saying everyone must arrive exactly at nine collapses two statuses.
Case 44 | “By nine” versus “at nine”
“By” includes earlier arrival; “at” points to a specific time. Small prepositions can define the action window.
Case 45 | “From nine” versus “until nine”
One marks start, the other endpoint. The same number can support opposite time relations.
Case 46 | One exception mentioned before the general rule
The speaker begins with “Group C arrives at ten; everyone else comes at nine.” Learners expecting general-then-exception architecture can misclassify. Logical structure should be inferred from scope language, not mention order.
Case 47 | Rule changes after a future date
Current users follow one process; applications submitted after next month follow another. A question about present procedure differs from future procedure. Effective date is a state boundary.
Case 48 | Refund condition
A fee is refundable only before a deadline. The amount and refundability are separate attributes. Do not assume “paid” means “non-refundable” or “refundable” means “no fee”.
Case 49 | Capacity limit
The speaker says the room holds 40, but registration is capped at 30 to allow spacing. Which number is the participant limit? The functional rule may differ from physical capacity.
Case 50 | Recommended route differs from shortest route
The speaker recommends a longer accessible route. A learner looking at a map may choose the visually shortest path. Audio status—recommended route—controls the answer.
Practical Lab 1 | Naked-number ban
For one session, every written number must have a label: ARR 9:15, FEE 20, RM 4, DEADLINE 18 Jun. The constraint reveals whether number errors are recognition or binding problems. Later, labels can be shortened as the habit becomes automatic.
Practical Lab 2 | Status-word collection
Build short clips around required, optional, recommended, prohibited, postponed, cancelled, confirmed and pending. The learner identifies status before content details. This strengthens the vocabulary that governs action.
Practical Lab 3 | Condition pairs
Compare two near-identical announcements differing only in if, unless, only if or provided that. Ask how the eligible group changes. Minimal contrasts sharpen logic.
Practical Lab 4 | Exception density
Start with one general rule and one exception, then add another subgroup. Keep vocabulary stable. The learner practises rule binding rather than language difficulty.
Practical Lab 5 | Partial correction
Give time, place and fee, then correct only one. Ask which fields remain unchanged. This prevents over-updating.
Practical Lab 6 | Two-revision chain
Original time changes once and then changes again. The learner must track until the state stabilises. The rule is not “choose the second number”; it is “hold provisional values until the decision closes”.
Practical Lab 7 | Action versus explanation
Use announcements where action precedes reason and others where reason precedes action. The learner identifies both roles regardless of order.
Practical Lab 8 | Procedure branch
Use a simple flow with one conditional branch. The learner draws a two-line diagram rather than a paragraph. Once accurate, increase to two decision points.
Practical Lab 9 | Recovery after code
Insert one difficult reference number before an easy final instruction. The later instruction is the main score. This teaches that exact-data uncertainty should not destroy the next action.
Practical Lab 10 | Full unseen practical section
Mix announcement, form completion, schedule change and short instruction under target conditions. Review errors by state category: role, value, condition, exception, sequence, modality, recovery or output.
Teacher Lab | Designing useful distractors
Use values genuinely mentioned in the audio: original time, standard fee, optional item, general rule. Make the wrong option plausible because of a predictable status error, not because of obscure trick wording. High-quality distractors teach state control.
Teacher Lab | Avoiding meaningless number overload
Several numbers can create realistic density, but every number should belong to a communicative context. Random digit bombardment trains short-term memory more than listening comprehension. The educational target is labelled evidence under time.
Teacher Lab | Teaching “small words, big effect”
Highlight a short set of relational words after audio-first practice and show how each changes the action. Then return to natural speech. The goal is not connector spotting but proposition accuracy.
Teacher Lab | Separating spelling from listening
If the learner hears the name correctly but spells it wrongly, the repair is orthographic. If the sound sequence itself is wrong, the repair is auditory. Do not treat all form-completion errors as listening weakness.
Self-study Lab | Action-state recap
After one announcement, write only WHO / ACTION / WHEN / CONDITION / EXCEPTION / FINAL. Then compare with the transcript or key. This exposes which state fields disappear under pressure.
Self-study Lab | Role-labelled replay
Before replaying, state the unresolved role: “deadline?”, “deposit?”, “arrival time?”. Targeted replay improves diagnostic value.
Parent Lab | One change, one condition
Read a short practical message such as “We planned to leave at three, but we’ll leave at four if the rain stops.” Ask for original, final/conditional plan and trigger. The exercise builds everyday state tracking without formal exam language.
Exam Pressure Lab | Dense numbers
When several values arrive, prioritise those linked to visible questions or high-value action states. Do not rehearse one number so long that the next role is missed. Label and release.
Exam Pressure Lab | One uncertain condition
If “if” versus “unless” is unclear, mark the item and keep listening. Later restatement can resolve the logic. Do not allow one connector to occupy the next instruction.
Exam Pressure Lab | Final-state check
Before moving on from a practical section, ask only: which values changed, which rules had exceptions, and which action is final? This compact check captures the highest-risk state errors without rereading everything.
Advanced exit criterion | Values remain bound
Numbers, dates and names stay attached to the correct role even in dense audio.
Advanced exit criterion | Conditions survive
If, unless, only if and related constraints remain part of the final answer.
Advanced exit criterion | Exceptions remain visible
Subgroup rules are not overwritten by dominant patterns.
Advanced exit criterion | Modality remains precise
Required, recommended, optional and prohibited are reliably distinguished.
Advanced exit criterion | Procedures remain relational
Prerequisites, parallel actions and branches are represented correctly.
Advanced exit criterion | Corrections update selectively
Only changed fields are replaced and final state remains clear.
Advanced exit criterion | Recovery protects later action
One uncertain code, name or value rarely causes a cascade.
Advanced exit criterion | Practical transfer survives novelty
The same state-control system works across bookings, schedules, notices, service information and unfamiliar practical contexts.
Advanced closing synthesis | The correct answer is the correct state
Practical listening is reliable when the learner stops storing values as isolated facts and starts storing them as labelled states. Nine o’clock is not simply a number; it might be normal opening, previous opening, arrival deadline or event start. A book is not simply an item; it may be optional while identification is required. Friday is not simply a date; it may be application deadline rather than event day. Small relational words decide which interpretation is operationally true.
The mature listener therefore builds an action-state model that can be updated without rewriting the world. When the speaker corrects one field, only that field changes. When an exception appears, the general rule remains for everyone else. When a condition appears, it stays attached to the action. When a detail is missed, the next instruction remains protected. That is how simple everyday language becomes precise examination performance.