See every request that is still waiting on a decision.
Leave, attendance corrections, and - when you use them - comp-off, letters, certificates, and manager changes. HR gets one company-wide queue: whose request, which step, who it is sitting with, and how many days it has waited.
One desk for requests that have not been decided yet.
This is HR’s view across the company, not a replacement for the manager’s own inbox. When HR approves or rejects, their own name is recorded on that step.
Only the step that needs a decision now
Days waiting, with the assigned people
Approve or reject the current step
View access does not have to include the buttons
HR sees the pile. Managers stay the assigned approvers. Leadership can ask what is ageing.
Workflows design the path. This page is the list of what is stuck on that path right now.
Monday morning is a queue, not a scavenger hunt.
You search by name or employee code, filter by department and dates, and see what is waiting at the current step. Leave and attendance corrections are always there. If the company uses comp-off, letters, certificates, or manager-change approval, those queues appear too - and stay hidden if you do not. People who may view but not decide see the list without approve and reject buttons.
- Current step only - you see where it is stuck, not every future step as if it were ready
- Assigned approver names and how many days it has waited
- Approve or reject that step, with remarks. The request leaves the queue when it is fully decided
Ageing approvals are an operating problem, not an HR mood.
A leave that sits for twelve days is a coverage problem. A manager change that sits is an organisation problem. Leadership does not need five inboxes. They need HR to say what is waiting and how old it is. When HR steps in, the record shows HR acted - it does not pretend the original manager pressed the button.
- One place to ask “what is still open?”
- The person who decided the step is the person who was logged in
- Available on every plan, so the queue is not an upgrade surprise
Their own approvals still come to them. HR can see when the pile is ageing.
This page does not take the manager’s job away. The request still shows who it is assigned to. If a manager is away and the step is blocking work, HR can clear that current step in their own name. The next step, if there is one, becomes the one that is waiting. Managers are not skipped in silence.
- You cannot jump to a later step while an earlier one is open
- Rejecting leave restores the balance. Rejecting a time correction does not apply the new times
- A manager deciding the same step at the same moment is caught, so two people do not both “win”
Why “the manager will get to it” is not a queue.
Companies already have managers. What they do not have is a single honest picture of which requests are still sitting, how long they have sat, and a way for HR to unblock the current step without inventing history.
Each manager’s email
HR cannot see the company pile, only the complaints
One queue of current steps across the organisation
A workflow diagram
The diagram shows the path. It does not show what is waiting today
Pending Approvals is the live list. Workflows remains the path
HR logs in as the manager
The trail says the wrong person decided
HR’s own name is stored on the step they decide
WhatsApp “please approve”
No days-waiting number, no assigned person, no reject that restores leave
Days waiting, assigned approvers, and a reject that actually finishes the request
Five admin screens for five request types
Letters and certificates age in a place HR does not open
Optional tabs in the same queue, hidden when you do not use them
Everyone in HR can click approve
A junior viewer clears a leave they should only have reported
View and approve are separate permissions
The waiting requests teams stop losing in inboxes.
Each one is a real delay, visible in one place instead of five.
Leave requests live in one place, attendance corrections in another, and letters in a third.
One HR queue, with a tab per kind of request your company actually uses.
Nobody knows a request has been waiting nine days.
Each row shows days waiting, the current step, and who it is assigned to.
HR approves “as the manager” and the trail is a lie.
The logged-in HR person is recorded as the one who approved or rejected that step.
Someone approves the last step while the middle step is still open.
Only the earliest open step can be decided. Later steps stay waiting.
A rejected leave still eats the balance.
Rejecting the request rejects it fully, cancels the remaining steps, and puts the balance back.
A time correction is rejected but the new times still land on attendance.
New times are applied only when the last step is approved. A rejection does not apply them.
Comp-off, certificates, or a manager change stay invisible because they are “someone else’s job”.
Those tabs appear when the company uses them, with the same rules for who can see the list and who can approve.
A viewer in HR can accidentally decide a request.
View and approve are separate. View shows the queue. Approve shows the buttons.
An empty week looks like a broken screen.
If nothing is waiting at a current step, you get an empty state - not a fake list.
Six reasons a company-wide queue is different from another inbox.
Approving step three while step two is still open is how trails get fiction in them. This queue will not do that.
Company-wide, not one manager’s inbox
HR can see what is waiting across departments, including items assigned to other people.
Only the step that can be decided now
Future steps stay visible in the detail as waiting. You act on the current one. The request stays in the queue until the last step is done.
HR’s name stays HR’s name
When HR decides a step, the record shows that HR person. It does not rewrite history to look like the assigned manager did it.
Queues you do not use stay hidden
No comp-off, no letter studio, no certificates, no manager-change approval - those tabs are not there to confuse the morning.
Reject means the request is really rejected
Remaining steps are cancelled. Leave balance comes back. A rejected time correction does not change attendance. A rejected manager change does not move the manager.
Look and decide are different permissions
Some HR roles should see ageing. Not all of them should be able to approve. The buttons follow that split.
What you can actually do.
Leave waiting on a decision
- Rows show the current step, such as step 2 of 3, the assigned people, and days waiting
- Open the request and see which steps are done, current, or still waiting
- Approve the current step, with optional remarks. The next step becomes current
- The last approval completes the leave and the row leaves the queue
- Reject ends the request, cancels later steps, and restores the leave balance
Attendance corrections
- Same pattern: current step only, days waiting, assigned approvers
- The new times are written to attendance only when the last step is approved
- A rejection does not apply those times
Comp-off, when you use it
- The tab appears only if comp-off is part of your company setup
- See the date worked, full or half credit, and where the request came from
- The last approval credits the balance. A rejection does not
Letters, certificates, and manager changes
- HR letter approvals appear when you use company letters
- Certificate approvals appear when you use certificates
- Manager-change approvals appear when that approval is switched on
- The last approval of a manager change updates who the person reports to
- A rejection leaves the manager as they are
Find what is ageing
- Search by name or employee code
- Filter by department and date range
- The list is paged, so a large company does not get one endless page
- Each kind of request loads when you open its tab
Who may look, and who may decide
- On Starter, Professional, and Enterprise
- View shows the queues
- Approve adds approve and reject on the current step
- Remarks on the decision
- If a manager clears the same step first, HR’s later click does not double-apply it
On every plan. The extra queues appear only if you use those areas.
Leave and attendance corrections are the base. Comp-off, letters, certificates, and manager changes show up when those parts of the product are on.
Every plan
The queue is part of running HR, not an upgrade.
- Leave and attendance corrections on Starter, Professional, and Enterprise
- View and approve are separate, so you can let someone see the pile without deciding it
- Search, department, dates, and days waiting
Extra tabs follow what you use
You do not buy a second queue product.
- Comp-off if comp-off is on
- Letters if Document Studio is on
- Certificates if certificate management is on
- Manager changes if that approval is on
What makes the approach different.
Built for the requests that are still open
Finished items are not the point. The screen is the work that has not had a decision.
Separate from designing the approval path
Workflows is where you set who approves. This is where HR sees what those approvers have not finished.
Stepping in does not fake the manager’s click
HR can clear a stuck step. The history shows that HR did it. That is easier to defend than a trail that lies.
Age is visible
Days waiting is on the row. You do not have to open each request to see which one has gone quiet.
A no is a complete no
Reject does not leave ghost steps pending, and it does not apply the thing you rejected - balance, times, or a new manager.
One habit for several kinds of request
Leave, time corrections, and the optional queues share the same idea: current step, assigned people, days waiting, decide or not.
Pending Approvals - questions buyers actually ask.
Stop finding a two-week-old leave request in someone’s unread mail.
Book a short walkthrough: open the company queue, filter a department, see days waiting, and approve only the current step - with HR’s name on that decision.
Trusted HRMS for Modern Businesses
