Admissions
Applications, shortlisting and enrolment in one pipeline.
Admissions is usually several systems at once: a form, a mailbox, a spreadsheet of who has replied, and somebody's memory of what was promised on the phone.
This is one pipeline, from the enquiry to the enrolled pupil. You build your own form — the questions, the sections, which of them are compulsory, which appear only when an earlier answer calls for them. Families fill it in on their own link, guardians consent on theirs, and referees reply on a link of their own that the applicant can never read.
An accepted applicant becomes a pupil in the register in one step, which is the join most schools do by re-typing.
HOW IT CONNECTS
A shared institutional foundation.
This module works within the same institution and student register as the rest of CampusOS. Staff access is controlled by their role and module permissions.
KEY CAPABILITIES
What changes in the workflow
Your own form: sections, question types, conditional questions, word limits
Guardian consent collected properly, in line with the DPDP Act
Confidential references, on the referee's own one-time link
Application fees, early-bird phases, coupons and waivers
Review, score and decide — with the school's own words in the offer email
Reminders for the families and referees who have gone quiet
An insights dashboard, including where your applicants come from
YOUR WORKFLOW IN CAMPUSOS
Show us how your institution works.
We’ll focus on this workflow in the live product and show you how it connects to the rest of the institution.