Institutional operations
The services around the classroom: stores, hostel and mess, transport, complaints and correspondence.
Built for the people who run it
- Administrative officers
- Stores and purchase sections
- Hostel wardens
- Estate and maintenance teams
What usually prompts the call
- Stock and issues are recorded in registers that cannot be reported on.
- Maintenance and other complaints are raised informally and closed without a record.
- Hostel, mess and transport are run apart from the fee heads that pay for them.
What it does
Which of these are included in a deployment is set out in the proposal for that institution.
Stores and inventory
Purchase, issue and stock position across departments, laboratories and hostels.
Hostel and mess
Management of residential facilities, linked to academics, finance and purchase.
Transport
Allotment, logging and payment for official transport.
Complaints
Maintenance, academic and other complaints from students, faculty and staff, tracked to closure.
Grievance redressal
Student grievances with configurable workflows, a restricted queue for sensitive matters, and reports.
Dispatch
Inward and outward correspondence registers.
Conferences
Registration and administration for institutional conferences and seminars.
How it runs, start to finish
An illustration of a typical sequence. Your own process is configured during implementation.
A department raises an indent or a complaint.
The responsible section acts on it and records the action.
Stock, allotments and charges update.
Reports show position and pending items.
What institutions have said
Excerpts from signed letters. Each is dated; follow the link to read it in full.
We are satisfied with the operation of OLT Campus software & Support / Services provided by the company.
Read the case study
Frequently asked
Do we have to take every module?
No. Institutions take the modules that address their current problem and add others later. Which modules are included is set out in your proposal; nothing on this site should be read as meaning every module is part of every deployment.
What does the software cover?
Admissions; academics and student administration, including electives, examinations, grading and transcripts; fees and finance; HR and payroll; institutional operations such as stores, hostel and transport; and placement and executive education. Each area is described on its own solution page.
Can it be adapted to our ordinances and regulations?
Much of what varies between institutions is configuration that your own staff control: the admission form, scoring criteria, fee structures, grade scales and curves, elective rules and feedback forms. Where a regulation needs something the standard modules do not do, we assess it as customised development and say so in the proposal.
See operations with your own workflow
Tell us how your office works today and the demonstration will follow that.