One student record, with a core every institution has and fifteen optional modules for teaching, assessment, learning and student services. Take the modules you need now and add others when you need them.
Which of these are included in a deployment is set out in the proposal for that institution.
Students, programmes, subjects, faculty and sections.
The academic calendar, class rooms and announcements.
Marks, grades, results, rankings and grade cards.
Reports across the record, user accounts, and single sign-on.
A record of sign-ins, changes, exports and configuration changes: who, what and when.
Privacy notices and consent records, personal-data export and erasure, and a retention schedule the institution sets.
A module the institution has not taken does not appear in menus, on the home page, in help or in links from other pages.
Switching a module off hides it; nothing recorded is deleted, and switching it back on brings everything back.
Each institution’s records are held in its own database.
Each module can be taken on its own unless a dependency is noted.
A bundle is a named set of modules. Any bundle can be tailored module by module, and modules can be added or removed after the institution has started.
The core, with attendance, timetable, electives and student leave.
Essentials, plus examinations, online quizzes, feedback and IQAC, CO–PO outcomes, transcripts, the document locker and courses.
Every optional module except AI assistance, which is added separately and billed by use.
An illustration of a typical sequence. Your own process is configured during implementation.
Choose a bundle as a starting point, then add or remove modules.
Programmes, subjects, faculty and students are set up or imported from spreadsheets.
Staff and students sign in, through single sign-on where it is configured.
The term runs: timetable, attendance, assessment and marks.
Results are processed and grade cards issued.
Further modules are switched on as the institution needs them, working from the same student record.
A & S has built and supported student administration software for higher education institutions for over two decades. The institutions we have worked with, and the letters they have written, are on the clients page.
One student record from registration to transcript, covering courses, attendance, assessment, grading and attainment reporting.
Course pages, video, SCORM lessons and external tools, on the same student record.
Fee plans, collection, online payments, settlements and refunds for each student’s account.
No. Every institution has the core, and takes the optional modules that address its current problem. A bundle is only a starting point: modules can be added or removed one by one, now or later. Which modules are included is set out in your proposal.
We reply to arrange a time, and ask which offices and workflows matter most so the demonstration covers those. You do not need to prepare anything. If you have used the requirements builder, you can attach its summary to the request.
It depends on the number of students, the modules you take and the deployment model. AI assistance is billed by use on top of that. Tell us those and we will give you a figure.
Tell us which offices and workflows matter most and the demonstration will follow that.
