Skip to main content

Using Fluency Lab

Learn about how to use Fluency Lab in Connections Reading.

Overview

Fluency Lab helps you collect, review, and respond to oral reading. Students record themselves reading an assigned passage; you review the recording with the help of AI-assisted error detection and a prosody rubric, adjust anything that needs your judgment, and release feedback. Class and student reports let you watch growth over time.

Use Fluency Lab as an instructional data point — not as a standalone high-stakes assessment.

Introduction

Fluency Lab is:

  • A progress-monitoring tool for oral reading fluency

  • A bridge between oral reading and comprehension when a cold read includes questions

  • A way to identify who needs added support in pacing, accuracy, phrasing, and expression

  • A tool that supports both AI-assisted review and fully teacher-scored review

  • A short routine that can sit near the beginning and end of a chapter without replacing the core lesson

Fluency Lab is not:

  • A universal screener or benchmark replacement

  • A diagnostic placement tool

  • A grading-only system

  • A measure of phonics or decoding mastery by itself

  • A Tier 3 intervention program by itself

Fluency Lab supports two read types — a cold read (with a short comprehension check) and a warm read (fluency-only). For details on when to use each and how they fit into a chapter, see the Cold Reads and Warm Reads and Where Fluency Lab Fits in Instruction sections below.

Fluency Lab Feedback

After a student records and submits, Fluency Lab produces feedback for you to review. It includes:

  • WCPM (Words Correct Per Minute)

  • Fluency (0–100) — flow and pacing

  • Accuracy (0–100) — word-level correctness (words read as written)

  • Prosody (0–100, plus a 4-dimension rubric scored out of /16)

  • Error counts by type: Mispronunciations, Omissions, Hesitations/Pauses

  • 3 comprehension responses (cold reads only): student answers vs. correct answers

  • A detailed error list with playback for each flagged word

The three scores measure different things — and why you need all three

Each 0–100 score answers a different question about the same reading:

Score

The question it answers

In one word

Accuracy

Did they say the right words?

Correctness

Fluency

Did they read smoothly and at a reasonable pace?

Effortlessness (automaticity)

Prosody

Did it sound like meaningful, expressive language?

Expression

Why all three are needed. A student can be strong on one and weak on another, and each gap points to a different instructional next step:

  • High Accuracy, low Fluency — reads the words correctly but slowly or haltingly → build automaticity (e.g., repeated reading).

  • High Fluency, low Prosody — fast and smooth but flat or monotone → work on expression and phrasing.

  • High Accuracy and Fluency, low Prosody — decodes effortlessly but isn't yet reading for meaning → coach expressive, meaning-driven reading.

If the three scores were redundant, these profiles couldn't happen. The fact that a student can look very different across them is exactly why we report them separately.

A note on overlap. These are distinct measures, but they are not perfectly independent — reading is one connected act, and the research they're based on treats accuracy, automaticity, and prosody as related components of fluency (Rasinski, 2004). Where a behavior reasonably bears on more than one score, it does — but each score has a single primary focus. The clearest example is pace: Fluency uses pace as a broad check on whether the overall rate sits in a reasonable range, while Prosody's Pace dimension judges whether the rate and pausing sound natural and support meaning. Related questions, deliberately kept distinct.

Core rule: Scores update as you confirm/dismiss errors and adjust rubric inputs, so your review directly affects the final result the student sees.

How Accuracy is scored — and how we handle insertions and substitutions

Accuracy uses the standard Oral Reading Fluency (ORF) formula:

Accuracy = (total words − total errors) ÷ total words × 100

This matches what teachers are familiar with from running records, DIBELS, and AIMSweb. Every error type counts equally as one error — there is no weighting between error types.

How insertions and substitutions are handled:

  • A substitution counts as a single omission (one passage word = one miscue). When a student says a different word for a passage word, the engine tags the passage word as missed rather than counting both a "missing" passage word and an "extra" inserted word. This keeps one misread word as one error (matching traditional miscue counting) instead of double-penalizing it.

  • Insertions (extra words) count as errors but are not shown as a separate count. Extra words most often come from self-corrections, restarts, repeated attempts, or background noise. They lower the Accuracy score (so genuinely sloppy reading is reflected) but are intentionally not surfaced as discrete student-facing errors, to cut noise from normal disfluencies. Self-corrections where the student recovers cleanly can be dismissed in review.

  • Hesitations/pauses are excluded from Accuracy. They only affect the Fluency score.

  • A global sequence alignment (Needleman–Wunsch style) keeps the read on track. This prevents a single hesitation, repetition, or self-correction from knocking the rest of the passage out of alignment and cascading into a string of false errors. A side effect is that some self-corrections/restarts surface as insertions rather than corrections.

  • What you actually see: the report surfaces mispronunciation and omission counts. Insertions and substitutions affect the Accuracy score but are not displayed as their own counts.

