When a Music Teacher Leaves: A Student Handover Template
A music-teacher handover template for current pieces, lesson goals, performances and family contact, with a separate staff-access checklist.
Mia
Community & Content. Writer and lifelong pianist. Writes about gear, production, and the business side of making music.

A teacher’s final lesson can leave a surprising amount unfinished: a recital choice, a changed fingering, a parent expecting a reply, or a piece whose title in the school database is simply “Sonatina.” The next teacher needs enough context to begin sensibly. They also need their own authorised access to the records.
Prepare a short, current handover for each student, then have the receiving teacher confirm it is usable. Give a named administrator responsibility for accounts, permissions and unfinished office tasks. Passing on lesson notes does not complete that second job.
What you need: recent lesson notes, the actual scores, upcoming dates and an approved place to store the packet. The template works on paper or in your existing document system; no new app, subscription or particular software version is required.
Name the person who will finish the handover
Set the outgoing teacher’s last lesson, the incoming teacher’s first lesson and a deadline for checking the packet. Where there is a gap, identify who answers student questions and confirms the next appointment. A proposed teacher or time should stay labelled as proposed until the school and family have agreed it.
The MTNA Code of Ethics encourages communication during a change of teachers while respecting student and family privacy. It also recognises the student’s choice of teacher. A school’s administrative plan should therefore include the learner and family, rather than treating them as records to move between lists.
Use two parallel tracks so one does not conceal an unfinished task in the other:
Teaching continuity
- Outgoing teacherWrites the current musical picture.
- Incoming teacherOpens the scores and resolves questions.
- Student and teacherAgree the next task at the first lesson.
Account responsibility
- School administratorLists records, permissions and deadlines.
- Authorised staffSet up and check the new access.
- School administratorEnds unneeded access on the agreed date.
For an unexpected departure, the school may have to assemble the packet from existing records and the student’s own account of recent work. Mark unverified details as questions. Do not invent a previous teacher’s intentions to fill an empty field.
A handover packet the new teacher can use
Keep the current summary short and link to the supporting history. Our lesson-notes template helps with the underlying record; the handover adds the changeover dates, unresolved decisions and person responsible for each next action.
The following case is fictional. Its observations and dates demonstrate the level of detail, not a prescribed plan for a real student. The Burgmüller edition is real: IMSLP’s edition record identifies the Oesterle-edited Schirmer volume.
Fictional worked example · version 1
Maya · piano · prepared 20 September 2026
Outgoing: Lena · incoming: Arun · school contact: office administrator
- Changeover
- Last lesson with Lena: 25 September. First agreed lesson with Arun: 2 October, 16:00. Office confirms the room and sends the family reminder.
- Current music
- Burgmüller, Op. 100 No. 2, Arabesque. G. Schirmer, Library Vol. 500, edited by Louis Oesterle, 1903, plate 14104. Maya brings her marked copy. Also preparing an eight-bar original melody called Rain at the Window, invented for this example.
- Latest observation
- At the 18 September lesson, Maya played the opening eight bars of Arabesque with separate hands at quarter note = 60. Joining hands caused two pauses.
- Agreed next task
- Join the first four bars without stopping at a comfortable pulse. Keep the chosen fingering visible in the score. Arun listens before setting a new tempo target.
- Student priorities
- Maya wants to finish her own melody and include it in a studio sharing session. She prefers to hear a short demonstration before trying a new rhythmic pattern.
- Upcoming event
- School sharing session: 24 October. Arabesque is a possible choice, not yet confirmed. Arun and Maya decide by 9 October; the office needs the final title that day. No exam entry is pending.
- Materials and history
- Marked score with the student; recent lesson summaries in the school-approved record. No recording to transfer.
- Contact and open question
- Office handles scheduling; Arun handles musical questions through the agreed school channel. Confirm whether Maya can bring her composition notebook to the first lesson. Contact details remain in the authorised directory.
“Latest observation” is more helpful than a label such as “weak reader” or “unmotivated.” State what happened, when it happened and what helped. Leave the new teacher room to assess the student afresh. If the learner has an agreed access arrangement, pass the practical teaching adjustment through the appropriate school process; keep sensitive background information out of a general handover sheet.
For each active piece, identify the composer, work, movement and edition or arrangement. Record which passages are current, which fingerings have been agreed and whether a performance or exam commitment is confirmed. “Grade 3 piece” alone will not identify the music or its present state.
Copy the blank version below into your own approved document. Add one music row per active piece, and remove fields that genuinely do not apply:
Open the copyable student-handover template
Student / instrument / summary date / version: ______
Outgoing teacher / incoming teacher / school contact: ______
Last lesson / confirmed first lesson / cover during any gap: ______
Current work / movement / edition / score location: ______
Most recent dated observation / current passage: ______
Agreed practice task / useful teaching approach: ______
Student’s own goal or question: ______
Confirmed event or exam / pending decision / deadline / owner: ______
Authorised supporting records / practical access arrangements: ______
Family communication owner / next message / date: ______
Questions checked by incoming teacher / date: ______
Run the staff-access checklist separately
The UK National Cyber Security Centre’s access guidance calls for a joiners, movers and leavers process, including removal of access that is no longer needed. For a music school, the list may include teaching software, shared score folders, calendars, messaging, meeting links and school-owned devices.
Have the authorised administrator work through this checklist. The school still decides its own retention, privacy and contractual requirements; our practice-data privacy post outlines the wider issues to discuss with its responsible lead.
- Identify the owner of each record. Separate school records from a teacher’s personal materials and students’ own accounts. Confirm what can be shared and with whom before making copies.
- Give the successor their own account. Use the appropriate role and student connections. Do not hand over the departing teacher’s password or keep everyone using the same login.
- Check access from the successor’s account. They should be able to open the relevant student, current score and permitted history. A name appearing on a roster is not enough. Avoid granting a wider class list than the role requires.
- Resolve outstanding work. List assignments, upcoming lessons, room bookings, family messages and recital decisions. Give each an owner; copying a note does not necessarily change ownership inside the software.
- Schedule the access cut-off. Remove access that is no longer authorised at the agreed time. Review direct sharing links and other services as well as the main teaching system. An urgent security or safeguarding concern follows the school’s escalation process immediately.
- Record completion and retention decisions. Keep the needed school history in its approved location, resolve any school-device return, and follow policy for retained or removed copies. Do not delete the only usable record simply to empty an account.
In Practis, roster assignment and account access are separate. Institution administrators can assign a student’s primary teacher. Reassignment does not automatically transfer ownership of every historic assignment or lesson, and separately established private teacher connections need their own review. Verify the incoming teacher’s access and unfinished tasks before treating the changeover as complete.
If your school is organising this across several studios, Practis for institutions is the relevant place to discuss roster and practice visibility. The shared-tracking setup walkthrough covers the initial connection check. Neither replaces the school’s decisions about who may retain or see a record.
Use the first lesson to confirm, then move forward
Begin with something the student already knows and ask what they were working towards. Listen to one passage from the packet. If the observation no longer fits, update it with what happened today instead of treating the handover as a fixed assessment.
Keep a successful fingering or practice approach while you work out whether a change is needed. A new teacher can introduce different ideas without making the first meeting a verdict on the previous teacher’s work. The student should leave knowing what to practise and when the next lesson takes place.
After the lesson, the incoming teacher records the agreed task and closes any musical questions in the packet. The administrator confirms that the scheduled access and contact changes are complete.
Further reading
TeachingMusic Lesson Notes Template: What Teachers Should Track After Each Lesson
A 60-second lesson note, done right, makes the next lesson start informed and writes your parent updates for you. Here is the template — and what to leave out.
10 min read
TeachingShared Practice Tracking for Music Schools: The First Afternoon
Set up shared practice tracking for a music school with a two-hour workshop: connect teachers and students, test one record, and agree the weekly handoff.
10 min read
InstitutionsPractice Data & Student Privacy: What Music Institutions Must Know (GDPR/FERPA)
Music programs collect more student data than ever — logs, recordings, progress — usually through third-party tools. Who is legally responsible for protecting it? You are. A plain-English guide to FERPA, GDPR, and practice-data governance.
12 min read