Use this section as a quick repair kit. Spot the issue, grab the fix, and try the “Before → After” lines out loud.
Use this section as a quick repair kit. Spot the issue, grab the fix, and try the “Before → After” lines out loud.
Problem: You start talking without a main point.
Fix: One-line opener that matches the task (advice/opinion/choice/location).
Before → After
Problem: “It’s better, faster, cheaper” with no proof.
Fix: Add one tiny example (time/place/number) to each reason.
Before → After
Problem: “things, stuff, good, bad” repeated.
Fix: Swap in precise, everyday words and rotate synonyms.
Before → After
Problem: Long sentences, filler chains (“uh, like”), monotone.
Fix: Shorter sentences, one-beat pauses, simple connectors (because/so/for example), light stress on key words.
Before → After
Problem: Not answering the prompt or using the wrong style.
Fix: Match the audience and purpose (speak to a person in Task 1; choose one in Task 5; use future in Task 4; make a direct request in Task 6).
Before → After
Problem: You end with silence or race the last lines.
Fix: Use a time map; add a wrap line if you finish early; if time is short, stop new points and close cleanly.
Wrap bank
Error signs: No opener, mixed order, missing examples.
Fix: Use a simple arc: opening → reason A (+ example) → reason B (+ example) → wrap.
Ten-second drill: Write four cues: [Opening] / [A+ex] / [B+ex] / [Wrap].
Error signs: Vague words, memorized phrases, unnatural “fancy” terms.
Fix: Use everyday collocations (rush hour, repair timeline, schedule update). Rotate structures, not only words.
Swap bank
Error signs: Filler chains, run-ons, choppy rhythm.
Fix: One idea per sentence. Use because/so/for example. Self-correct in a few words and move on.
Self-correct frames
Error signs: Ignored instruction, wrong tone, time not used.
Fix: Check the sub-task (choose, request, describe, predict). Use the full time with a clear close.
One-line check: “Did I answer exactly what they asked, with the right tone, and finish strong?”
Common errors: Talking about the topic instead of to the person; weak steps with no reason.
Fix: Use you; give two steps with a brief reason/example.
Rescue line: “First, [step], because [reason]. Second, [step]; for example, [detail].”
Common errors: Rambling story; no result or lesson.
Fix: Context → what happened → result → takeaway.
Rescue line: “Last week at [place], I [action]; as a result, [impact]. I learned [lesson].”
Common errors: Guessing stories; generic nouns; random order.
Fix: Overview → 3 concrete details → clue-based inference. Name roles/objects; choose a scan (left→right or front→back).
Rescue line: “This looks like [place]. I’ll go left to right. First, a cashier is scanning…”
Common errors: Staying in the present; no reason.
Fix: Future forms (will/going to/might) + because/so + visible clue.
Rescue line: “Because I see [clue], they will [next], so [result].”
Common errors: Not choosing; describing both; no call to action.
Fix: Pick one in line 1; give two benefits with examples; one-line counterpoint; ask for action.
Rescue line: “I recommend [Option]. First, it [benefit]… Second, it [benefit]… Although the other [small plus], it doesn’t fix [main issue]. Let’s book this.”
Common errors: Long emotional backstory; no request; confrontational tone.
Fix: Problem → request → reason → option → confirm; polite and firm.
Rescue line: “Hello, this is [name]. [Problem]. Could you [request]? Because [impact]. If not, [option]. Please confirm.”
Common errors: Hiding your position; repeating the same point; no wrap.
Fix: Position in line 1, two different reasons with small examples, brief nod, clear close.
Rescue line: “I support [X]. First, [reason + example]. Second, [reason + example]. Overall, it solves the main issue.”
Common errors: No exact location; no concrete clues; vague ask.
Fix: Who/why → where (landmarks) → what’s odd (2 clues) → action → reference.
Rescue line: “Hi [role], I’m at [place + landmark]. I see [clue 1] and [clue 2]. Could you [action]? Reference [#/time/unit].”
Problem: Scripted answers or reading a “perfect” speech.
Why it hurts: Raters value spontaneous, natural speech over memorized text.
Safer approach: Use flexible frames (POINT, CARE, SIGHT, WILL) and fill them with fresh details from the prompt.
Before → After
All tasks
Task-specific
Pro Membership
Unlock all premium features