Skip to main content
GullySystem
Education · Software for language schools

Place each learner at the right level and keep classes, tutors, course books and exam entries accounted for.

A language school lives on placement tests, level groups, hourly tutors and learners who enrol in week three and vanish in week nine. One learner record holds the placement result, register, unit progress and tutor hours, so promotion and payment follow what happened in the room. Nothing gets retyped twice.

At a glance

A language school sells levels, not subjects. A learner sits a written paper and a speaking interview, joins the matching group, and moves up only when the teacher signs off the unit test. Intake never stops. Evening beginner groups swell in January while the advanced morning group shrinks to five, so every month needs its own seat count.

Tutors are mostly part-time and paid by the taught hour, with cover lessons, trial classes and exam-prep sessions each carrying a different rate. Learners buy a ten-lesson pack, a term or a full course, and many add one-to-one conversation practice beside the weekly group class. Three desks, three partial views.

How the work runs today

Reception takes enquiries by phone, walk-in and messaging, books the placement paper, and hands the written mark and the oral band to the academic coordinator. A group at that level is then picked, with seats checked against the room capacity and the tutor’s timetable, and a trial lesson often comes first.

Tutors take a register each lesson, note the course book unit and page reached, and set homework from the workbook so a substitute starts on the right page. A progress test closes every unit. Promotion follows: who moves up, who repeats the level, and who joins the weekend revision group before the next intake opens for the new term. A missed lesson is made up in a parallel class, but only when a seat is free and the tutor’s register can take one more name.

Corporate groups meet at the client’s office, exam classes work toward a fixed test date, and online lessons run on their own calendar. Month end is slow. The owner adds up tutor hours, cover lessons, cancelled sessions and book sales from several sheets, and one wrong cell shifts a pay slip.

Where it breaks

What goes wrong for language schools without a proper system.

Placement results sit apart from class lists

The placement mark sits on the coordinator’s sheet. The group list lives in reception’s file. A learner scoring upper-intermediate can land in a pre-intermediate group because nobody put the two pages side by side before the learner had bought the wrong course book.

Level progress lives in teachers’ notebooks

A tutor falls ill or quits mid-term. Nobody can say which unit the class reached, which learners passed the progress test, or whether the listening module was covered, so the substitute teaches a lesson twice.

Make-up lessons are arranged by message

A learner misses two lessons. She asks for a seat elsewhere, and reception pages through the Monday, Wednesday and Saturday timetables by hand while the make-up never gets subtracted from the lesson pack.

Teacher pay is rebuilt from registers

Hourly tutors earn one rate for taught lessons, another for cover and a third for trial classes, and the month’s figure is rebuilt from paper registers. A cancelled lesson is easy to pay twice.

Exam entries and course book sales are tracked separately

The exam board’s entry form, closing date and fee sit in one folder, so a learner reaches exam week without a confirmed seat at the test centre. The issued course book is in a notebook.

What the software does

What we would build for language schools.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Enquiries and placement tests

Log each enquiry by source, book the placement paper and speaking interview, and store both marks with the level band the coordinator assigned and the trial date.

Classes by level and room

Set up groups by language, level, tutor, room and weekday, with seat limits, a waiting list for full groups, and a clash warning when a tutor is double-booked.

Registers and unit coverage

Take attendance per lesson and record the course book unit and page covered, so a substitute opens the register and sees exactly where to start.

Progress tests and promotion

Enter unit test marks, apply the school’s pass rule for each level, and move a learner to the next level or a revision group with a dated note.

Lesson packs and make-ups

Sell lessons by pack, term or course, count each attended and missed lesson against the balance, and offer a make-up seat in a matching class.

Teacher hours and cover

Roster tutors across groups, record cover and trial lessons at their own rates, and total hourly pay per tutor straight from the registers.

Exam entries and course books

Track entries for external language exams with their closing dates and fees, plus the course books and workbooks issued to each learner and the ones still owed.

Before you talk to a supplier

A requirements checklist for language schools.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for language schools.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Language School Management Software

Placement tests, level classes, registers, lesson packs, make-up lessons, teacher hours, exam entries, course book issue and company group accounts for language schools.

See the product
Services

The services behind it.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions language schools ask before they call.

Can we use our own placement test and level names?

Yes. Whether the school uses CEFR bands, its own ladder or colour codes, the level names and the pass mark for each unit are entered exactly as you use them. The paper and interview notes stay with you, and the system stores only the marks, the assigned level and the coordinator’s note.

Does it handle one-to-one lessons beside group classes?

Yes. A private lesson is booked with a named tutor and a slot, deducted from the learner’s pack, and paid to the tutor at the one-to-one rate you set.

Can online lessons be recorded here?

Yes. An online lesson is a normal lesson with a meeting link beside the register, so Zoom or Teams stays as it is and attendance is taken the usual way.

How is the first set-up of learners and classes done?

Existing records are imported from the paper registers or spreadsheets you keep today, one row per learner. Current students, open lesson packs and classes already mid-unit all come across. Before the first live week the coordinator checks every learner’s level and remaining lessons, and the written quotation states how records can be exported later.

How is a language school quoted?

Branches, classrooms and tutors count, as do staff users and the parts chosen: placement, registers, progress tests, make-ups or exam entries. Online lessons and a fees tool may need linking. The quotation puts a separate figure beside each part.

What should a school have to hand at the beginning?

Your placement test and level names, a class list, one register page, a progress test form and the tutor hours sheet. Name the academic coordinator, a receptionist and a person from accounts. Screens are then tested against real classes.

Do learner and class records stay with the school on leaving?

Learner, class, register and test records are the school’s, and so is the code. They can be saved as open-format files. Builders keep supporting it. GullySystem hosts the system, unless the school wants a host of its own.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements