How to Use Exit Tickets in the Classroom Without Wasting Time

Exit tickets are popular in classrooms, but most of them don't work the way teachers think they do. The idea is simple: at the end of class, students answer a brief question to demonstrate whether they understood the lesson. Teacher reviews them, adjusts next lesson accordingly. Clean, efficient feedback loop.

In practice, exit tickets are often too vague to tell the teacher anything, collected but never reviewed before next class, or designed around the wrong question. Used well, exit tickets are one of the highest-efficiency formative assessment tools available. Used poorly, they're paperwork.

What Makes an Exit Ticket Worth Doing

A useful exit ticket answers a specific question about a specific skill or concept from that lesson. It has to be:

Answerable in 2-3 minutes. Exit tickets that take longer than that eat into transition time and will be rushed or skipped. If a question requires full paragraphs to answer, it's a mini-assessment, not an exit ticket.

Specific to today's learning. "What did you learn today?" produces generic responses and doesn't tell you what you need to know. "What is one difference between photosynthesis and cellular respiration?" tells you whether students grasped the key distinction from today's lesson.

Designed around your next instructional decision. Before you write the exit ticket, ask yourself: what will I do differently tomorrow if most students can't answer this? If you don't have a plan, the exit ticket is just data collection without purpose. The data matters because it will change something — if it won't, don't collect it.

Reviewable before next class. If you can't look at them before the next lesson, the feedback loop breaks. Design your exit ticket collection and review process to be fast enough that you actually do it.

Types of Exit Ticket Formats

Direct question. "What is the difference between a simile and a metaphor? Give an example of each." This is the most common format and works well for knowledge and comprehension-level objectives.

Application task. "Solve one problem using the factoring method we learned today." This checks whether students can apply a procedure, not just name it. For math and procedural skills, application tasks are more diagnostic than recall questions.

Self-assessment plus evidence. "On a scale of 1-3, how confident are you about [today's skill]? Write one sentence explaining why you rated yourself that way." This combines metacognitive check-in with evidence — students who rate themselves a 3 but write "because I feel like I understand it" have told you less than students who rate themselves a 2 and write "because I can do the first step but then I get confused."

Muddiest point. "What is still unclear from today's lesson? If nothing is unclear, write one thing you could now teach someone else." This is useful when you want honest confusion data and when you expect significant variation in where students are.

Exit ticket as transfer check. Give students a new problem or scenario that requires applying today's concept in a slightly different context than what was practiced. This checks understanding rather than recognition.

How to Review Them Quickly

You don't need to read every exit ticket in detail. Sort them physically or mentally into three piles:

• Got it: student demonstrated the concept clearly
• Getting there: partial understanding, identifiable gap
• Not yet: significant confusion or blank

Count rough percentages. 80% "got it" means you can move forward with a brief review. 50% "not yet" means tomorrow's lesson needs significant reteaching. 20% "not yet" with identifiable students means those students need targeted support while the rest progress.

This sorting process should take 5-10 minutes. If it takes longer, the exit ticket was too complex.

Closing the Loop With Students

Exit tickets only change the learning relationship when students know they've influenced what happens next. A simple structure:

At the start of next class: "I looked at yesterday's exit tickets. About [X]% of you had [this confusion/this misconception]. So we're going to spend the first ten minutes on that before moving forward."

Students who see their confusion taken seriously invest more honestly in future exit tickets. Students who experience exit tickets as disappearing into a void start treating them as compliance tasks.

What Not to Grade

Exit tickets should almost never be graded. Once students know exit tickets are graded, they stop reporting honest confusion and start performing competence. The data becomes useless. Keep exit tickets explicitly low-stakes: "I'm not grading these — I'm using them to figure out what to teach tomorrow. Give me your real answer."

The rare exception: exit tickets used as accountability checks in skill-building sequences, where completing the ticket is the evidence of lesson engagement. Even then, the grade should be completion, not correctness.

Your Next Step

Before your next lesson, design the exit ticket first. Ask yourself: what would students being able to do tell me that the lesson succeeded? Write an exit ticket that directly tests that. Then build your lesson around ensuring students can answer it. Designing the assessment before the instruction keeps your objective clear and your lesson focused on the thing that matters.