Approvals & Workflows

Every sensitive action gets the right eyes — automatically

Salary increments, leave, loans, advances, holds and HR cases all flow through one approval engine. Routes resolve approvers by role, designation, reporting line or amount — and every decision is recorded, permanently. And when something goes wrong on site, formal investigations and disciplinary cases run through the same recorded machinery, from witness statement to final letter.

See it live — demo in minutes →

Sound familiar?

Approvals happen in chat messages that vanish

Big-amount decisions signed off by whoever was available

Disciplinary actions inconsistent across departments

No way to prove who approved what, months later

Capabilities

What you get

10 capabilities

One engine, many workflows

Six-plus request types — increments, leave, encashment, loans, advances, holds — share the same routing engine and audit trail.

Smart approver resolution

Route steps to a role, a designation, a specific person, or 'the requester's manager' via the reporting line.

Amount-based routing

Bigger amounts climb higher: routing bands send large requests to senior approvers automatically.

Snapshot at submission

Routes are frozen when a request is submitted, so changing a route never disturbs requests already in flight.

Disciplinary case management

A formal measure ladder from counselling to termination, with letters, acknowledgments, appeals and immutable snapshots.

Incident investigations

Record an incident, collect the facts and close with a documented outcome — every case has a full lifecycle: submit, withdraw, reopen, close.

Signed witness statements

Statements are taken in the app and signed — or formally refused — by the person who gave them, so what was said is never disputed later.

Investigation-to-discipline hand-off

When an investigation warrants action, it escalates into a formal disciplinary case in one step, carrying its statements and evidence with it.

Escalation

Stale approvals escalate automatically so requests never rot in an absent approver's queue.

In-app notifications

Approvers see pending work on the notification bell with unread counts — decisions don't wait in an inbox.

Straight from the product

Real screens from the demo company — the same system your login opens.

HumanR approvals queue with pending requests
One queue for leave, encashments, increments and salary holds — every decision recorded with its trail.
A HumanR incident investigation with findings and signed witness statements
An investigation from incident to outcome — findings, recommendations and witness statements signed in the app, the wording locked to what was signed.
The HumanR notification bell open over the dashboard with unread approvals
The bell knows what's waiting — approvals due, overdue escalations and policy acknowledgments, each one a click from the decision.

Questions

Can different request types have different routes?

Yes — each request type has its own route, and amount bands within it can route to different approvers.

What happens if an approver leaves?

Routes resolve by role or designation, so the seat matters, not the person — and in-flight requests can be escalated.

Can we run a formal investigation before deciding on action?

Yes — record the incident, collect signed (or formally refused) witness statements, and close with a documented outcome. If action is warranted, the investigation escalates into a disciplinary case carrying its evidence with it.

Jionee mwenyewe kwa data inayofanana na yako

Omba demo na tutakutumia kwa barua pepe akaunti yako binafsi ya kuingia katika kampuni ya mfano iliyojaa data — chunguza skrini halisi zenye data ya kweli ndani ya dakika chache.

Hakuna kadi ya mkopo. Hakuna simu ya mauzo. Akaunti halisi ya kuingia, inayotumwa kwa barua pepe.