How to Run a STAAR Mock Test Day That Actually Prepares Students

There's a version of a mock test day that wastes everyone's time: you print off the released STAAR test, students sit silently for 90 minutes, you collect the papers, grade them over the weekend, and read out class averages on Monday. Students learn they got 58% and feel bad. You learn nothing you didn't already suspect. Nothing changes.

There's another version that actually works. Here's how to run it.

Why a STAAR Mock Test Day Is Worth Your Time

A well-run mock STAAR test does three things that no other prep activity can:

1. It builds stamina. Most students have never sat and worked independently on one task for 90 minutes straight. STAAR will be the first time — unless you practice it first. Stamina is a skill, and it degrades without practice.
2. It shows you what your intervention list should actually be. Not what you think it should be based on instructional progress, but what the test data says. These are often different.
3. It reduces test anxiety by making the format familiar. Students who have been through a realistic mock test know what to expect on test day. That familiarity reduces the panic that causes careless errors on the real thing.

None of those benefits come automatically from handing out a test. They come from how you structure the day before, during, and after.

Action step: Before you plan anything else, decide what your mock test day is primarily for: information gathering (you want accurate diagnostic data) or experience building (you want students to practice the conditions). Both are valid goals, but they require slightly different structures. Pick one and build around it.

Choosing the Right Test to Use

Use a released STAAR test from TEA whenever possible. The item types, format, and vocabulary in released tests are as close to the real thing as you can get. Third-party tests vary significantly in quality — some are excellent, many are not, and students can tell when a question is poorly written. A bad question erodes their trust in the process, and the data you collect is less useful.

For grades with multiple released tests available, choose one that students haven't already seen. If you've been pulling questions from a specific released test all year for bell ringers and practice, don't use that one for the mock — students may recognize items and your data will be skewed.

If you want to target specific reporting categories, a focused mock test — 10-12 questions per RC, 40-48 questions total — gives you reportable data per RC without requiring a full-length test administration. This works especially well if you've already identified which RC needs the most work.

Action step: Pull two released STAAR tests for your grade and subject. If you're using the full test, pick the one students haven't seen. If you're building a focused mock, select 10 questions per RC from released tests and verify they're genuinely TEKS-aligned before building the test document.

Setting Up the Conditions That Actually Matter

The closer the mock mirrors actual STAAR conditions, the more useful it is for stamina-building and for giving you reliable data. That means:

• No interruptions. Turn off your projector notification sounds, put a sign on your door, and let the front office know you're testing. One PA announcement ruins 90 minutes of silence you won't get back.
• Seats arranged like the real test if you can manage it. If your students will test in a specific seating configuration, practice in that configuration.
• Only allowed materials. Scratch paper and a pencil. No more, no less. Students who are used to having charts on the wall or formula sheets propped up will struggle on test day if they've always relied on them.
• Timed, but not stressfully so. Give them the actual STAAR time limit. Don't call out "45 minutes left!" every 15 minutes — just let them work. If students finish early, redirect them to review their work rather than sitting idle.

Action step: Write out your mock test day schedule before the bell rings: what students will see when they walk in, when you'll distribute materials, when the clock starts, and what the "done" procedure looks like. Post it on the board so there's no procedural confusion eating into testing time.

What to Do While Students Are Testing

Walk the room slowly. You're watching for:

• Students who go too fast — if they're done in 30 minutes and put their head down, the data is suspect. Quietly redirect them to check their work.
• Students who stop writing entirely — this is usually anxiety or confusion, not deliberate refusal. A quiet check-in ("you've got plenty of time, just move to the next one") can get them moving again without disrupting anyone else.
• Students who are randomly bubbling — you can usually tell by posture and the rhythm of their pencil. Gently redirect them to read before marking.

Don't hover or make students feel watched. But don't grade papers at your desk either. Your presence and attention during the mock signals that this matters — and students perform closer to their actual ability when they believe the task is real.

Action step: Stand at the back of the room for the first 15 minutes, then circulate slowly. If you sit down and start grading, students start treating it like a regular assignment. Your physical presence is part of the condition you're setting.

How to Turn the Data Into Reteach Priorities

This is where most mock test days fail. Teachers score the tests, look at the class average, and feel discouraged or relieved depending on the number. Neither response leads to better instruction.

What you want is question-level data by student. That sounds overwhelming, but it doesn't have to be. Use a simple class grid: students' names down the left side, question numbers across the top, check marks for correct and X's for incorrect. Once you fill it in — or have students self-score under supervision — you can see in 90 seconds which questions the whole class missed, which ones only a few students missed, and which students missed nearly everything.

The whole-class misses are your reteach targets. The isolated student misses tell you who needs small group work. The students who missed most of everything need a different conversation — about study habits, test-taking strategy, or whether they need support beyond your classroom.

Action step: Before you score anything, write down what you predict your class's weakest reporting category will be. Then score the tests and check your prediction. The gap between what you expected and what the data shows is where the most valuable instructional learning happens.

What to Tell Students After the Mock Test

Don't hand back scores and move on. Don't just read out the class average. Students need to understand what the data means and what they can do with it.

Walk through 3-4 questions the class mostly missed. Show the question on the projector. Show the correct answer. Explain exactly why each distractor was wrong. Then let students look at their own tests and see if they chose that distractor. When students recognize "I did the exact thing this question was designed to make me do," they develop real test awareness — and they'll be less likely to repeat the mistake when it counts.

Also tell students something honest about what's coming: "You've got X weeks. Based on what I saw today, most of us need the most work on RC2. Here's what we're going to do about it." Teachers who name the plan earn trust. Teachers who hand back papers and immediately start new content generate anxiety instead.

Action step: Prepare a 5-minute talk for the day after the mock test: what the class did well, what you're going to work on together, and what individual students can do if they're worried about a specific area. Have it ready before you hand back results — don't wing it in the moment.

When to Run the Mock Test

Three to four weeks before STAAR is ideal. Early enough that you can act on the data; late enough that there's meaningful content to assess. A mock test six weeks out surfaces gaps you already know exist and generates anxiety without a clear payoff. A mock test one week out doesn't leave time to change anything.

If you can only run one, do it at the three-week mark and build your final sprint around the data. If you can run two, try the first at five weeks (to set your reteach priorities) and the second at two weeks (to measure whether the reteach worked). Two data points also let you show students their own growth — which matters more for motivation than any pep talk.

The mock test day is not a break from instruction. It's one of the most instructionally valuable things you can do in the final stretch — if you use the data. Without the follow-through, it's just a stressful Tuesday. With it, it's the clearest window you'll have into what your students actually know before the real test.