Using the Feedback

Open a submission to review it in one of two modes. The mode is set when the product loads the review (AI-assisted by default; teacher-scored when configured for a no-AI experience).

AI-Assisted mode

The app pre-populates likely reading errors and prosody suggestions. To complete your review:

  1. Listen to the recording and confirm or dismiss each flagged error — and flag any errors the AI missed.

  2. Adjust Error Sensitivity (High / Medium / Low) if needed to widen or narrow what is shown and scored.

  3. Review the AI prosody suggestions and confirm or enter a score for each of the four rubric dimensions.

  4. Enter teacher comments.

  5. Submit.

For full submission in AI-Assisted mode, every filtered error must receive a verdict (confirm or dismiss) and all four prosody dimensions must be filled.

Note: Changing sensitivity after you have made edits can reset confirmations, dismissals, and annotations, so finalize sensitivity before deep review.

Teacher-Scored mode (no AI surface)

  • No AI errors are pre-filled.

  • You mark errors manually by clicking words in the passage.

  • You enter the four prosody rubric scores manually.

  • Sensitivity controls and AI badges are hidden.

This mode is useful when teachers or districts want a no-AI review experience while still using Fluency Lab recording, playback, and reporting. See the Disabling AI section below.

Rating the Feedback

In AI-Assisted mode, your job is to rate and correct what the AI proposes before it reaches the student:

  • Confirm or dismiss each flagged error. Confirmed errors count toward scores and are shown to the student; dismissed errors are removed and never shown.

  • Add errors the AI missed by clicking the relevant word(s).

  • Tune Error Sensitivity. Detection always runs at the widest net; the sensitivity level (High / Medium / Low) filters which errors are shown and scored. Default is Medium. Use Play Error to verify any flag before acting on it.

  • Accept or override the prosody suggestions. Each of the four dimensions has an AI-suggested 1–4 level; you can copy it into your rubric field or enter your own based on what you hear.

As you confirm/dismiss and adjust rubric scores, WCPM, Fluency, Accuracy, and Prosody recalculate live so the final numbers reflect your decisions.

The Fluency and Prosody Rubric

Fluency Lab's prosody rubric is built on a well-established, research-based instrument: the Multidimensional Fluency Scale (MDFS), developed by Zutell & Rasinski (1991) and presented by Rasinski (2004, Assessing Reading Fluency; also in The Fluent Reader). The working copy we built our rubric from is the reproduction published by Flow Reading Fluency (2019, www.FlowReadingFluency.com) under the name Multidimensional Prosody Scale. It rates oral reading on four dimensions — Expression & Volume, Phrasing, Fluidity (Smoothness), and Pace — each 1–4 points, for a total of 4–16.

This is also the scale Florida specifically calls for: the state's Secondary Foundations: A Focus on Fluency materials present the Multidimensional Fluency Scale as the prosody rubric for the B.E.S.T. ELA fluency benchmark (ELA.612.F.2.4). Our rubric uses the same instrument.

Fluency vs. prosody, and why we use Rasinski's scale

Fluency is not one thing — and prosody is one part of it. Reading researchers, including Rasinski, define reading fluency as multidimensional: it is made up of three related components (National Reading Panel, 2000; Rasinski, 2004, Assessing Reading Fluency):

  • Accuracy — decoding the words correctly.

  • Automaticity — decoding them effortlessly, with minimal conscious attention; observed through reading rate.

  • Prosody — reading with appropriate phrasing and expression (stress, pitch, intonation, pausing) to convey meaning.

Rasinski describes fluency as a bridge between word decoding and comprehension: at one end it connects to accuracy and automaticity in decoding; at the other end it connects to comprehension through prosody — the "expressive interpretation" of the text (Rasinski, 2004). In other words, prosody is the expressive component of fluency, and it is distinct from the rate/automaticity component. That distinction is exactly why Fluency Lab reports them as separate scores rather than one number:

