Exit Tickets and Quick Writes: Formative Assessment During a David Copperfield Unit
Published on October 5th, 2026 by the GraideMind team
A novel unit is long, and waiting until the final essay to learn whether students understood the story is a risky strategy. Exit tickets and quick writes provide frequent, low-stakes checkpoints that reveal comprehension and thinking along the way. During a David Copperfield: Adapted for Young Readers unit, they can capture reactions to key moments while the reading is still fresh.

The most effective exit tickets ask one focused question that requires a short written answer. After reading the chapters about David's time at the warehouse, a prompt might ask what David's most important feeling is in this section and which detail shows it. That prompt checks comprehension, requires evidence, and takes under five minutes.
The point of formative assessment is to adjust teaching, so tickets should be reviewed quickly and used the next day. Sorting responses into three piles, such as understood, partly understood, and confused, takes only a few minutes and tells you whether to move forward or reteach. Without that step, the tickets become busywork.
Designing prompts that reveal thinking
Good prompts target a specific skill rather than general recall. One day the focus might be inferring a character's feelings, another day identifying evidence for a claim, and another day explaining why an event matters. Rotating the skill keeps the tickets purposeful and lets you track growth across the unit.
- Ask one clear question per ticket tied to a specific skill
- Require a text detail so answers cannot be pure opinion
- Keep the time limit to five minutes or less
- Review responses quickly and sort them by level of understanding
- Use patterns to decide what to reteach the next day
Stop spending your evenings grading essays
Let AI generate rubric-based feedback instantly, so you can focus on teaching instead.
Try it free in secondsA five-minute check today can save a week of confusion before the final essay.
Grading lightly but usefully
Formative tasks should not be graded like formal essays. A simple check, plus, or minus system, or a comment on a handful of tickets each day, preserves their low-stakes nature while still giving feedback. Students are more willing to take intellectual risks when they know a quick response will not damage their grade.
Returning a few tickets with a brief personal comment each day also builds relationships. Students notice when a teacher engages with their ideas, even in two sentences. Over a unit, that attention encourages stronger participation in class discussions.
Processing short responses efficiently
With four sections of exit tickets each day, even quick reviews add up. AI tools such as GraideMind can scan a batch of short responses, sort them by level of understanding, and highlight common misconceptions, giving the teacher an instant snapshot of where the class stands. This is especially helpful when planning the next day's lesson on short notice.
The summary does not replace reading a sample of responses yourself. Individual tickets sometimes reveal a student's confusion or insight in a way that data cannot capture. Combining a quick automated overview with selective personal reading offers the best of both approaches.
See how fast your grading workflow can be
Most teachers go from hours per batch to minutes.
Create free account


