How Music Teachers Can See What Happened Between Lessons

Tuesday, 4 p.m. A student sits down, plays the assigned piece, and somewhere around bar 12 the teacher starts doing detective work. The opening is cleaner than last week, so something happened. The middle section has the same stumble in the same spot, so whatever happened did not happen there. The new fingering is gone, which means it probably survived about two days. By the end of the run-through the teacher has built a theory of the week from ninety seconds of playing.

Every private teacher knows this routine. It is skilled work - and it is guesswork. The lesson shows the result of the week, never the week itself. This post is about closing that gap: what teachers actually miss, why asking about it does not work, and how to get real visibility into the six days between lessons without turning into the practice police.

A lesson is a thirty-minute window on a seven-day process

Run the numbers on a typical studio student. One lesson a week, thirty to sixty minutes. Then five or six practice sessions at home, alone, unobserved. Over a year, the teacher is present for maybe 25 to 50 hours of a process that spans 150 to 300 hours. Most of music learning happens where no teacher can see it - and the youngest, least experienced practicers get the least supervision at exactly the stage when their practice habits are forming.

What actually happens in those unseen hours is sobering. In a three-year longitudinal study published in Music Education Research, Gary McPherson and James Renwick had seven young beginners videotape their home practice. The footage showed that most practice time went to playing pieces straight through once or twice, that errors were usually ignored rather than fixed, and that many of those ignored errors became permanent. Self-monitoring - the skill the lesson assumes is happening at home - was largely absent.

The teacher in that situation is not failing. The teacher simply cannot coach what they cannot see. The corrections happen on Tuesday; the errors get rehearsed Wednesday through Monday.

Why "how did practice go?" tells you almost nothing

The traditional fix is to ask. Every lesson opens with some version of "how was your week?" - and the answer is nearly useless, for reasons that have little to do with honesty.

First, memory compresses. A week of practice collapses into a general feeling: it went fine, it was hard, I didn't get to it much. The student is not lying; they genuinely cannot reconstruct which days they practiced, what they worked on first, or where the time actually went. Research keeps finding daylight between what musicians report and what they observably do. When Peter Miksza compared self-reported practice habits with videotaped practice behavior in sixty high school wind players, the relationships between what players said they did and what the tape showed were mostly small. Self-report is a blurry instrument even for motivated, experienced students.

Second, the question carries social weight. The student knows "how did practice go?" is partly an audit, so the answer gets shaded toward what the teacher wants to hear. A vague "pretty good" is the safest possible move. The teacher then probes, the student gets defensive, and five minutes of lesson time disappear into reconstruction that still ends in a guess.

"The student is not hiding the week from you. The week is hidden from the student too - memory compresses seven days into a feeling."

Asking better questions helps - we covered lesson-opening questions in our post on getting students to practice more without nagging - but even the best question cannot recover information that no longer exists in anyone's memory. The week has to be captured while it happens, not reconstructed afterwards.

Flying blind quietly changes how you teach

The visibility gap does not just cost information. It bends the whole shape of the lesson toward the only thing the teacher can see: the playing happening right now.

A 2025 review in Frontiers in Psychology by dos Santos Silva, Blackwell, McPherson, and Boruchovitch looked at how teacher feedback is actually distributed in instrumental lessons, drawing on coded video of university-level lessons taught by renowned teachers. The breakdown is striking: about 85% of feedback addressed the task the student had just played, 9% addressed the process - strategies for how to improve the next attempt - and under 6% addressed self-regulation, the skills students need to monitor their own practice. Feedback aimed at future learning ("feed forward") made up only about 16% of the total.

That distribution is exactly what you would expect from teachers who cannot see the week. When the only evidence in the room is the run-through, feedback naturally attaches to the run-through. The teacher fixes what they hear, the student writes down corrections, and the part of the system that decides everything - what the student will actually do on Thursday afternoon - stays uncoached. As McPherson, Blackwell, and Hattie argue in their framework for feedback in music performance teaching, the feedback that builds independent musicians is the kind aimed at process and self-monitoring - precisely the kind that needs information about how the student practices, not just how they played.

There is a repetition cost too. Without a record of the week, every lesson starts from the same blank page, and recurring problems take weeks to recognize as recurring. A student who consistently practices only on the two days after the lesson looks, in the lesson itself, identical to a student who practices six days and plateaus. The two need completely different help.

