Transcript T3 · Questioning strong, data loop broken

Mixed session · Tutor: Diego (college sophomore, week 4) · Students: Jayla, Omar, Sofia (Grade 7) · Skill: two-step equations; misconceptions in play: applying an operation to only one side (M1) + a check run against the wrong equation (Jayla’s arithmetic is correct — she tests the wrong equation)

Fictional transcript, constructed for training purposes. Invented tutor and students; not a recording of real children. Numbered annotations follow each exchange — format.

[0:00]

Diego: Hey — Jayla, Omar, Sofia. Sofia, yesterday you nailed the check-back step; we’re building on that. Jayla, I owe you a rematch on the puzzle from Tuesday. Omar — good to see you, man.

[1] R1 + R2 (strong open: every student named; two specific references). Diego’s relationships work is genuinely good — worth saying, because weak sessions are usually weak somewhere specific, not everywhere.

[0:03] Warm-up — and where the session starts drifting

Diego: Warm-up: 6x − 9 = 3x on the board. Go.

(Students work. At 0:08, Omar is still on his first step.)

[2] S1 (weakness #1: warm-up has no review block — the previous exit ticket’s common error is never surfaced to the group; no timer, so drift sets in). The block still has a purpose (reactivate), but nothing ties it to recorded data (D3). The review block silently vanishes.

[0:10] Guided practice

Diego: Main event: 5x + 7 = 2x + 19. Sofia, talk to me — what’s your move?

Sofia: Get the x’s together? Subtract 2x from both sides: 3x + 7 = 19.

Diego: Clean. Why 2x and not the 7 first?

Sofia: Either works, but x’s first means smaller numbers later.

[3] Q1 + F3 (probing question; “why” asked after a correct step). Diego’s questioning here is genuinely strong — he asks for reasoning, not just answers.

Jayla: I did 3x = 19 − 7… so 3x = 12… (counts on fingers) x = 4.

Diego: (three seconds — real wait time) And check it?

Jayla: 3(4) + 7 = 19. And 2(4) + 19 = 27… that’s not equal?

[4] Q4 (wait time — good) but then the stumble: Jayla’s check reveals the error, and the next move decides the session’s quality. Watch what Diego does with it.

Diego: Right, so where’s the mismatch — left side or right?

Jayla: The right side. I moved the 19 over but… oh. I subtracted 2x on the left but not the right?

Diego: There it is. What does the equals sign promise?

Jayla: Both sides stay equal. So I needed 2x gone from both: 3x + 7 = 19 − … no — right side becomes just 19? No wait, minus nothing…

[5] Q3 (excellent error handling: the probing question exposes where the error lives — Jayla applied the operation to one side only, the canonical M1 pattern per the misconception bank). But see annotation [6]: the repair is now oscillating, and Diego is about to do the thing this program trains against — not yet, though. He almost holds.

Diego: Slow down. You had 2x + 19. Subtracting 2x from the right side leaves…?

Jayla: …19. Just 19.

Diego: And the left side?

Jayla: 3x + 7. So 3x + 7 = 19. Then x = 4 — again? But the check said no!

[6] The confusable moment: two errors stacked (the M1 one-side subtraction, and a check run against the wrong equation — Jayla’s arithmetic itself is correct both times; the mistake is which equation she is checking: left side from the modified 3x + 7 = 19, right side from the original 2x + 19). Diego handles the first well. The second — the check’s basis — he’s about to start computing for her. Watch [7].

Diego: Recompute the check with x = 4: left is 3(4) + 7 = 19. Right is 2(4) + 19…

Jayla: 27.

Diego: So x = 4 fails the check. What does that tell you?

Jayla: …my solve was wrong somewhere?

[7] Mixed moment #1: the tutor does the arithmetic for the student (“left is 3(4)+7=19”) instead of asking her to compute it. Small, and it keeps the thinking alive — but it’s the exact “answering for the student” habit T6 will take to its extreme. The stronger move: “Compute both sides with x = 4 — what do you get?”

Diego: Somewhere in the move. One more look at 5x + 7 = 2x + 19: subtract 2x from both sides gives you…?

Jayla: 3x + 7 = 19. That’s what I had!

Diego: It is. So the solve was right — where else could the check have gone wrong?

Jayla: (pause) …2 times 4 is 8, plus 19… wait, the ORIGINAL right side is 2x + 19. But I wrote the answer for x on my check wrong. I checked 2x + 19 where x was 4… oh no, 8 + 19 is 27, that IS the right side after I moved stuff. The original equation is 5x + 7 = 2x + 19 — 27 = 27!

Diego: There it is — your solve was right; your check mixed up which equation it was testing. That’s why the check exists.

[8] F1 (when it lands, it’s specific and correct: names exactly what was and wasn’t wrong — the solve stood, the check was misapplied), with one honest caveat: Diego’s own recomputation at [7] continued the mixed-equation framing. “Left is 3(4) + 7 = 19” is the modified equation’s left side; “right is 2(4) + 19…” is the original equation’s right side — the same hybrid Jayla started with, now spoken by the tutor. The rescue works because Jayla finally redoes it against the original (27 = 27), not because the modeling was clean. The level-4 version: “Check the original equation — substitute x = 4 into 5x + 7 and into 2x + 19. What do you get?” Credit where due: Jayla did the arithmetic herself on the recovery. Score Domain 3 at 4 here — and see [10] for what follows.

[0:22] Independent try — cut short

Diego: One solo problem: 4x + 3 = x + 12. Three minutes.

(At 0:26, Omar finishes; Diego starts walking through the solution at the board “since we have two minutes.”)

[9] Mixed moment #2: the independent try exists but is foreshortened, and the “walk-through at the board” restores the tutor as the producer of steps — undoing, at the end of the session, exactly the discipline the middle built. Not fatal (Omar had finished; Jayla rechecks her work) — but the block’s purpose (prove transfer without you) is compromised.

[0:29] — and then the bell

Diego: That’s time — great session, everyone. Tickets tomorrow, I promise, we’re out of minutes. Omar, stick around for one sec?

[10] The session’s real failure: **no exit ticket (S3, D1 broken).** “Tomorrow, I promise” is how the data loop dies politely — and the measurement plan tracks exactly this: sessions-with-exit-ticket is a headline fidelity metric, target ≥90%. Without the ticket, Diego can’t choose Thursday’s review from data (D3) and can’t catch a student stuck two sessions running (D4). One skipped block, four downstream failures.

What to notice in T3

Domain 3 is excellent — probing questions, wait time [4], error exposed not corrected [5], the rescue at [8]. If the observation stopped at questioning, this session would look like a 4.
Domain 2 and Domain 5 fail quietly: no review block [2], a compressed independent try [9], no exit ticket [10].
This is the coaching conversation T3 is built for: the rubric’s per-domain scoring separates the compliment from the fix, so the debrief leads with the strength (questioning) and lands on one focus (the ticket), not a lecture. See the coaching conversation guide.

Rubric read

Observation rubric: Domain 1 = 3 (all three greeted by name; Sofia and Jayla get specific references — Omar’s is only “good to see you,” so the level-4 “each student’s recorded work” anchor isn’t met) · Domain 2 = 1 (no review block; independent try compromised; no exit ticket — the rubric states this alone caps the domain at 1) · Domain 3 = 4 · Domain 4 = 3 (specific when it landed [8]; one instance of computing for the student [7]) · Domain 5 = 1 (no ticket given, collected, or recorded). T3 is a calibration anchor for split scoring — sessions are not overall “good” or “bad,” and the rubric should say so per domain.

Related: T4 — structure intact, feedback generic (the mirror image: T3 teaches well and measures nothing; T4 measures everything and teaches generically) · T1 — both halves working.