Exit Tickets for STAAR Prep: How to Turn Daily Data Into Better Results

You asked your class how the lesson went. Three hands went up. You moved on. Now it's two days before the unit test and you're realizing you have no idea which students actually understood the standard and which ones were nodding along while completely lost.

That's exactly what exit tickets solve — but only if you're using them correctly. A sticky note with "I got it / I didn't get it" doesn't tell you what to fix. A TEKS-aligned three-question exit ticket tells you precisely where the gaps are and who has them. Here's how to build a system that takes five minutes at the end of class and saves you from guessing every morning about whether to move forward or reteach.

What Makes an Exit Ticket Actually Useful for STAAR Prep

Most exit ticket failure comes from one thing: questions that aren't specific enough to tell you what to do tomorrow. "Did you understand today's lesson?" is not useful data. "Which of the following best describes the central idea of the passage?" — answered correctly or incorrectly by your students — is data you can act on.

For STAAR prep specifically, a useful exit ticket has three qualities:

• It tests a single TEKS. When a student misses it, you know exactly which standard to address. If the question conflates three standards at once, a wrong answer tells you nothing specific enough to be useful.
• It uses STAAR question format. Multiple choice with distractors, or a short-answer that asks students to explain their reasoning. Not fill-in-the-blank, not "list three things" — formats that bypass the thinking the actual test requires.
• It's short enough to complete in three minutes. One to three questions. If it takes longer, students rush the end or give up before finishing. Either way, your data is corrupted.

Action step: Look at your last exit ticket. Does each question map to exactly one TEKS? Is it in STAAR format? Could your students complete it in under three minutes? If any answer is no, rewrite it before you use it again.

How to Write a Three-Question Exit Ticket That Tells You Something

This structure works for nearly any subject and grade level:

1. Question 1 — Direct application: One STAAR-style question on today's target standard. This tells you whether today's instruction landed.
2. Question 2 — Transfer: A slightly different context for the same standard — a new scenario, a different text type, a different type of word problem. This tells you whether students truly understand the concept or whether they only recognize the version you just taught them.
3. Question 3 — Spiral: One question from a previous unit your data says is still a gap. You're not grading this one for today's lesson — you're monitoring whether a persistent weakness is improving over time.

Three questions, five minutes max. When you collect them, look for three things: Who got Q1 wrong (today's instruction didn't stick)? Who got Q1 right but Q2 wrong (surface-level understanding, not transferred)? Who's still missing the spiral standard (persistent gap that needs deliberate intervention)?

Action step: Write a three-question exit ticket for your next lesson using this structure before you leave today. Write the TEKS code next to each question. This takes ten minutes once, and you can reuse the question bank next year.

What to Do With Exit Ticket Data the Next Morning

This is where most teachers lose the thread. You collect the exit tickets, fully intending to review them. Something else happens. The next day arrives and you're teaching the next lesson with no idea what yesterday told you.

Here's a constraint that makes this manageable: give yourself five minutes at the end of the period — before you leave the room — to sort the exit tickets into three piles.

• Got it: Correct on Q1 and Q2
• Partial: Correct on Q1, wrong on Q2 — or right answer, wrong reasoning
• Not there yet: Wrong on Q1

Don't count. Don't calculate percentages. Just sort. That takes three minutes. Then look at the pile sizes. If the "not there yet" pile is more than a quarter of your class, you're reopening that standard tomorrow before moving on. If it's two or three students, you're pulling them during work time. If almost everyone got it, you're moving forward.

That three-minute sort is the entire system. Everything else is optional refinement.

Action step: Sort the exit tickets from this week's lessons before you leave today. Three piles. Don't overthink it. Then write your plan for tomorrow's opening five minutes based on what the piles tell you.

How to Group Students Based on Exit Ticket Results

Once you've identified your "not there yet" students on a particular standard, you have your small-group list. The goal is to work with that group while the rest of your class practices independently — which means your independent task needs to be solid enough that students can do it without you hovering.

A small-group pull after exit ticket data works like this:

• Keep the group small. Four to six students. More than that and it starts to feel like another whole-class lesson. You lose the benefit of the intimate setting where you can actually hear student thinking.
• Start with diagnosis, not reteach. Ask students to talk through their thinking on the exit ticket item before you explain anything. You need to know whether the gap is conceptual (they don't understand the idea), vocabulary-based (they didn't understand the question), or procedural (they know what to do but make execution errors). Those are different problems with different solutions.
• Reteach using a different approach. If you used numbers and they're still missing it, try a visual. If you used a visual, try a real-world context. Different representation, same underlying concept.
• Give one more item before they return to their seats. If they get it, they're ready for independent practice. If not, you know this standard needs another day with this group.

Action step: Identify the three students who have missed the same exit ticket standard twice or more in the past two weeks. Schedule a five-minute small-group pull for tomorrow. That's your intervention starting point — not a formal RTI referral, just five minutes and a targeted question.

Exit Ticket Mistakes That Undermine the Whole System

A few things that make exit tickets stop working:

• Making them a grade. The moment it's a grade, students start copying neighbors to protect their average. Your data is now corrupted. Keep exit tickets formative and ungraded — if administrators push back, explain that you're using them for instructional decisions, not evaluation.
• Using reflection prompts instead of assessments. "What did you learn today?" is a reflection prompt. Reflection has its place — it's just not the same thing as assessment data. Both have value. Don't confuse them.
• Collecting data and never adjusting instruction. If exit tickets aren't changing what you do the next day, you're adding paperwork without adding value. Trim the system until you can actually act on it every time. A system you use is better than a system that's theoretically optimal.
• Writing new questions from scratch every day. Build a question bank as you go. When you teach a standard, write three exit ticket questions for it and save them. By December you'll have a library that takes 30 seconds to pull from instead of 20 minutes to build fresh.

Exit tickets are one of the highest-leverage daily tools you have for STAAR prep because they give you real-time data on the exact standards being tested. The system doesn't have to be complicated — it has to be consistent. Pick a structure, run it every day, and actually use what it tells you. That's what moves scores.