Exit Ticket

An Exit Ticket is a short written response participants produce at the very end of a session — typically in two to three minutes — that captures one specific takeaway, commitment, or question before participants leave the room or log off the call. The participant submits the ticket to the workshop leader (physically, digitally, or via form) before exiting. The format is structurally similar to a Minute Paper with one distinct difference: Exit Tickets are always at session close, and they typically include a forward-looking commitment rather than only a backward-looking reflection. The commitment is what makes the ticket an exit, not just a reflection — participants leave the session with a named next step, and the workshop leader leaves with the cohort's collective commitments as input for the next session's design.

The Exit Ticket is documented in Thomas Angelo and K. Patricia Cross's Classroom Assessment Techniques (1993) as a variant of the Minute Paper specifically positioned at session end. Robert Marzano's The Art and Science of Teaching and its extension work on classroom techniques documented the contemporary K–12 and higher-education application. Dylan Wiliam and Siobhán Leahy's Embedding Formative Assessment (2015) codified it as one of the core formative-assessment techniques in the formative-assessment movement. In workshop contexts, Exit Tickets are particularly strong for multi-session programs where the commitments captured at each session's end feed directly into the next session's opening check-in.

Exit Ticket closes the retrieval-and-reflection family. Where Minute Paper can run at any moment for retrieval, Muddiest Point surfaces confusion, Two-Stars-and-a-Wish structures peer feedback, and Structured Silence protects internal reflection, Exit Ticket specifically anchors the session's close with a forward-looking commitment. The position at the end is structural, not incidental.

What It Is

Four structural components define Exit Ticket.

• Placement at the session's very end. The Exit Ticket is the last thing participants do before leaving. Placement matters — running an "Exit Ticket" at the middle of a session collapses it into a Minute Paper. The end-of-session positioning is what makes the ticket an exit.
• A short, structured prompt — typically forward-looking. The prompt asks for a takeaway plus a commitment, a single action the participant will take, or a specific question they are leaving the session with. What is one thing you will do differently in your work this week based on today's session? What is the single most important idea you are taking away, and what will you do with it? What question are you leaving with that needs to be addressed in our next session? Forward-looking prompts produce commitments; backward-only prompts produce reflections without action. The forward-looking discipline is the activity's load-bearing element.
• A collected submission. Participants hand in or submit their Exit Tickets before leaving. Physical cards in a box, digital submission via form, post to a shared channel — the specific mechanism varies, but the submission is structural. Tickets that are written and kept privately are reflections, not exits; the submission is what makes the commitment visible to the workshop leader and, by implication, to the participant themselves.
• Workshop-leader review between sessions. The leader reads the collected tickets and uses them as input for the next session's design. Recurring patterns in the commitments, common questions, and the relationship between previous-session commitments and current-session reports become iterative design data. Exit Tickets collected and ignored have the same effect as Muddiest Points ignored — participants learn the ticket does not matter and their subsequent tickets become performative.

When to Use It

Exit Ticket fits any session where the close should include a forward-looking commitment and where the workshop leader will actually review and use the responses. It is especially strong in multi-session programs where each session's exit tickets feed into the next session's opening, creating a visible commit-act-reflect rhythm across the program.

Good candidates:

• Multi-session programs where commit-act-reflect cycles across sessions are structural.
• Single sessions where participants should leave with a specific next action, not just general impressions.
• Cohorts that benefit from social visibility on their commitments — the submission produces visibility the workshop leader can reference in the next session.
• Sessions where the workshop leader wants diagnostic data about what landed and what participants are committing to do with it.

Less suitable:

• Sessions where no commitment or next action makes sense — rare, but possible for purely exploratory sessions.
• Programs where the workshop leader will not actually read and respond to the tickets — the activity degrades quickly if commitments go unacknowledged.
• Very short sessions where the two-to-three-minute Exit Ticket cannot fit.
• Cohorts that experience the submission ritual as performative or inauthentic — in which case a lighter Minute Paper or Structured Silence may fit better.

In-Person and Virtual Delivery

Exit Ticket runs cleanly in both in-person and virtual delivery. The collection mechanism differs, but the core structure translates without loss.

In person. Participants write on index cards and submit them in a box or pile on their way out of the room. The physical submission ritual — literally exiting past the collection point — reinforces the activity's framing. In-person delivery has a small advantage: participants cannot skip the submission without the leader noticing, which reinforces the expectation across sessions.

Virtual. Participants submit via a form (Google Forms, Typeform, Airtable), a shared document, or a post to the program's communication channel. The submission happens before participants leave the call. Virtual delivery's advantage: the form format automatically aggregates responses for the leader to review, which makes between-session pattern analysis easier than handling physical cards.

