Click to upload or drag and drop
PDF, DOCX, PPTX, TXT, JPG, JPEG, PNG, HEIC, ODP, ODT, BMP, or TIFF
up to 20MB
Uploading...
The fastest way to build an exit ticket is to pull the questions straight out of the material you just taught rather than inventing them at the door. Take the slide deck or reading from that lesson, choose the two or three ideas the next lesson depends on, and write one short question for each. Three questions is the ceiling. Anything longer stops being an exit ticket and becomes a quiz students rush through with their backpacks on.
An exit ticket has one job: tell you, before tomorrow, whether the class understood the thing you need them to have understood. It is not a grade, it is not coverage, and it is not a participation check. Everything below follows from that.
| Design choice | Do this | Why |
|---|---|---|
| Number of questions | 1 to 3 | It has to fit in the last four minutes, coats on |
| What to ask about | Only what tomorrow's lesson assumes | An exit ticket you cannot act on is just paperwork |
| Question type | One short answer, or two multiple choice plus one open | Short answer shows reasoning, multiple choice is fast to scan |
| Grading | Not graded, or completion only | Grading it turns honest confusion into guessing |
| Reading time | Under five minutes for the whole class set | If sorting takes longer, you will stop doing it by week three |
The first is a direct check on the day's core idea, phrased in the same language you used in class. If the lesson defined osmosis, ask something only a student who followed the definition can answer, not a term they could have guessed from the word itself.
The second is an application item. Give a one line scenario and ask which principle applies. This is where the gap between recognizing a definition and using it shows up, and it is the single most informative question type on an exit ticket.
The third is the confidence or confusion prompt: what is still unclear from today. It feels soft and it consistently surfaces things the other two miss, particularly the vocabulary problem hiding underneath a content problem.
Most teachers build exit tickets from memory at the end of a long day, which is why they drift toward the easiest thing to ask rather than the most important. Working from the actual file fixes that. Open the deck or reading, mark the two or three points the next lesson stands on, and build only from those.
If you teach from slides, the deck already encodes your priorities: the ideas that got their own slide are the ideas you decided mattered. Running the deck through slides to quiz gives you a pool of questions phrased in the vocabulary students just saw, and you keep the two or three that match tomorrow's dependency.
If the lesson was reading based, the same applies to the text. Send the chapter or article through PDF to quiz, then discard most of what comes back. Discarding is the point. A generator gives you thirty candidates in a minute so that choosing three takes thirty seconds instead of twenty minutes of drafting from a blank page.
One caution worth repeating: check the wrong answers before you use anything generated. Stems and coverage tend to be solid because they come from your source. Distractors are where a human eye still matters, especially two options that quietly mean the same thing.
| Format | Best when | Cost |
|---|---|---|
| Index card or half sheet | Phones are away, or devices are unreliable | You sort a stack by hand, which is fast for three questions |
| Shared quiz link | One to one devices, and you want results already sorted | Two minutes of class time lost to logging in |
| Projected question, verbal answer | Very short lessons, small groups | No record, and quiet students disappear |
Paper is underrated here. Three answers on a half sheet can be sorted into two piles, got it and did not, in under four minutes for a class of thirty, and those two piles are the whole point.
Sort, do not grade. Two piles, or three if you want a middle. The size of the did not pile decides tomorrow's first ten minutes: a handful means a small group while everyone else moves on, a third of the class means reteaching the idea differently before anything new gets introduced.
Look for the shared wrong answer too. When fifteen students pick the same incorrect option, that is not fifteen mistakes, it is one misconception with fifteen copies, and it usually points at something specific in how the idea was introduced. That is the most useful thing an exit ticket can hand you.
Keep the tickets that produce good information. Over a couple of terms you accumulate a set that works for each unit, which is what turns this from a nightly task into a five minute one. The question bank generator is built around exactly that habit of reusing what you already made.
An exit ticket is a very short check, usually one to three questions, that students complete in the last few minutes of class before they leave. Its purpose is diagnostic rather than evaluative: it tells the teacher what to do at the start of the next lesson. Most exit tickets are ungraded or scored for completion only.
Three at most, and often one is enough. The constraint is the clock: whatever you ask has to be answerable in three or four minutes by your slowest writer, while the class is packing up. A single well chosen application question beats five recall questions nobody finishes.
Generally no. Grading changes what students write, because a graded ticket rewards a confident guess and punishes an honest "I did not follow the second half." Completion credit keeps participation high without buying the guessing. Save grades for the assessments that are meant to measure rather than diagnose.
One that separates students who understood from students who copied. The reliable test is whether a student who was present but not paying attention could answer it from context alone. If they could, the question checks attendance rather than understanding, and it should be replaced with an application item.
Build them from the lesson file rather than from memory, and reuse them across years. Generate a pool of candidate questions from the deck or reading, keep two or three, and save the set with that unit. If you also want a cleaner deck to teach from next time, turning the source document into slides and generating from that keeps the lesson and its check aligned to the same material.
Exit tickets fail for one reason far more often than any other: they take too long to build and too long to read, so they quietly stop happening around week four. Keep it to three questions from material you already have, sort rather than grade, and act on the piles the next morning. That version survives a full year, and it is the one that changes what happens in the room.
From the same family of tools