Every request, to the right approver
A leave request sitting in one manager's inbox. A bank-detail change on a form nobody filed. A new-hire ask buried three replies deep in a thread. When requests run on email, memory and follow-up, they stall, get lost, or come back missing half the fields. Request management gives every request a form, the right approvers and a trail.
When requests live in inboxes
A request is a small thing until it's the fifth one this week that stalled. Run informally, this is what it costs.
A form for every request, not a fixed list
Request management isn't built around a set menu of request types. It's a framework: every type has its own form, its own fields and its own approvers, broad enough to cover any process that needs a request and a sign-off.
People processes
Personal updates
Time-related
Operational
Documents
Any process you need
Flows that fit the process, not a fixed hierarchy
Each request type carries its own approval flow, single- or multi-level. Any role can be an approver: a department head, a financial controller, a security officer. Not just the direct manager. Approvers can approve, reject, or return with commentary so the requester knows exactly what to fix.
Every step can carry a deadline, with reminders before it and escalation when it passes, so a request never stalls because one person is unavailable. Who the approver is comes from the role ownership defined in Organisation management.
The right approver, a deadline, a trail. Nothing waits in an inbox.
From request to resolution, in four steps
A structured, traceable workflow, without adding friction for the people using it.
Request submitted
An authorised user submits via the configured form: the right fields, attachments and context for that type.
Approver notified
The first approver gets a task, reviews, and approves, returns, or rejects within the deadline.
Flow progresses
Each step completes in sequence. The requester tracks status themselves. No need to ask HR.
Approved: action fires
Final approval closes the request and, where configured, triggers the next action automatically.
Approval is the start, not the end
For many request types, the sign-off is the trigger for what comes next. No manual handover, no re-entry. An approved new-hire request initiates the hire flow; an approved role change starts the move; an approved laptop or badge request creates the assignment task.
The request becomes the opening move of a broader process, orchestrated by Employee lifecycle, with the kit handled in Asset management. The full approval trail stays attached as event history.
Approved here. Started everywhere it needs to be.
Nothing lost, everyone in the loop
Every request follows a defined path: the right form, the right approvers, the right deadlines. And every action is logged. Requesters see their own status in real time, so HR stops being a status desk. What was an inbox full of one-off favours becomes a set of processes you can trust and prove.
A process, not a favour. Traceable end to end.
Part of Core HR
Request management is the inbound edge of the Core HR record, where a person asks, and a process begins. It works closely with:
Give every request a path
A form, the right approvers, a deadline and a trail, for every request type your organisation runs, from a leave day to a new hire.
Request a demo →