Your Friday violin teacher may have finished three other teaching days before arriving at your school. Asking them to check a new dashboard every morning changes the job considerably, even if the software itself is easy to use. A useful rollout begins by agreeing when their part of the work will happen and what it will replace.
Build the routine around the teaching week: one clear place for the current task, a protected review moment, and someone available to handle problems between visits. The teacher should be able to explain that routine to a student without promising a response on days they work elsewhere.
Featured photograph: Pavel Danilyuk / Pexels. General lesson image; the school and staff examples below are fictional.
Start with the week staff actually work
Consider a fictional school with piano teachers on Tuesdays, string teachers on Fridays and an office open throughout the week. Its head of music wants a better account of the work between lessons and fewer last-minute requests for recital programmes. Teachers already write lesson notes, send a weekly update to the head and answer occasional requests for the same repertoire information.
The obvious temptation is to add the platform to that list. The more useful first discussion is about duplication. Which part of the weekly email will the head now read in the shared record? Which programme list will staff stop maintaining? What information still belongs in attendance, billing or the school's existing support process?
This is a practical workload question. The 2026 evaluation of England’s Music Hubs reports qualitative accounts of paperwork with short deadlines, differing ways of working between partners and varied contractual arrangements. Those findings describe the organisational context; they do not establish that any practice app reduces workload. The ISM’s 2022 workforce report had already documented concerns about unpaid administration and timetabling. Its date matters: it is historical evidence, not a current statement of an individual teacher's terms.
Ask visiting teachers to walk through a normal day before fixing the new expectations. An apparent gap in a timetable may be travel time, a break or time committed to another school. Agree and resource the work explicitly rather than treating those gaps, or evenings, as available by default.
In our fictional school, the first change is modest. Participating teachers stop sending the separate weekly repertoire-and-concern email. The head reads the current programme and relevant follow-ups instead. Attendance and family appointment messages stay in the existing office system because they serve a different job.
Agree one useful teaching cycle
At the start of a lesson, the teacher looks at the student's current task and any useful practice observation. During the lesson, they hear the playing and decide the next work. At the end, teacher and student make sure the instruction is clear enough to begin at home. A short record supports that exchange; it does not replace listening.
Suppose a student writes that the new shift succeeds slowly but becomes uncertain in the phrase. That gives the teacher a useful starting point. “Practised for 24 minutes” may still be an honest entry, but it leaves the musical question open. Do not make teachers read long reflections from every session merely because the software can store them.
The head's review has a different purpose. They need to find an unresolved concern that needs another colleague, an approaching programme that is incomplete, or a repeated access problem the office should solve. Re-reading every student's diary would turn oversight into a second set of lessons.
Tell families when ordinary records will be read. “Your teacher reviews the practice record around your Friday lesson” is a workable expectation. “Your teacher can see it at any time” describes technical access and leaves the response expectation unresolved.
Where two products remain in use, choose which record is authoritative for each task. Our Practis and My Music Staff comparison follows the consequences of that choice, including the extra work when a programme changes.
An agreement the staff can use
The example below is a completed proposed arrangement for the fictional school. Staff should adapt it together before use. It is an operating agreement about this teaching routine, not an employment contract or a claim that these time allowances suit every school.
Purpose: Keep the next musical task and upcoming programme visible to the student, their teacher and the staff who need to act.
Teacher review: Tuesday staff review around Tuesday lessons; Friday staff around Friday lessons. The school agrees time for this work with each teacher. Daily checking between visits is not part of this arrangement.
What we record: The current piece or passage, the next useful task and any concern requiring a named action. Students can add a brief observation from practice. Existing necessary lesson records continue.
What stops: Participating teachers no longer send the separate weekly repertoire-and-concern email. The head reads those records in the shared workspace. Booking, attendance and billing stay with the office.
Between visits: The office handles access questions during its published hours. A teaching question normally waits for the teacher's agreed review; an issue that cannot wait uses the school's existing contact route.
Cover: The coordinator checks the cover teacher's own account and student access before the lesson. The outgoing teacher identifies the current task and any unfinished action. Staff do not share passwords.
Review of the arrangement: After two teaching visits, each participating teacher brings one useful record and one point of friction. The coordinator checks actual time spent, duplicate work and unresolved access problems, then agrees changes before adding more staff.
Download the editable staff agreement (DOCX). It contains this example and a blank version for your own review days, responsibilities and contact route.
The agreement earns its place when it removes an ambiguity. If the office believes the Friday teacher is monitoring entries on Monday while the teacher expects to read them on Friday, both can follow their own understanding and still leave a student waiting.
Make the time visible before expanding the routine
A proposed allowance helps staff discuss the work, but it is not a measured result. The figures below are deliberately small, explicit examples to test in the fictional school. They assume access is already working and exclude the initial training session, technical problems, actual teaching and substantial student-support conversations.
| Role | Illustrative weekly work | Proposed allowance and replacement |
|---|---|---|
| Visiting teacher with 12 participating students | Read 12 short records; update six changed tasks; clarify three items needing further action. | 12 × 1 minute + 6 × 1 minute + 3 × 2 minutes = 24 minutes. The separate weekly summary email stops. Check the actual net change; its previous writing time is not assumed. |
| Head of music | Review the relevant open items once; discuss one decision with the responsible teacher. | 20 minutes: a proposed 15-minute review and five-minute conversation. This replaces reading the separate weekly summaries, not musical assessment. |
| Office coordinator | Check access/support requests on three agreed office days; make one roster or cover check. | 3 × 5 minutes + 10 minutes = 25 minutes. Some support work is additional. Record it openly rather than calling the rollout a saving. |
A one-minute allowance will not fit every record. If the teacher needs four minutes to understand a student's note, find out why: an unclear task, a navigation problem and a substantial musical question need different responses. Shortening the note might solve the first problem; it would be a poor response to the third.
Ask staff to note the time actually spent during a couple of ordinary teaching visits. Separate reading, entry, troubleshooting and discussion. Include work pushed into another person's day. Reducing the teacher's email time by moving all its contents into the coordinator's spreadsheet is a transfer of work, not a saving for the school.
There is also a cost to interruption. An otherwise short task becomes awkward when a teacher has to sign in between every student while collecting instruments and moving rooms. Try a protected review period or a simpler record before judging the teacher's willingness to use the system.
The first awkward week tells you what to change
On Saturday, a Friday student records that they cannot find the assigned movement in their score. They assume someone will answer in the diary. On Monday, the head notices the entry but assumes the teacher has seen it. By Friday, the student has worked on a different movement.
The problem is not solved by insisting that the teacher check every day. The school first needs to explain what that record is for. In this example, the diary is the place to preserve the practice observation; it is not the school's monitored help desk. For a task they cannot begin, the student should use the established office contact route so someone can arrange clarification.
The head also changes the way the assignment is introduced. At the next lesson, the student points to the actual movement in their own score and explains where to start. That reduces a particular ambiguity without adding a compulsory long reflection to every session.
A different failure might be entirely technical. A teacher can sign in but cannot see the intended student; repeated instructions to refresh the page will not fix a missing roster assignment. The office records who is affected, which account they used and the expected teacher connection, then has an authorised administrator investigate. It should not ask for the teacher's password or request a real pupil's record through a public channel.
For the first supported session with students, use the separate music-school setup workshop. That checks the initial student-to-teacher journey. The staff agreement here covers the weeks after everyone has gone home.
Cover needs access as well as a teaching note
A cover teacher needs the current task, relevant context and the authority to see it. Renaming a follow-up owner is not a substitute for establishing the correct student connection. Test the incoming teacher's own access before the first lesson and review temporary arrangements when the cover ends.
In Practis, our institution workspace scopes teachers to their rostered students. Department heads have read access within their department; administrators have wider institutional access. A head can notice an incomplete programme, but the department-head role is read-only. Arrange for an authorised teacher or administrator to make the necessary change.
Those boundaries should appear in the school's agreement. A coordinator who is expected to repair access needs the appropriate authority or a named administrator who can act. A visiting teacher should know whom to contact when the record is missing, rather than discovering that their only support contact works on a different day.
Follow-ups can help carry an existing teaching concern from one visit to the next, with an owner and a next step. They do not schedule the colleague's work or guarantee that they have read it. Our student follow-up guide shows the actual controls and the separate decisions involved in closing an item.
Give teachers a real part in changing the arrangement
The EEF’s implementation guidance treats implementation as a collaborative process: people help shape what happens, share an understanding of the purpose and approach, then reflect and adapt. For a visiting team, that requires a way to contribute that does not depend on attending a meeting on someone else's teaching day.
After the two visits in our proposed agreement, the coordinator can collect a short response from each teacher: a record that helped, an obstacle and the actual work it required. Discuss the decisions with the affected staff during agreed time. A Friday teacher's report of duplicate entry deserves the same consideration as feedback from the teacher who happens to share an office with the head.
If only enthusiastic staff have tried the routine, find out how it works for someone with a tighter timetable or less reliable room access before expanding. A successful login count cannot answer that. Neither can a large number of student practice entries if teachers have no agreed opportunity to use them.
For a school considering Practis, arrange an institution walkthrough around your teachers’ actual working week. Bring the days staff attend, the task you want to replace and the person who handles problems between visits. The demonstration should show whether that arrangement is workable.
The next useful decision may be to shorten a record, move the review time, resource more support or stop a duplicate request. Make that decision before inviting the next department. Staff should be able to point to what has changed in their week, not just to another account they have been given.
