By Margaret Cawley, Your Life Gym HRIS Project Management & People Change
A new HR system is a people project, not just a technology project
I have seen how tempting it is to focus on the new system: the dashboards, the workflows and the promise of less administration. But an HRIS implementation succeeds or fails on what happens around the technology. Are your records accurate? Do payroll and HR agree on the rules? Do managers know what will change? And, crucially, has anyone tested what happens when real life does not follow the happy path?
An HR information system (HRIS) brings employee information and people processes into one place. For a small or growing business, that can mean less duplication, more reliable reporting and a better experience for employees. It can also expose years of inconsistent data and processes. That is why I would rather spend an extra week getting the foundations right than rush towards a date the business is not ready to meet.
Here is the eight-step approach I recommend for UK SMEs, whether you are replacing spreadsheets, moving from one provider to another or introducing HR and payroll integrations for the first time.
Your eight-step HRIS implementation plan
| Step | What happens | What good looks like |
|---|---|---|
| 1. Define the need | Problems, users and requirements | Prioritised must-haves and nice-to-haves |
| 2. Build the case | Benefits, full costs and capacity | Approved budget and accountable sponsor |
| 3. Select the supplier | Demos, security and contract checks | Documented selection and contract |
| 4. Set up governance | Ownership, risks, timeline and privacy assessment | Project plan and risk controls |
| 5. Prepare the data | Clean, map and rehearse migration | Reconciled test migration |
| 6. Configure and connect | Workflows, permissions and integrations | Configured system and tested interfaces |
| 7. Test and prepare people | Real scenarios, communications and training | Evidence-based readiness decision |
| 8. Go live and stabilise | Support, reconciliation and review | Stable service and improvement plan |
1. Start with the problem you want to solve
Before you book a single demonstration, talk to the people doing the work. Ask HR what they repeat every month, payroll what causes errors, managers where approvals get stuck and employees which processes feel unnecessarily difficult. You may find that the real issue is not the absence of a system but the absence of a consistent process.
Turn what you hear into requirements. Separate the essentials — employee records, absence, holiday, access permissions, reporting and payroll data — from features that would be useful but are not critical. Agree who can approve changes to that list. Otherwise, attractive extras can quietly become expensive scope creep.
2. Build a business case that includes people’s time
A licence fee is only one part of the cost. Allow for configuration, integrations, data cleansing, testing, training, support and the time your own people will need to give the project. For a small HR team, that internal capacity is often the biggest hidden risk.
Make the benefits equally practical: fewer manual corrections, quicker onboarding, clearer absence information, better reporting and less time spent chasing approvals. Set a few baseline measures now, so you can tell after go-live whether the change has genuinely helped.
Remember that employment record-keeping duties matter too. Check the current rules that apply to holiday, payroll, pensions and right-to-work records rather than assuming one retention period covers everything.
3. Choose a vendor you can work with, not just a system you like
A polished demonstration tells you what software can do under ideal conditions. Ask the vendor to show you your actual scenarios: a starter joining partway through a pay period, a change in contracted hours, an absence adjustment or a leaver with outstanding holiday. Ask who will resolve issues, how quickly, and what happens if a key integration is delayed.
Treat information security and privacy as selection criteria. Ask where information is hosted and accessed, who the sub-processors are, how access is controlled, and how your records will be returned or deleted when the contract ends. The ICO provides guidance on processor contracts and international transfers, while the NCSC publishes cloud security principles. A UK-hosted system is not automatically the only compliant option; the actual transfer arrangements and safeguards matter.
4. Give the project clear ownership and assess privacy risks early
Someone needs to own the overall result, not just attend meetings. Identify a business sponsor, a day-to-day project lead and decision-makers for HR, payroll, IT and finance. Keep one plan with milestones, dependencies, issues, owners and a clear process for approving changes.
Start privacy assessment early. A data protection impact assessment (DPIA) is legally required where processing is likely to create a high risk to individuals; it is not automatically mandatory for every HRIS replacement. Because employment records can contain sensitive information and new systems may change access or combine datasets, screening for DPIA requirements should be a deliberate step. Where a DPIA is required, complete it before the relevant processing begins.
Set a realistic go-live date, but do not treat the date as the definition of success. Agree what must be true before you can safely proceed — particularly around data, payroll and security.
5. Clean the data before you move it
Data migration is rarely glamorous, but it is where many projects lose time. Duplicate employees, old job titles, missing start dates, inconsistent locations and unclear absence balances do not disappear when you move them into a new system. They simply become more visible.
Audit what you have, decide what genuinely needs to be retained, assign an owner to each data set and map every important field from the old system to the new one. Run a test migration and reconcile the results against agreed totals and samples. Then do it again after corrections. If your migration affects payroll, compare pay-critical fields rather than relying on employee counts alone.
This is also an opportunity to apply your retention schedule and access controls. Moving everything “just in case” is not a sound data protection strategy.
6. Configure the processes and test the connections
Configuration should reflect agreed business rules, not simply copy every workaround from the old process. Check holiday entitlements, approvals, security roles, onboarding steps and reports with the people who own those processes.
Where HRIS data feeds payroll, finance, recruitment or time and attendance, treat every interface as a separate dependency. Agree field mappings, timing, error handling and reconciliation responsibilities. An integration that transfers data successfully is not necessarily an integration that transfers the right data.
7. Test real work, then prepare people for the change
User acceptance testing should reflect the awkward situations that actually happen: backdated changes, starters and leavers, sickness, part-time holiday, changes in pay and exceptions to normal approval routes. Give testers clear scripts and a simple way to record what happened, what they expected and the evidence of a failure.
Track issues by severity. An untidy dashboard is not the same risk as an incorrect pay calculation or inappropriate access to confidential records. Agree who can sign off each workstream and what unresolved issues would stop go-live.
Communication and training deserve their own plan. Explain what is changing, why it matters and what employees and managers will need to do differently. Train managers early enough to practise. Give employees clear instructions and somewhere to get help. People are far more likely to use a system confidently when they have been included in the change.
8. Go live with a plan for the days afterwards
Go-live is a transition, not the finish line. Set up a short period of enhanced support, daily issue reviews where appropriate and named owners for urgent fixes. If payroll is changing or depends on new HRIS data, consider a parallel run and reconcile key outputs before switching off the old process. The number of cycles needed depends on the complexity and risk; one cycle is not a universal guarantee.
Check employee access, manager approvals, reporting and payroll outcomes after launch. Review progress at 30, 60 and 90 days: what is working, what still creates workarounds and what should be improved next? Only retire the old system once data, retention and contractual exit requirements have been addressed.
The go/no-go decision: what I would check
- Critical employee and payroll data have been reconciled and signed off.
- High-risk defects are resolved or have an explicitly accepted, workable mitigation.
- Security permissions and privacy controls have been tested.
- Payroll, HR and operational owners agree the process is ready.
- Managers and employees know what to do and where to get help.
- A support plan, rollback or contingency approach and clear decision-maker are in place.
A strong project team does not pretend every issue has vanished. It makes the remaining risks visible, decides who owns them and can explain why the business is ready — or why a short delay is safer.
Frequently asked questions
How long does an HRIS implementation take?
There is no single timetable. A straightforward employee-records system can be quicker than a programme involving payroll, scheduling, recruitment and multiple integrations. The quality of your starting data, the vendor’s availability and the time your people can dedicate will shape the plan. Build contingency around migration, testing and sign-off.
Do we need a DPIA for a new HR system?
Not automatically. You must carry out a DPIA where the proposed processing is likely to result in a high risk to people. Screen the project early, document the decision and complete a DPIA if the risks and processing activities require one. It is often useful good practice even when not legally mandatory.
Should the HRIS connect to payroll?
Often, yes — a well-designed integration can reduce rekeying and errors. But it needs careful mapping, testing and reconciliation. Pay-critical data should have clear owners and a reliable way to identify and correct exceptions.
What happens to our data if we move systems again?
Ask this before signing. Your supplier agreement should explain how information can be exported, returned or deleted, including arrangements for backups and sub-processors. Test whether the available export format would actually be usable.
How Your Life Gym can help
At Your Life Gym, I bring together HR and organisational development experience with hands-on HRIS project management and change delivery. That means looking beyond configuration to the people, processes, payroll dependencies and decisions that determine whether the system works in practice.
I support London and UK businesses with requirements, vendor coordination, project governance, migration readiness, user testing, communication and go-live planning. If you are considering a new HR system — or have an implementation that is starting to feel difficult — book a discovery call and we can talk through what needs attention first.
Related reading
- HR audit checklist for small businesses (2026 edition)
- HR support for small businesses: when to outsource
- Employment Rights Act 2025 timeline: what changes when
This article provides general information, not legal or data protection advice. Requirements and guidance can change; check current regulator guidance for your circumstances.
Sources and further guidance
- Acas – Employment Rights Act changes
- NCSC – Cloud security guidance
- ICO – International transfers
- ICO – Contracts and liabilities between controllers and processors
- ICO – Data protection impact assessments
- ICO – Employment information
- The Pensions Regulator – Employers
- GOV.UK – Check a job applicant’s right to work
- Acas – Consultation

