Change the request. Watch the route change.

Routes come from rules you set. Every request spells out which rule picked each step, and who is covering when someone is away.

Waiting on Rabin

Sample data

Routes come from rules you set. "Why this route?" spells out which rule picked each step.

Try itSlide the days up, switch to unpaid leave, then mark the manager as away.

One engine for every request: Leave, timesheets, travel advances, overtime and offers use the same routes, inbox and history.
Rules, not hard-coded chains: A rule can look at the request type, the number of days, an amount or the department, and add or skip a step.
Delegation with an end date: When someone is away, they name a cover. The request shows who is acting and for whom, and the cover stops on the date you set.
Deadlines everyone can see: A request shows who it is waiting on and since when, and reminders go to the approver, not to HR.

Nobody types the same thing twice. Here is what moves between approvals and its neighbours.

Reporting lines as they are: Head Office and branch managers both appear in routes, so a Pokhara request does not detour through Kathmandu.
Approve from email or the phone: Notifications go out by email and in the app, with digests for busy approvers. Managers approve from the phone browser.
Dates in Bikram Sambat: Delegation windows, deadlines and request dates are in BS, with the AD date beside them.
Thresholds are yours: The days and amounts that bring in HR, Finance or the director are your policy, not ours. Change them without a developer.

Yes. The employee app has an approvals inbox with the same route and reasons.