See what course management changes at your institution
Before vs. after adding course management to iVake
Where you are today
Holding you back
The curriculum lives in three files
Regulations in a PDF, subject codes in a spreadsheet and batch lists on a shared drive, and no two of them agree.
Pain point
Prerequisites checked from memory
A student is registered for an advanced subject without the one before it, because nobody checks the rule consistently.
Pain point
Credits added up by hand
Before a student can progress or exit, someone counts credits from marksheets against the regulation, one file at a time.
Pain point
One new elective, four updates
Adding a subject means changing the regulation file, the registration form, the timetable sheet and the website separately.
Pain point
- 3+Files that describe one programme
- 2+Times a subject is re-entered
- WeeksTo check a batch’s credits
Your institution, transformed
Everything connected
One academic structure
Campus, school, department, programme and batch in one tree, with settings inherited down it.
Solved
Rules checked at registration
Prerequisites and elective limits are checked when a student registers, not discovered at the examination.
Solved
Credits kept as they are earned
Credits attach to courses and results as they are earned, so progression and ABC deposits are a read.
Solved
Change once, seen everywhere
A new elective is added to the programme once, and registration, the timetable and results pick it up.
Solved
- 1Structure every module reads
- 0Credit sheets kept by hand
- 1Place to add a subject
Ready to make the switch? See how it works for your institution.
One academic structure for the whole institution
Define every programme, regulation, subject and credit requirement once. When the academic office changes a definition, registration, timetables, examinations and the student record all read the new version.
- Campus, school, department, programme, batch and section in one tree, semester or annual
- Subjects with code, credits, teaching hours and theory, practical or lab components
- Prerequisite and co-requisite rules checked when students register
Batch and section management at any size
Put students into batches and sections with a capacity, the subjects they take and the teachers who teach them. Class lists follow the student record, so moving a student between sections is done once.
- Batches with start and end dates, capacity and the subjects offered to them
- Teachers assigned by subject and section, with teaching load visible as you assign
- Class lists follow the student record when a student joins, leaves or changes section
Credit tracking that shows progress while it can be fixed
Advisers should not add up credits from marksheets. Credits attach to results as they are earned and are counted against the regulation, so a student short in one basket is visible while there is still a semester to put it right.
- Credits counted by basket: core, programme electives, open electives and projects
- NEP entry and exit points, with the certificate, diploma or degree a student has reached
- Credits deposited to the Academic Bank of Credits against the student’s APAAR ID
Course management features
Everything you need to manage programmes, subjects and credits
Programmes & regulations
Programmes by department, with the regulation each batch was admitted under.
Subjects
Code, credits, hours and theory or practical components for every subject.
Batches & sections
Capacity, dates and class lists that follow the student record.
Subject offerings
Subjects linked to batches and sections, with teachers assigned.
Credit system
Credit baskets with earned, in-progress and remaining credits.
Prerequisites & co-requisites
Rules checked at registration, with approved exceptions logged.
Electives
Elective groups with selection limits, and clashes caught at timetabling.
NEP & ABC
Entry and exit points, with credits deposited against the APAAR ID.
Frequently asked questions
Get answers to common questions about course management
Can iVake model our academic structure?
Yes. Structure is configuration, not custom code: campus, school, department, programme, batch and section, with settings inherited down the tree, semester or annual. Schools use class, section and subject for CBSE, ICSE or a state board, and skilling institutes use rolling batches. The structure is written down with your academic office in the first week of rollout.
What happens when the curriculum changes for students already enrolled?
Each batch stays on the regulation it was admitted under, and new batches follow the revised one. Students who repeat a year or rejoin after a break are moved to a regulation by a rule you set, and the change is recorded on the audit trail.
Can we track credits towards a degree, diploma or exit certificate?
Yes. Credits attach to courses and results as they are earned and are counted by basket against the programme’s requirement. NEP entry and exit points show what a student has reached, and credits are deposited to the Academic Bank of Credits against their APAAR ID.
How are prerequisites enforced?
Rules are checked when a student registers for a subject. If a prerequisite is missing, the registration says what is needed. An authorised person can approve an exception, and the approval is written to the audit trail with their name.
Can teachers see the subjects and sections they are assigned?
Yes. Teachers see their own classes in the app, with the timetable, class lists and grade books for those sections, and substitutions and deadlines sent to them.
Can we bring in our existing course catalogue?
Yes. Programmes, subjects and batches are imported from your current system or spreadsheets during migration and checked with you before go-live. If your website lists courses, it can read them through the REST API instead of keeping a second copy.
Does it work for both affiliated and autonomous colleges?
Yes. Affiliated colleges follow the university’s prescribed curriculum, and autonomous colleges design their own, each with its own examination scheme. Both are set up the same way.
How does course setup work for a school?
A school uses class, section and subject rather than credits and semesters, with term assessment and report cards. Board attempts, including a second attempt in the same year, are recorded against the student.
Cloud, hosted in your region- REST API & webhooks
SSO: Google, Microsoft & SAML- Encrypted, backed up daily
Built for the DPDP Act- Full security details
Built for your institution type
See how this feature works for your specific institution
Degree collegesAffiliated or autonomous curriculum, with credit baskets
UniversitiesProgrammes and regulations inherited down each campus
CBSE, ICSE & state-board schoolsClass, section and subject for CBSE, ICSE or a state board
ITIs, polytechnics & skill centresRolling batches with capacity and trainer allocation
Coaching institutesBatches with fixed start and end dates
Professional collegesTheory, practical and lab components, with each batch’s regulation
Integrations, comparisons & tools
Extend course management with integrations, see how iVake compares, and run the numbers
Related features
Admission Management
Enquiries, applications, documents and fees on the record that becomes the student.
Student Management
One student record from enquiry to alumni, read by every module.
Examination System
Eligibility, hall tickets and results from the records already kept.
Faculty Management
Teaching load, substitutions and exam duty, visible rather than assumed.
Financial Management
Programme and category fee heads on the same student record.
Timetable Management
Timetables built around availability, workload, rooms and elective clashes.
Ready to transform your course management?
See how iVake holds programmes, subjects and credits in one structure that every module reads, so a curriculum change is made once.
Try it free for 30 days. No credit card required.