Between screening windows: progress monitoring that actually feeds small-group instruction
Under Wisconsin’s Act 20, K–3 classrooms screen three times a year — fall, midyear, and spring — and 4K screens in fall and spring (per the DPI’s Act 20 FAQ). That means the screener speaks two or three times a year. Your instruction happens every day in between.
So the real question isn’t “did we screen?” — the state’s selected screener has that covered. It’s: what happens in the twelve-ish weeks between windows? That’s where progress monitoring earns its keep — or turns into paperwork.
Who vs. what
It helps to be precise about what each layer of assessment is for:
- Screening tells you WHO. A universal screener is a wide, quick net. It flags which children may be at risk and need a closer look. That’s its job, and it does it at scale.
- Skill-level monitoring tells you WHAT. Once you know who needs help, the screener’s composite can’t tell you whether Tuesday’s group should work on hearing first sounds or blending three of them. Only a check of the specific skill can.
Act 20 itself is built on this logic. When a student’s screening score triggers a personal reading plan, the DPI’s FAQ says the plan must identify the student’s specific early literacy skill deficiencies, set goals and benchmarks, and describe how the pupil’s progress will be monitored. Monitoring between windows isn’t an extra you bolt on — it’s the engine of the plan.
A weekly rhythm that holds up in a real classroom
The failure mode of progress monitoring is trying to monitor everything, for everyone, every week. It collapses in October. Here’s a rhythm that doesn’t:
Monday — check a little. Two or three quick skill checks, only for the students whose grouping decision you’re unsure about. Five minutes with a child, not a testing block. If you already know Marcus needs blending work, don’t spend Monday proving it.
Tuesday — regroup. Look at the skill picture and let it move students: someone graduates out of the syllables group, someone new joins the letter-sound group. Groups that never change membership aren’t groups — they’re labels.
Tuesday to Thursday — teach the groups. This is where the minutes should go. The whole point of assessing less is teaching more.
Friday — confirm one thing. Pick the skill you taught hardest this week and check whether it moved for the three or four students you’re worried about. That answer shapes next Monday.
Two rules keep the rhythm honest: only assess what would change your grouping, and let the smallest sufficient check win. If a thirty-second syllable check answers the question, the thirty-second check is the right instrument.
Keep the record tiny
Monitoring dies of over-documentation more often than under-assessment. The record that survives a real school year is one line per check: the skill, the date, and where the student landed. That’s enough to draw a growth line, enough to justify Tuesday’s regrouping, and little enough that you’ll actually keep doing it in February. If your system asks for a paragraph per child per week, the system is the problem — the point of the record is the next instructional decision, not the archive.
The same one-line habit answers the classic small-group questions without a meeting: When did this group last change? (Look at the dates.) Is anyone stuck? (Three checks, no movement — change the instruction, not just the group.) Who’s ready to move on? (The checks say so before the screener does.)
When a personal reading plan is in play
For K–3 students below the 25th percentile, Act 20 turns monitoring from good practice into a named commitment: the DPI’s FAQ says personal reading plans must include goals and benchmarks toward grade-level literacy skills and a description of how progress will be monitored, alongside the interventions being provided. The weekly rhythm above is precisely that description, already running: the Monday/Friday checks are the monitoring, the regrouping is the intervention responding to it, and the one-line records are the evidence trail — for the plan, for the family, and for the data meeting. If you’re already living the rhythm, the plan’s monitoring section writes itself.
Making the loop visible
Between-window monitoring pays off twice: once in Tuesday’s groups, and again when you need to show growth — to families at conferences, to your principal, to the midyear screening data meeting. A skill checked in September, November, and January is a story: here’s where she started, here’s the group she worked in, here’s where she is now.
This loop is exactly what Literacy Assessments is designed around: skill-level progress monitoring between screening windows, results that flow straight into small-group tools, and progress reports that show growth across collection windows. For Wisconsin classrooms, that’s the Act 20-aligned rhythm — with one boundary worth restating plainly: Literacy Assessments is not the DPI-selected universal screener (that’s aimswebPlus, per DPI), and it does not satisfy the statutory screening requirement. It’s the between-windows layer: what to teach next, and proof it’s working.
Getting started this week
You don’t need a system overhaul to begin — you need one loop:
- Pick the three students whose grouping you’re least sure about.
- Check one skill for each on Monday — five minutes total.
- Let the result move (or keep) each student’s group, teach the groups midweek, and confirm the taught skill on Friday.
Run that loop for two weeks and you’ll know more about those three readers than the last screening window could tell you — and your groups will already be moving.
Ready to build the rhythm with your class? Start a free 14-day trial or see it in the demo — synthetic data only.