Fluency Lab score

Rasinski fluency component it reflects

Accuracy

Accuracy (correct decoding)

Fluency (pace, pauses, flow)

Automaticity (effortless, well-paced decoding)

Prosody (rubric)

Prosody (expressive interpretation)

This three-part framing is not unique to Rasinski — it is codified in state reading standards. Florida's B.E.S.T. ELA fluency benchmark (ELA.612.F.2.4), for example, defines fluent reading as reading "with accuracy, automaticity, and appropriate prosody or expression" — the same three components Fluency Lab reports as separate scores.

Why a rubric, and why this one. Because expression is subjective and hard to quantify, the field measures prosody with listening-based rubrics rather than lab software. Rasinski notes these rubrics "provide valid measurements of the third component of reading fluency – prosodic reading" and, "in the hands of knowledgeable teachers, provide valid and reliable information" on a student's expressive reading (Rasinski, 2004). He presents the Multidimensional Fluency Scale (developed with Jerry Zutell; Zutell & Rasinski, 1991) as the more precise, dimension-by-dimension option, rating oral reading on four dimensions — Expression & Volume, Phrasing, Smoothness, and Pace — each 1–4.

In a later interview he reiterates why a rubric is the practical choice:

"You can put kids on a spectrograph and do some analysis there, but … teachers [can] just listen to students read and rate their reading along some dimensions on a rubric. Actually, I have one. I developed it with my colleague, Jerry Zutell … It's a multidimensional fluency scale, which looks at four different dimensions of fluency … It's actually been found to be quite reliable and valid."

— Timothy Rasinski, An Interview with Timothy Rasinski, The Language Teacher (JALT), 2021

We chose the Multidimensional Fluency Scale as the baseline for Fluency Lab's prosody rubric because it is research-grounded, already familiar to teachers, diagnostic dimension-by-dimension, and practical to approximate from acoustic analysis. The sections below show the source scale, the adapted rubric we actually use, and exactly what we changed and why.The source scale (Multidimensional Fluency Scale)

Dimension

1

2

3

4

Expression & Volume

Reads words as if simply to get them out. Little sense of trying to make text sound like natural language. Tends to read in a quiet voice.

Begins to make text sound like natural language in some areas but not others. Focus remains on saying the words. Still quiet.

Makes text sound like natural language through the better part of the passage. Occasional slips into expressionless reading. Volume generally appropriate.

Reads with good expression and enthusiasm throughout. Sounds like natural language. Varies expression and volume to match interpretation.

Phrasing

Monotonic, little sense of phrase boundaries; frequent word-by-word reading.

Frequent two- and three-word phrases; choppy; improper stress/intonation that fail to mark ends of sentences and clauses.

Mixture of run-ons, mid-sentence pauses, and some choppiness; reasonable stress and intonation.

Generally well phrased in clause and sentence units, with adequate attention to expression.

Smoothness

Frequent extended pauses, hesitations, false starts, sound-outs, repetitions, and/or multiple attempts.

Several "rough spots"; extended pauses/hesitations are more frequent and disruptive.

Occasional breaks in smoothness caused by difficulties with specific words/structures.

Generally smooth with some breaks, but difficulties are resolved quickly, usually through self-correction.

Pace

Slow and laborious.

Moderately slow.

Uneven mixture of fast and slow reading.

Consistently conversational.

Interpreting the total (source scale): Scores range 4–16. Totals below 8 may indicate the need for direct prosody instruction; totals of 8 and above indicate the student is reading with adequate prosody (per the Flow Reading Fluency, 2019 reproduction we built from).

Fluency Lab's adapted rubric (our chart)

This is the rubric as it actually appears in the tool. It keeps the four dimensions and the 1–4 / 16-point total, but the descriptors — especially Pace and Fluidity — are rewritten to match how Fluency Lab derives them from acoustic analysis.

Dimension

1 Point

2 Points

3 Points

4 Points

A. Expression and Volume

Voice lacks expression or enthusiasm. Calls out words to simply get them out. Cannot make the text sound like natural language. Quiet; does not project.

Shows some expression. Beginning to make portions sound like natural language. Mainly word calling. Does not project voice.

