School · 500 students · PK
Admissions enquiries that stop falling through
Walk-in and phone enquiries moved from a paper register to a tracked list that turns into an admission.
- Tracked
- Every enquiry
- No re-entry
- Enquiry to admission
Students join mid-course, pay in instalments and attend sessions rather than school years. Scolvia is set up around that, not around a timetable built for a school.
Book a demoAn academy does not have a class seven. It has the evening physics batch that started in March, the weekend test-preparation course with thirty seats, and the student who joined both halfway through and is paying in three instalments.
School software expects a fixed year, a fixed class and a fixed fee. Bend it to fit and the attendance report counts sessions that never happened, the fee report shows balances that are not due yet, and enquiries live in a notebook because there is no admissions season to put them in.
Scolvia lets an academy work in batches and courses. Enquiries are tracked to enrolment, fees follow the course and its instalments, and attendance is marked per session for the batch that actually met.
What a batch-based institution needs, and nothing it does not.
Every walk-in, call and form tracked until the student joins or the lead goes cold.
Batches with their own start dates, capacity and teacher, not fixed class years.
Marked for each session the batch actually held, visible to students and parents.
Fees per course with instalment plans and discounts, and a clear view of what is due.
Regular tests, marks entry and progress over the length of a course.
Notes, assignments and quizzes, with live classes on your meeting provider.
Batch announcements, schedule changes and fee reminders.
Teacher records and the monthly salary run.
Sell course books and materials at the counter, with stock behind it.
The student who joins in week four. They owe a part-course fee, they missed three sessions that should not count against them, and the teacher needs them on the attendance list from today. A year-based system gets at least one of those wrong.
The same student in two batches. Mathematics on weekday evenings, a test-preparation course at weekends. Two attendance records, two fee plans, one person and one contact for the parent.
The instalment that is not overdue yet. A fee report that treats the whole course fee as outstanding from day one makes every student look like a defaulter and hides the ones who really are.
The enquiry that comes back in three months. They asked about the summer course, did not join, and called again in the autumn. With the first enquiry on record, the conversation picks up where it stopped.
Small team or several branches, each person sees what they need.
Owner and front desk: enquiries, batches, fees, teachers and reports.
Teachers: their batches, session attendance, tests and material.
Students: schedule, attendance, material, tests and fees.
Parents: attendance, test results and fees for each child enrolled.
Setup is quick because the structure is simple: the courses you run, the batches within each, their fees and instalment plans. Current students and open enquiries come across from your existing lists.
Most academies go live with enquiries, batches, attendance and fees in the first week. Tests, online material and live classes follow as teachers start using the staff portal.
If you run several branches, each one operates on its own while the owner sees all of them together. Payment and SMS options depend on your country, and we confirm them before you commit.
School · 500 students · PK
Walk-in and phone enquiries moved from a paper register to a tracked list that turns into an admission.
The one with late joiners and three instalment plans. We will set it up with you in the demo.
Book a demo