How to Choose Decodable Readers That Match Your Phonics Programme

One of the most common mistakes teachers make when first adopting decodable readers is picking books without checking phonics alignment. A decodable reader is only as useful as its match to what students have already been taught. Here's how to choose the right ones for your programme.

Know Your Scope and Sequence First

Before choosing decodable readers, identify the phonics programme your school or classroom uses. Is it UFLI Foundations? Sounds-Write? Jolly Phonics? A state-developed programme? Each has a different scope and sequence, meaning the order in which phonics patterns are introduced varies. A book that is fully decodable for students following one programme may contain untaught patterns for students following another.

Match to Teaching Point, Not Reading Level

Decodable readers should be matched to a student's phonics teaching point, not a generic reading level like a PM level or Lexile score. A student who has been taught CVC patterns and initial blends needs a book that only uses those patterns, regardless of what a general reading level assessment says.

Check the Publisher's Scope and Sequence

Quality decodable reader publishers provide a scope and sequence document that maps each book or series level to specific phonics patterns. Before purchasing, check whether the publisher's sequence aligns with your teaching programme. If they publish a UFLI Foundations alignment document, that is a strong indicator the books will work for your classroom.

Don't Mix Unaligned Series

Using multiple decodable reader series that follow different scopes and sequences can confuse students and make it harder to track progress. Wherever possible, choose a single series with a clear progression from introductory CVC words through to complex, advanced vowel teams and multisyllabic patterns.

Innerlinks decodable readers align to recognised systematic phonics sequences worldwide, including UFLI Foundations frameworks. Find your level at innerlinks.info.

Back to blog