Exit Tickets That Actually Work: How to Design End-of-Lesson Checks That Inform Tomorrow's Teaching

Exit tickets are one of the most over-used and under-effective tools in teaching. Teachers use them because they feel formative — you can see what students know at the end of class. But in most classrooms, exit tickets are collected, briefly scanned, and then class proceeds as planned the next day regardless of what the data showed.

That's not formative assessment. That's summative assessment on a sticky note.

Exit tickets become genuinely useful when you design them around a question whose answer will actually change what you do next.

Design Around a Decision Point

Before writing an exit ticket, ask: what decision am I trying to make with this data?

"Do I need to reteach this concept before moving on, or can I proceed?" is a real decision. "Do I need to provide additional scaffolding for the bottom third before the assignment is due?" is a real decision. "Which specific misconception is most common, so I can address it first tomorrow?" is a real decision.

"How well do students understand today's lesson?" is too vague to drive instruction. It doesn't tell you what to do tomorrow.

When you know the decision the exit ticket should inform, you can write a question that actually helps you make that decision.

Write a Single, Precise Question

Multi-question exit tickets spread student attention and spread your data across multiple variables. Pick one question that most precisely targets the decision you're making.

A good exit ticket question:

• Requires students to demonstrate understanding, not recall — "explain why X happens" not "define X"
• Has a wrong answer that reveals a specific misconception — so you know not just that students are wrong, but how
• Can be read and responded to in three to five minutes

Poor exit ticket: "What did you learn today?" (no diagnostic value)

Better exit ticket: "A student claims that [specific misconception]. Do you agree or disagree, and why?" (reveals exactly whether the main misconception was corrected)

Sort, Don't Read

The fastest way to use exit ticket data: sort the responses into three piles as you read — got it, partially got it, didn't get it. Don't write feedback on every one. Just sort.

The sort takes five to ten minutes. It tells you exactly what percentage of students is in each category, and it reveals which specific misconceptions to address. You now have real data for lesson planning.

If 80% or more "got it," proceed. If 40-60% are in the "partially" or "didn't get it" category, reteach before moving forward. If you see the same misconception in a third of the papers, start tomorrow's lesson by addressing exactly that misconception.

Close the Loop With Students

One of the highest-leverage moves with exit tickets: open the next class by showing students what you found.

"Yesterday's exit ticket showed me three things. Most of you understood X. About a third of you had this specific confusion — let me address that. And two of you wrote something that made me think we need to talk about Y."

This closes the loop for students — they see their responses actually changed instruction, which builds trust and motivates engagement with future exit tickets. Students who feel their thinking is invisible put less effort into check-in tasks.

LessonDraft and Formative Planning

LessonDraft can help you design exit tickets tied to specific decision points — so you're not collecting data without a plan for using it. The exit ticket is only as good as the instruction decision it informs.

Next Step

Design your next exit ticket starting with the question: what decision am I making with this data? Write that decision down. Then write one question whose answer will help you make it. That's a real exit ticket.