Why HRMS Implementations Slip, and What Readiness Actually Requires
Author: Shabbir Kazmi, Head of Operations, gulfHR · Last reviewed: 19 August 2026
Applies to: UAE, Saudi Arabia and the wider GCC, plus Iraq, Egypt and North Africa. Country requirements are labelled individually throughout.
The short answer
An HRMS implementation rarely slips because the software was hard to configure. It slips because the decisions and the data your organisation owns arrive late, and because the people who will use the system were not brought along in time. Readiness means five things settled before kickoff: the organisational and legal entity structure, employee master data, payroll and leave policy decisions, approval and delegation chains, and a named sponsor with a case for change.
Most HRMS implementations do not slip because the software was hard to configure. They slip because the decisions and the data your organisation owns arrive late, and because the people who will use the system were not brought along in time. Legal entities nobody confirmed. Employee records with gaps. A leave policy still under debate. Configuration moves quickly once those inputs are settled. This article sets out where the time actually goes, and what we mean when we say an organisation is ready.
What the research shows
The best evidence on HR system projects comes from the Sapient Insights Group 27th Annual HR Systems Survey, covering 3,318 organisations across 59 countries and more than 25 million employees. Two findings from it shape everything below.
First, structured change management separates the projects that land from the projects that drift. Organisations running an adaptive change approach were roughly twice as likely to exceed expectations on budget (23% against 8%), on adoption (20% against 8%) and on timeline (18% against 8%) as those running change work sporadically. Second, almost half of organisations were not running it properly at all: 39% described their approach as sporadic with no criteria, and a further 9% had no plans.
The funding gap is starker. Only 7% of organisations allocate the recommended 20% of an initiative’s budget to change management. Nearly a quarter reported that their project did not meet adoption expectations.
The pattern repeats in adjacent enterprise programmes. ISG research published in February 2026, based on 200 senior decision-makers at large global companies, found nearly 60% of SAP migration projects running late and over budget, with underestimated complexity, scope expansion and a poor grasp of internal constraints named as the causes. Gartner adds the data dimension: 59% of organisations do not measure data quality at all, and Gartner identifies inconsistency in data across sources as the most challenging data quality problem organisations face.
None of that describes a software defect. All of it describes readiness.
Where HRMS implementation time actually goes
An HRMS implementation runs through five stages. We share ownership with you throughout, but the first two stages rest almost entirely on decisions and data your team supplies, and everything downstream inherits their quality. The nine HRMS implementation success dimensions we publish separately describe the same project from the delivery side.
Where HRMS implementation time is actually lost. Source: gulfHR, Preparing for Your HRMS Implementation: A Readiness Guide (2026), prepared by Shabbir Kazmi, Head of Operations.
Five reasons HRMS implementations slip
1. Employee master data is treated as an export, not a decision
Pulling a headcount file from your existing system takes an afternoon. Reconciling it takes weeks, because several fields that look administrative are carrying the structure of the whole system.
Employee ID is the primary key that every other record and transaction references. Reports To builds the approval hierarchy for leave, expenses and every workflow that follows. Cost Centre determines whether finance can allocate payroll cost correctly from the first run. An error in any of the three does not stay where you found it. It travels into approvals, into reporting, into payroll allocation, and each correction sends work back into configuration.
Gartner’s point about inconsistency across sources is exactly what this looks like in practice. The HR system names one manager, the payroll spreadsheet names another, the org chart in the shared drive names a third, and all three were correct at some point. Deciding which one is now authoritative is a business decision. We can help you structure it, but we cannot make it for you. This is the same ground covered in our note on employee-record integrity in the GCC.
2. The organisation model does not match the legal reality
This is the gap that surfaces latest and costs the most.
Organisations usually model themselves in an HRMS as a single company, because operationally that is how they behave. In practice they sponsor employees under several legal entities, and payroll disbursement is regulated at entity level rather than at group level. The mismatch stays invisible until the first payroll file has to be split by sponsoring entity, and by then the employee master data has to be revisited under time pressure. We have written separately about managing payroll across multiple entities.
Capture the sponsoring entity as a field in its own right, separate from the operational company, while you are still preparing data. Everything else can continue to run under one consolidated setup, and disbursement files can be produced per sponsor. Adding that field before kickoff costs an afternoon. Retrofitting it costs a phase.
3. Policy decisions get deferred into configuration
We cannot configure “we will decide that later.” The decisions that most often stall a build are these:
- Leave carry-forward and encashment rules, and whether they differ by grade, entity or country
- The end-of-service or severance rule applied to each employee population
- Which employees are included in or suspended from payroll runs, and what triggers the change
- Whether an employee’s time is tracked, and whether attendance data feeds payroll calculations
- Approval and delegation chains for leave, payroll changes and self-service requests, including escalation
Every one of these has a defensible answer and none of them has a default. Left open at kickoff, each becomes a blocked configuration task, and blocked configuration tasks are what move go-live dates.
4. The organisation is not prepared for the change
An HRMS changes how people work. Managers who approved leave by email now approve it in a system that records the decision. Employees who asked HR for a payslip now retrieve it themselves. Payroll teams who reconciled in spreadsheets now work to a validation calendar. Every one of those is a behavioural change, and behavioural change needs resourcing in the same way data migration does.
Most organisations underfund it. As the Sapient Insights survey found, only 7% allocate the recommended fifth of an initiative’s budget to change management, while 39% run change work sporadically against no criteria at all. The consequence shows up in adoption: nearly a quarter of organisations reported that their project fell short of adoption expectations.
Your people are also arriving with less appetite for change than they had a decade ago. Gartner data reported in Harvard Business Review shows the average employee faced two planned enterprise changes in 2016 and ten by 2022. Over the same period, willingness to support enterprise change fell from 74% to 43%. As the authors put it, “relentless sprinting means many employees are running on fumes.” An HRMS rollout is not landing on a blank page. It is joining a queue.
Two things make the difference, and both are inexpensive relative to what they protect.
Visible sponsorship
Prosci reports that 79% of projects with extremely effective sponsors are likely to meet objectives, against 27% where sponsorship is ineffective. Sponsorship here means a named senior leader who explains why the change is happening and stays visible through the difficult middle of the project, not a name on a steering slide. It is the same discipline that decides whether an HR digital transformation gets past its first quarter.
Clear ownership of decisions
Implementations move fastest when each category of decision has one accountable person, identified before kickoff rather than discovered during it.
| Role | Owns |
|---|---|
| Project Sponsor | The decision on scope, timeline and priorities, and the visible case for why the change is happening |
| HR Data Owner | Employee master data, organisational structure and leave policy |
| Payroll Lead | Salary structures, wage protection submissions and statutory details |
| IT / Systems Contact | System access, integrations and technical questions |
Table 1. The four decision owners an HRMS implementation needs named before kickoff.
Where these roles sit with nobody in particular, decisions circulate instead of resolving. That circulation never appears on a project plan and always appears in the go-live date.
Practically, the change work that pays for itself is modest: tell people what is changing and when, before they hear it informally; train managers and approvers before you train everyone else, because they set the tone; plan the retirement of the spreadsheets and side-trackers the old process depended on, since a workaround that survives go-live tends to survive permanently; and measure self-service adoption in the first quarter rather than assuming it.
5. The region is treated as one payroll environment
The Middle East is not a single regulatory environment, and planning an implementation as though it were is a reliable way to lose a quarter. This is the case we set out in more detail on multi-country payroll as a control requirement.
The table below sets out statutory models an HR and payroll system may have to hold at the same time. Three of the five rows are the same country.
Statutory models one system may have to hold at the same time
| Jurisdiction | What the system must hold | Effective date and source |
|---|---|---|
| UAE, mainland (MoHRE) | End-of-service gratuity under Federal Decree-Law No. 33 of 2021: payable after one year of continuous service, calculated on the basic wage, with total gratuity capped at two years’ wage. Wages paid monthly through the Wage Protection System. | In force; UAE Government portal, MoHRE |
| UAE, voluntary alternative end-of-service scheme | Employer contributions of 5.83% of monthly basic salary for employees with under five years’ service, and 8.3% at five years or more, paid into an accredited fund. Voluntary, and employers choose which employee categories participate. | Effective 1 November 2023; ILO, April 2024 |
| UAE, DIFC | DEWS, or a certified qualifying alternative, is mandatory for DIFC employers: minimum 5.83% monthly for employees with under five years’ service, 8.33% at five years or more. Gratuity accrued before the scheme started remains payable. | Effective 1 February 2020; Mercer, January 2020 |
| Iraq | Social Security Law No. 18 of 2023: employer 20% and employee 5% outside oil and gas, 25% and 5% within it. Contributions calculated on base pay plus all allowances, capped at five times the minimum wage. | Signed 3 December 2023; WTW, April 2024 |
| Egypt | Social insurance at 18.75% employer and 11% employee, on an insurable salary between EGP 2,700 and EGP 16,700, with thresholds rising 15% each 1 January. | Thresholds effective 1 January 2026; PwC Worldwide Tax Summaries, reviewed 4 February 2026 |
Table 2. Five statutory end-of-service and social insurance models across three countries. Three of the five rows are the UAE.
An organisation with staff on the UAE mainland, in the DIFC, and enrolled in the voluntary alternative scheme is already running three end-of-service models inside one country. Add an Iraq branch and an Egypt entity and the system is holding five statutory models against a single employee master file. Identify that during discovery and we build for it. Identify it during testing and we rebuild for it.
Verify country requirements before relying on them
Verify country requirements against the relevant national authority for your own entities and employee categories before relying on them. Rates, thresholds and scheme rules change, and free zones and sector-specific regimes frequently sit outside the national rule.
What HRMS implementation readiness actually looks like
Readiness is not one milestone. Different inputs are needed at different points, which means you can sequence the preparation rather than attempt all of it at once.
| Area | What to prepare | When it is needed |
|---|---|---|
| Organisational structure | Legal entities, branches and cost centres; department hierarchy; reporting lines and job grades | Before kickoff |
| Employee master data | Personal and employment details for all active employees; national ID, passport, visa and labour card details; joining dates and current reporting manager | Before kickoff |
| Payroll and compensation | Salary structures, allowances and deductions; pay grades and compensation policy; wage protection and bank account details | Structures before kickoff; bank and wage protection details before the first payroll run |
| Leave management | Leave types and entitlement policy; carry-forward and encashment rules; approval chain by department | Before kickoff |
| Statutory and compliance | Social insurance and wage protection registration details; end-of-service policy; nationalisation targets where applicable | Before kickoff |
| Approval workflows | Approval hierarchy for leave, payroll changes and self-service requests; delegation and escalation rules | Before kickoff |
| Change and communications | Named sponsor and the case for change; communication plan by audience; manager and approver training plan; the list of manual trackers being retired | Sponsor and case before kickoff; the rest during configuration |
| Time and attendance | Shift patterns and attendance rules; biometric or access-control integration details, where applicable | During configuration |
| System access and roles | System users and role-based access requirements; employee self-service rollout plan | During configuration |
Table 3. HRMS implementation readiness checklist by area, and when each input is needed.
Almost everything on that list that must be ready before kickoff is a decision or a policy rather than a data file. The data files are the easier part.
gulfHR expert view
expert view
Shabbir Kazmi, Head of Operations at gulfHR, built the readiness checklist this article draws on, after running implementations across the region. Three observations from that work:
The organisation model is the most common late discovery. Companies describe themselves as one entity because that is how they operate day to day. The visa sponsor, the payroll disbursement entity and the operational company are frequently three different things. Capturing them as separate fields before kickoff avoids reworking employee master data mid-build.
Optional fields are rarely optional in practice. Passport and visa details are not required to go live. Organisations that load them anyway gain two things a spreadsheet cannot easily give them: automated reminders before documents expire, and one structured record in place of a tracker maintained outside the system. The same holds for home airport and ticket entitlement, where periodic flight entitlements are employer-funded and would otherwise be calculated by hand.
The readiness conversation belongs before the contract, not after it. Teams that receive the data and decision requirements while they are still evaluating vendors have months to prepare. Teams that receive them at kickoff have weeks, and they are doing the work on top of a full operational load. That is why we share this guide early, whether or not you go on to implement with us.
Where gulfHR fits
gulfHR is designed to help organisations manage HR, payroll, leave, employee self-service, approvals and reporting across multi-entity and multi-country environments, including setups where employees are sponsored under several legal entities within one operational company. Where configured, gulfHR can generate payroll disbursement files separately per sponsoring entity while the rest of the organisation continues to run under a single consolidated structure. The same control set underpins our enterprise HR and payroll platform.
Module scope, country coverage, integration feasibility and statutory configuration should be confirmed during scoping, against your own entities, employee categories and jurisdictions. That is what the discovery stage is for. If you are still comparing vendors, our buyer’s checklist for HR, Finance and IT covers the selection stage that precedes this one.
Frequently asked questions
How long before kickoff should we start preparing for an HRMS implementation?
Start while you are evaluating vendors, not when you sign. Organisational structure, employee master data, leave policy, approval chains and statutory registration details are all required before kickoff, and each one involves an internal decision rather than a system export. Beginning early turns them from project blockers into ordinary business decisions.
What is the single most common cause of HRMS implementation delay?
Employee master data that is incomplete or inconsistent across sources, followed closely by an organisational model that does not match the legal entity structure. Both tend to surface during build or testing, which is the most expensive point to find them.
How much should we budget for change management?
Research from the Sapient Insights Group HR Systems Survey points to around a fifth of the initiative budget, and finds that only 7% of organisations reach that level. Organisations running structured change work were roughly twice as likely to exceed expectations on budget, adoption and timeline as those running it sporadically.
Do we need passport and visa data to go live?
No. Those fields are not required for go-live. Loading them enables automated expiry reminders and removes the need for a separate document tracker, which is why most organisations choose to include them.
We operate in several countries. Can one system handle that?
It depends on the jurisdictions and employee categories involved, and it should be scoped explicitly. What does not work is assuming a single regional configuration. As the comparison above shows, the UAE alone can require three different end-of-service models, and Iraq and Egypt are separate again.
Who needs to be involved from our side?
At minimum a project sponsor, an HR data owner, a payroll lead and an IT or systems contact, each with named decision authority. Shared or unassigned ownership is a common and avoidable cause of delay.
Take the next step
Preparing for Your HRMS Implementation: A Readiness Guide
Preparing for Your HRMS Implementation: A Readiness Guide for the full readiness checklist, the stage-by-stage timing, and the field-by-field employee master data appendix. Written by Shabbir Kazmi, Head of Operations at gulfHR, and built to be useful whether or not you implement with us.
Sources
- Sapient Insights Group, 27th Annual HR Systems Survey Report, Adaptive Change and Implementations segment, November 2024. Survey of 3,318 organisations across 59 countries, fielded May to June 2024 (accessed 19 August 2026).
- Cian O Morain and Peter Aykens, Employees Are Losing Patience with Change Initiatives, Harvard Business Review, 9 May 2023, citing Gartner data (accessed 19 August 2026).
- Prosci, Change Management Success, drawing on Best Practices in Change Management research (accessed 19 August 2026).
- ISG research on SAP migration outcomes, reported by The Register, 5 February 2026 (accessed 19 August 2026).
- Gartner, Data Quality: Why It Matters and How to Achieve It (accessed 19 August 2026).
- UAE Government, End of service benefits for employees in the private sector, Federal Decree-Law No. 33 of 2021 (accessed 19 August 2026).
- UAE Ministry of Human Resources and Emiratisation, Wages Protection System (accessed 19 August 2026).
- International Labour Organization, UAE introduces voluntary pensions to replace end of service indemnities, 8 April 2024 (accessed 19 August 2026).
- Mercer, UAE: Savings plan effective 1 February for DIFC employees, 28 January 2020 (accessed 19 August 2026).
- WTW, Iraq: Changes to the social security retirement program, 22 April 2024 (accessed 19 August 2026).
- PwC Worldwide Tax Summaries, Egypt: Individual, Other taxes, reviewed 4 February 2026 (accessed 19 August 2026).
- Shabbir Kazmi, Head of Operations, gulfHR, Preparing for Your HRMS Implementation: A Readiness Guide, 2026.
Author: Shabbir Kazmi, Head of Operations, gulfHR. Last reviewed 19 August 2026.