---
name: exit-ticket
description: Use when asked to design a short end-of-lesson prompt or task that checks whether today's objective landed — as distinct from [[formative-assessment]], the broader practice of checking understanding throughout a lesson, of which this is one specific technique.
---

# Exit Ticket

An exit ticket is a short, specific prompt or task students complete
in the last few minutes of a lesson, used to check whether the day's
objective actually landed before anyone leaves the room. It's one
concrete technique within [[formative-assessment]] — the broader,
ongoing practice of checking understanding throughout a lesson — not a
substitute for checking understanding earlier as well.

## Key components

- **One targeted question or task** — tied directly to the session's
  stated objective, specific enough that a right answer only makes
  sense if the objective was actually met.
- **Short completion time** — a minute or two, not a full assessment;
  the point is a quick signal, not a comprehensive test.
- **Individual response** — completed by each student alone, so the
  result reflects individual understanding rather than a group
  consensus that can mask individual gaps.
- **A pre-decided response plan** — what happens to tomorrow's lesson
  if most tickets show a miss: reteach, regroup, or move on, decided
  before results come in.
- **Quick review turnaround** — reviewed before the next session, so
  its result can actually change what happens next.

## Making the prompt do real diagnostic work

A weak exit ticket asks students to rate their own understanding
("how confident do you feel?") or to recall a fact loosely related to
the lesson; a strong one asks them to actually perform the skill the
objective named, in miniature. If the objective was "add two fractions
with different denominators," the exit ticket should be one such
problem, not a question about how fractions felt today — the former
tells the teacher whether the objective was met, the latter tells them
almost nothing actionable. This is the same discipline a checkable
learning objective already demands: an exit ticket that isn't built
directly from the objective usually reveals that the objective itself
wasn't specific enough to check in the first place.

## Common pitfalls

- **Self-report instead of performance** — asking students to rate
  their own confidence rather than demonstrate the skill produces
  data that doesn't reliably track actual understanding.
- **Too broad to diagnose** — a prompt covering the whole lesson's
  content rather than the single objective makes a weak result hard to
  act on, since it's unclear which part actually failed.
- **Collected but never reviewed** — gathering tickets and moving on
  without looking at them before the next session turns the technique
  into paperwork instead of a formative check.
- **No plan for a bad result** — discovering most of the class missed
  the objective with no decided next step wastes the one advantage
  an exit ticket provides: time to react before the next lesson.
- **Used as a grade** — attaching real grading weight changes how
  honestly students respond and pushes the technique toward summative
  territory it isn't designed for.

## Learn more

- [[formative-assessment]] for the broader practice this is one
  technique within, including checks that happen earlier in a lesson.
- [[lesson-plan]] for where an exit ticket fits as the closing check
  for understanding in a single session.