From the first phone call to the first day
Every enquiry becomes an application, an interview, an offer and — when the family says yes — a student, a household and a place in a class, without anyone retyping a name.
The pipeline is a list like every other: filter by stage, by year group, by who is handling it. Accepting an application creates the contact, the household and the enrolment in one step, so the child's first tuition charge is raised from the same record the office has been looking at since September.
For the office
What a secretary, a bursar or a head of year can do with it.
- Enquiry, applied, interview, offered, waiting list, accepted, declined — as a list or grouped by stage
- The waiting list with a position, so a place that frees up goes to the right family
- Accepting an application creates the student, the household and the enrolment together
- Forms and consent collected before the first day, attached to the family
For whoever has to approve it
Where the data sits, who can read it, and what it connects to.
- No separate admissions database to reconcile — an applicant becomes a contact in place
- Public application forms post through a service-role endpoint with a honeypot and no direct table access
Questions we are asked
- Can parents apply from the website?
- Yes — a public form writes into the admissions list. Nothing about the school's data is exposed to it; the endpoint only accepts an application.
- Does a rejected application stay on file?
- Yes, with its reason and its history, and it can be reopened next year without retyping anything.
See it with your own school's data
Sixty days free, no card up front — or open a ready-made demo school and click around it first.