HR Process Automation: What to Automate First, and Why
Short answer: HR process automation works best on tasks that happen often, follow fixed rules and need little judgement: leave requests, onboarding tasks, employment letters, expense claims. Map and simplify the process before choosing a tool. Limits come from signature rules in some countries, GDPR restrictions on fully automated decisions and, in Germany, the works council's right to co-determine.
Since January 2023, German doctors no longer hand patients a paper sick note to post to their employer. Employers retrieve the certificate electronically from the employee’s health insurer. That is HR automation in its plainest form: a process made of letters and in-trays plus follow-up calls now runs through an interface. No AI involved, just a clear process and a law that forced it.
Every HR team has dozens of such processes. Not all of them are worth automating.
Which HR processes are good candidates
Three conditions point to a good candidate. The process happens often. It follows fixed rules. And it does not end in a judgement call about a person. The more judgement, the less automation.
| Criterion | frequent | rule-based | automatable |
|---|---|---|---|
| Leave request and approval | |||
| Onboarding tasks for IT and facilities | |||
| Employment verification letters | partly | ||
| Expense claims | partly | ||
| Sick leave records | partly | ||
| Performance reviews | partly | partly | |
| Disciplinary action, dismissal |
The last row is there on purpose. Dismissals involve legal process, judgement and, in some countries, strict form rules. German law requires a handwritten signature on paper for dismissals and fixed-term clauses, and employment references may not be issued electronically. Workflows can prepare the paperwork. They cannot replace the decision.
How much time automation really saves
Vendors like big percentages. An honest calculation with your own assumptions is more useful. Here is an example for leave requests at a company with 80 staff. The values are illustrative assumptions, not measurements.
- Requests per year: 80 × 6
- 480
- Time today: 480 × 12 min
- 96 hrs
- Time with workflow: 480 × 3 min
- 24 hrs
- Saved per year
- 72 hrs
Assumptions: 6 requests per person per year; 12 minutes per request on paper or email (request, check balance, approve, update records); 3 minutes with a workflow.
Seventy-two hours is almost two working weeks. Spread across a year, it is about an hour and a half per week. On its own, that rarely justifies a new system. The case changes when you look at five or six processes running in the same tool. The sum also leaves out errors: one wrongly carried-over leave balance can cost more time than ten requests.
The right order: map, simplify, automate
The most common mistake is pouring a clumsy process straight into software. You end up with a clumsy digital process.
- Map the current processWho does what, with which document, how often. A spreadsheet is enough.
- CutQuestion every signature, copy and forward. Often a third of the steps disappear.
- Write the rulesWhen is a request approved? Who covers for whom? What happens after five days without a response?
- Only then pick a toolCheck your existing HR software first, then workflow tools, custom builds last.
Step three is the one people underestimate. Automation needs rules that often exist only in someone’s head. “Priya approves leave, except in December, when the site manager decides” has to be written down somewhere, or no software can follow it.
Sick leave: where automation stops
Sickness absence is a useful test of how far automation reaches. The employee still has to report in, usually on the first morning. What comes after varies by country. German employers pull the certificate electronically from the insurer, but privately insured staff and certificates from doctors abroad are outside that system. UK fit notes can be issued and signed digitally, but they still arrive through the employee.
Good workflows catch the exceptions. Absence reported, certificate expected, and if nothing arrives within the defined period, a task goes to payroll. Nobody is left with an unexplained gap in the pay run.
Tools: from your HR system to a custom build
For most businesses, the existing software is the best starting point. Modern HR and payroll platforms ship self-service for leave and letters, often for personal data too, and it is often just not switched on. Check your contract, and ask the vendor which modules your licence already includes. The answer is often more than you are using.
Where gaps remain, workflow tools help. Microsoft Power Automate is included in many Microsoft 365 licences and connects forms with email and spreadsheets. That is enough for simple approvals. Anything that moves personal data between systems should involve IT, or you end up with a tangle of private automations nobody understands.
Watch which data each flow actually needs. Leave approvals need a name, dates and remaining balance. Health data, salaries or home addresses have no place in it. If a tool runs in a third party’s cloud, you need a data processing agreement under Article 28 GDPR, and whoever handles data protection should know where the data goes.
Custom development makes sense when standard software cannot handle a core process or several systems need a reliable connection. For those cases, studios like OnlineBuilders build custom solutions.
Where the law draws lines
Three rules are worth knowing before you start.
First, automated decisions. Under Article 22 GDPR and its UK counterpart, decisions based solely on automated processing that significantly affect people are restricted. Auto-approving leave when the balance and cover are there is unproblematic. Auto-rejecting without any human review is riskier. When the outcome is negative, route it to a person.
Second, works councils. German law treats almost any HR software that logs who did what as a system capable of monitoring employees, so the works council must agree before rollout. Plan for that early, see works councils and IT systems.
Third, form rules. UK and US law broadly accept electronic signatures, under the Electronic Communications Act 2000 and the federal ESIGN Act respectively. Germany keeps paper for dismissals, fixed-term clauses and references. Check before you design an all-digital offboarding flow.
Common mistakes in rollout
Projects without an owner stall. When HR describes the process, IT builds it and nobody owns the outcome, you get a half-finished workflow nobody maintains. Name one person per automated process who approves changes and answers when something breaks.
Communication matters more than the tool. Staff who have filled in paper forms for ten years won’t switch on their own. What usually works: a short explanation, a cut-off date after which only the new route is accepted, and a contact person for the first few weeks. Expect questions in the first month and few after that.
Cover arrangements break approval chains. Approvers go on holiday or fall ill. Define deputies from the start and set a rule for automatic escalation.
Where to start
My advice: start with leave requests. They affect everyone, they are simple, and the saving is visible to all. Then move to onboarding tasks, using the employee onboarding checklist as the template, and finally to records, covered in digital employee records.
Your next step: list the five HR processes that occur most often in your company, with a rough count per year and minutes per case. Half an hour with that list shows you where to start and what can wait.
Questions people ask
Which HR process should I automate first?
Usually leave requests. Every employee files several a year, the rules are clear and everyone notices the improvement immediately. The risk is low, and it builds trust for bigger projects.
Do I need new software to automate HR?
Not necessarily. Many HR and payroll systems include self-service features that are simply switched off. Workflow tools such as Microsoft Power Automate fill gaps. Custom development only pays when standard tools cannot handle a core process.
Can HR decisions be fully automated?
Approvals that follow clear rules, such as granting leave when there is enough balance and cover, are generally fine. Negative decisions with significant effects on people should keep a human in the loop, especially under GDPR and UK GDPR.
Can contracts and dismissals be signed electronically?
In the UK and US, electronic signatures are widely accepted for employment documents. Germany is stricter: dismissals and fixed-term clauses still require a handwritten signature on paper, and employment references cannot be issued electronically.
