Rules that fit your university.
Configure grading scales, credit limits, ID patterns, and retake policies. A flexible foundation that adapts to your academic governance.
University settings
The rules the university layer follows. Grading and retakes differ from one university to the next, so they are settings, not code.
Tokens: {DEPT} department code · {PROG} programme code · {YY} or {YYYY} intake year · {T} term in the year · {SEQ3}—{SEQ6} serial. Example: {DEPT}{YY}{T}{SEQ4} → CSE27I0001.
Best: a retake replaces the earlier grade in the CGPA only if it is higher. Both attempts stay on the transcript.
Preview mode. Explore the full configuration.
Tailored to your
academic
governance
No two universities operate the same way. Adon ERP gives you the controls to define your exact institutional rules, ensuring the software adapts to your university, not the other way around.
Institutional Rules
How do we enforce our specific grading and retake policies?
Every university is different. Configure exactly how retakes are handled, what the minimum passing CGPA is, and how the Dean's list is calculated. The system enforces these rules automatically across all student records.
Synced from Academic Policies
Student ID Generation
Can we customize how student IDs are formatted?
Yes. Define your exact numbering pattern using tokens like {DEPT} and {YY}. The system automatically generates unique, compliant student IDs for every new admission without manual intervention.
Synced from Registrar Rules
Term Structures
Does the system support our specific academic calendar?
Whether you run Semesters (Spring/Autumn), Trimesters, or a unique custom system, you can define the exact structure. The rest of the ERP modules adapt to this configuration.
Synced from Academic Calendar
Credit Limits
How do we prevent students from overloading their schedules?
Set the exact minimum and maximum credits a student can take per term. The registration engine automatically blocks enrollments that fall outside these bounds, protecting students from unmanageable workloads.
Synced from Registration Rules
Flexible enough for
complex institutions
From custom ID generation to complex retake policies, Adon ERP is built to handle the administrative intricacies that make your institution unique.
Dynamic ID Generation
Map student IDs to department codes, intake years, and serial numbers. The system guarantees a unique ID for every student, eliminating manual typos.
UGC Compliance
The default grading scale is aligned with UGC standards (CGPA 4.00), ensuring your transcripts and degree audits are officially compliant.
Retake Flexibility
Choose whether the newer grade replaces the old one, or if the better of the two counts. The system automatically recalculates CGPA based on your policy.
Custom Term Systems
Whether you operate on a two-semester system or a trimester system, you can configure the exact naming and structure of your academic year.
Probation & Honors
Set the CGPA threshold for academic probation and the term GPA required for the Dean's list. The system flags students automatically based on these numbers.
Credit Limits
Enforce minimum and maximum credit limits per term. The registration portal prevents students from enrolling in fewer or more courses than the institution allows.
A day for the IT Admin
9:00 am
The IT admin reviews the University Settings to ensure the grading scale is still aligned with the latest UGC directives.
11:00 am
A new department (Cyber Security) is launching. The admin updates the Student Number pattern to include the new department code.
1:30 pm
The academic council decides to change the retake policy. The admin updates the dropdown from 'The better grade counts' to 'Latest grade counts'.
3:00 pm
The admin adjusts the maximum credit limit from 21 to 24, allowing high-performing students to take extra courses next semester.
5:00 pm
The admin clicks 'Save' and verifies that the changes have instantly propagated across the student registration and grading modules.
Questions about
system configuration
What happens if we change the student number pattern?
Changing the pattern only affects future intakes. Existing students keep their originally assigned IDs to maintain historical accuracy and prevent data mix-ups.
Can we have different grading scales for different faculties?
The system currently supports a primary institution-wide grading scale (e.g., UGC 4.00). However, specific departmental overrides can be configured if your academic council requires it.
How does the 'The better grade counts' retake policy work?
If a student retakes a course, the system will automatically replace the older grade with the newer, higher grade in the CGPA calculation. Both attempts remain visible on the official transcript.
Who has access to change these settings?
Only users with the highest administrative privileges (e.g., the Registrar or Vice Chancellor) can access the University Settings page. All changes are logged for audit purposes.
Ready to configure
your institution's rules?
Get a personalized walkthrough of the Settings module. We'll show you how to tailor the ERP to your exact academic policies.