Independent writing tools and guides, edited by a human

Matching Texts to Readers: A Practical Guide to Reading Levels

Readability scores are only useful if you know what to do with them. How teachers and tutors can use reading levels to choose texts, spot mismatches, and avoid the two common mistakes.

Published
Read
5 min
30
Readers in one class
90–95%
Comprehension at instructional level
5–6
Words to pre-teach
On this page (07)
  1. 01What the scores actually measure
  2. 02The two common mistakes
  3. 03Using the score to choose
  4. 04What to do with a hard text
  5. 05What to do with an easy text
  6. 06The numbers that are worth tracking
  7. 07A summary for busy teachers

A readability score is a number. Like any number applied to a person, it is useful in aggregate and dangerous in individual cases. A class of thirty readers does not have one reading level, and a text does not have one difficulty.

Used well, reading levels help a teacher choose material that a student can actually read, which is the single largest factor in whether they improve. Used badly, they become a label that follows a student around and a reason to hand them a text that is technically accessible and intellectually insulting.

What the scores actually measure

Every common readability formula measures two things: sentence length and word length. Flesch–Kincaid, Gunning Fog, SMOG, and the rest are variations on the same arithmetic. They count words per sentence and syllables per word, then output a grade level.

That means the score is a proxy for surface complexity. It says nothing about whether the content is appropriate, whether the reader has background knowledge, or whether the text is interesting. A passage of simple sentences about a topic the reader has never encountered may score as easy and be impossible to comprehend. A complex sentence about something the reader knows intimately may score as hard and be perfectly readable.

The score is a starting point, not a verdict.

The two common mistakes

Mistake one: treating the score as a target. Rewriting a text until it hits a grade level produces short, choppy sentences with no connectives. The result scores well and reads badly, because the relationships between ideas have been stripped out along with the complexity. Cohesion matters more than sentence length, and no formula measures it.

Mistake two: treating the score as a ceiling. Handing a strong reader a text at their measured level denies them the stretch that produces growth. Reading levels are about access, not limits; the aim is a text a reader can read with support, which is usually slightly above their independent level.

The useful rule from reading research is the instructional level: material a reader can handle with about 90–95 per cent comprehension, with some support. That is deliberately harder than the easy text and easier than the frustrating one.

Using the score to choose

A practical routine for a teacher or tutor.

  1. Run the text through a checker. The readability checker gives several formulas at once; look at the range, not a single number.
  2. Read the first paragraph yourself. Ask whether a student at that level would know the words in it. Formulas cannot see vocabulary that is simple but unfamiliar.
  3. Check the background knowledge. A text about a topic the class has studied is easier than the score suggests. A text about an unfamiliar context is harder.
  4. Look at the structure. Headings, short paragraphs, and clear signposting make a text easier than its score. Dense pages make it harder.
  5. Try it with one student. Ten minutes with a real reader beats any formula.

What to do with a hard text

Most of the time the text is not negotiable — it is a set text, a textbook chapter, or an exam source. In that case the job is to scaffold, not to replace.

Pre-teach the vocabulary. Five or six key words, introduced before reading, remove most of the surface difficulty.

Build the background. A short video or a discussion before reading makes the content accessible even when the sentences are long.

Chunk the text. Read a section, stop, summarise. This is the single most effective support for a reader working above their independent level.

Read it aloud. Hearing a complex sentence often resolves what the eye cannot.

Provide a glossary. A list of terms with plain definitions turns a frustrating text into a manageable one.

None of these change the readability score, because the score measures the text and the support measures the lesson. That is the point.

What to do with an easy text

An easy text is not automatically a bad choice, especially for a reader who needs confidence. But a steady diet of easy text produces fluency without growth.

Two adjustments work well. First, keep the text and raise the task: ask for inference, evaluation, or a written response rather than literal comprehension. Second, keep the topic and raise the text: find a version at a slightly higher level on the same subject, so the reader brings their knowledge and stretches their reading at the same time.

The numbers that are worth tracking

If you want to track a reader's progress, text difficulty is a weak measure. Better indicators:

  • Words read per minute, with comprehension checked.
  • The proportion of words a reader self-corrects.
  • The kinds of questions they can answer: literal, inferential, evaluative.
  • Whether they choose to read when nobody is asking them to.

The last one is the outcome that matters most and the hardest to measure. A student who reads voluntarily will outgrow any level you assign them.

A summary for busy teachers

Readability scores are quick, cheap, and honest about surface complexity. Use them to flag texts that will need support, and to check that a text you have written is not accidentally harder than you meant it to be.

Then read the text yourself, look at your students, and make the decision the formula cannot. The score is a tool for the teacher, never a replacement.

Nicolas DavidEditor, Textoria

Writes and edits Textoria's guides on grammar, editing, and clear prose. Every guide is checked against real examples before publication; corrections are dated on the page.