Exit Ticket & Bell-Ringer Prompt
This prompt creates exit tickets and bell-ringers tied directly to the day's learning objective — no busywork, no review filler. Choose your format, get questions with answers and one-line explanations, a student confidence self-rating, and a final question designed to surface misconceptions. Formatted for half-sheet printing or projecting.
Five-minute formative checks tied to the day's objective — exit tickets and bell-ringers on demand.
Act as an assessment designer. Create a [exit ticket / bell-ringer / do-now] with these specs:
GRADE/SUBJECT: [e.g. 8th grade ELA]
TODAY'S OBJECTIVE: [e.g. 'identify theme in a short story']
FORMAT: [choose: 3 questions (2 quick + 1 short response) / single deep question / 5-question quick check]
TIME: [e.g. 5 minutes at end of class]
Rules: every question must directly assess today's objective (no review questions, no busywork); include the correct answers with 1-line explanations; add a 1–4 self-rating line for students ('How confident are you?'); make the last question reveal misconceptions, not just recall. Format for half-sheet printing or projecting.
See what this prompt creates
Exit tickets are the highest-ROI five minutes in teaching: they tell you, before the kids leave, whether today worked. The problem is that writing a good one daily — aligned to the objective, quick to answer, revealing about misconceptions — is exactly the kind of small creative task that falls off a tired teacher's plate. So exits become "write one thing you learned," which tells you nothing. This prompt restores the good version at zero marginal cost.
The design principle here is assessment, not activity. Every question must tie to today's objective; the last question is specifically engineered as a misconception trap rather than a recall check. That last question is where the data lives — a recall question tells you who was awake; a well-built misconception question tells you who actually understood. The confidence self-rating ("1–4, how sure are you?") adds a second data layer: confident-wrong answers flag the deepest misunderstandings.
Getting the best result
- Paste today's actual objective. "Identify theme in a short story" produces a tight ticket; "ELA stuff" produces mush. The ticket is only as aligned as the objective you give it.
- Use the answers diagnostically. Sort tomorrow's warm-up by what the tickets revealed — reteach the misconception the trap question caught, not the whole lesson.
- Bell-ringers are yesterday's exit tickets, evolved. Run the prompt in bell-ringer mode with today's prerequisite: "what they need to remember for today's lesson." It primes instead of reviews.
- Keep the ritual under 5 minutes. If grading exits takes longer than giving them, switch to the single-deep-question format — one rich response beats three shallow ones for data.
3 variations to try
Digital version: add "format as 3 Google Forms questions with answer validation" for the paperless classroom.
Peer-discussion exit: "pairs discuss for 2 minutes, then each writes the pair's best answer" — the collaborative variant that doubles as review.
Week-review Friday ticket: "5 questions, one per day's objective this week, labeled by day" — the spiral-review exit that feeds Monday planning.
How to use this prompt
- Copy it — hit the copy button above to grab the raw prompt text.
- Fill the brackets — replace anything in [BRACKETS] with your own details.
- Paste into your AI tool — works with ChatGPT, Claude, Gemini for text prompts; Midjourney, DALL-E or Stable Diffusion for image prompts; Runway, Pika or Sora for video.
- Iterate — tweak one bracket at a time until the output is exactly right.
Frequently asked questions
What's the difference between an exit ticket and a bell-ringer?
Direction in time: exit tickets check what today taught (looking back), bell-ringers prime what today will teach (looking forward). The prompt handles both — choose the mode in the first bracket and it adjusts the design accordingly.
How many questions should an exit ticket have?
Three is the sweet spot: two quick checks plus one short response. Enough for real signal, short enough to actually happen in the last five minutes. The single-deep-question format works better when you want writing data.
Do I need to grade exit tickets?
No — sort, don't score. Skim for patterns (which misconception won?) and let that drive tomorrow's warm-up. Grading every exit ticket is how teachers burn out on formative assessment; the data is the point, not the points.
What if students just write 'I learned stuff'?
That's a prompt-design failure, not a student failure — vague tickets invite vague answers. This prompt's questions are specific enough that 'stuff' isn't an available answer. Specificity in, specificity out.
