The enquiry-to-enrolment pipeline, end to end.
The commercial engine of a school, and the module built first.
Every enquiry, application, assessment, offer and acceptance lives in the record it creates.
Nine tracked states
Submitted, documents pending, under review, assessment scheduled, offered, waitlisted, declined, withdrawn and enrolled.
Four working views
Board for the pipeline, list for volume, leads for pre-application enquiries and events for open days, all on the same records.
Lead capture, classified
Website, walk-in and telephone enquiries land in one queue, classified and assignable to a named officer.
Founding cohort
The launch cohort is a first-class field with its own mark rather than a spreadsheet column, and it counts itself.
Nine states, one row of pills.
An admissions lead can see the entire pipeline without scrolling and move an applicant between states from the card itself. Board is for pipeline management, list is for volume work, leads holds pre-application enquiries and events runs open days. All four read the same records, so there is no view that is out of date.
- Search by name, guardian email, telephone or reference code
- Assign to a named officer and filter to your own caseload
- Reference codes issued at submission and carried through to enrolment
The website enquiry is the top of the pipeline.
Website forms, walk-ins and telephone enquiries land in one queue, classified as admissions, recruitment, spam or needs review, and assigned to a person rather than an inbox. Nothing is retyped between the website and the CRM, because the website is part of the system.
Full functionality
Every workflow below is specified with its trigger, its actor, the screen it happens on, the step sequence, the permissions and the edge cases.
01Lead capture and classification
- Website forms, telephone logs, walk-ins, open day bookings and referrals all create the same lead object.
- Automatic classification into admissions, recruitment, spam or needs review, with a human able to overturn any of it.
- Assignment to a named officer, with an ageing clock and an unassigned queue nobody can quietly ignore.
- Source and campaign captured at creation, so marketing spend can be traced to enrolments rather than to clicks.
02The application
A guardian completes one form, once. Everything it collects becomes the child's record rather than a document somebody later re-keys.
- Save and resume, with a magic link rather than yet another password.
- Sibling detection, so a second child inherits the family, the address and the billing relationship.
- Conditional sections by year group, so a Foundation Stage application does not ask about GCSE options.
- Arabic and English throughout, including the confirmation and the document checklist.
03Assessment days and open events
- Event capacity, sessions, entrances and staffing, with booking direct from the website.
- QR check-in on arrival, feeding live actual against expected per entrance.
- Assessment outcomes recorded against the application rather than on a separate sheet.
- Automatic follow-up to families who booked and did not attend.
04Offers, waitlists and acceptance
- Nine tracked states from submitted to enrolled, each with the permissions that govern who can move it.
- Offer letters generated from the record, in either language, with expiry dates that enforce themselves.
- Waitlist ordering by year group with visible reasons, so a difficult conversation has evidence behind it.
- Acceptance triggers the onboarding chain: contract, deposit, document request and welcome sequence.
05Documents and compliance
- Passport, visa, Emirates ID, birth certificate, transfer certificate, immunisation and previous reports, each with its own expiry rule.
- A pending-documents state that is a pipeline stage rather than a note in somebody's diary.
- Automatic re-request as an expiry approaches, without an administrator remembering.
- Everything lands in the child's record already filed, because it was requested from that record.
06Reporting and forecasting
- Conversion by stage, by source, by year group and by officer.
- Roll forecast against capacity per year group, which is the number a launching school actually governs by.
- Time in stage, so a bottleneck is visible while it can still be fixed.
- Founding cohort tracked as a first-class field with its own mark, because for a school opening its doors that number is the number.
07Handoff to enrolment
The moment a family accepts, the applicant becomes a pupil on the same record. No export, no import, no reconciliation.
- Class and form group allocation, with sibling and balance rules applied.
- Fee schedule, concessions and billing relationship created in finance.
- Parent portal account provisioned against the Workspace identity.
- Transport, canteen and QR identity issued in one step.
More of the platform
One record per child, composed from every department, with pastoral, inclusion and safeguarding built into it rather than bolted on.
A register a teacher finishes in forty seconds, with statutory reporting, absence follow-up and roll call already computed.
Curriculum design, timetable generation, gradebook, reporting and the cover engine that reads all three.
See it running on real data.
A working demonstration on a live database, walked through by the people who built it. Forty minutes, no slide deck.