Reads most of the text so it sounds like natural language. Occasional slips of emotionless reading. Generally appropriate volume.

Good expression and enthusiasm throughout. Sounds like natural language. Varies pitch, intonation, and volume to fit the passage.

B. Phrasing

Reads word-by-word in a monotone. Doesn't pause to indicate awareness of phrase boundaries.

Frequently strings two- and three-word phrases; choppy. Cannot stress/intonate to mark ends of sentences or clauses; creates run-ons.

Pauses in mid-sentence; some choppiness. Reasonably able to stress and intonate; recognizes most phrase boundaries.

Appropriate phrasing throughout. Pauses and intonation consistently mark phrase and sentence boundaries and support meaning.

C. Fluidity (Smoothness)

Frequent extended pauses, hesitations, false starts, and repetitions. Sounds out many words and/or makes multiple attempts.

Struggles with some areas; reading interrupted by extended pauses and hesitations.

Occasional break in smoothness when encountering unfamiliar words or structures.

Reads smoothly with very few hesitations. Quickly resolves difficulties (self-correction).

D. Pace

Slow, laborious, and halting; frequent stops/starts make the pace hard to follow.

Reading rate noticeably slow or fast relative to conversational pace; moves forward but pace detracts from natural flow, often due to pausing or hesitation.

Rate close to natural pace but with some drag from pauses or slight deviations; workable but not consistently smooth.

Mostly steady, natural-sounding rate for a first read; conversational feel appears more often than not, with brief slowdowns on harder parts.

You can accept the AI-suggested level for each dimension or override it. The four dimensions add to a total out of 16 — the same scale teachers already recognize from the MDFS.What we changed, and why

We deliberately kept the structure (four dimensions, 1–4 each, /16) so the rubric stays familiar and the total can be interpreted the traditional way. The changes below adapt a human, holistic scale to acoustic, AI-assisted scoring.

  1. Renamed "Smoothness" to "Fluidity (Smoothness)" and redefined what it measures. In the source scale, Smoothness captures extended pauses, hesitations, false starts, and repetitions. Fluency Lab already measures those in a separate Fluency (flow) score computed from word-level timing. To avoid double-counting the same behavior, the rubric's Fluidity dimension is driven by acoustic rhythm (evenness of syllable/word timing), while pause/hesitation counting lives in the Fluency score.

  2. Rewrote the "Pace" descriptors. The source Pace dimension is a subjective judgment made "during sections of minimal disruption." Fluency Lab's Pace comes from an acoustic speaking-speed measure: deviation from a conversational target rate (~2.7 syllables/sec) plus pause-ratio and average-pause penalties. We rewrote the level descriptions to describe rate naturalness and pause impact from the audio rather than a holistic human impression of speed.

  3. Added safeguards so isolated struggles don't unfairly tank the Pace score. When pause-duration variance is high (a few hard spots rather than pervasive slow reading), the average-pause penalty is dampened. Overlapping pause penalties are scaled down to avoid double-counting. An articulation-rate floor prevents a reader with at least moderate raw speed from being pushed to level 1 by pauses alone.

  4. Mapped a 1–4 human rubric onto continuous 0–100 acoustic scores with fixed thresholds: 0–49 → 1, 50–64 → 2, 65–79 → 3, 80–100 → 4.

  5. Aligned each rubric dimension to the closest acoustic feature. Expression & Volume ← stress/emphasis, Phrasing ← intonation (pitch contour), Fluidity ← rhythm, Pace ← speaking speed.

  6. Kept a human in the loop. The AI only suggests a level; you confirm or override it, and your scores are final. In Teacher-Scored mode no AI suggestion appears at all.

Note — two different "Pace" ideas: The Fluency score also has an internal pace component based on gross words-per-minute (an "ideal" band of roughly 80–160 WPM). That is separate from the Prosody rubric's Pace dimension, which reflects how the reading sounds (rate naturalness + pausing). They are complementary, not duplicates.

