Most of the value lost in an HRMS is lost after go-live. The system is set up, payroll runs, and then nothing changes for 2 years. Half the modules stay switched off and HR carries on with the spreadsheet beside them.
Why does adoption stall after go-live?
Because the project ends. The roll-out had a plan, a deadline and an owner. Day-to-day use has none of those, so it drifts back to whatever people did before.
The fix is dull. Name an internal owner after go-live, not just during it, and give them a quarterly review date.
Which modules get left switched off?
| Module | Why it stalls |
|---|---|
| Self-service | Never properly announced, so staff keep emailing HR |
| Performance | Cycle never set up, so appraisals stay in spreadsheets |
| Reporting | Nobody was shown how, so every question becomes a ticket |
| Document writing | Letters still written by hand from an old template |
| Asset register | Started at go-live, never kept up |
None of these fail on tech. They fail because no one owned switching them on.
What makes self-service actually stick?
Turning off the alternative. While staff can still get a payslip by emailing HR, a share always will, and HR keeps answering.
Announce the change, give it 2 weeks, then route payslip and leave-balance requests back to self-service with a link. Adoption is a decision, not a feature.
What should HR stop doing manually?
Three things, in order of hours saved. Leave-balance questions. Payslip reissues. Statutory register prep.
The third is the biggest and the least visible. PF at 12% with a 15,000 ceiling, ESI at 3.25% employer and 0.75% employee up to 21,000, and statutory bonus between 8.33% and 20% each produce a register, on their own cycle. Rules sit with the Employees Provident Fund Organisation and the Employees State Insurance Corporation.
Why does data quality decay?
Because nobody owns it after migration. Bank details change, addresses change, dependants change, and the record quietly goes stale.
That matters more than it sounds. ESIC says "ESIC provides monthly payment apportioned among dependants in case of death due to employment injury." A dependant record nobody refreshed is discovered at the worst moment.
What does a stale record actually cost?
A benefit nobody can claim. ESIC says "ESIC provides 100% of average daily wages in cash up to 26 weeks in confinement and 6 week in case of miscarriage, during maternity leave and 12 weeks for commissioning mother and adopting mother."
That pays out on records your HRMS holds. If the enrolment lapsed or the KYC never matched, the gap shows up as a refused claim rather than a system error.
What should a quarterly review cover?
- Which modules are live, and which are still off
- Self-service usage: how many requests still arrive by email
- Data quality: missing KYC, stale bank details, unfiled nominations
- Statutory filings made on time, by stream
- One process to hand over before the next review
One page, four times a year. That is the difference between an HRMS that pays for itself and one that became a more expensive spreadsheet.
How do you measure whether it is working?
Count HR hours spent on routine requests, payroll corrections per cycle, and days to close month-end. All three should fall, and if none of them has after 2 quarters, the system is not the problem.
ESIC also says "ESIC provides reasonable Medical Care for self and family from day one of entering into insurable employment", so enrolment speed is a measurable outcome too. The wider framework is published by the Ministry of Labour and Employment, and what the modules cover is on complete HRMS.