4.3 Fluency
Key Takeaways
- Fluency measures the rhythm, phrasing, pausing, and reaction time of your speech, not how fast you talk
- The engine reads long silences, filled pauses like 'um,' and audible restarts as low fluency
- It is driven by Reading Aloud, Repeats, Sentence Builds, and Story Retelling — the tasks requiring sustained or timed speech
- Racing through sentences can lower the score because it blurs delivery and triggers more stumbles
- A no-restart rule, phrasing drills, and replacing fillers with brief silent pauses retrain the habits this subscore rewards
What Fluency Measures
Fluency is the subscore that captures the rhythm and timing of your speech — the spacing between your words, your phrasing, your reaction time after a prompt, and how much you hesitate or restart. It is not a measure of how fast you talk. A person who races through sentences can score lower than one who speaks at a steady, natural pace, because the engine is listening for smooth, well-paced delivery with minimal disruption, not raw speed.
Concretely, the engine reads three things as low fluency: long silences before or during a response, filled pauses (um, uh, er), and audible false starts and self-corrections ("I think— no, I mean—"). It reads high fluency as speech that flows in natural phrases with appropriate, brief pauses at clause boundaries.
Which Tasks Drive It
Fluency is drawn from the four tasks that require sustained or timed speech:
| Task | How it tests Fluency |
|---|---|
| Reading Aloud | Natural phrasing and steady pace on a printed sentence |
| Repeats | Reproducing a sentence in one smooth pass |
| Sentence Builds | Delivering the rebuilt sentence without restarts |
| Story Retelling | Keeping a smooth flow for the full 30-second window |
Worked Contrasts
- Reading the sentence "The train to the airport leaves every twenty minutes."
- Fluent: delivered in two natural phrases — "The train to the airport / leaves every twenty minutes" — steady pace.
- Disfluent: "The train... um... to the, to the airport... leaves... every twenty minutes." — same words, but pauses, a restart, and a filler drag the score down.
- In a retell: "She— she called the, um, the manager and, and reported it." The content is fine, but the doubled words and fillers signal disfluency.
How the Engine Reads Pausing and Timing
Not all pauses are equal. A brief pause at a clause boundary — after a comma, between two ideas — is natural and does not hurt you; skilled speakers pause there constantly. What lowers the score is a pause in the wrong place: mid-phrase, between an article and its noun ("the... umbrella"), or before you have even started. The engine also weighs your reaction time: the gap between the end of the prompt and the start of your response. A long lead-in silence reads as slow processing. This is why having a ready opening frame — "The story is about...", "I prefer..." — matters so much: it lets you start on time and pause only where a fluent speaker would.
Speed and rhythm interact, too. Fluency is not the same as talking fast; it is talking at an even, sustainable rate with natural stress and phrasing. A common mistake is to sprint at the start of a response and then grind to a halt when a hard word comes up, producing a lurching rhythm. A steady middle pace that you can maintain for the whole window scores better than bursts of speed broken by stalls. Think of it as a comfortable walking pace, not a sprint-and-rest.
Finally, remember that Fluency is drawn from four different tasks, so a single stumble does not sink the subscore — but a habit of fillers and restarts across all of them will. That is why the drills below target the habits themselves rather than any one performance.
Common Traps
- Equating fast with fluent. Racing blurs your pronunciation and often triggers more stumbles. A calm, even pace scores better.
- Filled pauses. Um and uh are the most common fluency leak. A short silent pause sounds far more controlled than a filled one.
- Restarting. Every "I mean, let me start again" is a black mark. Commit to your sentence and finish it.
- Freezing after the prompt. A long silence before you begin is scored as slow reaction time. Have an opening frame ready so you start within a second.
Drills That Raise It
- Timed reading with phrasing marks. Mark a text into sense-groups with slashes and read it aloud at a steady pace, pausing only at the slashes. This builds natural rhythm.
- Metronome or pace pacing. Read along to a slow, steady beat to break the habit of rushing or lurching.
- The no-restart rule. Practice speaking answers with a personal rule: once you start a sentence, you must finish it, even if imperfect. This kills the self-correction habit that the engine penalizes.
- Filler tracking. Record yourself and count every um and uh. Simply becoming aware of them, and replacing each with a brief silent pause, cuts them fast.
- One-second-start drill. Practice answering prompts with a stopwatch, forcing yourself to begin speaking within one second of the prompt ending, using a ready opening frame. This attacks reaction-time silence, which the engine reads as slow processing.
Fluency is a habit as much as a skill, so the drills work by retraining reflexes — steady pacing, silent pauses instead of filled ones, and finishing every sentence you begin. Within a couple of weeks those habits show up as a smoother, higher-scoring delivery even when the content is unchanged.
Two candidates say the same sentence. One races through it quickly with two 'um' fillers and a restart; the other speaks at a steady pace in natural phrases. Why does the steady speaker score higher on Fluency?
Which habit does the recommended 'no-restart rule' drill target?
According to the fluency guidance, what should replace a filled pause like 'um' when you need a moment to think?