How the prosody score is produced

  • The acoustic engine returns 0–100 scores for intonation, stress, rhythm, and speaking speed.

  • The composite Prosody (0–100) weights them: intonation 30%, stress 25%, rhythm 25%, speaking speed 20% (weights renormalize if a dimension can't be computed).

  • The rubric (/16) maps each measure to a 1–4 level using the thresholds above.

  • If a dimension can't be derived (e.g., unreliable pitch tracking from noise or low voicing), it's shown as missing rather than guessed — and you can enter it yourself.

Feedback to the Student

After you finish your review and submit, the student can view read-only feedback:

  • Student feedback displays teacher-approved outcomes only.

  • Confirmed errors are shown to the student; dismissed errors are not.

  • Students see each confirmed marked word with its error type and a short practice tip, but not the per-word audio ("Play" / "Play Correct") — replaying the recording and playing the correct pronunciation are teacher-only review tools.

Students never see raw AI error details, dismissed errors, or AI prosody suggestions — only your final, approved result.

When students see their results

Whether and when a student can open their feedback is controlled by the "Show results to students" setting on the assignment (in Create/Edit Assignment, just under the start/due dates). The options are:

  • After the assignment due date/time — results release once the due date passes.

  • After the assignment is graded for all students (default) — results release only once every assigned student's submission has been graded.

  • As students' assignments are graded — each student sees their results as soon as you finish grading their submission.

Note: With the default ("after the assignment is graded for all students"), if any assigned student hasn't completed the assignment or hasn't been graded yet, results stay hidden for the whole class. If you want each student to see feedback as soon as you finish reviewing their submission, choose "as students' assignments are graded."

How the assignment is recorded in the gradebook

When you create or edit a fluency assignment, you also choose its category — the dropdown just under the Start Date / Due Date fields and the Enable Grace Period option. The choices are:

  • Assignment

  • Homework

  • Instruction

  • Practice

  • Quiz

This category controls how the fluency assignment is recorded in the gradebook (how it's grouped and weighted). Pick the category that matches how you want the reading to count — for example, Practice for low-stakes progress reads, or Quiz / Assignment when the reading should carry more weight. The reading is scored and reviewed the same way regardless of category; the category only affects gradebook treatment.

Teacher Responsibility

The score submitted to the student reflects your judgment, not raw AI output. Before releasing results:

  • Listen to the recording and verify flagged errors (use Play Error).

  • Confirm or dismiss each error and add any the AI missed.

  • Confirm or override each prosody dimension based on what you hear.

  • Grade individual readings as you normally would, but combine results with classroom evidence — don't base a high-stakes decision such as placement or special-education eligibility on a single attempt.

Teacher judgment remains the final authority for all submitted feedback.

Disabling AI (Teacher-Scored Mode)

Fluency Lab can be used with no AI surface. In Teacher-Scored mode:

  • AI error suggestions, the sensitivity selector, and AI badges are hidden.

  • You mark errors manually and enter all four prosody scores yourself.

  • Recording, playback, rubric scoring, and reporting still work.

AI feedback can be turned off at the admin/district level. When it's disabled, Fluency Lab still runs fully — recording, playback, rubric scoring, and reporting all work — just without AI suggestions. The scoring mode is applied when the product loads the review.

Products with Fluency Lab

Fluency Lab is used with Connections Reading passage sets spanning grades 6–12, with cold reads near the start of a chapter and warm reads near the end. It also includes the Additional Passage Library of Lexile-banded practice passages (see Where Fluency Lab Fits in Instruction below).

Data Privacy

Student recordings are analyzed by two components:

  • Speech recognition & pronunciation assessment — Azure Speech Service. For the real-time assessment Fluency Lab performs, Microsoft processes audio in server memory only, encrypts it in transit, does not retain it after the request, and does not use it to train its models. Under Microsoft's Data Protection Addendum, Azure operates as a FERPA "school official."

  • Prosody analysis — self-hosted DisVoice. Prosody runs on a self-hosted service, so that analysis is not sent to any external third party.

Districts remain responsible for any required parental consent (e.g., COPPA for students under 13).

Data retention. Student recordings and results are retained for the school year so students and teachers can reference and replay them, and are deleted at the end of the school year.

[Confirm before publishing] Confirm where student recordings and results are stored within Perfection Learning's systems, and that end-of-school-year deletion is wired up to the actual audio files (not just database records). The retention policy itself is confirmed: retained for the school year for student/teacher reference, deleted at the end of the school year.

How the AI Works

Fluency Lab does not use a generative AI / large language model to write feedback. It uses two automated analysis components:

  • Speech recognition & pronunciation assessment — Azure Speech SDK (v1.47.0) runs continuous, phoneme-level pronunciation assessment on the recording. It returns word-level accuracy, error types (e.g., mispronunciation), and timing. This drives the suggested word errors, WCPM, and accuracy.

  • Acoustic prosody analysis — DisVoice analyzes intonation, stress, rhythm, and speaking speed from the audio. These drive the suggested prosody levels and the Prosody score.

Both produce suggestions that you review, confirm, override, or dismiss. Because they rely on automated speech analysis, they can be wrong in predictable ways — see the next section.

Additional Fluency Lab Guidance

The sections below go beyond the core workflow above. They cover the AI's limitations, how Fluency Lab compares to traditional scoring, and the instructional use of results.

Where the AI Falls Short (Limitations)

AI speech recognition flags potential errors and suggests prosody scores. Always listen to the recording and apply your judgment before releasing results. Below are the known failure modes (also surfaced in the in-app AI grading disclaimer).

Errors the AI may flag incorrectly (false positives)

  • Short and function words ("a," "an," "the," "to") are deprioritized in omission detection to reduce noise — but occasionally a correctly read content word may still appear as omitted if the engine didn't recognize it.

  • Natural pauses at punctuation may be flagged as hesitations, even when the pause reflects good expression.

  • Proper nouns and unusual names are scored unpredictably and may be flagged as mispronunciations even when read correctly.

  • Self-corrections and restarts often appear as inserted words rather than corrections. Dismiss these if the student recovered cleanly.

  • Background noise or environmental sounds may be interpreted as inserted words.

Errors the AI may miss (false negatives)

  • Sound-alike substitutions ("where" for "were," "their" for "there") may not be caught if alignment treats them as close enough to the passage word.

  • Subtle mispronunciations where the transcript looks correct — phoneme analysis catches some, but a wrong vowel sound on a correctly-spelled word can slip through.

  • Skipped short and function words ("a," "an," "the") generally won't be flagged. This is intentional to reduce false positives, but it means real omissions of these words won't appear.

  • Omissions late in the passage — if a student stops early, words in the final portion may be treated as an incomplete read rather than individual omissions.

Scoring notes to keep in mind

  • Scores are not adjusted for grade level. Accuracy, Fluency, Prosody, and WCPM reflect the reading itself, not grade-based expectations — the same reading earns the same scores whether the reader is in grade 6 or grade 12. In particular, the Fluency pace band (~80–160 WPM) is fixed for all grades, and WCPM is a raw rate. Interpret both against your own grade-level expectations. (Grade is used only to select the correct passage, not to compute scores.)

  • WCPM includes hesitation errors, not just miscues. This differs from traditional ORF scoring, so AI-calculated WCPM may be lower than a manual count.

  • The Fluency score penalizes reading above ~160 WPM or below ~80 WPM. A fast, accurate reader may still receive a reduced Fluency score due to pace.

  • Prosody scores are AI-suggested only. Enter your own rubric scores based on what you hear — the AI suggestion is a starting point, not a final assessment.

Bottom line: The score submitted to the student reflects your judgment, not raw AI output.

How Fluency Lab Compares to Traditional Fluency Scoring

Traditional MDFS / hand-scored ORF

Fluency Lab

Who scores

Teacher, by ear, in real time or from a recording

AI suggests; teacher confirms/overrides (or scores fully manually in Teacher-Scored mode)

Prosody dimensions

Expression & Volume, Phrasing, Smoothness, Pace (holistic, 1–4)

Same four dimensions, 1–4, mapped from acoustic features; Smoothness/Pace redefined acoustically

Smoothness / pauses

Folded into the "Smoothness" rubric dimension

Pulled out into a separate Fluency (flow) score from word timing, to avoid double-counting

Pace

Subjective slow→conversational judgment

Acoustic speaking-speed vs. conversational target + dampened pause penalties

WCPM

Words read minus miscues, over time

Includes hesitation errors, so AI WCPM can read lower than a hand calculation

Consistency

Varies by rater and conditions

Consistent suggestion engine, but subject to speech-recognition error

Speed/scale

Time-intensive per student

Fast across a class; recordings are replayable for verification

Best use

Expert, context-rich judgment

Progress monitoring and a teacher-reviewed starting point — not a benchmark replacement

The takeaway: Fluency Lab reproduces the familiar four-dimension rubric and /16 total, but the numbers come from acoustic analysis plus your review. Treat it as an accelerator for teacher judgment, not a substitute for it.

Cold Reads and Warm Reads

Cold read (near the beginning of a chapter)

  1. The student opens the assigned passage and records aloud.

  2. The student answers 3 comprehension questions.

  3. You review fluency metrics, error patterns, prosody, and comprehension responses.

Use the cold read to understand how students approach the text before instruction has done most of the support work.

Warm read (near the end of a chapter)

In the current product flow, the warm read is fluency-only:

  1. The student records aloud.

  2. The student submits the recording without comprehension questions.

  3. You review fluency metrics, error patterns, prosody, and comments.

Because warm reads do not include comprehension questions, interpret them primarily as fluency evidence and combine them with classroom comprehension evidence.

Where Fluency Lab Fits in Instruction

A typical chapter sequence can be:

  1. Cold read near the beginning of the chapter

  2. Core chapter instruction, discussion, vocabulary, and comprehension work

  3. Targeted fluency support for students who need it

  4. Warm read near the end of the chapter or instructional cycle

  5. Teacher review and next-step planning

You can use Fluency Lab with the whole class, small groups, or selected students. For students receiving Tier 2 support, use it as one part of a larger support cycle alongside classroom evidence and existing MTSS processes.

Tip: Avoid over-testing. Keep the routine short and connected to instruction.

Passage sources: Connections Reading and the Additional Passage Library

Fluency Lab passages (available for grades 6–12) come from two sources:

  • Connections Reading passages — grade-leveled passages tied to chapters, with state editions where applicable (e.g., Florida/FL). Each passage carries a grade and a testing window (e.g., fall), and cold reads include comprehension questions.

  • Additional Passage Library — a supplemental set of practice passages organized into approximate (unofficial) Lexile bands: 610–800L, 810–1000L, 1010–1200L, 1210–1400L, and 1410–1600L. These bands are an internal guide to relative difficulty, not official Lexile® certifications. Any teacher can assign any passage from any band to any student — there are no grade or band restrictions — so you can match a passage to a student's reading level for differentiation or intervention regardless of enrolled grade. Each passage includes comprehension questions and is labeled for additional practice rather than a fixed testing window.

Scoring is identical for both sources — Accuracy, Fluency, Prosody, and WCPM are computed the same way. Because Additional Library passages are chosen by reading level (not grade), they carry no grade label; combine their results with your own grade-level expectations (see the Scoring notes above).

Incomplete Reading Handling

Fluency Lab handles incomplete reads explicitly, while leaving the final call with you.

  • When it triggers. If less than ~80% of the passage is actually read aloud (measured by how much of the passage the recording covers), the submission is flagged incomplete. Silent or near-silent recordings are caught the same way, since almost none of the passage is covered.

  • What you see. The submission stays in Needs grading (it is not auto-completed). When you open it, the review screen is gated: the score summary, error list, and detailed feedback are hidden, and you're given two choices:

    • Submit as Incomplete — close the attempt without recording an ORF (reading) score. The student does not receive fluency scores for that reading. (Any comments you leave are still shown to the student.)

    • Score Anyway — clear the gate, review the partial recording, and grade it as a normal submission (including AI scoring if it's enabled for your school). The student then receives that grade and feedback like any other read — no incomplete notice is shown.

  • You can always override. Score Anyway is available in both AI-Assisted and Teacher-Scored modes, so if you'd rather give the student a full, graded result on a partial reading, you can. Once you submit a Score-Anyway grade, the attempt is treated as graded and won't re-raise the incomplete gate if you reopen it.

  • Why scores are hidden until you decide. On a very short or silent read the raw numbers are unreliable (an inflated WCPM, or prosody computed from near-silence), so Fluency Lab suppresses them rather than showing a misleading score before your review.

Interpreting Results and Next Steps

Use patterns across multiple passages and time points, not a single score.

Pattern

Likely focus

Low WCPM with adequate accuracy

Phrasing, repeated reading, smooth pacing

Low accuracy

Word-level support, vocabulary, text access/scaffolds

Low prosody with fair accuracy

Model expression, phrasing, and oral reading performance

Low cold-read comprehension but stronger fluency metrics

More meaning-focused discussion and checks for understanding

Stronger warm-read fluency after a lower cold read

Evidence that instruction and rereading are helping

Flat or declining fluency across several reads

Review supports; consider more intensive help via MTSS

Always combine Fluency Lab results with classroom evidence, existing screening data, and MTSS procedures.

Suggested classroom supports

These instructional moves can be used outside the scoring tool when the data indicate a need (they mirror evidence-based fluency practices: teacher/peer modeling, repeated reading, phrase-cued reading, echo/choral/partner reading, and text dissection).

  • Low WCPM, adequate accuracy: repeated reading of a short section; model fluent reading; phrase-cued reading; reread after feedback.

  • Low accuracy: build vocabulary and text access before rereading; use shorter chunks; teacher modeling, echo reading, or partner reading.

  • Low prosody, adequate accuracy: model expression, phrasing, and attention to punctuation; echo/choral/partner reading; practice a short section for smoothness and expression.

  • Low cold-read comprehension: revisit key vocabulary, gist, and meaning-making routines; ask for a retell or main idea; connect fluency back to meaning through discussion.

Reports Dashboard

From the main app, open Reports to review performance over time. Reports support class-level snapshots, student-level trend views, assignment/gradebook views, and band-based interpretation.

Performance bands (the color legend shown in Reports):

Band (as shown)

Score

Color

<65%

Under 65%

Red

65-79%

65–79%

Orange

80-89%

80–89%

Green

90%+

90%+

Blue

Note: The Reports legend labels these as numeric ranges with colors — it does not show named proficiency tiers in the product. (If you want tier names for your own communication you might call them Below / Approaching / Proficient / Advanced, but those names are not surfaced in the app.)

Reports display raw WCPM and class-average comparisons; the bands above apply to the 0–100 scores. (Percentile-vs-norm rankings are computed internally but are not surfaced in the current Reports build.)

Best practice: Use reports to identify trends and plan instruction — not to make placement decisions from a single attempt.

Practical Teacher Decision Guide

Use this quick sequence after each reviewed submission:

  1. Check the read type: cold read (with comprehension questions) or warm read (without).

  2. Check read completeness and audio quality.

  3. Review Accuracy and the error-type pattern first.

  4. Review WCPM and Fluency for pacing/flow.

  5. Review Prosody dimensions for expression and phrasing.

  6. Review comprehension results when the attempt is a cold read.

  7. Assign 1–2 specific next-step supports.

  8. Recheck progress on a later read.

Optional Student Self-Monitoring

You may choose to share simple, teacher-approved progress patterns with students — for example, whether WCPM, accuracy, or prosody improved over time. Keep this reflective and instructional, not punitive.

Possible student reflection prompts:

  • What helped you read more smoothly this time?

  • Which words or parts were hardest?

  • What will you practice before the next read?

Frequently Asked Questions

Is Fluency Lab a benchmark or screener?
No. It's a progress-monitoring and instructional tool — teachers grade individual readings, but you shouldn't base a high-stakes decision such as placement or eligibility on a single attempt.

Why is the AI's WCPM lower than my hand count?
Fluency Lab's WCPM includes hesitation errors, not just miscues, so it can read lower than a traditional ORF count.

A correctly read word is flagged as an error — what do I do?
Use Play Error to listen, then dismiss it. Proper nouns, self-corrections, and natural pauses at punctuation are common false positives.

Can I turn the AI off?
Yes. Teacher-Scored mode hides AI suggestions, the sensitivity selector, and AI badges while keeping recording, playback, rubric scoring, and reporting.

Does Fluency Lab use ChatGPT / a generative AI model?
No. It uses Azure speech recognition for word accuracy and DisVoice acoustic analysis for prosody — not a generative language model.

Why are there two "Pace" ideas?
The Fluency score has an internal pace component based on gross WPM; the Prosody rubric's Pace dimension reflects acoustic rate naturalness and pausing. They're complementary.

A prosody dimension shows as missing — is that a bug?
No. When a measure can't be reliably derived (e.g., unreliable pitch tracking from noise), Fluency Lab shows it as missing rather than guessing. You can enter that dimension yourself.

Does the student see the errors I dismissed?
No. Students see only confirmed errors and approved scores.

Key Message to Teachers

Fluency Lab works best as an instructional feedback loop:

  • Record

  • Review

  • Respond with targeted support

  • Reassess and monitor growth over time

It should strengthen teacher decision-making, not replace it.

Did this answer your question?