Your provider gets the system live. Your people decide whether it pays off.
This free playbook covers the part no implementation plan does: how to help hundreds or thousands of busy people change how they book leave, check a payslip, complete a review or approve a timesheet. What to say, who to say it to, in what order, and what to do when launch energy fades in week three.
- A three-stage methodology, developed with independent researchers at the University of Kent
- Checklists for HR, leaders, managers and employees at every stage
- Sample communications timelines, template messages and an adoption scorecard you can use straight away
What’s new in the 2026 edition
Work has changed since the first edition in 2025. People face more change than ever, new questions about AI and monitoring, and managers with less time than most rollout plans assume. This edition keeps the three-stage structure that made the first one useful, and updates it for how UK workplaces run now.
New in this edition:
- The five questions your employees will ask about a new HR system, but not out loud, and how to answer them before anyone has to
- How to reach frontline, shift and deskless staff who never open a company email
- How to design for 20 minutes of manager attention, not a half-day workshop
- How to plan for the week-three dip, so a normal slowdown isn’t mistaken for a failed launch
- A one-page adoption scorecard that gives your executive sponsor the evidence to defend the spend
Who this HR software adoption playbook is for
It’s written for UK HR and payroll teams who have chosen a new system, or are about to, and need people to use it. It works whichever provider you chose.
HR and payroll teams with a go-live ahead
You own the comms, the training and the case for the investment. The playbook gives you the plan, the timeline and the words, stage by stage.
Executive sponsors and project leads
You signed off the spend, and your name carries weight a project update can’t. The leaders’ checklists show where your example makes the biggest difference, and the scorecard shows what to report back.
Organisations with a frontline or deskless workforce
In care, housing, retail, hospitality, manufacturing, logistics and education, many people will never see an intranet post. Their whole relationship with the HR system may happen on a personal phone. The playbook shows how to map your audiences by how they get information, not where they work.
Teams already live, where usage has stalled
Adoption doesn’t end when the project does. Stage 3 covers how to prove the impact, keep training current and use the moments when people already have a reason to log in, from leave year rollover to review season.
What’s inside the guide
Why system adoption is harder than it used to be
Four shifts change what you need to say and who you need to say it to. Gartner found employee willingness to support organisational change fell from 74% in 2016 to 43% in 2022. A new HR system now lands on top of change fatigue, worries about AI, a workforce without desks and managers with less headspace. Each shift comes with a clear “what to do differently”.
A three-stage plan for implementing a new HR system
The methodology runs from well before go-live to long after it. The loop from stage 3 back to stage 2 is deliberate: every new joiner, new manager and new module is a small relaunch.
Stage 1: prepare and engage
Everything that happens before go-live, where good launches are made. Name one executive sponsor, map every audience, audit the change load your people already face, baseline the measures you’ll report on later, and recruit super users and champions. This is the people side of your HR software implementation plan.
Stage 2: launch and support
Launch week gets the attention, but week three is where adoption is won or lost. Make the first two minutes in the system a win, with a payslip or a holiday balance rather than a data check. Offer training in more than one format, and give managers something that makes their own week easier first.
Stage 3: evaluate and enhance
The project has an end date. Adoption doesn’t. Go back to the person who approved the investment with evidence before they ask for it, in their language: hours returned, queries avoided, errors prevented. Then keep training alive through induction, promotions and topic refreshers tied to your business rhythm.
Five questions your employees will ask, but not out loud
When you announce a new HR system, people ask about login details and training dates. Privately, they want to know something else:
- What does it hold about me?
- Who can see the data?
- Does anything in it make decisions about me?
- Is it a way to monitor me?
- Is this a prelude to staff cuts?
A 2026 GMB Union poll of more than 5,000 workers found 48% are worried AI will take their jobs. The playbook shows how to answer each question honestly, get the answers signed off, and make sure every manager and champion gives the same one.
Templates you can use straight away
Three appendices turn the methodology into work you can start on this week:
Sample communications timelines
What to send, when and why, from five to six months before go-live through to each new release, with a frontline method for every message
Template messages
The project announcement, what to say when someone asks if this is about job cuts or whether AI makes decisions about them, a reply for managers who say they don’t have time, a payslip insert for people with no company email, the week-three nudge, and what to say when something goes wrong
The adoption scorecard
A one-page quarterly report on usage, effort removed, and quality and risk, with guidance on how to translate the numbers for the board
A sample from the playbook
Here’s one of the template messages, for the manager who says they don’t have time:
“Fair. Here’s the deal: 20 minutes of training, and from then on approving leave takes you about 30 seconds instead of finding the email, checking the spreadsheet and replying. The first month costs you time. After that you get it back.”
The full playbook has a message like this for every moment that can make or break user adoption.
Built on research with HR professionals who’ve done it
The three-stage methodology was developed with independent researchers from the University of Kent, who drew on the experience of HR professionals who had recently led a system rollout. The result is a software adoption strategy grounded in what worked for real UK teams, written for lean HR teams and employees who have seen systems come and go.
Why Ciphr wrote this guide
The gap between a signed contract and real results is where HR software most often disappoints, and no demo covers it. Our implementation consultants, many of them CIPD or CIPP qualified and drawn from real HR and payroll roles, get your system live. This playbook helps with the other half: a workforce that uses it, and the evidence to prove the difference it makes.
Ciphr customers: your HR admins can also find training materials in the Ciphr Academy.
FAQs: HR software implementation
Yes. Fill in the form and we’ll email you the 2026 edition.
No. The playbook works for any new HR or payroll system, whichever provider you chose.
Yes. It covers a new HR or payroll system, an HRIS implementation, or a new module added to a system you already use. The scorecard includes payroll measures such as corrections per pay cycle.
Earlier than most teams expect. The sample timeline starts five to six months before go-live, with an executive briefing, and assumes a six-month implementation. Adjust it to fit your own plan.
Ciphr HR implementation takes from 7 weeks. Payroll follows a considered migration of around three months, with two parallel pay runs to prove the numbers before cutover.
The three stages are the same. The 2026 edition adds the five unspoken employee questions, guidance for deskless and frontline workforces, a realistic view of manager capacity, and an updated scorecard and template bank.
Make your new HR system stick
You chose the system. Now give your people every reason to use it.
