Admissions¶
The admissions funnel runs enquiry → registration → merit → admit. Admitting an applicant creates the student record.
Enquiry register¶
A 30-second capture at the front desk: the child's name, parent or guardian, class seeking admission, current school and class, address, contact, source, notes and follow-ups. Every enquiry gets an enquiry number when it's logged.
Registration desk¶
Registration is the full application, on a full-page form with sections for basic details, parents and guardian, contact, class applying for, identity and language, previous school, and logistics and health.
- The funnel remembers. Opening registration from an enquiry prefills it. Typing a phone number that matches an open enquiry shows "{name} already enquired on {date}" with Link and prefill, which fills only empty fields and never overwrites what the clerk typed.
- Registration fee. The fee is set once on the admission round and inherited by each application, still editable for concessions. It's collected into the same receipt sequence as every other fee, so accounts sees one day book.
- Printable form. The registration form PDF carries the institution letterhead with its UDISE or affiliation number, the particulars, a declaration with signature lines and an office-use block with the fee receipt. It can be reprinted any time.
- Search by name, registration number and registration date. The date is editable so paper registrations can be back-dated.
On admit, demographics such as mother tongue, religion and APAAR ID carry onto the student record.
Document numbering¶
| Document | Number allocated when | Default format |
|---|---|---|
| Enquiry | logged | ENQ000001 |
| Application | registration created | APP000001 |
| Admission | admitted | ADM000001 |
| Fee receipt | payment recorded | REC000001 |
Institutions shape their numbers in ERP Settings → Document numbering: a prefix (SIS/), an optional academic session token (2026-27/, April to March), zero-padding width, and a forward-only next number so a migrating school can continue its old sequence. The settings page previews the next number.
Form builder¶
In build. Institutions will define their own fields and forms without a migration on our side.
Fields come in three layers:
- Built-in fields are real columns we own: name, admission number, gender, category, quota, APAAR ID, date of birth, guardians and the standard demographics.
- Field policy is each institution's choice of which built-ins to use. A Karnataka school turns on SATS No, a Delhi school turns on PEN No.
- Custom fields are the institution's own inventions (hostel block, parent occupation), stored as JSON beside the row.
In the builder all three look the same. Built-ins just can't be removed. Templates are versioned and each record pins the version it was captured with, so a form printed in January reprints identically in June.
A form leaves the list in exactly one of three ways, decided by its state:
| Form state | Action offered |
|---|---|
| A version is published | Unpublish |
| Offline, and was published or has submissions | Archive (all versions at once) |
| Offline, never published, no submissions | Delete |
No admin is ever offered a button that destroys responses.
Where it lives¶
- Web:
apps/web/src/erp/pages/ErpAdmissionsPage,ErpRegistrationPage,ErpFormsPage,ErpFormBuilderPage,ErpFormFieldsPage,ErpSettingsPage - Backend:
apps/backend/src/erp/admissions/,apps/backend/src/erp/forms/