Choosing the modality. Match to the program's dominant format. For virtual delivery, choose a submission mechanism that aggregates cleanly (forms over open chat). For in-person, keep the submission ritual physically visible (collection box at the exit, not quietly dropped somewhere).

How to Run It

Before the Session

1. Draft the specific prompt (leader design work). Pre-draft the Exit Ticket prompt for the session. The prompt should match the session's content — an Exit Ticket after a content-heavy session asks different questions than one after an application-focused session. Forward-looking language is structural: "what will you do" or "what commitment are you making" rather than "what did you learn."
2. Prepare the submission mechanism (logistics). In person: index cards, collection box or folder, clear placement near the exit. Virtual: form with a single submit question, tested before the session so the submission link is ready to post.
3. Plan the between-session response (leader design work). Decide how you will use the collected tickets — mention specific commitments in the next session's opening, address recurring questions, surface patterns publicly or privately. Planning the response makes the tickets input rather than paperwork.

During the Session

1. Build the Exit Ticket into the session timing from the start. Do not treat it as an optional extension past the session's end. Reserve three to five minutes at the end for writing plus submission, and honor that time even if the session runs long.
2. Frame the Exit Ticket briefly (30 seconds). At the transition to the session close: "Before we end, I'd like you to spend two minutes on an Exit Ticket. The prompt is: [prompt]. Submit your card/form before you leave." Brief, clear, matter-of-fact.
3. Writing time (2–3 minutes). Participants write silently. The leader stays available for logistical questions but does not fill the space.
4. Collection and close (1–2 minutes). Participants submit their tickets as they exit. The leader may briefly acknowledge the submissions ("thank you — I'll read through these before next session") but does not discuss specific content in the moment. The session ends.

After the Session

1. Read the tickets and identify patterns (leader work, between sessions). Group responses by theme. Identify commitments that appeared across multiple participants, questions that recurred, and specific commitments worth surfacing or following up on at the next session.
2. Respond at the next session's opening. Reference the Exit Tickets from last time. Acknowledge a pattern, respond to a common question, invite participants to report on whether the commitments they made at the last session actually happened. The acknowledgment closes the commit-act-reflect loop and reinforces the Exit Ticket's structural role.
3. Use ticket patterns as iterative design feedback. Recurring themes across multiple cohorts' tickets are the strongest signal that the session content or pacing needs revision. Exit Ticket data improves the program's design across iterations, not just the next session's response.

An Example in Practice

A twelve-week cohort program for eight coaches building new workshop offers. Each weekly session ends with an Exit Ticket at minute 88 of the 90-minute session.

At week four's session close, the workshop leader displays the Exit Ticket prompt: "In one sentence: what is the specific thing you will change or complete in your offer design this week based on what we covered today, and when specifically will you do it?"

Participants write for two minutes on index cards. Submit them to the collection folder as they leave. The session ends.

Between sessions, the leader reads the eight tickets. One coach commits to rewriting the outcome statement for her cohort offer by Thursday. Another commits to running a ten-minute diagnostic call with a past client to pressure-test his new positioning draft. A third commits to mapping her session-by-session design against the content-density framework from week three and identifying the two sessions that are overloaded. The commitments vary in specificity; two are vague and the leader flags them as conversations to have with those participants directly before the next session.

At week five's opening, the leader briefly references the patterns: "Last week's Exit Tickets showed about half of you are now working on outcome-clarity revisions and about half on content-density rebalancing. Both are exactly where we'd expect this program to be at week four-to-five. Quick check-in: who made the commitment they made last week, and who didn't? No judgment, just signal." Five coaches raise their hands. Three did not complete their commitments; two of them name the reason (unexpected client work, travel). The leader adjusts the week-five session's application segment to include fifteen minutes for those three to work on what they had committed to.

Over the twelve weeks, the Exit Ticket rhythm produces visible evidence of the cohort's work between sessions. By week nine, the leader can reference patterns in the accumulated tickets — which principles are landing, which are not, which coaches are making consistent week-to-week progress versus sporadic — and adjust the program accordingly.

Variations

• Commitment-Only Exit Ticket. The prompt asks only for the forward-looking commitment, not for a backward-looking takeaway. Used when the session has already included other retrieval moments (Minute Paper, Muddiest Point) and the exit moment should focus purely on action.
• Question-Only Exit Ticket. The prompt asks only for the question the participant is leaving with. Used when the session has raised as many questions as answers and the leader wants explicit visibility on what is unresolved before the next session.
• Public Exit Ticket. Tickets are written on public sticky notes on a cohort wall or shared digital board rather than collected privately. The cohort sees each other's commitments. Used when cohort-level accountability is a target outcome and the cohort's trust supports public commitment-making.
• Paired Exit Ticket. Pairs write their exit tickets, then exchange them briefly with a partner before submission. The partner sees the commitment, which adds lightweight accountability. Used in cohorts where partner accountability is part of the program's structure.

