Running a language school or a study-travel operation is not managing a simple course list: enquiries arrive through several channels, bookings depend on courses and accommodation, agencies expect commission statements, and at the end of the month every payment has to match an invoice. Management software that covers only part of this doesn’t remove the work — it just moves it.
This checklist sums up the questions that twenty years of working with language schools have shown to be decisive. It applies whichever system you end up choosing.
In short: seven questions separate management systems faster than any feature list — full journey coverage (enquiry to paid invoice), a real accommodation module, website forms that land in the system, automated payment reconciliation, proper agency connections, clear data governance, and a concrete migration plan with a test import.
1. Does the software cover the whole journey — from enquiry to paid invoice?
The most common mistake is stitching tools together: a form builder for enquiries, a spreadsheet for courses, a separate invoicing app. Every seam between two tools produces double entry and transcription errors. Check whether one system handles the continuous flow: enquiry → quote → booking → invoice → payment — with the same master data from start to finish.
2. Is accommodation management a real module or a text field?
For study-travel schools, accommodation is half the operation: host families and residences with availability, occupancy periods and attributes (room type, board, distance). Ask concretely: can the system prevent a double booking? Can the accommodation team see at a glance who is staying where, and when?
3. How do enquiries get from your website into the system?
Enquiry and enrolment forms belong on your own website — and should land in the management system directly, not in an inbox. Make sure forms can be embedded into common website platforms, and that fields, mandatory inputs and languages are configurable.
4. How much manual work is hidden in payment reconciliation?
Matching bank transactions against open invoices is one of the biggest silent time sinks. Modern systems read bank statements automatically (open banking) and propose the matching invoice. In your demo call, ask: “Show me how an incoming transfer gets matched to an invoice.” The answer tells you more than any brochure.
5. Can agencies and partners be connected properly?
If you work with placement agencies, you need more than a notes field: per-agency price lists and commission rates, traceable statements, and ideally a portal where partners can see their own bookings. Otherwise every agency statement becomes manual work.
6. Where does the data live — and who can see it?
You manage personal data of minors, health information from enrolment forms, payment data. Clarify: where is the system hosted? Are there role-based permissions, so the accommodation team sees different data than accounting? How are backups handled? A serious vendor answers these questions in writing (see Art. 28 GDPR on processor contracts) — including a data processing agreement.
7. What does the switch actually look like?
Changing management systems rarely fails because of the new software — it fails at the transition: legacy data, live bookings, established routines. Ask for a concrete migration plan: which data gets imported? Does the old system run in parallel for a while? Who trains the team? A vendor who answers these questions routinely has guided the switch many times.
The takeaway
The right question is not “what features does the software have?” but: “does it model our operation completely — and what happens at the seams?” Take this checklist into every demo call, including ours: book a free demo.