How to Run a Daily STAAR Math Problem-Solving Routine That Actually Builds Skills

You've got a stack of STAAR practice packets on your desk. They've been there since February. You hand them out, students work quietly for ten minutes, you go over the answers, and then you move on to whatever was actually on the lesson plan. It doesn't feel like it's doing much — because it isn't. Answering five random questions and checking a key is practice, not skill-building. There's a difference.

A daily STAAR math problem-solving routine, done right, is one of the highest-leverage things you can do in the months before the test. Not because it covers more content — it doesn't — but because it builds the habits students need to work through problems they've never seen before. Here's what that routine looks like and how to make it stick.

Why Most Daily Math Practice Doesn't Work

Most bell ringer math practice runs the same way: students work independently, teacher circulates or takes attendance, class goes over answers by calling on students or just reading the key aloud. Students who got it right feel good. Students who got it wrong copy the right answer and file it away.

Nothing about that routine builds problem-solving skill. It builds answer-checking skill. Students learn to compare their answer to the correct answer — they don't learn to reason through a problem they're stuck on.

The fix is to shift the routine from answer-focused to process-focused. The question isn't "did you get it right?" — the question is "how did you think through it?"

Action step: Tomorrow, before you go over the bell ringer answers, ask three students to explain how they started the problem — not what answer they got, but what they did first. That one change will tell you more about what your students actually know than a week of answer-checking.

The Four-Part Routine That Works

This routine takes 10-12 minutes and works for grades 3 through 8. The discipline is in doing it consistently — the structure stays the same every day, even when you're behind on the pacing guide.

Step 1: Read and Annotate (2 minutes)

Students read the problem independently and annotate: underline what the question is asking, circle important numbers, cross out information that's irrelevant. No solving yet. Just reading and marking.

This step sounds obvious, but most students skip it. They read the problem once, grab the first number they see, and start computing. Teaching them to annotate before solving is teaching them to slow down and understand before they act — which is exactly what multi-step STAAR problems require.

Step 2: Plan (1-2 minutes)

Students write one sentence: "I'm going to _____ because _____." This is their plan. It doesn't have to be right. It has to exist. Students who can't write a plan haven't understood the problem yet.

This step reveals the most. A student who writes "I'm going to multiply the number of groups by the number in each group because the question is asking for a total" understands the problem. A student who writes "I'm going to multiply" with no "because" is operating on instinct, not reasoning. That's the student who needs small group time.

Step 3: Solve and Check (4-5 minutes)

Students work through the problem using their plan. If their plan doesn't work, they revise and try again. When they have an answer, they verify it makes sense in the context of the problem — not by checking the key, but by asking "does this answer make sense for what the question actually asked?"

Step 4: Discuss (2-3 minutes)

Whole-class discussion — but not "what did you get?" Instead: "What did you annotate?" and "What plan did you use?" and "If you got stuck, where did you get stuck?" This is where the learning actually happens. Students hear how other students reasoned through the same problem, including students who solved it differently or caught their own error mid-solve.

Action step: Run this routine with one problem tomorrow. Don't introduce it as a new structure — just say "before we solve, let's annotate together" and "before you start computing, write your plan." See what happens. You'll know if it's working by how many students can articulate their reasoning out loud.

Choosing the Right Problems

The problem you choose makes or breaks the routine. A problem that's too easy gives students nothing to think through. A problem that's too hard stops the routine before it starts.

What makes a good daily problem:

• It requires more than one step
• It's written in STAAR-style language — not your textbook's cleaner prose
• It targets a TEKS you've taught but haven't revisited recently
• It has at least one plausible wrong answer that reflects a specific misconception

Released STAAR items from TEA are the best source. They're written in the exact register of the test, they're calibrated to grade-level difficulty, and they're free. Organize them by TEKS and reporting category and cycle through them based on what your class needs most. If RC2 is your lowest category from the last benchmark, pull RC2 items for the next two weeks. The TestPrepGrow STAAR content library also has items sorted by TEKS and difficulty if you want something already organized.

Alternate the difficulty level. Don't use hard problems every day — students disengage when every problem is a battle. Mix in problems students can get with effort but without frustration. Reserve the hardest items for days when you have more discussion time.

Action step: Pull ten released STAAR items for your grade level and sort them by reporting category. That's two weeks of daily problems. Put them in a folder. Routine solved.

How to Protect the Time

The honest answer: this routine only works if you protect the ten minutes. The late announcement over the intercom, the student who walks in needing an admit slip, the fire drill that cost you your planning period yesterday and now you're behind on everything — all of it will try to eat your routine. You have to treat those ten minutes as non-negotiable.

A few things that help:

• Post the problem before the bell rings. Students start annotating the second they sit down, not after you take attendance and get settled. You gain a minute and a half just by having it on the board early.
• Don't skip discussion on bad days. The temptation when you're behind is to skip the discussion and just tell students the answer. That's precisely when they learn the least. Even two minutes of "what did you annotate?" is better than none.
• Keep the structure identical every day. Read, annotate, plan, solve, discuss. Same sequence, every time. Students who know exactly what comes next spend their mental energy on the math, not on figuring out today's format.

Action step: Add "problem-solving routine" as a named block in your lesson plan template — not just "bell ringer." Naming it specifically and keeping it in the template makes it harder to cut.

What to Do When Students Resist

Some classes will push back on the annotation and planning steps. "Can't we just solve it?" Yes — that's what they want. But if they could solve it reliably, you wouldn't be running prep routines.

The pushback usually means one of two things: the problem is too easy and they genuinely don't need the scaffolding, or they've learned to perform speed rather than thinking. Both are fixable.

For the student who legitimately doesn't need the scaffolding: have them write the plan anyway, then ask them to find a second way to solve it. "You got 48. Can you show me a different way to get there?" That's extension, not punishment.

For the student who's performing speed: slow down the class discussion and ask them to explain why they chose their operation. If they can explain clearly, they've earned the shortcut. If they can't, they've just identified their own gap — which is more powerful than you telling them what they don't know.

The Payoff on Test Day

What you're building with this routine isn't content knowledge — it's problem-solving habits. The student who has annotated problems every day for three months will automatically read the STAAR question carefully, identify what's being asked, and think before they compute. That habit shows up in every reporting category, on every problem type, even the ones they've never seen before.

Ten minutes a day. Consistent structure. Real problems. That's the routine. It's not a dramatic intervention, but it works — and it works better than test-prep packets that students fill out and forget.