Replacing a paper process with one the rules enforce automatically.

The problem this solves

Before this system, working out what a student could enroll in each semester meant cross-checking their transcript against a printed scheme of study by hand — prerequisites, credit-hour caps, which F/D grades qualify for improvement, whether a course is even offered that session. Small mistakes here cost real time for students, advisors, and the Controller's office once the paper UG‑1 form reaches them.

This system reads a student's actual result record, matches it against their exact scheme of study (by admission session, not just program), and computes what they're eligible for — so the enrollment form that reaches an advisor for approval has already been checked against every rule the university's own regulations require.

Who it's for, today

Currently scoped to BS Computer Science, BS Information Technology, and BS Software Engineering at UAF's Burewala Constituent College — the programs whose schemes, student records, and results are already loaded and verified. The architecture (a real university-wide org chart of every Faculty/Department/Institute, and a scheme-upload pipeline that works from Excel or a scanned PDF) is built to extend to every other program and campus without a redesign, whenever their own scheme data is ready to load.

How it's built

A Django application with one real database as its single source of truth — no parallel spreadsheet or JSON export drifting out of sync with what the live pages show. Every role (Student, Faculty, Admin, and the Advisor/Focal Person duties layered onto a faculty account) works against the same underlying data, scoped to what that role is allowed to see and change.