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.
Every request type gets its own form
Request management is a framework: you define which request types exist, and 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
The approval sits with the role that can judge it
Each request type carries its own approval flow, single- or multi-level, and any role can be an approver: a department head, a financial controller, a security officer, the direct manager. Approvers 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.
Today a request often passes through HR even when HR cannot judge it: a laptop belongs with IT, a company car with the fleet manager, a job change with the manager who owns the role. Who approves follows from the role ownership defined in Organisation management, and HR keeps the full view of everything running, returned or closed, including the flows it never touched.
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.
For many types the sign-off is the trigger. An approved new-hire request starts the hire flow in Employee lifecycle, a laptop request creates the assignment in Asset management, a leave request lands in Popay Leave, and a training request becomes an enrolment in Popay Learn. The approval trail stays attached as event history.
Nothing lost, everyone in the loop
Every request follows a defined path: the right form, the right approvers, the right deadlines. A manager can raise one on behalf of someone in their team. Everyone keeps sight of the requests they handled, long after they closed. And an approved change to someone's details is written straight into their record. What was an inbox full of one-off favours becomes a set of processes you can trust and prove.
Every request a process. Traceable end to end.
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.
Book a demo →