Leave approvals that follow your org chart
· 1 min read
Send each request to the person who should decide it, cover holidays, and keep every balance right without a spreadsheet.
Company-wide approval queues fail in two ways: everyone with admin rights gets every request, or nobody feels it is theirs to approve. CRM Dost routes each request to the specific people who should decide it.
The right approver, every time
- By default, a request goes to the person’s reporting manager.
- You can give someone a specific approver instead, and add a backup approver alongside.
- If nobody is set, attendance admins decide.
- Nobody can approve their own request, and only the people who can decide a request are notified about it.
Holidays covered
Before going on leave, an approver can name a stand-in for those dates. The stand-in decides alongside them rather than replacing them, so nothing waits for someone who is away.
A second approval for long leave
Turn on multi-level approval and longer requests — three days or more by default — need a second approval from people you choose, after the first approver says yes.
Balances that add up
- Credit leave yearly, monthly, weekly or as needed, with a leave year that ends when you choose.
- Carry unused leave forward per leave type, up to a cap, with the rest lapsing.
- Let people choose optional holidays, earn comp off for overtime, and, if you allow it, encash leave near the year end.
- Set opening balances and corrections as separate entries, so every balance can be traced.
Changes after the fact
An approver can cancel leave that was already approved, and the days go back to the person’s balance. Once a pay period is locked — five days after it ends, by default — its days can no longer be changed, so payroll stays settled.
Set up reporting managers before anything else. Once the reporting lines are right, most approvals route themselves.