Sounds I Can Make · RF.K.4

A hundred separable facts, and twelve questions

The alphabet code is the only part of kindergarten English where a machine can honestly keep score, because the answer set is closed. A child either produces a sound or does not.

01What a child does

A letter appears with its Letterland character — Annie Apple, Impy Ink, Jumping Jim. The child says the sound. An adult is beside them and taps whether it came. Two minutes, about a dozen letters, then a scratch-off reward in the child's own colour.

The adult is not optional. This is an oral task: the child's answer is a sound, and nothing in a microphone can tell a confident /d/ from a guessed one. The tool holds the list and the record; the teacher makes the judgement, which is the right division of labour.

02What the child gets out of it

Two minutes, not twenty. Short enough that it is a visit rather than a test, and short enough to do often, which is what actually makes spaced practice work.
A character to hang the sound on. Letterland gives a five-year-old a story for a shape, which is a far better memory hook than a flashcard.
It starts and ends on something they can do. Deliberately. A probe that is all failure teaches a child that reading is where they are bad at things, and you pay that back for years.
Their name is never stored. They type it once, it becomes a five-digit number, and the number is what the card is filed under.

03What the data notices — and what it should

What the tool records today is whether each letter's sound came. That is real and useful, and it is also the narrowest version of this. The design for what it should record is written up in Mapping the Alphabet Code; the two pieces that matter most are these.

Confusion pairs

A child who reads d as /b/ has a completely different problem from one who shrugs, and a completely different lesson. Recording what they said rather than just whether it was right costs one extra tap and is the single largest gain available here.

Pair	Why it goes wrong	What to do
b / d	Mirror shapes, same mouth position family	Separate them in time. Never introduce both in the same week
p / q	The same mirror problem, one step later	Teach one to secure, then contrast deliberately
m / n	Both nasal, both hummed — the ear, not the eye	Exaggerate the mouth shape, not the letter
f / v	Same mouth, one voiced	Hand on the throat. One buzzes
short vowels	Five sounds in a small acoustic space	Contrast two at a time, never five

Blending — the gate it cannot see

A child can know all twenty-six sounds and still not read a word. Turning /c/ /a/ /t/ into cat is a separate skill that lives in the ear and has nothing to do with letters. If you test only sounds, that child looks fine on every report and keeps failing to read.

This is why blending is first on the build list. Until it is in, a clean set of letter-sound results should be read as “knows the sounds”, never as “can read”.

04How it should adapt to one child

Twenty-six sounds is about 220 separable items across the full foundational strand in a year. At three seconds an item you cannot test them all, so the job is choosing the twelve that tell you the most. The designed scheduler spends a session like this:

State	Means	Next seen	Share of a session
Unknown	Never produced	Every session	Seven at the edge
Learning	Produced once	Next day	Seven at the edge
Review	Twice, on different days	Four days	Three maintaining
Secure	Three times, across at least two sessions, three days apart	Monthly spot-check	Two already secure

The spacing does the work, not the repetition. Any mastery rule that can be satisfied in one sitting will overstate what the child knows — three correct answers in one morning is short-term memory; three across three weeks is learning.

And a dependency gate: the scheduler should refuse to offer a digraph whose parts are not secure. Teaching sh before s and h are solid wastes the lesson.

05Being a better teammate

This is where letter-sound data earns its keep, because the moves it implies are unusually clear-cut.

What the data shows	What you do on Monday
Sounds secure, blending weak	Stop drilling sounds. Blend three phonemes orally, with no print in front of them
A specific confusion pair	Separate them in time; teach one to secure, then contrast
Names known, sounds not	Sounds only. More alphabet song will not help
Neither, and weak phonological awareness	Drop out of print entirely. Rhyme, syllables, onset and rime
Fewer than one new item a week for four weeks	Change the method, not the dose. Flag for intervention
Secure items decaying between sessions	Shorten the review interval rather than reteaching

Every row there names a move. That is the test for any measure worth collecting: if a number does not change what happens on Monday morning, it is decoration, and gathering it cost a child instructional time.

It is not a reading level. Ten letter sounds is not a Lexile, and the moment a number looks official it ends up in a file that follows the child.

It is not mastery. Twelve items sampled from fifty-two is an estimate, and the screen should say so.

It does not assess what has not been taught. That produces noise and teaches a child that the tool is where they fail.

06Using it

Sit beside them. This is the one tool in the suite that does not work without an adult, by design.
Little and often. Two minutes twice a week beats ten minutes once.
Cap it at about five per cent of instructional minutes. The commonest failure of progress monitoring is that it eats the teaching it was meant to direct.
Read a clean result as “knows the sounds” until blending is built, and not one word more than that.

Open Sounds I Can Make →

RF.K.4 is Phonics and Word Recognition in the North Carolina standards — consonant sounds, long and short vowels, high-frequency words. It is numbered 4 rather than 3 because North Carolina inserts a Handwriting cluster at RF.K.2 that Common Core has no equivalent for, and every foundational code after it shifts by one.