Module 5 · Using exit tickets and data
About 25 minutes · Competency domain: Data use · competency model
Objectives
By the end of this module you can:
- Run the full data loop every session: exit ticket given and collected (D1) → results recorded same day in the progress tracker (D2) → next session’s plan chosen from the results (D3) → stuck students escalated after two consecutive below-mastery tickets (D4).
- Keep the data privacy-safe: initials only, no grades that identify students beyond the group, no photos of student work, storage per your school’s agreement (measurement plan §privacy).
Scenario hook: the folder nobody read
Marcus collects exit tickets religiously — into a folder. At month’s end, the folder holds 360 tickets and zero decisions. Meanwhile his student Aisha has missed the same sign-move on six straight tickets, which nobody noticed because “the group average looked fine.”
Averages hide individuals — that was one of the State of Tutoring 2026 analysis’s sharpest findings: 91% of the variation in weekly minutes was among students in the same program, invisible in program averages. The same is true of exit tickets: the group’s “82% correct” is made of individual students at 100 and 40.
Key idea: the loop, not the collection
The exit ticket has one job: to change your next session plan. A ticket that doesn’t alter a plan is busywork. Four steps, ~4 minutes of your time per session:
- Give it — one to two items from the exit-ticket bank, tagged to this week’s skill and misconception. Last 3 minutes, every session, no exceptions.
- Record it same-day — initials, skill tag, mastery 1–4 (tracker template). Same-day matters: memory decays; the tracker is the program’s memory.
- Read it for the plan — the review block of your next session comes from the most common error; guided practice targets the skill behind it. Write the connection on the session plan (“review: M1 one-side subtraction — from Tuesday’s tickets”).
- Escalate the stuck — a student below mastery on the same skill tag for two consecutive tickets goes to your site coordinator (that’s the coaching cycle’s trigger), with the tagged tickets attached. Waiting for the next observation wastes two weeks of the student’s dosage.
Model: the loop T5 never ran
First, the failure — verbatim from Transcript T5 (fictional, constructed for training), the end of the session (annotation 7):
Nadia: Oh no, we’re out of time — the exit ticket! We’ll do it Thursday, I promise, we just ran over because the examples took longer than I thought. Same time Thursday — you guys were great today.
What it costs: nothing in that session produced data. Nadia can’t choose Thursday’s review from results, can’t catch a student stuck two sessions running, and her coordinator sees no gap — the loop never closed, so there is nothing to read.
Then the loop working. The 90-second same-day check-in that T5’s session never had — a constructed example (not from a transcript; students shown by initials, as the tracker records them):
Tutor: Tuesday’s tickets: A.O. 3 on distribute, 2 on signs. J.M. 3 and 3. L.R. 1 on signs — again. Second time on that tag.
Coordinator: So Thursday?
Tutor: Review the balance idea for the whole group — J.M. can explain it, that’s a real job. A.O. goes first in guided practice on signs. And I’m flagging L.R.: two ones in a row, same tag. I want a second pair of eyes on whether it’s the sign itself or the moving-terms idea underneath.
What to notice: three different decisions from one ticket round (review topic, sequencing, escalation) — and the tutor distinguishes the symptom (sign) from the concept (balance). That distinction is what the misconception tags are for.
Practice with feedback
Your turn: You get these four tickets back (skill tags: SOLVE = two-step solve, DIST = distribute, SIGN = sign when moving, BAL = balance meaning):
| Student | SOLVE | SIGN | DIST | BAL |
|---|---|---|---|---|
| A.O. | 3 | 1 | 4 | 2 |
| J.M. | 3 | 3 | 3 | 3 |
| L.R. | 2 | 1 | 2 | 1 |
| D.K. | 4 | 4 | 3 | 3 |
Write: (a) your review block topic, (b) your guided-practice target, (c) who you escalate, (d) one thing you still don’t know from these numbers.
(a) Review: the balance idea / sign-when-moving — the group’s weakest shared concept (SIGN: 1, 3, 1, 4). (b) Guided practice: distribute with negatives, bracketed by A.O. and L.R.’s 2s, while D.K. gets a similar-but-harder offer. (c) Escalate: A.O. and L.R. — both have SIGN = 1 with the concept tag (BAL) low too; two consecutive (per the scenario’s history) or one ticket + concept gap both justify the flag. (d) What you don’t know: why — a 1 says the skill failed, not which misconception drove it. That’s what the probing question is for: the ticket tells you where to dig, not what you’ll find.
In your next session, try…
- Put the chosen exit ticket into the plan before the session — tickets chosen after the fact drift toward “whatever we did.”
- Record initials + tags the same day, at the site, before you leave.
- Bring one escalation (or an explicit “no escalations this week”) to your coordinator check-in.
Reflection
In the tutor self-reflection form: What did this week’s tickets change in my plan? If nothing — why was I collecting them?
Check yourself
- Your group’s average is 85% but one student is at 40%. Whose problem is the average hiding? (Exactly the student the loop exists for — the 91%-within-programs finding, at ticket scale.)
- The coordinator asks for data. What do you share? (Initials-only tracker rows and tagged tickets per the school’s data agreement — never student names in email, never photos of graded work.)
- Ticket says Luis failed SIGN twice. Do you reteach signs? (Dig first: his BAL tag is also low — the “moving terms” error may be a balance misunderstanding wearing a sign costume. Probing question before plan.)