Morning priority queue
Open decisions sorted by the first class, enquiry or test they affect, with the owner named beside each one.
The general manager of a language school watches tutor cover, group sizes, placement test rooms and enquiries from partner agencies, often all before the first class starts. We build a manager oversight app for language schools that gathers those open decisions into one queue, so the manager can act while the next class can still be saved.
Learners often choose a language school through a partner agency, a friend who studied there or a search for a course that fits their timetable. Agencies send enquiries in batches and expect a fast answer about places, start dates and the cost of a placement test. A manager who can see every waiting enquiry, and how long it has been waiting, can keep those agencies sending students.
Once a learner is enrolled, the manager's decisions shift to class quality. A group that drops from twelve learners to four needs rebalancing, a tutor on leave needs a cover, and an online class with a poor link needs a fix before it starts. The oversight app keeps those decisions visible in the order they will affect learners.
The general manager will judge the app on whether classes run as timetabled and whether agency enquiries get a reply on the same working day. Record the number of classes started late or cancelled at short notice in the four weeks before launch, and the average time an agency enquiry waits for an answer. Those figures show the difference the queue makes.
Equally important is trust in the queue itself. If the manager sees an item that is already handled, they stop looking at the list. The app should close items when the action is done, record who did it and show the outcome beside the original request.
At 5:40 pm the manager receives an item in the queue: the tutor for the online B2 evening class has not logged in, and the class starts at six. The app shows nine learners who have joined the link, the materials planned for the lesson and a list of tutors who are free and qualified at that level.
The manager chooses to move the nine learners into the 6:30 B2 group, which has space and the same tutor's materials ready. The app sends each learner a message with the new time and link, and asks them to confirm. Seven confirm within ten minutes, and the other two are called from the reception list.
At 6:05 the queue shows the item closed, with the reason, the new group and the confirmations attached. The next morning's report counts the event as a rebalanced class, so the manager can see how often that happens and whether the same tutor is involved more than once.
Open decisions sorted by the first class, enquiry or test they affect, with the owner named beside each one.
Flags a tutor who has not joined, lists learners waiting and offers free qualified cover at the same level.
Suggests moving learners from a small group into another class at their level, with a confirmation step for each one.
Keeps partner agency enquiries in one list with their age, the course asked about and the reply status.
Shows placement test rooms and exam invigilator slots for the coming weeks, with gaps highlighted.
Language schools have sharp peaks. September and January bring large intakes, summer runs intensive courses, and English test seasons fill every placement room. Each peak changes the number of groups, the number of tutors and the number of invigilators needed, sometimes all in one week.
The oversight app should warn the manager of those pressures before they arrive. It can show the next four weeks of group sizes, cover needs and invigilator slots on one screen, so the manager adds tutors or opens a second room while there is still choice, not on the morning of the test.
A common error is letting every tutor see every learner's record. A tutor needs the learners in their own groups, and the manager needs more. Set the access rules by role from the start, so personal details and agency terms are kept where they belong.
Another is building a timetable tool that duplicates the scheduling software already in use. The oversight app should read the timetable and add the decisions on top of it. When two systems both claim to be the timetable, the manager will not know which one to trust.
Track the number of classes that run as planned, the time from a no-show to a replacement, and the number of agency enquiries answered the same day. Count them each month and compare the same measures with the four months before launch, so the change is visible.
Look for patterns rather than single events. If the same tutor's classes keep moving, the cover plan needs attention. If agency enquiries are answered quickly but still convert poorly, the problem may lie with the offer, not the queue.
No. Each learner receives a message with the new time and must confirm. Anyone who declines goes back into the queue with a note, and the manager arranges an alternative.
The app flags the absence as soon as the tutor has not joined the class at the start time, and it can send an alert to the manager's phone. The flag sits at the top of the queue until someone acts.
Only the roles you choose, which in practice means the general manager and the finance contact. Those details stay out of tutor and reception views by default, and each change is logged.
It can, if that software exposes class, room and tutor data. We check the export during scoping and tell you whether a daily import is enough for the first version.
Yes. Each enquiry keeps its full history, from the first message through to the placement test result or the enrolment, so the manager can see the outcome beside the original request.
Share your timetable, agency enquiry volume and placement calendar, and we will show where the oversight app would act first, with a scope and price.