Skip to content

Exit Ticket

A micro-check instrument — instantiates Formative Feedback Loop

A one-or-two-question prompt at the very end of a session that captures what landed and what's still murky, timed so the teacher can adjust the next session before the class moves on.

An Exit Ticket is a very short prompt — a question or two — that learners answer in the last minutes of a session, capturing what they understood, where they're stuck, or what they need next. Its defining features are timing and audience: it is collected at the boundary between sessions and read primarily by the instructor, so it can reshape the next session before the class has moved on. It trades depth for speed and freshness — a fast pulse taken while the session is still warm, kept brief enough to answer in seconds and read across a whole group in minutes.

Example

A chemistry teacher ends a class on balancing equations by putting one problem and one question on the board: balance this equation, and in one sentence, what part of balancing still feels shaky? Students hand in a half-slip on the way out; it isn't graded. Reading thirty slips over lunch takes ten minutes and tells her what no in-class show-of-hands would: two-thirds balanced the equation fine, but a cluster wrote that they "don't get why you can't just change the little subscript numbers." That's a specific, shared confusion. She opens the next class with a five-minute detour on exactly that — before building polyatomic ions on top of a cracked foundation.

How it works

  • It fires at the end-of-session boundary, inside the window where next-session instruction can still respond.
  • It is deliberately tiny — one or two prompts — so it costs seconds to answer and minutes to read across a whole group.
  • It is read for instructional adjustment: the output is a change to the teacher's plan, not a grade for the student.
  • A short self-report prompt ("what's still shaky") catches confusion a learner can feel but not yet fix.

Tuning parameters

  • Prompt count — one question keeps it instant; three gets richer signal but erodes the speed that makes it work.
  • Question type — a content check ("solve this"), a self-report ("what's murky"), or both; content checks are objective, self-reports catch felt confusion.
  • Turnaround — how fast the teacher reads and responds; an exit ticket answered a week later has fallen out of its window and become mere commentary.
  • Anonymity — named versus anonymous; anonymous frees honesty, named lets the teacher follow up with individuals.
  • Aggregation — read individually or tallied for the class pattern; tallying finds the shared gap worth a whole-class detour.

When it helps, and when it misleads

Its strength is converting a whole group's private, end-of-session state into a cheap, actionable read on what to teach next — captured while it's still fresh and timed to land where the plan can still change.

Its failure mode is inertness: if nothing in the next session changes in response, it's just collected paper. One or two prompts can only sample, so it misses gaps it didn't happen to ask about, and if it's treated as graded, students write what they think is wanted rather than what's true. The classic misuse is collecting exit tickets as a compliance ritual — proof that "checking for understanding" happened — without ever letting them alter instruction. The discipline that guards against this is to read them before the next session and let at least the strongest signal change the plan.[1]

How it implements the components

  • progress_signal — the end-of-session answers are the evidence that starts the loop.
  • feedback_timing_window — its whole design is to land inside the window where the next session can still respond.
  • instructional_response_channel — it feeds the teacher's next-session plan rather than returning directly to the learner.

It does not lean on a low-stakes frame as its defining purpose (low_stakes_frame — Low-Stakes Quiz), diagnose a specific misconception by design (gap_diagnosis — Misconception Probe), or hand the learner concrete next steps (actionable_feedback, learner_response_channel — Coaching Check-In).

  • Instantiates: Formative Feedback Loop — it supplies the between-session signal that lets the next session respond.
  • Sibling mechanisms: Low-Stakes Quiz · Misconception Probe · Adaptive Practice Set · Coaching Check-In · Draft Feedback Cycle · Formative Rubric · Peer Review Protocol · Practice Review · Progress Dashboard · Rapid Feedback Cycle

References

[1] The minute paper (or "one-minute paper"), a Classroom Assessment Technique catalogued by Angelo and Cross, asks students to briefly write what they learned and what remains unclear at a session's close; the exit ticket is a close relative used as a between-session instructional signal. ↩