You were hired to run the academic side of a school — teaching standards, level placement, teacher development, the quality of what actually happens in the room. Then the enrolment peak arrives and you spend three weeks moving names between spreadsheets.
The Director of Studies admin workload is rarely one big task. It is forty small ones, each defensible on its own, which together eat the part of the week the role was created for.
This post breaks down where those hours go and what to do about each one. Some of it is a software problem. A lot of it is a workflow problem no software will fix, and it is worth being honest about which is which before you go shopping for a system. By the end you should be able to name the three or four tasks worth attacking first — and the ones to stop doing entirely.
Where the week actually goes
Ask a Director of Studies what they did last week and the answer sounds nothing like the job description.
Monday, a student who enrolled on Friday turns up. Admissions has her in the enrolment sheet. She is not on the class list, not in the register, and the teacher emails you at 9:20 to ask who she is. You add her to the levels spreadsheet, email the teacher, message accounts so the invoice goes out, and then move two students because that class is now over capacity. At 11:00 a parent rings about a payment you cannot see from where you are sitting, so you forward the call.
None of that is difficult. That is precisely the trap. Every one of these tasks is small enough that it never gets escalated and easy enough that it always lands on the person who can do it fastest — which is you, because you are the only one who knows where everything lives.
The result is a role that looks academic on the org chart and clerical in the calendar. Nobody decided that. It accumulated.
The four tasks that actually consume the week
1. The same student, entered three times
This is the big one, and it is worth naming precisely: admissions holds one version of the student, academic records holds a second, and finance holds a third. Each one lives in a different sheet or a different tool, and the person who keeps the three of them in agreement is you.
The real cost is not the typing. It is the divergence. A student moves from B1 to B2 on Tuesday. The register is updated, the level spreadsheet is updated, but finance is still billing the old programme and the attendance sheet still has her in the old group. Two weeks later somebody notices, and now you are not doing data entry — you are doing forensics.
The process half. Decide, explicitly, which record is the source of truth for each fact: who owns enrolment status, who owns level, who owns the fee. Even on spreadsheets this helps, because most re-entry errors come from two people editing two copies with equal confidence.
The system half. In a platform built for education, an enrolment creates the student record, the class placement and the finance charge in a single action, because they are the same event. That is what an online admission process is for, and it is the reason payments and family statements belong in the same system as the academic record rather than in a parallel accounting file. No amount of process discipline gets you there if the three systems physically cannot see each other.
2. The timetable that never stops moving
In a language academy the timetable is not a document, it is a live object. Weekly starts, rolling intakes, level moves mid-course, a teacher out sick on Thursday, a group that suddenly has fourteen students in a room built for ten. In a K-12 school the churn is different but the effect is the same: cover, room clashes, a group split late in the term.
The process half. Batch the changes. Most level moves are not urgent; they only feel urgent because they arrive one at a time. Set a fixed day when moves take effect and hold to it, and you convert a stream of interruptions into one scheduled task. Do the same for teacher-hour queries.
The system half. Timetabling pain multiplies when class lists, teacher allocation and room capacity live in three places, because every change has to be made three times to stay true. Software designed around semesters makes it worse — it assumes a cohort that starts together and ends together, which is not how a language academy with rolling intakes works at all.
3. The report someone asks for on Thursday afternoon
The Principal wants attendance by level for the board. The accrediting body wants records for an inspection. Marketing wants conversion from last month's enquiries. Each one takes you a morning to assemble from four exports, and it is out of date before you have finished formatting it.
The process half. Before building anything, ask what decision the report supports. A surprising share of recurring reports are habits — someone asked once, and now it exists forever. The rest collapse into a small standard set that the same three people ask for repeatedly. Agree that set and refuse the bespoke ones.
The system half. If the underlying data is entered once and lives in one place, a report is a filter, not a construction project. When the data is scattered, a "quick report" is a reconciliation exercise wearing a disguise.
4. Interruptions that are really lookups
"Is this student paid up?" "How many classes has she missed?" "Which group is he in now?" You are answering these because you are the only reliable index of the school. That makes you a bottleneck, and — worse — it makes the answers dependent on your availability.
The process half. Every time you answer a lookup, note who asked and what they wanted. After two weeks you will have a very short list of the questions behind most of your interruptions.
The system half. Those questions should be self-serve, with permissions that let a teacher see their own groups and attendance, reception see balances, and a parent see their child's record without going through anyone. Role-based access is not a security feature here — it is a workload feature.
What to give a system, what to give a person, what to delete
Not everything on your plate should be automated. Sorting it honestly is most of the work.
Give to a system the tasks that are repetitive, rule-based and verifiable: duplicate data entry, payment reminders, chasing missing documents, attendance capture, recurring reports, enrolment confirmations. These do not need judgement, and doing them personally does not make them better.
Give to a person the tasks that are judgement: a contested level placement, a teacher observation, a difficult conversation with a family, deciding whether to split a group. If you catch yourself defending a clerical task because "it needs care", check whether what needs care is the decision or just the typing. Usually it is the decision, and the typing can go.
Delete the rest. Reports nobody reads. The parallel spreadsheet somebody keeps "just in case". The weekly summary email that duplicates something already visible. Deleting a task is the only intervention that is guaranteed to work.
What to push back on
The hard part is not the tooling. Most of this workload arrived through people asking you nicely. A few things worth saying out loud:
"Can you just send me a list of…" — ask which decision it supports. If there isn't one, it isn't a report.
New spreadsheets. Every new sheet is a permanent maintenance commitment for someone, and that someone is usually you.
Being the routing point. If every question about a student comes to you first, the fix is access, not effort.
Owning document chasing. Collecting passports, contracts and consent forms is an admissions workflow with automatic reminders, not an academic task.
What this looks like with a proper system
The change worth aiming at is not "less typing". It is that you stop being the integration layer between departments.
In KMPUS, the student is one record. An enrolment made online creates the record, the placement and the charge together. Attendance — taken manually, by QR or by fingerprint — lands on the same profile, so the register, the level history and the family's account statement are all describing the same student rather than three approximations of her. Levels, periods, teacher allocation and classroom assignment sit in one academic module, so moving a student is one action rather than four.
The knock-on effect is the interruptions. Teachers see their own groups and take their own registers. Families see balances and their child's progress from the mobile app. Reception answers a payment question without walking to your desk. You are still accountable for the academic picture; you are no longer the only route to it.
It matters more as the school grows. NED College runs Dublin and Limerick with roughly 1,500 students; Erin School of English runs Cork and Dublin with around 1,400. A second campus does not add administration in a straight line — it multiplies the places where the same fact has to be kept in agreement. The same applies to a K-12 school running terms and report cards, where the duplication sits between the register, the report card and the fee ledger.
Two honest caveats. Migration is real work — someone has to clean the spreadsheets before they become records, and that is a project, not an afternoon. And a system will not decide your process for you: if two departments disagree about who owns enrolment status, the software will reproduce the disagreement faithfully. Settle that first, and the rest is configuration.
Frequently asked questions
How much of a Director of Studies' week should be administrative?
There is no credible benchmark, and anyone quoting one is guessing. A better test is qualitative: in the last month, how many of the academic tasks you consider central — lesson observations, teacher feedback, curriculum review, placement quality — actually happened? If the answer is "none, it's been a busy period" for three months running, the balance is wrong whatever any ratio says.
Should we fix our processes or buy a system first?
Fix the decisions, buy the system, in that order — but not as two separate projects. Decide who owns each piece of student data before you evaluate anything, because those decisions are what you will configure. What software cannot do is arbitrate between two departments that both believe they own enrolment.
How do we reduce administrative work without hiring another administrator?
Attack duplication before you attack volume. Adding a person to a workflow where every student is entered three times gives you a fourth place for the data to disagree. Once each fact is entered once, in one place, the remaining volume is usually manageable by the team you already have.
Can a small academy justify a management platform, or is it only for large schools?
Size changes the payback, not the logic. NL College runs Madrid and Barcelona with around 250 students and adopted a platform to resolve exactly this — years of disorganisation and poor communication between departments. The trigger is usually a second site, a second person doing enrolments, or the first inspection where the records took a week to assemble.
What should a Director of Studies stop doing entirely?
Chasing documents, rebuilding the same report by hand, maintaining a private spreadsheet that mirrors an official record, and answering lookups other people could answer themselves. Those four cover most of the recoverable time in the week.
If your week has stopped looking like the job you were hired for, the fastest way to see what changes is to try it with your own data — start a free trial of KMPUS, no credit card required.
