Admissions pipeline

Admissions runs on cycles tied to an academic year and intake grade. Each cycle defines public apply links, form fields, fees, test and interview stages, and seat capacity. Staff move applications through pipeline stages until enrollment creates a student roster record, auto-invites the guardian to the parent portal, and provisions fee instances when structures exist.

Pipeline stages

Public vs staff surfaces

What enrollment produces

• Student user on the roster (registration number, class section, roll number)
• Student email kept separate from the guardian - application studentEmail, or {registration}@students.local - so the parent email stays free for the portal
• Parent record + parent portal user + welcome magic-link email (primary path)
• Fee instances for the cycle academic year when fee structures exist; family fee notifications only when a portal user was created

• Parent portal

  What guardians see after the post-enroll invite

• Parent account linking

  Manual /parents linking for edge cases

• Student roster

  Roster lifecycle after enrollment