Keep lifecycle events distinct from everyday portal activity
Programme changes need governed records. A college student may change an elective, while a university student may move to a different programme cohort under approved rules. The student record must maintain the effective academic context so timetable and examination teams do not act on an outdated enrolment. A student viewing attendance or a faculty member reading a notice should not change the authoritative student record simply by opening a portal screen. Student Management owns core identity, enrolment and academic relationships; role-based portals and the student and parent apps provide access to selected information and actions under institutional policy. When a student exits under NEP 2020 multiple entry and exit, or graduates, the institution still needs an accurate historical record for certificates, transcripts and approved reporting. That does not mean every old service allocation should remain active indefinitely. Core identity. Maintain a stable enrolment number or PRN and verified demographic fields. The student office must know which identity fields are verified, which changes take effect later and what downstream records need updating. Academic lifecycle. Record current programme, semester, section, enrolment status and authorised changes, including detention, year back and readmission.


