What is the difference between this and the ERMS product?+
HRMS runs the processes — recruitment, attendance, leave, workload, payroll, appraisal, exit. ERMS is the permanent record of what those processes produced, held under retention and audit rules that outlive any employment. The practical test: if you are asking "how much leave does she have left this year", that is HRMS. If you are asking "produce her complete service history, every posting and increment, with evidence, for a pension query in 2041", that is ERMS. Most institutions need both, and they share one staff identity so nothing is entered twice.
Can it handle guest faculty paid per period?+
Yes, and it is one of the reasons this exists as a separate product. Sessions actually delivered come from the timetable and the substitution record rather than from a register someone maintains, rate cards are per faculty member and per activity type, and the payout runs in the same payroll cycle as permanent staff with the correct statutory treatment applied to each.
Our leave rules came from government service rules and were then amended by our trust. Is that configurable?+
That is the normal case rather than the exception, and it is why the leave engine is rule-based rather than template-based. Accrual, carry-forward, lapse, encashment, half-pay treatment, and vacation-department entitlement are all configured per staff class. We ask for your service rules document during scoping and encode from it directly.
Do we have to use your ERP for workload to work?+
No, but it is easier. With our ERP the timetable is already there and workload is derived with nothing entered twice. Without it, the timetable is imported on a schedule and everything downstream — load, substitution, guest payout — works the same way. What does not work is maintaining the timetable in two places, and we would not recommend it.
Will payroll match what we pay today?+
That is the acceptance criterion. Two full cycles run in parallel with your existing payroll and are reconciled to the rupee before cutover. Where they differ, the differences are almost always an existing manual correction that nobody documented, and finding those is a genuine benefit of the exercise.
Can staff see their own workload and leave balance?+
Yes, and it removes a large volume of HR queries. Staff see their live workload against the ceiling, leave balance and history, payslips, appraisal status, and training record. What they cannot see is anyone else's, including within their own department.
How does it handle multiple campuses under one trust?+
One staff identity, scoped postings. Someone teaching at two campuses holds one record with load and attendance at each, and one payroll. The trust sees consolidated cost and strength; each principal sees their own institution. Transfers between campuses are recorded as postings rather than as a resignation and a new appointment, which matters for service continuity.