Pear Deck turns slides into a conversation — every student answering, not just the ones with their hands up — which makes it a natural home for the last three minutes of a lesson. Exit tickets and check-ins in Pear Deck ride on a tool your class already uses mid-lesson: add a ticket slide at the end of the deck, project the responses as they land, and let the muddiest points plan tomorrow. This guide shows how to build exit tickets into a Pear Deck lesson, how check-ins differ from full tickets, how Pear Pop handles the days you didn’t plan one, and how the classic muddiest point technique works in this format. For the platform-neutral routine, see our guide to the exit ticket; for the sister workflow in the testing platform, see exit tickets in Pear Assessment.
Why Pear Deck works for exit tickets and check-ins
Pear Deck’s formative design is the reason this pairing works. Every response type in a deck — text, multiple choice, number, draggable, drawing — collects answers from all students simultaneously and shows them to the teacher in a dashboard, which is precisely the exit ticket requirement of universal, reviewable evidence. Because the ticket is just the last slide of the lesson students are already in, there is no transition cost: no new tab, no new login, no three minutes of “go to this link” at the exact moment the class is itchiest to leave.
The second advantage is tone. Pear Deck sessions feel participatory rather than test-like, and students’ responses can be shown anonymously on the projector — a feature teachers use to display strong answers and common errors without naming anyone. Exit tickets thrive on that low-stakes honesty.
The response types also widen who can answer well. A draggable slide (“drag the label to the matching part of the diagram”) checks understanding from students whose writing lags their thinking; a drawing slide does the same for a science process or a math representation; a number slide handles the quick computational check. Rotating the ticket’s response type across the week means the exit data stops being a proxy for writing fluency — the same unbundling argument that drives differentiated tickets generally. The teacher still gets one sortable class picture; more students get a fair way to contribute to it. And when the session ends, Pear Deck’s Takeaways give students a copy of their own responses, which turns the ticket into a study artifact instead of a vanished form: the question they fumbled is sitting in their Drive tonight, next to their own attempt at it. Our broader overview of Pear Deck assessment covers how the platform’s response data supports grading and feedback beyond the ticket itself.
Building an exit ticket into your deck
The build is a three-slide habit at the end of any lesson deck:
- The core slide. One text-response slide asking the day’s objective question — “Explain why the character’s decision backfires, using one detail from the chapter.” Text response is the workhorse because the explanation is where misconceptions show.
- The confidence slide. A multiple-choice or number slide: “How confident are you in today’s idea? 1 = lost, 4 = could teach it.” Five seconds per student, and it splits your wrong answers into help-requests and misconceptions.
- The open slide. “What is still unclear?” — the floor for anything the first two slides missed.
Practical settings: keep the session in instructor-paced mode for a whole-class close, or switch the final slides to student-paced if classes end unevenly (early finishers in a lab, for instance). Anonymity on the projector view is worth setting deliberately — show responses without names when you discuss them, while the teacher dashboard keeps the names you need for follow-up. Teachers new to the platform sometimes worry the ticket slides “spoil” the deck for the next section; in practice, duplicating the deck per section or simply re-running the session keeps each class’s data clean.
Reusable template decks — bell ringers, checks for understanding, and exit tickets — are a documented part of the Pear Deck workflow, so build your three-slide close once, save it as your template, and append it to every lesson deck rather than designing under time pressure at 3 p.m.
the muddiest point exit ticket technique
The muddiest point exit ticket technique is the oldest check-in in the book — it comes from Angelo and Cross’s classroom assessment techniques — and Pear Deck’s text responses are its perfect modern vessel. The prompt is disarmingly simple: “What was the muddiest point in today’s lesson?” Students name the idea, step, or term that remains least clear. No right answer exists, which is precisely why students answer it honestly.
Why it outperforms generic “any questions?” by a mile: it asks for the location of confusion, and students are surprisingly precise cartographers of their own fog. Sorted tonight, twenty muddiest points cluster with almost embarrassing clarity — twelve students stuck on the same step, five on vocabulary, three lone wolves. Tomorrow’s opener writes itself. In Pear Deck, run it as the final text slide, scan the dashboard clusters live as students write, and read two or three anonymous entries aloud before dismissal — hearing their confusion named publicly, without blame, teaches the class that the muddiest point is data, not failure.
Two pitfalls keep the technique honest. First, students new to it answer vaguely (“everything,” “the whole lesson”) — model specificity once by showing what a useful muddiest point looks like: not “fractions” but “why the denominators don’t get added.” Precision is teachable and appears within a week of modeling. Second, resist answering every muddy point yourself tomorrow; the vocabulary cluster can be handled with a two-minute word wall review by students, and the lone wolves often pair-teach each other. The teacher’s response should target the big cluster — that’s the allocation the data is actually recommending. Rotate it with the confidence slide across the week so reflection doesn’t become rote; muddiest point on heavy-content days, confidence rating on skills days, core-question tickets when a hinge concept lands.
how can an educator use pear deck for formative assessment
Step back and the exit ticket is one answer to a bigger question: how can an educator use pear deck for formative assessment across the whole lesson, not just its close? The same response system serves every phase. Openers: a first slide that retrieves yesterday’s concept (which yesterday’s exit ticket selected for you). Mid-lesson: choice and draggable slides at hinge points, with the dashboard deciding whether the class proceeds or re-groups. Workshops: student-paced decks where you circulate, reading responses on your device and conferring with the students whose answers flag trouble. Close: the exit ticket trio above.
The through-line is the feedback loop’s speed. Pear Deck compresses the gather-interpret-respond cycle from a day (paper tickets) to a minute (the dashboard), and formative assessment research is unambiguous that tighter loops help learning more. The educator’s craft is in the question design — prompts that demand explanation and expose misconceptions — and in visibly acting on what the dashboard shows. The platform’s own site, peardeck.com, documents the response types and session modes this workflow uses.
Across weeks, the accumulated responses become a formative record worth mining. The student whose text answers are consistently one step behind the class, the concept that generated muddiest points in three separate lessons, the class period whose confidence ratings run oddly low on lab days — these longitudinal patterns are invisible in any single session and invaluable in conferences, intervention planning, and your own reflection on which lessons need redesigning. Treat the deck archive as a journal your students co-write: brief to collect, rich to reread.
pear pop quick prompts for exit tickets and check-ins
Not every day gets a planned deck. Pear Pop quick prompts for exit tickets and check-ins cover the gaps: Pear Pop lets a teacher launch a quick question prompt on the fly — no pre-built slides required — so a spur-of-the-moment check-in at the end of an unplanned lesson (the assembly ran long, the lab improvised itself) still produces collected, reviewable responses instead of a verbal “everyone good?”
The use pattern is simple. When the lesson ends somewhere you didn’t script, launch a Pear Pop prompt with the muddiest point question or a one-line core check, give the class ninety seconds, and read the cluster before they leave. It preserves the two things that make exit tickets work — universality and a record — on days when the template deck never got built. Teachers also use Pear Pop mid-lesson as an unplanned hinge check when discussion reveals unexpected confusion; the same tool serves the whole formative family, which is why it earns a permanent spot in the routine rather than novelty status. Compare this with the fully planned workflow in our guide to exit tickets in Pear Assessment: same philosophy — evidence before dismissal — different moment of the learning cycle.
Frequently asked questions
Can students see each other’s exit ticket answers in Pear Deck?
The teacher controls visibility. Responses can be projected anonymously for discussion, while the teacher dashboard retains names for follow-up. Students don’t browse each other’s answers by default.
What is the difference between a check-in and an exit ticket?
An exit ticket checks the lesson’s objective — it has a right-answer core. A check-in checks the student’s state — confidence, clarity, the muddiest point. Strong routines rotate both; they measure different things.
Do exit ticket slides work in student-paced mode?
Yes, and they’re often better there: students reach the close at their own pace, and absent students can complete the ticket from home in the same deck. Use instructor-paced mode when you want a synchronized whole-class ending.
How do Takeaways help after an exit ticket?
Takeaways give each student a copy of the session including their own responses. A student can review tonight exactly what they wrote about today’s concept — including the item they missed — which makes the ticket a study tool, not just a teacher tool.
How long should a Pear Deck exit ticket take?
Same as any ticket: three to four minutes for the three-slide close. If responses routinely run long, your text prompt is probably asking for an essay — narrow it to one idea, one explanation, one example, and watch completion quality rise.
The bottom line
Exit tickets and check-ins in Pear Deck succeed because the ticket is not another tool — it’s the last slide of the lesson you’re already teaching. Build the three-slide close into a template, rotate the muddiest point and confidence checks through the week, keep Pear Pop in your pocket for unscripted days, and let the dashboard’s clusters write tomorrow’s opener. The platform gathers the evidence; you close the loop.