DonkeyHR

Rolling out an ESS app to your employees: a simple plan

Launch employee self-service with a small pilot, clear instructions, practical training and private support for staff who need help.

DonkeyHR Team · 2026-10-27 · 6 min read

Launch an employee self-service portal by testing it with a small group, explaining what employees should use it for, and practising everyday tasks before expanding access. Keep an assisted route for employees without smartphones, and name someone who will handle questions. Measure success by checking whether people can complete tasks and receive help.

What should you decide before inviting employees?

An employee self-service portal, often shortened to ESS, gives employees a place to handle routine HR tasks. Your rollout needs to explain which tasks belong there and what happens after someone submits a request.

Choose a manageable starting scope. You might begin with viewing payslips and applying for leave. Add other available functions once employees understand the basics. Announcing everything together can make a simple change feel complicated.

Assign someone to own the rollout. This person coordinates access, instructions and support. Managers also need to understand their role, especially if leave requests require their approval before going to HR.

Decide what employees should do if access fails. Keep that fallback clear so an employee does not miss a request because a password or device caused trouble.

Who should join the pilot?

Choose a small group that reflects how your workplace operates. Include someone comfortable with phones, someone who needs guidance, a manager who handles requests, and someone whose usual work does not involve a computer.

Ask pilot employees to complete real tasks where practical. Can they find their payslip? Can they submit a leave request and understand its status? Can the manager find the request and act on it?

Observe where they hesitate. A confusing instruction, unfamiliar label or unclear approval step is useful feedback. Fix those problems before inviting everyone else.

Check access privately. Each employee should see their own information. Avoid demonstrations that display an employee’s salary or personal details to the group.

What could an illustrative rollout look like?

Illustrative worked example: this is a 4-week rollout for an employer with 20 employees. The group sizes and timing are planning choices, not statutory requirements.

  • Week 1: Invite a pilot group of 5 employees. Help them sign in, find a payslip and practise the leave process. Record problems and check that managers understand their approval role.
  • Week 2: Correct the pilot problems and invite the remaining 15 employees. The arithmetic is 5 pilot employees plus 15 additional employees equals 20 employees invited. Explain the support route to everyone.
  • Week 3: Hold practical training and offer private assisted sessions. Check whether employees can complete the starting tasks, including those who need access without a smartphone.
  • Week 4: Review unresolved problems, check completed tasks and ask employees what remains confusing. Continue support and introduce further available functions only when the starting process works reliably.

An invitation does not prove that someone has used the portal. Keep separate notes on who has access, who has completed a task, and who still needs help.

What should your launch message say?

Explain the change in terms employees recognise. Say where they will find payslips, how they should apply for leave, and whom they should contact when something goes wrong. Mention only functions that are available in your chosen system.

State when the new process starts and how existing requests will be handled. If an employee has already asked for leave through the old route, explain whether they need to do anything further. Avoid duplicate submissions.

Use the languages employees understand. A short spoken explanation during a shift briefing can help alongside written instructions.

Tell managers what to communicate too. Employees should receive consistent answers about where to submit requests and how to follow up.

How should you train employees?

Teach tasks rather than menus. Show the route to a payslip, explain how to read a request status, and demonstrate the steps for applying for leave.

Then let employees try the task themselves. Watching a demonstration is different from completing a request without prompting. Give people time to ask questions without feeling tested.

Use sample information for group demonstrations where possible. If someone needs help with their own record, move to a private session.

Provide short instructions employees can find again. Include how to get help and what information to provide when reporting a problem. Never ask them to send passwords or share salary details in a group chat.

How can staff without smartphones use self-service?

Ask about access before launch. Some employees may use a basic phone, share a family device, or have limited connectivity. A rollout should accommodate those situations.

Check which access routes your chosen system actually supports. If it works through a browser, a private workplace computer may help. Arrange access around shifts so employees can use it without disrupting their work.

For assisted sessions, let employees enter their own credentials and review their own submissions. The helper should explain the steps without keeping passwords.

On shared devices, sign out after use and avoid saving credentials. Check for downloaded payslips or other personal files before the next person uses the device.

Keep a documented alternative for employees who cannot use the portal. Explain who receives the request and how the employee will receive confirmation.

What support and adoption checks should you keep?

Give employees a named contact and a clear way to raise problems. Separate access issues from questions about payroll information or leave decisions. Each needs the right person to resolve it.

Use this checklist during the rollout:

  • Check that each employee knows how to access their account.
  • Ask employees to complete a starting task themselves.
  • Confirm that managers can find and handle pending requests.
  • Check that staff without smartphones have a workable route.
  • Review requests that remain unresolved or appear twice.
  • Record repeated questions and improve the instructions.
  • Ask whether employees know whom to contact for help.

These checks show where support is needed. If someone continues using the old process, find out why. They may lack access, misunderstand the task or be waiting for help.

Common mistakes

Treating invitations as adoption hides problems. Check whether employees can finish tasks.

Removing the old route before testing the new one leaves people stuck. Keep a clear fallback while access problems are resolved.

Training employees but overlooking managers creates delays. Test the approval process from submission through to the response employees see.

Giving public demonstrations with real salary records creates avoidable privacy risks. Keep personal assistance private.

FAQ

Must every employee have a smartphone?

Plan an access route for employees who do not. Check the system’s supported devices and arrange private assistance or a documented alternative where needed.

Should all available functions launch together?

Start with tasks employees need and can practise. Expand when access, instructions and support work reliably.

What if employees keep asking HR for help?

Use those questions to identify gaps. Repeated questions often point to unclear instructions or an access problem that needs fixing.

How do we know the rollout is working?

Employees can complete routine tasks, managers handle requests, and people know how to get help. Check actual outcomes alongside login activity.

How can the software support this plan?

DonkeyHR is in beta and has an employee self-service portal for viewing payslips, applying for leave, seeing attendance, submitting IT declarations and editing profiles. Base your rollout on the functions your employees need, with clear instructions and private support.

Related reading