One platform for every campus, every department, every affiliated college.
Multi-campus hierarchy, centralised admissions, exam-controller workspace, grants ledger, affiliated-college roll lists — all under one university umbrella with strict isolation between campuses.
Workflows that match how universities actually run.
Centralised admissions, decentralised teaching, distributed exam centres, audited finance — the architecture matches the org chart.
Each campus is a sub-organisation under the university — shared identity, isolated operations, university-level rollup.
Entrance-test → counselling → multi-campus seat allocation → enrolment. AI form-filler from Aadhaar / marksheets.
Question-paper management, descriptive evaluation routing, result-publish workflow, re-evaluation requests, university-vs-internal split.
Track research-grant disbursement, project-wise expense, audit-ready financials. Maker-checker on every voucher.
Same engine, university-scaled rules: fund grants, faculty promotions, programme launches, special-leave approvals.
Inter-campus accounting, period close, audit log, NAAC-ready statements. UGC-grant tracking.
Multi-cadre payroll (7th pay commission), PhD scholar stipends, retirement pensions, contractual faculty.
Bulk affiliated-college enrolment, roll-list intake, exam-form submission, result publishing.
University-level placement KPIs across all campuses + affiliated colleges. NAAC §5.2 + NIRF data ready.
Every framework. One source of truth.
The data your IQAC, NIRF coordinator, UGC liaison, and Registrar all need — generated from the same database your day-to-day operations run on.
The 5 NIRF metrics — TLR / RPC / GO / OI / PR — populated from the same data you already enter. Year-on-year comparable.
Per-grant project ledger, expense vs sanctioned, utilisation certificates, settlement reports — exportable in UGC formats.
Track multi-disciplinary credit accumulation, lateral entry, multiple-exit options. Aligned to UGC's NEP-HE guidelines.
Credit accumulation per student per semester, hand-off to ABC portal in the prescribed JSON schema. Field for ABC ID on student profile.
Self-Study Report data points pre-populated — faculty/student ratios, research outputs, placement %, extension activities.
Annual AISHE submission via one-click CSV in the column order the AISHE portal expects.
What Vice-Chancellors and Registrars ask
How does the multi-campus model work technically?
Each campus is a sub-organisation inside the university account. Staff and admins can be scoped to one campus (default) or to the university level (rollup view). Data isolation is enforced via the assignment table — a campus-scoped admin physically cannot query another campus's records.
Can affiliated colleges live in our account or do they each need their own?
Both work. Small affiliated colleges (under 500 students) live as sub-organisations under the university umbrella with separate logins. Larger affiliated colleges that want their own ERP get their own School Console account; the university then ingests their roll lists and exam forms via API.
Does the exam-controller workspace handle our re-evaluation and supplementary processes?
Yes — re-evaluation, revaluation, supplementary exams, exemption requests, and grace-mark policies are all modelled. Workflow state machine: request → fee-paid → routed-to-evaluator → graded → result-revised → notification.
How does grant accounting work?
Each grant is its own project under Finance & Accounts. Expenses are tagged to the grant + activity line. Utilisation certificates and settlement reports generate from the project ledger. Maker-checker is mandatory on every voucher.
Where does our data physically live?
Each customer university gets its own dedicated database. For universities, we typically deploy in your preferred Indian region (Mumbai, Hyderabad, or Chennai). Per-customer data residency is configurable. More on data isolation →