How Much of a Music Teacher's Job Is Actually Admin (And How to Cut It)
Across education systems, teaching accounts for well under half of a teacher's working time — and private studio teachers carry a whole business on top. Where the hours really go, and a four-bucket method for getting the worst of them back.
Pract.is Editorial
Research-based practice guidance for musicians from the Pract.is editorial team.

Ask a music teacher what they do for a living and they'll say "I teach." The time sheet disagrees. In the OECD's TALIS survey — the largest international study of teachers' working lives — teaching accounts for about 43% of teachers' self-reported working time. Less than half. The rest is the invisible job: planning, marking, messages, records, coordination. And that's for employed teachers, whose school quietly absorbs the payroll, the scheduling, the building, and the billing. A private studio teacher absorbs all of that personally, on top of the invisible half everyone else already carries.
This piece is about naming that honestly and then cutting it — not with productivity mysticism, but with a blunt sorting exercise. Because the real problem isn't that admin exists; some of it is genuinely part of teaching well. The problem is that most teachers treat all of it as one undifferentiated blob of "stuff I have to do," which means the pointless parts survive right alongside the essential ones, year after year, eating the evenings.
The number nobody says out loud
Sit with the TALIS findings for a moment, because they're worth quoting precisely. Teachers across the surveyed systems report an average working week of about 38 hours, of which actual teaching is the single biggest activity — but still a minority of the total. Lesson planning and preparation alone averages around seven hours a week. Narrowly-defined administrative tasks run about 6% of working time on average, climbing past 9% in Japan and near 12% in Korea — and that narrow definition excludes marking, parent communication, and record-keeping, which sit in their own buckets. Add the non-teaching buckets together and the pattern the OECD itself states plainly emerges: in most education systems, teaching does not account for the majority of teachers' total workload.
~43%
of working time is actual teaching (TALIS average)
38 hrs
the average reported working week
~7 hrs
of that week goes to planning and preparation alone
Source: OECD TALIS, teachers' self-reported working time across participating education systems.
Two things follow. First: if you feel like the teaching is the smallest part of your week, you are not disorganised or bad at this — you are describing the documented condition of the entire profession. Second: the school-employed teachers in that survey are the lucky case. Their 57% non-teaching share exists after an institution has swallowed the business layer entirely.
The studio teacher is a school of one
A private teacher runs everything a school runs, alone, in miniature. The scheduling office is you, including every "can we move Thursday?" text and the three-message negotiation that follows. The billing department is you — invoices, chasing the two families who always pay late, the spreadsheet that reconciles it. Marketing, enrolment, the studio policy document, the tax return: you, you, you, you. And then, on top of the business layer, the same pedagogical admin every teacher carries: planning each student's week, writing lesson notes, setting assignments, keeping some record of who is working on what.
The useful way to see it is as a tail attached to every teaching hour. The hour itself is the job you signed up for; hanging off it is a string of small tasks — the note afterwards, the assignment, the rescheduling message, the invoice line, the prep before the next one. None is dramatic alone. Multiplied across twenty-five teaching hours a week, the tail is the second job. Here's a sketch of a typical hour — deliberately illustrative, your proportions will differ — just to make the invisible visible:
The admin tail on one taught hour (a sketch)
A sketch, not a survey — but multiply your own tail by your weekly teaching hours and the second job appears.
"No single task in the tail is dramatic. Multiplied across twenty-five teaching hours, the tail is the second job."
Kill, batch, automate, keep
Now the cut. The mistake is trying to "get more efficient" at the blob as a whole; the fix is sorting every recurring task into one of four buckets and treating each bucket completely differently. Do the sort once, on paper, listing everything you did last week that wasn't teaching — the honest inventory usually takes twenty minutes and is uncomfortable in a useful way.
Kill
Admin that exists for appearances, not outcomes. The elaborate lesson report nobody reads. The over-detailed log you never revisit. If it vanished and nothing in your teaching would change, it's dead weight — stop, without replacement.
Batch
Legitimate work that's expensive only because it arrives in drips. Invoice monthly, not per lesson. Answer parent messages on a stated weekly cadence, not on arrival. Ten interruptions become one sitting.
Automate
Work a machine does better: a booking link instead of scheduling ping-pong, recurring auto-invoices, practice visibility instead of "how did the week go?" messaging. Pay once in setup, save weekly forever.
Keep
The admin that is teaching: the one-line lesson note that feeds next week, the assignment, the monthly personal word to a parent. Protect it — this is judgment work wearing admin's clothes.
To make the sort concrete, here's how it typically lands for a twenty-student studio doing the inventory for the first time. Into kill: the end-of-term written progress report that took a weekend and that, on honest reflection, two parents read; the colour-coded repertoire spreadsheet maintained for nobody. Into batch: invoicing, which moves from twenty per-lesson transactions to one monthly run; parent replies, which move to a Friday half-hour with a stated cadence. Into automate: the scheduling ping-pong (a booking link), the payment chasing (recurring invoices), and the weekly "how did practice go?" reconnaissance (a shared log the students keep). And into keep: the one-line note after each lesson and the assignment it produces — ten seconds each, irreplaceable, the connective tissue of actual teaching. Most teachers who run this exercise find two to three weekly hours sitting in the first three buckets, hiding in plain sight behind the fourth.
The bucket sort matters because the four treatments are opposites. Killing a task you should batch loses real value; batching a task you should kill just makes dead weight more efficient; and — the most common studio mistake — hand-performing tasks that were automatable years ago, out of habit. The sorting question for each item is simple: does this need my judgment, my hands, or nobody's? Judgment → keep (and maybe batch). Hands only → automate. Nobody's → kill.
The hours that come back first
Three tail segments give back the most for the least effort, and they're the same three in almost every studio. Scheduling traffic collapses the day a booking-and-reschedule link replaces the message ping-pong. Payment chasing collapses with recurring invoicing. And the third — the one this blog cares most about — is the information chase: the "did you practise?" interrogation that opens lessons, the status messages to parents, the mental bookkeeping of who's working on what. That whole category is automatable with a shared practice log the students keep and you glance at — the visibility does the reporting, which is precisely the slice our own Practis removes (so weigh the mention accordingly); the scheduling and billing slices belong to other tools, and picking that combination well is its own decision we've mapped in the music teacher software stack.
Two related deep-dives if a specific tail segment is eating you: assigning weekly practice without the admin covers the assignment slice, and keeping parents in the loop without drowning in messages covers the communication slice — both are the same move, replacing recurring per-student effort with visible-by-default structure.
"Sort every task by one question: does it need my judgment, my hands, or nobody's? Keep the first, automate the second, kill the third."
Common questions
Isn't some admin just the price of running a studio?
Yes — and that's exactly why the sort matters. The "keep" bucket is real: notes, assignments, the occasional personal parent message are judgment work that makes the teaching better. The claim isn't that admin should be zero; it's that most studios carry two or three hours a week of killable or automatable tail out of pure habit, and it's hiding behind the legitimate parts.
Do I need to buy software to cut admin?
Not for the first two buckets — killing and batching cost nothing and usually recover the first hour on their own. Automation generally does involve a tool (a booking link, recurring invoices, a practice log), and the honest test is the one we use for any studio purchase: when the weekly hours it saves are worth more than the subscription, it's paying you. Start free, sort first, automate the survivors.
What should I do with the reclaimed hours?
Deliberately, one of two things: teach them (two reclaimed hours is roughly a student slot — real revenue), or live them, unapologetically. What tends to happen instead is that reclaimed time silently refills with new low-value tasks, because unclaimed hours attract clutter. Decide in advance where the recovered time goes, or the tail grows back.
The 43% number shouldn't depress you — it should relieve you, because it says the drowning feeling was never a personal failing, and then it should provoke you, because nearly half of the non-teaching majority doesn't have to exist. Do the twenty-minute inventory this week. Sort ruthlessly into the four buckets. Kill what nobody reads, batch what drips, automate what needs no judgment — and give the hours back to the two things that were ever worth them: the students in front of you, and the life around the studio.
More on teaching.

Tonara Alternatives for Teachers and Studios After the Shutdown
Tonara alternatives for teachers and studios, compared by assignments, practice logs, recordings, messaging, admin tools, pricing, and migration friction.
Pract.is Editorial

What to Charge for Piano Lessons in 2026 (Data + a Calculator Mindset)
Set sustainable piano lesson rates for 2026 using current benchmarks, real workload, collected hours, payment fees, and a practical rate-floor formula.
Pract.is Editorial

How to Start Teaching Piano Online in 2026 (From First Student to Full Studio)
Start teaching piano online with a clear offer, first-student plan, studio policy, lesson workflow, and growth system that stays manageable.
Pract.is Editorial