Loading…For IELTS, PTE, Japanese and Korean EPS institutes: monthly intakes, daily shifts, course fees and verifiable certificates. Your calendar, not a school year.
A language institute starts a new intake most months and runs the same course four times a day. Almost every education product in the market assumes exactly the opposite.
A new batch starts every month, and the system wants one academic year with one start date.
The same course runs at 6am, 10am, 2pm and 6pm, and the learners are different people in each.
A learner finishes L1 and starts L2 six weeks later, and the record has to pretend they are a new student.
Attendance matters because a visa file or an EPS application may depend on it, and it is kept on paper.
Fees are per course, sometimes in two instalments, never one annual figure.
A completion certificate is a Word file with the name changed, and there is no way for anyone outside to check it is real.
Learner records, fees, staff and permissions, on a calendar shaped like yours.
Intakes run as sessions in their own right rather than academic years: each batch with its own start and end date, its own days and its own shift time, and a learner able to sit in more than one at once as they move from one level to the next.
Fee heads and structures, invoices generated in runs, payments recorded against them, concessions, refunds and late fines. Every reversal needs a reason and keeps its trail, so the books reconcile rather than merely balance.
Permissions are set per role and per person, and enforced on the server on every request. Hiding a button is not security here: a request crafted by hand gets the same answer as one that came from a click.
Full staff records with departments, designations and qualifications, one leave flow that marks attendance when it is approved, and Nepal payroll with PF, SSF, TDS and festival allowance.
Bulk import with a dry run first: validate, see exactly what would change, fix it in a grid, then commit. Guardian records are de-duplicated and Bikram Sambat dates are detected rather than mangled.
Your data is backed up nightly to storage held with a different provider in a different jurisdiction, encrypted before it leaves our servers, and we practise restoring it. A backup nobody has restored from is a hope, not a backup.
Attendance is recorded per session rather than per day, so a 6am shift and a 2pm shift are separate registers, and learners who fall below the attendance an application or a certificate requires are flagged while there is still time to fix it.
Numbered completion certificates are issued from the learner's own record, each with a public verification page, so a consultancy or an employer can check one is genuine without ringing your office.
Your intakes and shifts go in first, because they are the shape everything else takes.
Tell us how your intakes and shifts actually run, and what your learners need proof of.
Send us the learner and staff records you already keep, in whatever form they are in.
We validate them before anything is written and show you exactly what would change.
Your batches, shift times and course packages are set up to match your timetable.
Fees, attendance, certificates and staff all run from the same records.
Show us how your language institute works today, registers, spreadsheets or another system, and we will show you what moving across actually looks like. No pressure, and a straight answer on price.