Which Method It Serves

Exit Ticket is a cross-method activity. It adds session-closing commitment capture to any method. The underlying principle is closing commitment — the research-supported observation that learning transfers to action more reliably when participants articulate a specific commitment at the end of a learning experience than when they leave with general impressions.

Exit Ticket functions across methods. In Action Learning, Exit Tickets at set meetings capture the between-session action commitments structurally. In Project-Based Learning, Exit Tickets capture what each participant will build or revise before the next session. In Problem-Based Learning, Exit Tickets capture the transferable principle each participant is taking from a specific problem-based session. In Collaborative Learning workshops, Exit Tickets capture individual commitments that group work alone might leave abstract. In multi-session programs using any method, Exit Tickets become the explicit commit-act-reflect rhythm backbone — the structural mechanism that turns sessions into a cumulative arc rather than isolated learning events.

Design Considerations

• The forward-looking structure of the prompt determines the value of the activity. Exit Ticket is defined by the commitment it captures. A backward-only prompt ("what did you learn?") produces a reflection that ends at the session close. A forward-looking prompt ("what will you do this week?") produces a commitment that extends the session's effect into the participant's ongoing work. Before running Exit Tickets, pressure-test the prompt: does it ask for something the participant will do or decide after the session, and is the commitment concrete enough to be reportable at the next session? If either answer is soft, the ticket captures intention without action, which collapses into a reflection.
• Read and respond to the tickets, or the activity collapses across iterations. Like Muddiest Point, Exit Tickets collected and ignored degrade quickly. Participants learn the ticket does not matter and subsequent tickets become performative. The workshop leader's response — at the next session's opening, in direct follow-up, in program design adjustment — is what keeps the activity load-bearing. Commit to a response path and sustain it across the program.
• Build the ticket into session timing from the start, not at the end. Sessions that run long often skip the Exit Ticket because "we ran out of time." Budget the ticket's two-to-three minutes plus submission ritual as protected time, the same way you would budget any other activity. Skipping the ticket because the content ran long teaches participants the ticket is optional, which undermines the commit-act-reflect rhythm the ticket is building.
• Match prompt specificity to cohort capacity. A cohort new to Exit Tickets may need more scaffolded prompts ("what is one thing you will do this week — specifically what, when, and how?") than a cohort that has been making commitments for weeks and can handle a shorter prompt ("commitment for this week?"). Calibrate the prompt to where the cohort is in the program, not to a fixed format.
• Use Exit Tickets as the explicit commit-act-reflect backbone in multi-session programs. In programs that run alongside Action Learning Sets or Work-Cycle Check-Ins, the Exit Ticket captures the commitment at the session's end and the next session's opening reports on whether the commitment happened. The rhythm becomes the program's structural heartbeat. Programs without this rhythm often have content that lands but does not translate into action; programs with it convert content into changed behavior at substantially higher rates.

Where this goes next: Exit Ticket closes the retrieval-and-reflection family with a session-end commitment capture. The next family shifts to the quick real-time signals workshop leaders use to read cohort state in-session — brief moves that surface energy, understanding, or positioning without the writing or reflection infrastructure the retrieval-reflection activities require. See Stand-Up/Sit-Down.

Related

Read this next:

• Stand-Up/Sit-Down — the first activity in the polling-and-temperature family; shifts from written-reflection activities to quick real-time in-session signals.

Foundations of this activity:

• Minute Paper — the Minute Paper counterpart that can run anywhere in a session; Exit Ticket is the end-of-session forward-looking variant.
• Muddiest Point — the confusion-surfacing counterpart; compare the session-end commitment focus with Muddiest Point's segment-end confusion focus.
• Work-Cycle Check-In — the action-family activity that Exit Tickets feed into when programs use both — Exit Tickets capture commitments; Check-Ins report on their execution.
• The Guiding Principles of Active Learning — the principles activated, especially purposeful initiative and honest reflection.

Where this leads:

• Which Active Learning Method Fits Your Workshop? — Exit Ticket is the strongest sub-activity when session-closing commitment capture is the target, especially in multi-session programs.
• Action Learning — the method where Exit Tickets become the explicit commit-act-reflect rhythm backbone of the program's structure.

References

Angelo, T. A., & Cross, K. P. (1993). Classroom assessment techniques: A handbook for college teachers (2nd ed.). Jossey-Bass.

Marzano, R. J. (2012). The art and science of teaching: Classroom techniques to help students really learn. ASCD.

Wiliam, D., & Leahy, S. (2015). Embedding formative assessment: Practical techniques for K–12 classrooms. Learning Sciences International.