HR in every employee's pocket

Self-service is not only about relieving HR

The usual case for self-service is that it lightens the load on HR. True and incomplete: the larger effect is not the number of requests it saves but what it turns from verbal into documented.

Leave asked for in a corridor and approved with a nod is known to nobody but those two. If they disagree two months later about what was agreed, there is nothing to refer to. A request going through the system carries its date, who approved and when — not because nobody trusts anybody, but because human memory is not a record.

What an employee raises themselves

Everything that used to travel on paper or in a message, straight from the phone:

A leave request

— with its type and dates, and the validation result appears immediately — so a refusal's reason is known in seconds rather than days.

Permissions and assignments

— authorised absence for a few hours, and work away from the workplace — each on its documented path.

A forgotten-punch request

— for a day attended but not recorded — treated as a virtual punch at calculation without touching the device record.

Overtime

— a prior request with a start and end time, so the obligation is known before it arises rather than at month end.

The payslip

— detailed, every month — which alone measurably reduces the questions HR fields.

Complaints, suggestions and letter requests

— a documented channel reaching HR directly, rather than a message on someone's phone.

A request refused in a second rather than a week

What most frustrates an employee about a leave request is not the refusal but waiting a week to learn their balance was short. Immediate validation on submission solves that: the reason appears before they leave the screen.

The reasons are known and specific: insufficient balance, an overlap with another leave, a day inside a blackout period, exceeding the type's monthly cap, or more than half the department being away in the same window — a check no manager can run reliably in their head.

The other side: what a manager sees

Self-service is half the picture; the other half is requests reaching whoever actually decides. The route follows the org structure, so it moves automatically with any transfer or reporting change — rather than a manual list that goes stale within months.

The most dangerous failure here is the quietest: a request stuck on an approver who has left. No error, no alert — the request simply does not move and the employee assumes someone is considering it. So delegation is defined in advance: who stands in while a manager travels or takes leave, so work continues and the record reflects who actually decided rather than shared credentials.

Why every employee gets an account, even non-computer users

The common objection: half our people are plant workers who do not use a computer. It is an objection to the wrong tool — self-service is used from a phone, and everyone has a phone.

Excluding a group does not remove their requests; it returns them to paper, creating two parallel systems — one in the software and one in a drawer, and it is the second that gets forgotten at payroll. So the login is created automatically at hiring, and default permissions define what each person sees.

On bulk import the account is created with a default password — which is why employees should be required to change it at first sign-in.

Transparency reduces questions, not just objections

Most of the questions HR fields are not "the figure is wrong" but "I do not understand how it was reached". Someone seeing a net with no detail asks; someone seeing a detailed payslip, their leave balance and the status of their requests has no need to.

The second effect is less obvious and more important: transparency makes a real error discoverable. The employee is the only person who knows they worked that day — and seeing their own data, they catch what nobody else could notice.