One workflow engine for the whole platform: leave, expenses, purchases, salary revisions and letters all route through chains you configure — by amount, by department, by role — with delegation for absences and a trail of who approved what, when.
Why it exists
Every organisation runs on yeses — leave, expenses, purchases, asset requests, salary revisions — and approval workflow software decides whether those yeses are fast, traceable and consistent, or a folklore of forwarded emails. Kuzhu has one approval engine for the whole platform: chains defined per module and per condition, so a two-day leave takes one hop while a ₹3 lakh purchase climbs three.
Chains are configuration: sequences of roles or named people, with conditions on amount, type or department deciding which chain applies. Delegation handles vacations — approvals route to the stand-in for the period, recorded as such. Escalations watch the clock: a request pending too long moves up or pings the approver, so requests do not age in silence.
For the approver, everything lands in one inbox — leave beside expenses beside purchase orders — each with the context to decide, approvable from the phone. For the auditor, every decision carries who, when, and in what capacity, which turns "who approved this" from an investigation into a lookup.
The outcome
“Policy that enforces itself, identically, in every module.”
Feature by feature
Start
01
Multi-level chains with conditions on amount, type and department
02
Delegation windows when an approver is on leave
03
Approvals from email and the mobile app, not just the desktop
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
Sequences per module — manager then HR, or finance beyond a threshold — with conditions choosing the right chain per request.
Every leave, claim, requisition or service request enters its chain automatically; requesters see where it stands.
All pending approvals in one queue, with context, on the phone. Deciding takes the time deciding takes — not the finding.
Vacations delegate to stand-ins for a period; overdue requests escalate on the schedule you set.
Every decision recorded with actor, timestamp and role — the audit answer is a filter, not a hunt.
Worth a closer look
Buyer questions
2 answers
The answer
The alternative — each module with its own approval logic — is how systems drift into inconsistency. Here leave, expenses, procurement, assets, services and documents all call the same engine, so a delegation set once covers everything, the inbox is genuinely complete, and a new module added later inherits mature approval behaviour on day one.
The answer
Most companies have a DOA matrix in a PDF nobody reads. Here it is executable: amount bands, categories and departments select chains automatically, so the ₹4,999 request does not sneak under a threshold twice and the exceptional case climbs to exactly whom the policy says. Changing the matrix is editing configuration, with the change logged.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Yes — conditions on amount, category, department or type pick the chain, so different requests climb different heights automatically.
Delegation routes their approvals to a stand-in for the period, and each decision records that it was made as delegate.
Yes — pending items past your threshold remind, then escalate up the chain, so silence has a cost.
Yes — the full inbox with context, approve or reject with comment, from the app.
Complete — every step of every request: who approved, when, in what capacity, with comments preserved.
Works best beside
Other platform modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
WhatsApp us
WhatsApp us