A platform that automates HR approvals needs four things: approval chains configurable without programming, automatic delegation when the approver is away, an auditable record of every decision, and integration with payroll software. Without the first, every change to the org chart goes back through IT. Without the second, the process stalls while the approver is on holiday. Without the third, there is no way to answer an audit. Without the fourth, someone keeps copying values by hand. This article sets out what to check for each type of request.
The scope here is choosing the platform. If the question is still what is worth automating in HR, the article on HR automation walks through the employee lifecycle from recruitment to offboarding, and is the natural read before this one.
The five types of internal request
Almost every internal request that passes through HR belongs to one of five families. Each has a different approval rule and each fails differently when handled by email.
- Absences and holidays. High volume, simple rule, critical dependency on up-to-date balances. What fails in the manual process is overlap: two people from the same team away in the same week because nobody cross-checked the requests before approving.
- Expenses and advances. Medium volume, rule with thresholds by amount. It fails at reconciliation: the receipt arrives as a photo, the data is retyped into a spreadsheet, and the discrepancy only surfaces at month-end close.
- Equipment, access and supplies. Low volume, but two approvers, the line manager and whoever owns the system or the stock. It fails at the end of the cycle: access is granted and never revoked when the person leaves.
- Contract changes. Low volume, high impact. It fails on traceability: the change is applied and the previous version disappears, which makes it impossible to reconstruct the history later.
- Documents and certificates. High volume, approval almost always unnecessary. It fails through excess process: human validation is required to issue a document the platform could generate on request.
This separation matters because most platforms handle the first family well and the rest badly. A demo built around holiday requests tells you very little about what happens to an access request with two approvers.
What the platform needs in each case
The table below summarises what to check per request type, and the signal that should raise doubts during evaluation.
| Request type | What the platform must support | Warning sign |
|---|---|---|
| Absences and holidays | Approval by the line manager, with balance and team overlap validation. Link to the team calendar and to payroll software | Does not validate balance or team conflicts before submission |
| Expenses and advances | Approval by the manager up to a threshold and by finance above it. Receipt data capture and a link to accounting or the ERP | Approval with no amount thresholds, or receipts attached without data extraction |
| Equipment, access and supplies | Two approvers, the manager and the owner of the system or stock. Link to inventory and identity management | Grants access without generating the matching revocation at offboarding |
| Contract changes | Approval by HR and the manager, with senior sign-off above a certain impact. Link to payroll software and to document storage | Applies the change without retaining the previous version |
| Documents and certificates | No approval, just a record of the request. Link to document storage and digital signature | Requires human approval to issue what could be generated on request |
Seven criteria for choosing
The general criteria for evaluating platforms are covered in how to choose a process automation platform. The seven below are the ones that specifically separate HR approval platforms once they reach production.
- Approval chains configurable without code. A team reorganisation should not require a ticket to IT. Check who, in practice, changes an approver, and how long it takes.
- Automatic delegation and cover. When the approver goes on holiday, the request must move to a defined stand-in. Without this, August is a lost month.
- An auditable record of every decision. Who approved, when, with what data in view, and what has changed since. This is what lets you answer an audit or a complaint without reconstructing mailboxes.
- Integration with payroll software. Approved absences and the month's variable inputs must reach payroll without being retyped. This is the point where most projects stop half-finished.
- Approval on mobile. Managers who travel are the main cause of delay. Approving has to be possible without opening a laptop.
- Notifications that do not create noise. A platform that emails on every step gets muted within two weeks. Look for daily digests and the ability to silence by request type.
- Data export without depending on the vendor. Approval history, balances and documents must come out in an open format, on request, not as a paid project.
What HR can configure without IT
This is the question that decides whether the automation survives its first year. A platform that depends on IT for every adjustment ends up abandoned, because the IT backlog rarely prioritises HR.
In practice, an HR team with no dedicated technical support should be able to do the following alone: create and change a request type, define who approves and in what order, change amount thresholds, set up cover arrangements, adjust notification wording and pull reports. If any of these requires outside help, the real cost of the platform is higher than advertised.
Where IT is still needed, legitimately: the initial connection to payroll software, corporate authentication, and any integration with internal systems. These are set-up tasks, not day-to-day operation. The distinction that matters is between configuring (HR, every day) and integrating (IT, once).
Recruitment and onboarding
Recruitment and onboarding are special cases, because they involve people who do not yet exist in the system. Four concrete points where automation pays off:
- Screening applications. The useful automation here is not deciding who to hire, it is organising: extracting structured data from CVs, grouping by objective requirements and removing duplicates. The decision stays human, and for legal reasons it should, with the criteria recorded.
- Scheduling interviews. This is the step with the best effort-to-gain ratio. Matching interviewer availability against the candidate's and sending invitations and reschedules without an email thread removes days of calendar time per process.
- Preparation before day one. Contract, access, equipment and initial training can all be settled in the week before the start date, triggered by the offer being accepted. A first day without a laptop is a workflow problem, not a logistics one.
- Sending contracts with tracking. When hiring in volume, the value is in knowing the status of each document without asking: sent, opened, signed, pending. Digital signature with status tracking solves this.
The approval workflows underpinning these steps follow the same principles as any other internal process, covered in digital approval workflows.
Common mistakes
- Automating the rule before simplifying it. A holiday request with four approval levels is still slow once automated. Reduce the levels first, then automate. This mistake and others like it are detailed in common mistakes when implementing automation.
- Digitising a bad workflow. Replacing a paper form with an on-screen form while keeping the same steps produces an equally slow process with an added licence cost.
- Buying modules that are never switched on. Appraisals, OKRs and training are often included and rarely used in the first year. Paying for them brings the cost forward without reducing risk.
- Forgetting offboarding. It is the least automated workflow and the highest risk. Access that is never revoked and equipment never returned are direct consequences of treating departures as exceptions.
Where Engi360 fits
Engi360 is Engibots' operational management platform, and it covers part of this territory: hours, absences, projects, tasks and tickets, all with approvals, plus the employee record, appraisals and OKRs. Monthly variable inputs and informal payslips are prepared for the company's payroll software.
It is worth being explicit about the limits, because that is what allows an informed decision. Engi360 does not run certified payroll, does not issue certified invoices and does not replace accounting. Expense management is also outside its current scope, so anyone looking for a single solution covering all five request types described above will need to combine tools or integrate the ones already in use. For automation that spans different systems, the route is EngiMatrix.
Frequently asked questions
How many approval levels are reasonable?
For absences, one. For expenses, two at most, with the second triggered only above an amount threshold. Beyond two levels, response time depends more on approvers' calendars than on the process, and automation stops solving the problem.
Do we need to replace our payroll software?
No. The aim is for approved absences and the month's variable inputs to reach payroll without being retyped. Certified payroll can stay where it is, provided there is a data entry route that is not a spreadsheet.
How long does it take to get the first workflow into production?
With a well-defined request type, absences being the usual choice, and the approval rule already simplified, four to six weeks is a realistic timeframe to supervised production. Integration with payroll software is usually the slowest step.
Can HR configure this without IT support?
Day-to-day configuration yes: request types, approvers, thresholds, cover and reports. The initial integrations with payroll and corporate authentication no, and it is not reasonable to expect otherwise. A platform that needs IT to change an approver is not fit for HR.
What about administrative processes outside HR?
The principles are the same, with different approval rules. The article on how to automate administrative processes covers that wider territory.