Pending approvals on the HR dashboard

How it works

1. HR opens the dashboard. Waiting for approval shows a total and a count for each of the six queues.
2. Each queue links to the page where the decision is made: Leave Applications, Attendance Regularization, Overtime, Shift Swaps or the probation queue.
3. Oldest leave requests lists the leave that has waited longest, with the person, the dates and a Review link.
4. Counts cover requests in the viewer's data scope, so a branch HR executive sees their own branch's queues.
5. After a decision on the linked page, the count drops at the next refresh, within a minute.
6. Probation reviews count people whose probation needs a decision, taken from the probation queue.

What you can set

• Queues: Leave requests, Attendance corrections, Work from home and on duty, Overtime, Shift swaps and Probation reviews.
• Oldest leave requests, each with a Review link.
• Scope: attendance queues follow the attendance data scope, and probation follows the employee data scope.
• Refresh: every 60 seconds.
• Decisions are made on each module's page, where the full request and its approval steps are shown.
• Empty state: Nothing is waiting for approval.

Why one approvals card matters

Requests arrive in six different places, each with its own page. Without a single view, HR checks each page in turn, or only when someone complains. One card with six counts turns that into a glance. It also shows the shape of the work: a pile of corrections usually points to a machine or a shift problem, while a pile of overtime near month end means payroll will be late unless someone acts today.

Worked example: the 25th of the month at a Mysuru hospital

On 25 September, the HR executive at a 350-staff Mysuru hospital opens the dashboard. Waiting for approval shows 41: 12 leave requests, 17 attendance corrections, 3 work from home and on duty, 6 overtime, 1 shift swap and 2 probation reviews. The oldest leave request is a staff nurse's EL for the first week of October, raised nine days ago and still waiting on her ward in-charge.

The executive calls the ward in-charge, who approves it from the app within the hour, and HR approves it after checking the ward's leave calendar. She then opens Attendance Regularization and finds that 11 of the 17 corrections come from one ward, whose biometric machine has been failing at the night shift change. She raises a repair ticket and approves the corrections the managers have already cleared. By 5 pm the card shows 19.

Keeping the queues short

Queues stay short when everyone knows how long a request should wait and who acts next. Agree a simple service level with managers and use the dashboard to hold everyone to it, HR included, especially in the last week of the month.

• Aim to clear leave within two working days and corrections within a week.
• Start each morning with the oldest leave requests list.
• Chase corrections and overtime hardest in the last week of the month.
• When one team keeps filling a queue, look for the cause rather than approving faster.

Frequently asked questions