The register, the fee counter and the hostel gate, on one system
Elevate ERP runs the administrative work of a college: departments and streams, a subject catalogue with credit hours, student records, fee instalments collected into your own bank account, exam datesheets and a marks ledger, attendance on the register and at a fingerprint reader, and a hostel with roll call and outpasses. Below is what it does, in enough detail to check in a demo — and then, in the same shape and the same size, what it does not.
What a college gets
Every line below names something you can open in a demo and watch work. Where a capability needs a key, a merchant account or a piece of hardware you supply, the row says so in its own sentence rather than in a footnote.
Departments, streams and a subject catalogue
Group staff and subjects into departments, and define streams or programmes with their own code and the class level they apply from, so a class belongs to a stream rather than to a spreadsheet. The subject catalogue records each subject with an auto-generated code, whether it is core, elective, lab or extracurricular, its credit hours, its department, and every class it is taught to. Credit hours are recorded and shown on the subject; nothing aggregates them into a total or a grade point.
A session divided into terms you name yourself
Set up the academic session once, then divide it into named terms with their own start and end dates — call them semesters, trimesters or anything else, because the name is yours to type. A term that ends before it starts is refused, terms that overlap are flagged on the timeline, and the session carries its own holiday bank with working days computed from what you entered rather than counted by hand. A closed session can be cloned to seed the next one.
Student records, and enrolling a department from a spreadsheet
One admission form creates the student and the linked family record together — father, mother, a separate guardian where there is one, address, blood group, allergies, emergency contact, and the previous institution with its transfer certificate number. Roll numbers come from a transactional counter, held per section and per session, that cannot hand the same number to two students. Bringing a whole department over from a spreadsheet maps your columns, validates every row before anything is written, flags duplicates, and hands the failed rows back for correction instead of dropping them. At session rollover a terminal class is moved to alumni status on the record — a state on the student, not a separate directory.
Fee instalments, concessions, and an amount the browser cannot change
Fee heads per class, each on its own frequency and due day, each able to carry a late-fee rule with a grace period, a flat or percentage charge and a cap. Hostel, transport and lab fees are opt-in heads, so they bill only the students who took them. Concessions are recorded by type — scholarship, sibling, staff ward, category, merit — as a percentage or a fixed amount with an optional ceiling. When an online payment starts, the server reads the demand and refuses unless the requested amount equals the outstanding balance to the paisa, and the gateway callback is verified with an HMAC-SHA256 signature under a constant-time comparison before any receipt is written. Every payment produces a numbered receipt PDF, on A4 or an 80mm thermal roll, reprints watermarked DUPLICATE, numbered from a single counter so there are no gaps. Online collection runs through your own Razorpay, PhonePe or Paytm merchant account, entered in fee settings, so settlements land in your bank rather than ours.
Exam datesheets that refuse to clash, and a marks ledger with a lease
Create an exam, pick the classes sitting it, and build the datesheet paper by paper with each paper’s date, start time, duration and maximum marks. Two papers on the same class at the same time will not publish — the datesheet is blocked, not warned about — and any two papers for the same class less than about a day and a half apart are flagged while you are still editing. The published datesheet downloads as a PDF. Marks are entered on a keyboard-driven grid with absence marked where a student did not sit the paper, and the ledger takes a lease: a second teacher opening the same class and subject sees who holds it and can only take over explicitly, stamped into the record. Finalising moves the exam into results-pending-approval so marks stop changing under a result being checked, and it can be unlocked for a correction. The marks ledger is one of sixteen reports that export to Excel or PDF.
Attendance on the register, and at the gate
Mark a class on the keyboard across six states — present, absent, late, half day, leave, medical — with anyone left unmarked treated as present, so a full class takes one pass. A monthly register per class prints for checking. Students below three quarters of the working days are listed, and one press produces a warning letter as a PDF to the guardian on the record, or a ZIP for the whole list; that three-quarter threshold is fixed in the software. Approved leave sits on the same record, so a shortfall figure reflects absence that was authorised. Separately, fingerprint readers of the ZKTeco and eSSL lineage push punches straight in over the iClock protocol they already speak, acknowledged with a count so the reader retries what was not accepted, and one person’s actual punch chain can be walked when a mark is disputed. That needs a compatible reader on your own network; none is supplied with the software.
Hostel: beds, an evening roll call, and outpasses
Set up buildings and rooms, then allocate a specific bed to a named student, filtering the room list to available beds or to rooms at capacity so a warden finds a free bed without reading the whole list. Roll call runs against the students allocated to each room, and a resident marked absent with no outpass covering that night raises a curfew breach the warden sees and resolves under their own name, with the resolution note kept. Outpasses record where a resident went and when they are due back; a home visit needs both the warden’s sign-off and the parent’s consent, and that consent is recorded by the member of staff who took it, at the desk, by phone or in writing — there is no parent link and nothing grants it automatically.
Timetable, teacher load and the morning someone calls in
Define the period structure once — how many periods, their timings, the breaks — then build each section’s week against it, so every timetable shares one clock. A teacher booked twice, a class booked twice and a room booked twice are each refused at the point of entry, on every create and every edit. A substitution board covers an absent teacher: pick them, see their classes for the day, assign cover per period, and a substitute who is already busy is refused. Each teacher can read the same week as their own schedule, and teacher load and the substitution log are both standing reports. Filling a section’s week automatically is also available: a deterministic solver places periods over every section at once from the subject allocations your staff actually hold, and reports which subjects it could not place rather than leaving a silent hole — that path runs behind the AI endpoint, so it needs an AI key.
Library, transport, notices and a portal of the student’s own
The library catalogue issues and returns against the same student and staff records the rest of the platform uses, with the loan period, fine per day, grace period, holding limits and renewal count set in settings, and overdue counted on calendar days so a same-morning return is not late. Transport keeps vehicles, drivers, routes and stops, with passengers allocated from the register and a live trip position that comes from the phone travelling in the vehicle — not from fitted tracker hardware, of which none is supplied. Notices are addressed to the whole institution, named classes or sections, individual students, a transport route or a saved group, resolved against live records, with scheduled publishing and automatic expiry. Students sign in to their own portal for timetable, subjects, published results, attendance, fees, library, transport, leave requests and the notices meant for them, and can pay fees there and raise a doubt that lands in a staff inbox.
An AI assistant that does the work inside your own permissions
Ask in plain language and Iris performs the action against your records rather than drafting a message about it — admitting a student, recording a payment, marking a class, entering results. Every action is checked three times before it happens: against the role of the person who asked, against what your subscription includes, and against your institution’s own data boundary; if the role cannot be read for any reason the action is refused rather than allowed, and students are mapped to no staff tools at all. Each change writes an audit row holding the values before and after and who asked for it, and the asker’s own last change can be undone, with the rollback itself logged. It works in a bounded loop and a tool that errors counts as a failure, so it cannot narrate a success over a write that did not land. This needs an AI key — your own from Groq, Google Gemini, xAI or OpenAI, sealed per institution — and with no key configured it says so plainly instead of appearing to work. Separately, the dashboard search bar answers counted questions like enrolment, outstanding fees and who is below the attendance threshold with no AI key at all.
What it does not do for a college
The list a segment page normally leaves out. Some of these were claimed on this page in an earlier version and should not have been; they are withdrawn here rather than quietly dropped. If one of them is the thing your institution actually needs, it is cheaper for both of us that you know now.
No SGPA, no CGPA, no transcript, no credit ledger
This is the plainest way to say it: there is no grade-point machinery in the product at all. Nothing multiplies a mark by a credit, nothing aggregates a grade point for a term, nothing carries a total across terms, and there is no transcript document. Credit hours are recorded against a subject and displayed there, and that is the whole of what happens to them. What comes out of an exam is entered marks, a datesheet and a marks ledger you can export. If your degree audit depends on a computed CGPA or an issued transcript, that work stays where it is today.
No APAAR, no Academic Bank of Credits, no board or government filing
Nothing here talks to APAAR, the Academic Bank of Credits, a university portal, UDISE+, DigiLocker, AISHE or a state MIS. There is no exporter and no API client for any of them, and no identifier from any of them is stored. Reports come out as Excel and PDF for you to submit yourself. Elevate is not affiliated with, endorsed by, certified by or approved by CBSE, the UGC, AICTE, any university or any state authority, and no output of this software has been reviewed by one.
No elective registration and no CBCS course election
A subject can be labelled an elective and reported on as one. What does not exist is any way for a student to choose one: no registration window, no elective group, no rule about how many from which basket, no clash-aware election, no add-drop period. Subject-to-class mapping is done by staff, for the whole class at once. Minor and major tracks with their own credit requirements do not exist either; a stream is a name, a code and the class level it applies from.
No hall tickets, seating plans or invigilation rosters
The datesheet is real and publishes with clash detection. The paperwork around the exam hall is not: there is no admit card or hall ticket, no seating plan, no room allocation for an exam, no invigilation roster, no re-evaluation flow and no compartment or supplementary exam handling. There is also no question-bank-to-paper assembly for a semester paper in this route.
The gate reader does not enforce curfew
Biometric attendance and hostel roll call are both real and they are separate systems. A curfew breach is raised by the warden’s evening roll call — a resident marked absent with no outpass covering that night — and it is the warden’s mark that raises it. A punch at the gate does not clear a resident, and a missing punch does not flag one. Nothing in the biometric module reads hostel allocations and nothing in the hostel module reads punches. If you want the reader to enforce the curfew, that is not what this does.
No mess-fee calculation and no maintenance tickets
A mess fee is a fee head you create and price yourself, on whatever frequency you choose. Nothing counts meals, days in residence, absences or rebates, so no mess bill is computed from consumption. A room or a bed can be flagged as under maintenance so it stops being allocated, and that flag is the entirety of it — there is no ticket, no one to report a fault to, no assignee, no status trail and no queue.
No placement cell and no alumni module
There is no recruitment-drive calendar, no company or recruiter record, no resume builder, no placement statistics and no donation tracking. Alumni is a status a student record moves to when a terminal class graduates at session rollover; there is no alumni directory, no alumni login and no way to reach them from here.
No payslip
Staff records, departments, per-employee salary structures and staff leave against leave types you define are all real. Producing a payslip is not: both payroll calculation paths refuse without a finalised monthly attendance summary, and nothing currently mounts the screen that would finalise one. Treat payroll as unavailable rather than as almost-ready. Statutory deductions are worth naming separately — provident fund, professional tax and TDS are free-text rows an administrator types, with no wage ceiling, no slab table and no computation, so do not read them as statutory compliance.
No parent login, no mobile app, no SMS and no WhatsApp
The one self-service login that exists is the student’s. Guardians are records on the student — named, contactable, addressed on a letter — but they have no accounts, and there is no native Android or iOS app and no push notification. A notice reaches the noticeboard and the student portal; it does not go out as an SMS or a WhatsApp message. Email is real for transactional sends once you have supplied your own mailbox or sending-domain credentials, and until you do the product refuses the send rather than pretending it succeeded.
One institution per deployment, and roles that hide menus
Data is scoped to one institution and Firestore security rules enforce that boundary on the server. There is no campus switcher, so a university with several constituent colleges is several deployments rather than one with a hierarchy above them. And the role model builds each person’s menu from what their role may reach, which is not the same as a check on every screen: several module pages render for anyone who types the URL, and it is the security rules rather than the page that withhold the data.
Elevate ERP is built by Omniflux. There is no named support rota and no response-time commitment; questions go to [email protected]. If anything on this page does not match what you are shown in a demo, that is a defect on our side — tell us and it gets corrected here.
The modules behind this
A college runs mostly from these six. Descriptions are read from the module index, so they cannot drift from what all twelve modules say about themselves.
Students
Admission through to alumni on one record: the admission form, documents, bulk operations for the work that is genuinely bulk, and a student portal students sign into themselves.
Academics
Build the session once — departments, streams, classes, sections, houses and the subject directory — then map curriculum and competencies onto it. Promotion between sessions runs off rules you set rather than a manual re-entry.
Fees
Fee heads, concessions and automated demand generation, then a cashier session that reconciles at the end of the day. A receipt is tied to the demand it settles, so what is outstanding is derived rather than tracked separately.
Examinations
Blueprint a paper, schedule the exam, enter grades on a keyboard-driven grid, and generate report cards from the marks already in the system. Papers can be edited in a Word-style editor and kept in a reusable library.
Hostel & events
Buildings, rooms and beds allocated to named students, with roll call and outpasses for the evening. Events and the school calendar sit alongside it, because both are about who is expected to be where.
Timetable
A grid built against real periods and teacher loads, with conflict detection while you edit rather than after you publish, and a substitution board for the morning a teacher calls in sick.
See it against your own institution
A demo on your departments, your fee heads and your exam pattern — so you can check the receipt and the marks ledger, not a screenshot.