Leave, overtime and claims are each submitted from their own screens, but deciding happens in one place. Approvals has three views, answering three different questions.
Waiting on me — the inbox
Approvals opens on Waiting on me: items you may decide, each row marked with how long it has been waiting (“Arrived today” / “Waiting N days” / “Overdue”) — the queue is newest-first, so the oldest item doesn’t float up on its own; the marker is what keeps it honest.
Opening a row opens the request’s own panel — the leave request, overtime claim or expense claim itself, with the approval section inside it:
- Approve — the primary action. The panel gives you the grounds first: who asked, the balance after approval (sufficient / exceeds), and who else is off the same day.
- Reject — a reason is required, and it isn’t ceremony: the reason travels back to the requester.
- Ask for more information — parks the item on the requester with your question; they reply in the same panel.
- Selecting rows raises the bulk-approve bar (capped at 50).
Decided by me is your record: what you approved or rejected, and when.
Manager: everyone’s
The branch-level Approvals console is every chain at the branch — in flight, decided, and the three stuck shapes: parked on the submitter’s answer, overdue, or decided but never applied. Export CSV carries exactly the filters the table shows. The Approvals tab under Company ▸ Oversight is the org-wide version (requires the org-wide approval read tier).
Where is my request?
Not here — on its own screen: a leave request on Leave, an overtime claim on Overtime, an expense claim on Claims — each carrying its own chain, saying whose desk it is on right now.