The four signals worth reading

Seeing the week does not mean seeing everything. Full session recordings, minute-by-minute timers, and exhaustive journals collapse under their own weight - the student stops logging, and the teacher stops reading. What a teacher actually needs fits into four signals, each answering one diagnostic question.

Frequency and spacing. Not total minutes - distribution. Did practice happen on two days or five? Front-loaded after the lesson, crammed the night before, or spread across the week? Spacing predicts retention, and it is the single clearest explanation for the "great on Wednesday, gone by Tuesday" pattern. A student logging four short, spread-out sessions is in better shape than one logging a single ninety-minute session, even though the minutes say otherwise.

What got practiced - and what got avoided. The assignment list and the practice list are rarely the same list. Students drift toward what already sounds good. If the étude got five sessions and the assigned rhythm spot got zero, that avoidance is the most important fact about the week, and it is invisible in a run-through that simply confirms the rhythm spot still is not fixed.

Where it broke down. One sentence per session is enough: "bar 24 still uneven at 60," "hands together fell apart in the B section." These are the notes that turn the next lesson from an audit into a continuation. Our post on what students should write down after practice goes into the note-taking side in detail.

What the student noticed. The reflection layer: what felt easier, what they think is wrong, what they want help with. This is where a teacher can finally coach self-monitoring - the skill the McPherson and Renwick footage showed beginners almost never develop alone. A student who writes "I think my thumb is the problem" has handed the teacher a process-level conversation that no run-through would have produced.

Visibility without surveillance

The fastest way to kill a practice-logging habit is to make it feel like monitoring. Students - teenagers especially - can smell surveillance, and adult learners resent it even faster. The relationship research backs the instinct: when Andrea Creech and Susan Hallam surveyed 337 violin students in Psychology of Music, the quality of pupil-teacher rapport accounted for significant variability in motivation, self-esteem, enjoyment, and attainment. A logging system that damages rapport costs more than it returns, no matter how good the data is.

The difference between surveillance and a shared record is mostly framing, and the framing is in the teacher's hands. Three rules keep it on the right side of the line.

The record serves the student's next session first. A note like "bar 24 uneven at 60" is something the student writes for their own Thursday self, not a compliance report for the teacher. If the log helps the student restart faster, it survives; if it is homework about homework, it dies in two weeks.

The teacher reads patterns, not minutes. Never open with "you only practiced three days." Open with what the evidence makes possible: "I saw the B section kept collapsing at the same spot - let's start there." Evidence that gets used to teach gets logged again next week. Evidence that gets used to judge stops arriving.

Keep the capture lighter than the practice. Thirty seconds after each session: what was worked on, one sentence about where it broke. Maybe a tempo number, occasionally a short clip of one assigned passage. Paper journals can do this - though they tend to fail for predictable reasons, and they stay home on lesson day. This is the problem practice-tracking apps actually solve: the log is captured at the instrument and visible to the teacher before the lesson starts. Our guide to practice tracking for teachers covers what to look for in that kind of tool.

"Evidence that gets used to teach gets logged again next week. Evidence that gets used to judge stops arriving."

What changes when you can see the week

The first change is the opening of the lesson. Two minutes of reading the week before the student arrives replaces five minutes of interrogation after they sit down. The lesson starts at the actual problem - "let's look at the spot that kept breaking on Thursday" - and the student walks in feeling seen rather than audited. That single shift does more for rapport than most studio policies.

The second change is slower and bigger: feedback starts moving down the stack. When the teacher can see how the student practices, process-level coaching becomes possible - "you played it through five times; next week, stop at the first error and fix it before continuing" is advice that can only be given with evidence of the five play-throughs. Over months, that is how students stop needing the teacher to find their problems for them.

The third change is pattern recognition across weeks. Three weeks of logs reveal what no single lesson can: the student who always skips the day before the lesson, the piece that has been "almost ready" for a month, the warm-up that quietly disappeared. Teachers who spot these patterns early fix them cheaply.

The weekly lesson was never designed to be the whole of music teaching - it is the steering wheel, and the week is the road. A teacher who can see even a rough sketch of those six days stops steering from memory. Start smaller than feels useful: one student, one week, one sentence per session, and read it before they walk in. The first lesson that opens with "I saw what happened with bar 24 - let's fix it" will make the case better than any system ever could.