Suppose a services company that, in the spring, replaced its payroll software, its time tracking tool and its leave forms with a single HRIS. By the autumn, absence requests are still reaching the human resources department on the old form. Annual reviews are being held outside the tool, and payroll administrators are re-entering what the system was supposed to send them. The project, for its part, is closed.
HRIS change management brings together the actions that lead employees, managers and HR administrators to carry out their human resources transactions in the new tool, and to stop carrying them out elsewhere. It differs from that of another project on four points: payroll imposes its timetable, the data are those of the employees themselves, managers inherit administrative transactions, and staff representatives are involved. Each can explain the situation described, and each is checked before acting.
Disengagement shows in payroll before it shows in log-ins
The number of log-ins tells you little. An employee who opens the portal each month to view their payslip counts as a user, even if they still book their leave on the old form. The useful measurement is made transaction by transaction: for each transaction the HRIS was meant to carry (absence, time, bank details, expense claim, annual review), what share goes through the tool, and what share through another route?
These other routes leave traces with payroll administrators: a spreadsheet of variable items received outside the tool, adjustments carried over to the following payslip, approvals bundled together in the hours before closing.
The record is made by population, because the lead differs. A gap concentrated among field employees, without a computer, points to access. Among managers, it points to workload. Among administrators, to confidence in the calculation.
Payroll falls due every month, whether the tool is mastered or not
Payroll is calculated on a fixed date, for the entire workforce. An error shows on a payslip, that is, on an income. An employee whose absence has been wrongly counted or whose bonus has been omitted may conclude that the tool gets things wrong, and say so to those around them.
A payroll administrator who has no proof that the calculation is correct has reasons to keep their checks and their files, which sustains double entry. The check therefore concerns what the project gave them: a payroll calculated in parallel, in the old and new systems, with discrepancies explained one by one; a published calendar of entry deadlines; a support desk on closing days.
Article L. 3243-2 of the French Labour Code allows the payslip to be issued in electronic form “unless the employee objects”. The project draws a practical consequence from this: plan how the payslip will reach those who object.
The question “who sees what” left unanswered
An HRIS brings together in a single database remuneration, absences, appraisals and family circumstances. Some of these data may fall within the special categories of Article 9 of Regulation (EU) 2016/679 (GDPR), which covers in particular data concerning health and data revealing trade union membership. Before asking how to do something, an employee may want to know who will see what they enter.
If the project has not answered, mistrust shows in optional fields left empty, supporting documents handed over in person, self-assessments reduced to a single line. Article 13 of the regulation lists the information owed to the person when data are collected from them, including the purposes of the processing and the recipients. Its Article 35 requires an impact assessment when the processing is likely to result in a high risk to the rights and freedoms of natural persons: the assessment is carried out with the data protection officer, where one has been appointed. Under French law, Article L. 1222-4 of the Labour Code prohibits collecting information personally concerning an employee by means of a system that has not previously been brought to their attention.
The remedy comes down to a short table: for each family of data, who has access, for what use and for how long. The configured access rights must still match it.
The manager, an HR front desk without having been prepared for it
The HRIS shifts work. Transactions that the human resources department used to handle come back to the manager: approving absences and time, opening reviews, approving a training request. For them, the tool remains occasional, and each annual campaign can feel like the first time.
Three checks locate the cause. Has the manager been trained in their own transactions, or only invited to the general presentation? Can they delegate approval during their leave? Do they know what happens to a team member’s payslip if they do not approve before the deadline? A negative answer is enough to explain bulk approvals.
The response goes through user training, which we include in our change management engagements: short sequences, one per transaction, offered at the moment the transaction comes up, such as at the opening of the review campaign. It also goes through configuration: delegations, reminders, approval from a phone for field managers.
The works council brought in after the solution has been chosen
An HRIS falls, in principle, under automated personnel management processing. Article L. 2312-38 of the French Labour Code provides that the social and economic committee (CSE) is informed of such processing prior to its introduction in the company. It also provides that the committee is informed and consulted, before the decision to implement, on the means or techniques allowing employees’ activity to be monitored, which a time tracking module may be. Article L. 2312-8 also lists among the subjects for consultation the introduction of new technologies and any major change altering working conditions. The Ministry of Labour’s guidance sheets present these powers as those of the committee in companies with at least fifty employees. Assessing a project against these texts is a matter for the human resources department and its lawyers.
Beyond the obligation, elected representatives can ask early the questions that employees will ask after go-live: what the tool records, who consults it, what becomes of the administrators’ jobs. A committee brought in on a tool that is already configured has little influence left over these answers. The check is a date: that of the first presentation to the committee, compared with that of the choice of solution.
Resuming HRIS change management after go-live
The remedies follow the human resources calendar, and the effort grows with the deadline.
Before the next payroll close come the adjustments: deadlines published, delegations opened, support desk staffed, record of what the administrators re-enter.
Before the next campaign, the effort focuses on people: train managers in the transaction they are about to carry out, publish the “who sees what” table once access rights have been checked, announce the date on which the department will stop processing requests received outside the tool, except for employees who have no access to it.
Before the next module or the next wave, the project is taken up again: presentation to the committee before any choice, parallel payroll, roll-out module by module starting with the one on which the payslip depends.
These remedies fit within the overall arrangements of change management, presented on that service’s page. When the HRIS covers several companies, the order of the waves and the trade-offs between modules fall under programme management. For building the messages, see our method for the project communication plan; for objections that persist, our reading of resistance to change.
An HRIS is adopted in the month when payroll is calculated, with no re-entry, from what employees and managers have entered themselves. The payroll department alone can observe it: it is the department the steering committee should be asking.