Transcript T4 · Structure intact, feedback generic

Mixed session · Tutor: Marcus (community member, week 10) · Students: Priya, Camila, Andre (Grade 8) · Skill: solving ax + b = c; misconception in play: equals sign as “the answer comes next” (M5)

Fictional transcript, constructed for training purposes. All names and exchanges are invented; no real children are depicted. Numbered annotations follow each exchange — format.

[0:00]

Marcus: Priya, Camila, Andre — sit, sit. Warm-up’s up: 2x + 6 = 14 and a stretch problem if you’re fast. Four minutes, like always.

[1] S1 (routine running: warm-up launched at minute zero — the habit T3 lacked). But notice what’s missing: no names-with-reference, no connection to yesterday’s ticket. The structure is in place; the relationship and data layers are running on autopilot.

[0:05] Review

Marcus: Yesterday’s ticket — most of you got the last one, good. The one people missed was the = 7 one. Answer was 2. Any questions on that? No? Moving on.

[2] D1/S1 (the review block exists and uses ticket data — but see [3]: it delivers answers, not diagnosis). “Most of you got it” is an average doing an individual’s job.

Andre: Yeah, I didn’t get that one. I had x + 4 = 7 and put 7 after the x.

Marcus: Okay, noted — we’ll hit that later.

[3] Missed moment: Andre has just handed the tutor a written confession of the M5 misconception (equals sign as “answer comes next”: he reads x + 4 = 7 left-to-right and treats = as “here comes the answer slot”). The strong move is a probing question now: “When you wrote 7 after the x, what were you saying the whole line meant?” Marcus defers it to “later” — and “later” never arrives.

[0:08] Guided practice

Marcus: Board: 3x + 5 = 20. Priya, take us.

Priya: Subtract 5 both sides: 3x = 15. Divide by 3: x = 5.

Marcus: Good job! Camila, next one: 4x − 2 = 18.

Camila: Add 2 both sides: 4x = 20… divide: x = 5!

Marcus: Nice work!

[4] F1 (the session’s core weakness, visible in two lines: “Good job!” and “Nice work!” — praise with zero content, interchangeable between students and problems). Neither student hears what she did right (subtract 5 from both sides kept the balance / moved the constant before the coefficient). The rubric’s Domain 4 anchor for level 2 is nearly verbatim this: “praise is generic; the student could not say what to repeat.”

Andre: Can I go? 6x = 24 — that’s just x = 4.

Marcus: Good job, Andre.

[5] R4 pressure building: Andre is quick and starts collecting the room’s praise. Watch [8] — nothing here redirects him into the work (the strong move is a “prove it” challenge), so his speed becomes the session’s currency.

[0:16] Guided practice, continued

Marcus: Harder one: 5x − 3 = 2x + 9. Priya?

Priya: I got x = 4.

Marcus: (beat) How’d you get there?

Priya: I… subtracted the 2x and added the 3? It came out to x = 4.

Marcus: (two seconds, then) It’s actually x = 4? Let me see — okay: 5x − 2x = 3x, and 9 + 3 = 12, so 3x = 12, x = 4. Yes, you’re right!

[6] Mixed moment #1: the tutor re-derives the solution at the board, filling the pause — wait time [Q4] never happens; the student’s vague “it came out to” stays vague. The fix landed correctly in math (Priya’s answer was right) but the why is now the tutor’s, not hers. The level-4 version: three seconds of silence, then “Walk me through the subtract-2x step — what did the right side become?”

Camila: Wait, how did the 3 get to the other side? I got x = 2.

Marcus: Camila, you subtract… hold on. Priya, help her out?

Priya: You move the −3 over and it becomes plus 3, so…

[7] Mixed moment #2: peer tutoring offered instead of a probing question — and Priya explains with the memorized “move it over and flip” procedure, the exact surface rule that produces M1/M2 errors later. The strong move: “Camila, when you moved the −3, what operation did you perform on both sides?” Marcus defers to the quick student instead of the hint ladder — faster, and it teaches less.

[0:25] Independent try + exit ticket

Marcus: Solo problem, three minutes: 7x + 2 = 23. Then ticket’s on the table — same skill, don’t rush.

(Tickets given, collected.)

Marcus: Andre, since you’re quick — start the stretch problems. Priya, Camila, same time tomorrow.

[8] S3 + D1 (the ticket happens — full credit on the loop’s mechanics) + R4 (Andre’s speed gets more work, not a role in the room). Note the contrast with T3: Marcus keeps the data habit and loses the thinking; T3 kept the thinking and lost the habit. Add the two and you get T1 — which is exactly how the rubric is built: five separate domains, not one “good/bad” grade.

What to notice in T4

Domain 2 is solid — blocks run on time, review happens from ticket data, exit ticket given and collected [1][2][8].
Domain 4 fails quietly: generic praise [4], a why-question never asked, the tutor re-deriving at [6]. Nobody in the room can say what they did right.
The M5 misconception walked in the door at [3] and was never picked up — Andre’s “I put 7 after the x” is a textbook equals-sign-as-answer-slot disclosure, and the session was too busy to notice. The exit-ticket bank tags M5 items precisely so this doesn’t depend on the tutor catching it live.
Andre is quick, engaged — and being shaped into “the fast one” [5][8] rather than given real responsibility (“prove it to the group”).

Rubric read

Observation rubric: Domain 1 = 2 (names, but no references to recorded work) · Domain 2 = 4 · Domain 3 = 2 (no probing questions on errors; tutor re-derives at [6]) · Domain 4 = 2 (generic praise throughout; no confirm-and-ask-why) · Domain 5 = 2 (ticket given and collected, but the results never shaped a decision — the review delivered an answer, not a diagnosis [2], and nothing in the next plan traces to the results; the level-3 anchor needs “a data-informed choice”). T4 is the calibration anchor for Domain 4, level 2.

Related: T3 — questioning strong, loop broken (T4’s mirror image) · T6 — the tutor answers for everyone.